bruce wrote:Certainly overclocking, bad drivers, bad power and/or too much heat can cause instability, but they're not the only possibilities. I've seen at least three theories.
[...]
3) GPU memory is filling up.
Theory 3 is similar but problems with VRAM allocation may not be properly managed.
In a
topic (post #87 bearing date Saturday, June 22, 2013 11:58 AM) PantherX addressed to me responding to my answers a user said he solved his problems on a Fermi card (nVidia GeForce GTX 560 Ti, Win7 64 bit Service Pack 1 - fully up to date, driver 320.18) by downclocking the video card's memory: 20 MHz below stock frequency. His problem began with 8900s WU but he completed earlier WU. Another user (he also had problems with 8900 WUs) solved the same problems on a Titan (not specified his model) in the same way. Once he solved this issues he overclocked his card (mantaining stock voltage) and had no problem.
Their error messages are:
WU##:FS00:0x17:ERROR:exception: Error invoking kernel execFFT: clEnqueueNDRangeKernel (-5)
WU##:FS00:0x17:ERROR:exception: Error invoking kernel gridInterpolateForce: clEnqueueNDRangeKernel (-5)
WU##:FS00:0x17:ERROR:exception: Error invoking kernel calcCenterOfMassMomentum: clEnqueueNDRangeKernel (-5) - ##% completed
WU##:FS00:0x17:ERROR:exception: Error invoking kernel copyDataToBuckets: clEnqueueNDRangeKernel (-5) ##% completed
The first user i mentioned above said he had problems with installation of .NET and with overheating, in addition his system was overclocked. So probabily some of these error messages were due to reason different from the ones you try to understand, but probably error 5 (and error 55 which generate a similar message) is related to clock frequency.
I had problems with 8900 WUs too (moreover every GPU FAH bench i did gave a crash immediately after memory and clock frequency reached their max values, that is immediately after the beginning of the benchmark); so i lowered the memory frequency with MSI Afterburner on my Mobility Radeon HD 5430 in a HP G series notebook (-10, -15, -20, -100 MHz), but this didn't solved the problem, seems my hardware isn't good enough for this kind of work. Hope this will be the solution for Om_Audio who encountered the same error code as mine, Error invoking kernel execFFT: clEnqueueNDRangeKernel (-55), although our two systems are similar (Intel i3 CPU, Cedar GPU, 13.9 Catalyst driver, error -55), but his hardware is better looking at PassMark Software charts, so maybe he has more chances.