I ran .62 and computor BM and stuff started to give strange fuzzy stuff in respons.
I do run SETI Beta as well.
I have done driver change for graphic card as well.

So I decided to go back to 7.0.60 and use the "old" newer cat driver 12.8 to see if random fuzzy stuff with computor starts to work again.

This is just a note, not a report.

Any one else seen strange random fuzzy things when going to .62 from .60 ??

What do you mean with 'fuzzy stuff'? Seeing artifacts, such as this?


When you see artifacts as that, it's caused by the videocard. Either its drivers are corrupt, or the card is damaged. A while back there were a lot of bad transistors around, that got onto everything hardware and would bulge up and then burn out over time. Perhaps it's something like that.

If you mean artifacts, it isn't something that BOINC does. BOINC has nothing to do with loading drivers onto hardware. It just gives a means to use the GPU on a videocard for calculations, just as it will do for the CPU.

---

Random stuff like MS essentials stoped working(1 time).
BM dies for no reason(1 time).
Errors of tasks occour(1 time).
Computor freezes)1 time).

Small stuff, nothin serious really.
But they started to come after 5mins, 15mins and then something else after 20 mins. Always different kind of malfunctions.

normally you do a change and then 1 or 2 things start to malfunction. You fix it and the same thing malfunctions.

But not here.

"Fuzzy stuff".

Like if your picture was perfect and then 1 small part of it geys blured like yours. You close picture program and restart it and another small part gets blured.

I am now running .60 and "fuzzy stuff" has only occoured once".

So computor seems more in shape now.(7.0.60)
I will see if "fuzzy stuff" comes back in the next day or so.

My SETI ATI ap tasks that "paused" with no warning has stoped after downgrading from .62 to .60

Sometimes 2 tasks of 6 or 4 tasks of 6 "pauses".

And .62 didn't allow me to run 2 Poem tasks when running 1 moowrapper configured in cc_config.xml with exclude.
.60 does

.60 works fine.

You can post in your thread ad nauseum, but without specific data there is nothing that we can see or do about any of it. Your problem, you have to explain in detail what you see, what you think you should see, where it differs from the last test you did. There's nothing in it that I can send to the developers either, as they'll just request debug logs and such, things that you neglect to give.

So you really have to do better than this. If not in text, then use pictures. Use Photobucket, Imageshack or TinyPic to store the image and give an URL or IMG to the image.

Since you're choosing to run development versions of BOINC, I also want to remind you of the disclaimer and reminder to alpha testers:

Disclaimer
On development versions of BOINC:
- Expect parts of it to be broken, or in the least to work in a different way than you are used to.
- Expect work failures, deadline misses and losing all your accumulated work in progress, or not getting credit for your work due to unknown and unforeseen circumstances.
- Only use it when you are willing to participate in the Alpha test program and do not mind sending (bug) reports in to the developers on the email list specially assigned for this purpose.
- Due to the OpenCL detection, your screen may flicker or turn off temporarily. This is normal.


REMINDER TO ALL ALPHA TESTERS:
It's far easier for the developers to fix problems when you send message logs with the appropriate flags set. The main flags are:

<cpu_sched_debug>: problems involving the choice of applications to run.
<work_fetch_debug>: problems involving work fetch (which projects are asked for work, and how much).
<rr_simulation>: problems involving jobs being run in high-priority mode.
<sched_op_debug>: problems involving scheduler operations and other low level information.

Use these flags from the cc_config.xml file.

Report any problems you get with it to the Alpha email list. This list needs registration. When sending logs or other attachments, make sure to CC David, Rom, or Charlie separately, since the email list will drop attachments!

Reporting bugs on this forum or any project's forum isn't very productive as the developers simply do not have time to scour through all forums looking for posts with your bug reports in them. While it may happen that we - other volunteers - forward your problem to them, history has shown it is quite difficult being the middle man in this when more information is needed from you. Hence why it's better for all concerned that you report the problem directly to the developers, who will come back directly to you when they need more information or better logs or to tell you that they've checked in a fix for the specific problem.

---

You can post in your thread ad nauseum, but without specific data there is nothing that we can see or do about any of it. Your problem, you have to explain in detail what you see, what you think you should see, where it differs from the last test you did. There's nothing in it that I can send to the developers either, as they'll just request debug logs and such, things that you neglect to give.

So you really have to do better than this. If not in text, then use pictures. Use Photobucket, Imageshack or TinyPic to store the image and give an URL or IMG to the image.

Since you're choosing to run development versions of BOINC, I also want to remind you of the disclaimer and reminder to alpha testers:

Disclaimer
On development versions of BOINC:
- Expect parts of it to be broken, or in the least to work in a different way than you are used to.
- Expect work failures, deadline misses and losing all your accumulated work in progress, or not getting credit for your work due to unknown and unforeseen circumstances.
- Only use it when you are willing to participate in the Alpha test program and do not mind sending (bug) reports in to the developers on the email list specially assigned for this purpose.
- Due to the OpenCL detection, your screen may flicker or turn off temporarily. This is normal.


REMINDER TO ALL ALPHA TESTERS:
It's far easier for the developers to fix problems when you send message logs with the appropriate flags set. The main flags are:

<cpu_sched_debug>: problems involving the choice of applications to run.
<work_fetch_debug>: problems involving work fetch (which projects are asked for work, and how much).
<rr_simulation>: problems involving jobs being run in high-priority mode.
<sched_op_debug>: problems involving scheduler operations and other low level information.

Use these flags from the cc_config.xml file.

Report any problems you get with it to the Alpha email list. This list needs registration. When sending logs or other attachments, make sure to CC David, Rom, or Charlie separately, since the email list will drop attachments!

Reporting bugs on this forum or any project's forum isn't very productive as the developers simply do not have time to scour through all forums looking for posts with your bug reports in them. While it may happen that we - other volunteers - forward your problem to them, history has shown it is quite difficult being the middle man in this when more information is needed from you. Hence why it's better for all concerned that you report the problem directly to the developers, who will come back directly to you when they need more information or better logs or to tell you that they've checked in a fix for the specific problem.

Thanks for your advice.

My feedback was mostly to describe a multiple problem including multiple test programs runned at the same time.

My intention was to give information about what I experience so if anyone else sees something similiar or partly similiar it might be worth further investigation.

The pauses of BM was most likely from a setting used when running SETI Beta task. -sbs 256(default=64) when using 64 problem dissapeared. I can use -256 with seti ati ap tasks without problem. I've spent some hours trying to find the cause of this. Now we know what and why.

GPU(0,1,2) order with catalyst, BM and SIV I informed SIV people it was probebly wrong order in their program.
SIV dev requested more info and I've proveded them with it.(hopefully fixed in next SIV version). using the same rules(standards) is of help i think.

exclude(GPU) in cc_config.xml that made me run 1 Moowrap task + 2 POEM tasks does not work in BM .62 but still works in .60


I will get rid of as many "fuzzy things" i can before upgrading BM from .60

And you guys wanted positive feedback as well as malfunction reports.

So I'd like to say. On my rig BM 7.0.60 works. No problems detected.