Since the new update (September 2012) of GPU crunching software (opencl) I (and others) have a lot of invalid's with the ATI cards (I about 20%).
On other PC's with nVidia cards I run Einstein@home on the GPU with no issue's at all and all are valid.
Then I tried this: I run Albert@home on the ATI's and from 6WU's 2 where invalid.
I run Einstein@home on the ATI and approx. 1 in 20 is invalid.

I have run Milkyway@home on the nVidia PC and none, really none, was invalid!

So, perhaps a bold statement but ATI cards are not the best one for crunching as they generate invalids, as all the projects that run on ATI AND nVidia I have tested.
All my new systems will have nViida cards (then I can crunch GPUGRID as well).

---

Greetings from,
TJ

Since the new update (September 2012) of GPU crunching software (opencl) I (and others) have a lot of invalid's with the ATI cards (I about 20%).
On other PC's with nVidia cards I run Einstein@home on the GPU with no issue's at all and all are valid.
Then I tried this: I run Albert@home on the ATI's and from 6WU's 2 where invalid.
I run Einstein@home on the ATI and approx. 1 in 20 is invalid.

I have run Milkyway@home on the nVidia PC and none, really none, was invalid!

So, perhaps a bold statement but ATI cards are not the best one for crunching as they generate invalids, as all the projects that run on ATI AND nVidia I have tested.
All my new systems will have nViida cards (then I can crunch GPUGRID as well).

I am currently using my ATI/AMD cards at Moo right now but have crunched on and off using them here and have never had a problem. I am currently using my Nvidia cards and don't have a problem either. I have some questions if you don't mind: what kind of AMD card do you have? What driver version are you using? Are you leaving a cpu open while you crunch or are they all busy crunching their own units? What version of Boinc are you using? How much ran does the pc have in it? What OS are you using? Your pc's are hidden so I can't see any of this for myself.

http://www.guru3d.com/files_details/amd_catalyst_13_2_beta_download.html

Ever tried this unofficial Beta Driver for ur ATI/AMD card ?

I am currently using my ATI/AMD cards at Moo right now but have crunched on and off using them here and have never had a problem. I am currently using my Nvidia cards and don't have a problem either. I have some questions if you don't mind: what kind of AMD card do you have? What driver version are you using? Are you leaving a cpu open while you crunch or are they all busy crunching their own units? What version of Boinc are you using? How much ran does the pc have in it? What OS are you using? Your pc's are hidden so I can't see any of this for myself.

Radon HD 5870 (2)
driver: OpenCL: ATI GPU 0: Cypress (driver version 1016.4 (VM), device version OpenCL 1.2 AMD-APP (1016.4), 1024MB, 991MB available)
i7, 8 core, 6 cores crunch Rosetta@home, so 2 free (0.5CPR per MilkyWay WU)
Boinc 7.0.28
12GB Ram
Win7 Ultimate x64

I have run MilkyWay@home on this PC for 25 months without issues, (all validate) it begun when they update to opencl.
My PC with nVidia run Einstein@home 24/7 and ALL validate. It must be an ATI thing.

And yes I have tried several drivers for ATI wich become a pain to de-install them eventually as they don't have the neatest de-installer.
The latest driver gave errors while running GPU WU's so I am happy with my current drivers, as all the other stuff is working fine.

---

Greetings from,
TJ

Can you post any config or app_info files you use?

Not using a config file or app-info file.

---

Greetings from,
TJ

http://www.techpowerup.com/gpuz/

I would be very interested to know , how high your gpu usage is when crunching one wu. could u post a screenshot of this software ? Maybe i got some valueable news for ya.

GPU usage is between 80-99% by CCC.
The 99% is a few seconds when the WU is about to be finished.

But these "invalids" have nothing to do with my system.
With a machine with older version of Boinc and nVidia all WU's are validated for 100%, for Milkyway and Einstein.

Running on ATI with opencl gives "invalids" for both projects.

I have checked all my wingman and they have a lot of "invalids" too when using ATI and opencl. It is something in that software.

---

Greetings from,
TJ

thats very sad. thought u can get more out of the gpu, at 20% maximum gain by cruching 2 wus simuntainously !? there only a raise from 10 to 15 % wus per day.

i dont know if thats worth to configurate an app_config.xml in the projects folder and update to boinc 7.0.44 ??

So you think nVidia GPUs don't generate invalid results...


