Simplex0 wrote:
4-5 days ago I think, every now an then it worked but usually it would get an error after running a short period of time and more unusual en error after running a longer time.
Now I have 35 work units crunched with the Milkyway@home application and currently 17 have been validated and approved and no errors so the graphic cards seams to be fine.
I guess Folding is preferring Nvidia GPU's and not so much effort is put on making the application run on AMD cards?
Milkyway@Home (or any other at that matter) is not the application to use in order to prove or disprove that your hardware is or is not stable.
Folding@Home has been working on AMD hardware before nVidia even knew about the project.
At the moment, AMD has a little bug in OpenCL implementation, BUT in your instance you ARE NOT experiencing this right now, because all the projects which have been affected by the bug, have been disabled on AMD hardware.
In you original comment you are quoting completely different error, which appears equally often on AMD and nVidia hardware.
Most times it suggests that folder's hardware is not stable. In other times, a specific WU is just faulty (it happens).
In your case it is very very likely that Project: 11742 (Run 0, Clone 2553, Gen 50) is FAULTY, because this very same WU has been assigned to other folder and also was returned as FAULTY