A big "oops" here...

With the dearth of GPUGrid WUs this morning I switched to Einstein. Ran out of WUs so switched to Milky Way. Got several completed. Noticed some available GPUGrid WUs so switched back. Got seven GIANNIs, all of which failed within seconds with:



Went back to Milky Way. Same failures. Switched the beat off.

Just restarted. Got two SANTIs. Both failed in seconds; same message.

What to do??

only cancel a number of incoming jobs, but you have to prosecute the moment when they initiating what is only a few seconds ..
It happens to me also sometimes, we do not know whether it is a nvidia driver or tasks errors ..

A big "oops" here...

With the dearth of GPUGrid WUs this morning I switched to Einstein. Ran out of WUs so switched to Milky Way. Got several completed. Noticed some available GPUGrid WUs so switched back. Got seven GIANNIs, all of which failed within seconds with:



Went back to Milky Way. Same failures. Switched the beat off.

Just restarted. Got two SANTIs. Both failed in seconds; same message.

What to do??

From my experience... Sometimes the drivers can get into a wonky state. It especially happens, for me, when watching a Flash video (like YouTube) while crunching on the GPU. Usually, a restart will get it non-wonky again.

However, if you prefer to take a more pro-active approach, you can report the problem to nVIDIA Driver Feedback. Be sure to include the .dmp dump files within the C:\Windows\LiveKernelReports\WATCHDOG directory, which is where the GPU "Display driver stopped responding" dump files get stored.

I haven't seen the problem in a long long time, but coincidentally, I did have it happen this week. It was apparently a conflict with watching a YouTube video while crunching one of the new POEM OpenCL 2.0 tasks. They don't play nicely.

Regards,
Jacob Klein

I've also had this happen to me while on YouTube or other streaming video sites and crunching with the GPU and CPU. After this happened a couple times, I tried lowering the number of CPU cores by one whenever I was going to be watching video for more than a minute or two. I don't know if that's a real fix, but it hasn't happened since.

This has also happened when crunching other GPU projects and switching to GPUGrid tasks that are queued up. The typical example is running Prime Grid PPS Sieve on each GPU and 5/8 cores on the CPU. When one of the Prime Grid tasks finish and the GPUGrid task starts up so that one GPU is on Prime Grid and the other on GPUGrid and still 5/8 cores active on CPU tasks. GPUGrid always eats an extra core, so if I set 62.5% of cores for CPU tasks, with GPUGrid on each GPU I will only get 50% of my CPU cores active on CPU tasks. I think somehow this switch between GPU projects and the CPU utilization difference causes the crash. At least, that's what I've observed several times.

I don't know why tasks would continue to fail after reboot, however. I guess my next step would be to try a clean re-installation of the driver.
____________

I've also had this happen to me while on YouTube or other streaming video sites and crunching with the GPU and CPU. After this happened a couple times, I tried lowering the number of CPU cores by one whenever I was going to be watching video for more than a minute or two. I don't know if that's a real fix, but it hasn't happened since.

This has also happened when crunching other GPU projects and switching to GPUGrid tasks that are queued up. The typical example is running Prime Grid PPS Sieve on each GPU and 5/8 cores on the CPU. When one of the Prime Grid tasks finish and the GPUGrid task starts up so that one GPU is on Prime Grid and the other on GPUGrid and still 5/8 cores active on CPU tasks. GPUGrid always eats an extra core, so if I set 62.5% of cores for CPU tasks, with GPUGrid on each GPU I will only get 50% of my CPU cores active on CPU tasks. I think somehow this switch between GPU projects and the CPU utilization difference causes the crash. At least, that's what I've observed several times.

I don't know why tasks would continue to fail after reboot, however. I guess my next step would be to try a clean re-installation of the driver.

What browser do you use to view the youtube videos?

Be sure to include the .dmp dump files within the C:\Windows\LiveKernelReports\WATCHDOG directory, which is where the GPU "Display driver stopped responding" dump files get stored.

What browser do you use to view the youtube videos?

I use Waterfox (64-bit version of Firefox).

Be sure to include the .dmp dump files within the C:\Windows\LiveKernelReports\WATCHDOG directory, which is where the GPU "Display driver stopped responding" dump files get stored.

Thanks for that Jacob. I have now accumulated 127 dump files!

I identified the potentially offending GPU and installed it into a different mobo slot. Same problem. I installed it into a spare PC with a different Nvidia driver. Same problem.

I've made a warranty claim against PNY.