Message boards :
News :
monitor suspend/resume bug in 295/296 drivers
Message board moderation
Previous · 1 · 2 · 3
Author | Message |
---|---|
Send message Joined: 12 Jun 11 Posts: 12 Credit: 150,069,999 RAC: 0 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Toshiba has now released a new display driver for notebooks that hava a NVIDIA card installed. The driver seems to be the 296.31 version. Has anyone tested this toshiba driver? I guess I better stick with my older version which has worked without a problem and wait for a new toshiba version based on the 300.xx series. ![]() |
Send message Joined: 12 Jun 11 Posts: 12 Credit: 150,069,999 RAC: 0 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Toshiba has now released a new display driver for notebooks with a NVIDIA card installed. To answer my own question, in case anyone might have the same problem... I had to install the latest driver from the manufacturer of my laptop for other reasons then boincing, and since I had the driver installed I decided to test with two short WU (1 Natham and 1 Noelia). I replicated the conditions under which WU failed with 295.xx and 296.xx, as they were explained above by Jacob Klein: for anyone trying to reproduce the problem, I have found that the problem occurs when Windows powers off the monitor first, and then BOINC tries to start or resume a CUDA task while the monitor is off. This means that, if you try to reproduce it using tasks that are already running before Windows powers down the monitor, those tasks will not fail. But any tasks that try to start or resume, while the monitor is off, will fail... according to my testing. None of the WU failed, which might mean that either NVIDA solved the problem in the 296.31 version, or Toshiba did that for them. |
©2025 Universitat Pompeu Fabra