Hey there!

I have been lurking, and have a question about cuda 4.2 tasks erroring out because of a "driver not responding" timeout error. I am running Win 7 Home Premium on a GTS 450 running nVidia 306.23 drivers on BOINC 7.0.28. The processor is old, an AMD Athlon 64 X2 4200. I started getting these occasionally, and now they are more frequent. I went to the MS site, and they had an installer that evidently backed off the timeout from default 2 seconds to 7, but I still get crashes, taking out the work unit. Does anybody know how high I can set the Registry time out to keep my WUs healthy? Thanks much!

I removed it entirely and everything was fine

---

Thanks - Steve

It's generally recommended to adjust your system for performance when crunching. This is almost a necessity for GPU crunching, so disabling Aero, useless start-up processes and unnecessary background services helps. In particular it's a good idea to Adjust the System Performance:

Start, Right Click on computer, Properties, Advanced System Settings, under the Advanced Tab and the Performance section, select Settings and Adjust for Best Performance.

If that, and a few other things (in the FAQ's) doesn't resolve the issue, consider adjusting the registry settings for Timeout Detection,

http://msdn.microsoft.com/en-us/windows/hardware/gg487368

Note that this might lead to system crashes, so it's not recommended on production systems, and make sure your files are backed up if you use the system for anything else.
If you are experiencing this problem on 24/7 crunching rigs the Timeout Registry edit looks like a good fix. I've seen this and similar errors many times over last few years, and various workarounds (which don't always work; probably driver dependent). This looks like the best fix.

BTW. I think this can't be implemented into an app as it would infringe upon the MS Logo licence - otherwise it might have been done by a few projects.

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help