NVIDIA 397.31 drivers - Stop working - Tasks postponed or fail

Questions and Answers : Windows : NVIDIA 397.31 drivers - Stop working - Tasks postponed or fail
Message board moderation

To post messages, you must log in.

AuthorMessage
Jacob Klein
Volunteer tester

Send message
Joined: 15 Apr 11
Posts: 149
Credit: 9,783,406
RAC: 9
United States
Message 1933324 - Posted: 3 May 2018, 5:38:26 UTC

Just a heads up...

I recently got these errors (pasted below), including "postponed" message for GPU tasks, on a Windows 10 v1803 PC, that has 3 GPUs: GTX 970, GTX 660 Ti, GTX 660 Ti, with NVIDIA 397.31 drivers.

When I restarted BOINC, it did not see the GPUs at all (CUDA nor OpenCL!)
Also, the NVIDIA system tray icon said "update available", and GeForce Experience said "Driver not found".
When I restarted the PC, everything was fine again, including BOINC GPU detection, and tasks running successfully.

From my experience, and additional research that I've done, I believe:
The NVIDIA 397.31 drivers have a problem "staying installed/detected" on Windows, and NVIDIA is working on it. Restart the PC as a workaround.


Running on device number: 0
Priority of worker thread raised successfully
Priority of process adjusted successfully, below normal priority class used
WARNING: boinc_get_opencl_ids failed with code -1
Error: Getting Platforms. (clGetPlatformsIDs)
BOINC assigns device 0
WARNING: BOINC failed to provide OpenCL device, using own enumeration abilities
ERROR: OpenCL kernel/call 'clGetDeviceIDs (second call)' call failed (-32) in file ..\..\..\src\GPU_lock.cpp near line 1310.
Waiting 30 sec before restart...
ID: 1933324 · Report as offensive
rob smith Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer moderator
Volunteer tester

Send message
Joined: 7 Mar 03
Posts: 21300
Credit: 416,307,556
RAC: 380
United Kingdom
Message 1933326 - Posted: 3 May 2018, 6:26:59 UTC

What you are describing is symptomatic of MS having installed their version of the nVidia driver which does not have the computational stuff included.

The solution is to get a clean set of drivers from the nVidia website and then do a "clean" installation - which may require a reboot or two. Then turn OFF all Windows hardware driver updates (sadly Windows 10 is infamous for turning this back on again...)
Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?
ID: 1933326 · Report as offensive
Jacob Klein
Volunteer tester

Send message
Joined: 15 Apr 11
Posts: 149
Credit: 9,783,406
RAC: 9
United States
Message 1933351 - Posted: 3 May 2018, 11:44:21 UTC - in response to Message 1933326.  
Last modified: 3 May 2018, 11:47:51 UTC

I'm telling you, this wasn't a problem on any previous latest driver.
So, even if it Windows Update installing the same driver on top of the existing one, it's something that NVIDIA used to prevent (on latest drivers), but is having trouble preventing (with this latest driver).

This is a 397.31 driver bug, NVIDIA is aware, and in the meantime, GPU projects will have users with this problem.

Note: I did confirm that OpenCL.dll was correctly in the System32 folder, even when I had the problem earlier, for what that's worth.

Regards,
Jacob
ID: 1933351 · Report as offensive
Jacob Klein
Volunteer tester

Send message
Joined: 15 Apr 11
Posts: 149
Credit: 9,783,406
RAC: 9
United States
Message 1933673 - Posted: 4 May 2018, 21:43:08 UTC

ID: 1933673 · Report as offensive

Questions and Answers : Windows : NVIDIA 397.31 drivers - Stop working - Tasks postponed or fail


 
©2023 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.