Advanced search

Message boards : Number crunching : Question about the old Monitor Sleep problem.

Author Message
Send message
Joined: 13 Mar 12
Posts: 21
Credit: 8,773,573
RAC: 0
Scientific publications
Message 34106 - Posted: 3 Dec 2013 | 2:58:51 UTC


It's been a long, long time since I did any crunching. But there once existed a problem due to an nVidia driver update, and I don't know if it's still an issue.

The old problem was, that as soon as the O/S put the monitor to sleep, the nVidia drivers would also shut down all CUDA computing. It was frustrating both members and Scientists, especially as the fear was that nVidia would never change this behavior.

I don't recall which driver update introduced this behavior, but do recall that there is a Windows 7 Admin setting, that totally prohibited any UserID from putting the monitor to sleep, just so that clients and Scientists would lose no more WUs. Also, clients were implored at that time not to upgrade their drivers.

My question is: Does this problem still exist?

I have a Windows 7 Pro, 64-bit system, with a by-now-old GeForce GTX460 GC. I'm wondering whether I should get back to crunching like in the old days, but want this subject answered before losing my first WU.

My nVidia driver is the 314.22 . And I've disabled auto-updates to the driver.


Jacob Klein
Send message
Joined: 11 Oct 08
Posts: 1127
Credit: 1,901,927,545
RAC: 0
Scientific publications
Message 34107 - Posted: 3 Dec 2013 | 3:40:03 UTC - in response to Message 34106.
Last modified: 3 Dec 2013 | 3:45:07 UTC

Hello Dirk,

I believe you are referring to this issue:

The problem does not exist anymore.
The issue was fixed in 301.24.
It affected 295.51 through anything less than 301.24.

Welcome back.
I still have a GTX460 that processes GPUGrid work 24/7.


Post to thread

Message boards : Number crunching : Question about the old Monitor Sleep problem.