I have just had a third system bluescreen with a BCCode of 116, all within the last 24 hours. Is anybody else seeing problems like this? These systems are GPU crunching for GPUGRID, and two of them do nothing but crunch. The affected systems are this one (where I updated the drivers and now don't seem to be able to get work), this one, and this one.

These systems have been stable for a long time (stable by my standards -- if a system bluescreens once a month when I'm not making changes to it or pushing the envelope in some way, I'll scrap it if I can't fix it). Is anybody else seeing problems?

Reduce your clock speed and/or increase your fan speed; some of the newer tasks run faster, so the clocks you have are probably not stable for these tasks (they run faster and will probably draw more power and produce more heat).

Your GTX 260 is picking up work now.


Good Luck,

All are running stock clocks.

The 260 may be getting work, but the 470 still isn't even after a driver rollback.

I have just had a third system bluescreen with a BCCode of 116, all within the last 24 hours. Is anybody else seeing problems like this? These systems are GPU crunching for GPUGRID, and two of them do nothing but crunch.

Yep had the same problem on 2 GTX295 systems. Always when a GPUgrid task starts. Was running 258.69 drivers on both rigs. Have updated one to 260.99. My cards aren't OC'ed. Only started when the cuda 3.1 app came out. Before that was fine. Only seems to occur on the GTX295's. My other single GPU rigs seem to be fine. Might be the cuda 3.1 bug where it gets confused with what device is running the task. The Seti optimizers went back to cuda 3.0 because of this bug.

---

BOINC blog

I have just had a third system bluescreen with a BCCode of 116, all within the last 24 hours. Is anybody else seeing problems like this? These systems are GPU crunching for GPUGRID, and two of them do nothing but crunch.

Yep had the same problem on 2 GTX295 systems. Always when a GPUgrid task starts. Was running 258.69 drivers on both rigs.

I had this happening on an XP64 GT 240 box every couple days, with a bluescreen message that there was an error caused by either the NVidia driver or hardware. This crash was happening with all the newer driver versions. Since rolling back to 197.45 drivers the problem seems to have disappeared.

There's another problem that happens with some cards that causes GPUGRID WUs crash immediately. I've noticed it mostly on GT 240 and slower GPUs. Seems that the GPU is being left in an unstable state by the previous GPUGRID WU. Only happens with GPUGRID WUs, never WUs from other projects. Interestingly other projects continue to run on the GPU, and often after a Collatz WU runs the next GPUGRID WU will work. Sometimes however the machine has to be rebooted to get GPUGRID crunching again. Some "groups" of WUs seem to be more prone to this than others.