EDIT@Rantanplan: with an app_info.xml in the projects folder you don't need to update BOINC.

---

So you think nVidia GPUs don't generate invalid results...


EDIT@Rantanplan: with an app_info.xml in the projects folder you don't need to update BOINC.

I'm not thinking that, I'm seeing that. I keep a close eye on the results and from the approximately 45 WU per day on nVidia for Einstein@home none is marked invalid.
I have alos let the machine run a day on Milkyway and even then none where marked invalid.
Einstein and Milkyway on the ATI gives quite amount of invalids, Milkyway way more though.

I don't mind not getting credit, but running WU' that become to often invalid is not what I want.

---

Greetings from,
TJ

Running an ATI Radeon HD 5850 (cat 12.1) I just checked my application details:
Consecutive valid tasks 15020
for
milkyway_separation 1.02 Windows x86 double OpenCL

Einstein and Milkyway on the ATI gives quite amount of invalids, Milkyway way more though.

Than something is wrong with your GPU (or eventually something else in that system), even the old CAL app I have to use for my HD3850 does not have such high error/invalid rates as you reported in your first post (and it has a known bug where sometimes the output is not written to the std_err). The new OpenCL apps are known to run more or less without any noteworthy issues.

---

Einstein and Milkyway on the ATI gives quite amount of invalids, Milkyway way more though.

Than something is wrong with your GPU (or eventually something else in that system), even the old CAL app I have to use for my HD3850 does not have such high error/invalid rates as you reported in your first post (and it has a known bug where sometimes the output is not written to the std_err). The new OpenCL apps are known to run more or less without any noteworthy issues.

Yes Link, that is exactly what I think, that's why I started this post.
I'm running some Alber@home's at the moment and then I will update to the latest ATI drivers.

---

Greetings from,
TJ

Running an ATI Radeon HD 5850 (cat 12.1) I just checked my application details:
Consecutive valid tasks 15020
for
milkyway_separation 1.02 Windows x86 double OpenCL

Amazing!

I got 1500 to 1700 until September.

Now I have only 3...

I did the latest update from ATI drivers, have now done 304 WU's , 145 valid and 23 invalid, 136 pending.

---

Greetings from,
TJ

I got 1500 to 1700 until September.

Now I have only 3...

I did the latest update from ATI drivers, have now done 304 WU's , 145 valid and 23 invalid, 136 pending.

Than I'd recommend to revert to the drivers you had in september and also check the GPU temperature and eventually clean the card from dust.

---

Running an ATI Radeon HD 5850 (cat 12.1) I just checked my application details:
Consecutive valid tasks 15020
for
milkyway_separation 1.02 Windows x86 double OpenCL

Amazing!

I got 1500 to 1700 until September.

Now I have only 3...

I did the latest update from ATI drivers, have now done 304 WU's , 145 valid and 23 invalid, 136 pending.

Also are you overclocking either the pc or the gpu?

Thanks for the input.
The drivers I had in September (before the update to opencl) didn't had the opencl feature so they won't work. That was the reason I updated the drivers from ATI.
The system is clean and free of dust I regularly use a compressor and vacuum cleaner for all the pc's but not a lot of dust.
And nothing is overclocked, for me the systems are too expensive to fiddle with that and cause overheating.
I lost a nVidia card that had run for 4 years (24/7) under not overclocked conditions. I guess when overclocking the lifespan will be shorter.

Also I must say that I have looked even more closely to my wing(wo)man, and some of them had also invalids with nVidia, but I still none ;-).

---

Greetings from,
TJ

The drivers I had in September (before the update to opencl) didn't had the opencl feature so they won't work. That was the reason I updated the drivers from ATI.

At Seti forums I've read, that the current ATI drivers have some issues with OpenCL. Not sure if that applies here, but the latest version they recommended there is 12.8. Maybe you could try these.

---

The drivers I had in September (before the update to opencl) didn't had the opencl feature so they won't work. That was the reason I updated the drivers from ATI.

At Seti forums I've read, that the current ATI drivers have some issues with OpenCL. Not sure if that applies here, but the latest version they recommended there is 12.8. Maybe you could try these.

Aha, nice to read that some issues with ATI are possible (likely).
Indeed the 12.8 drivers were good, I had them until a few day ago when I updated to the latest in the hope to get better results. But thanks anyway.

---

Greetings from,
TJ