Message boards :
Graphics cards (GPUs) :
NVIDIA driver change to 384.76, error in WU in current process and I do not receive new
Message board moderation
| Author | Message |
|---|---|
|
Send message Joined: 27 Nov 14 Posts: 10 Credit: 29,371,725 RAC: 0 Level ![]() Scientific publications ![]()
|
NVIDIA driver change to 384.76, error in WU in current process and I do not receive new. http://www.gpugrid.net/result.php?resultid=16381496 http://www.nvidia.es/download/driverResults.aspx/120607/es GeForce Game Ready Driver Versión: 384.76 WHQL Fecha de publicación: 2017.6.29 Sistema operativo: Windows 10 64-bit Idioma: Español (España) Tamaño: 433.44 MB https://forums.evga.com/Nvidias-latest-driver-causes-Watch-Dogs-2-to-crash-on-startup-m2688844.aspx |
Retvari ZoltanSend message Joined: 20 Jan 09 Posts: 2380 Credit: 16,897,957,044 RAC: 0 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
NVIDIA driver change to 384.76, error in WU in current processJudging by the stderr.txt of your task, you've updated your driver while the task was running. This method will always result in an error, as the update doesn't stop the GPU apps. You have to do it manually by suspending all GPU projects in BOINC manager before you start the update, then resume all GPU projects after the successful update. To minimize driver related problems, it is also recommended to restart your PC after the update (even if it not necessary), and resume the GPU projects after the restart. and I do not receive new.It's because right now there are more active hosts than available tasks, so your host will receive work only when it's 'lucky enough' to catch one. See the server status page. |
|
Send message Joined: 30 Apr 13 Posts: 106 Credit: 3,805,237,860 RAC: 65 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
I take it that the 384.76 driver should work? I just today upated to that driver and all other projects crash on compute errors (I assume GPU would, too, if I had a GPU task). I went back to the driver I had previously (376.19) and all is well. 376.19 is about 6 mo old. What is the latest driver that works? Thanks, Win |
|
Send message Joined: 11 Oct 08 Posts: 1127 Credit: 1,901,927,545 RAC: 0 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
Are you running at reference clocks? To find out, tell us the exact model name of your GPU, and also tell us what GPU-Z shows for "Graphics Card" tab > "GPU Clock" value. |
|
Send message Joined: 30 Apr 13 Posts: 106 Credit: 3,805,237,860 RAC: 65 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
Nvidia GTX 980ti, hybrid. Since the room is warm in the summer I'm running below reference clock with automatic control to maintain temperature (MSI Afterburner). Core clock is 1342. (ref is 1392). I assume you're saying 384.76 should work OK and there's another problem?? I wish someone would just say that. I've done an advance search on 384.76 and only get posts about problems. Thanks, Win |
Retvari ZoltanSend message Joined: 20 Jan 09 Posts: 2380 Credit: 16,897,957,044 RAC: 0 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
My GTX 1080Ti is processing a workunit with NVidia driver 384.76. Currently its progress is 37%. It will be finished in 4 hours and 40 minutes. Then you could check its result through the link above. |
|
Send message Joined: 30 Apr 13 Posts: 106 Credit: 3,805,237,860 RAC: 65 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
Thanks W |
|
Send message Joined: 22 Feb 14 Posts: 26 Credit: 672,639,304 RAC: 0 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
If you have changed to driver 384.76 WHILE you were "crunching" the WU is normal that you get an ERROR. I have a 384.76 driver too but I don't know if it will "crunch" well because, as many others, I don't have new WU since the third of July. A commentary from the moderator about the lack of WUs will be welcome. |
|
Send message Joined: 28 Jul 12 Posts: 819 Credit: 1,591,285,971 RAC: 0 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
I have a 384.76 driver too but I don't know if it will "crunch" well because, as many others, I don't have new WU since the third of July. I just upgraded my GTX 1060 from my old standby, the 373.06 drivers to 384.76 (Win7 64-bit) with no problems, though I always uninstall the old drivers with DDU (safe mode). I can't get any work here either, but both drivers use CUDA 8, and that really doesn't change from one release to another, so it would be surprising if the new drivers made any difference on GPUGrid. However, I checked on both Einstein and SETI, which use OpenCL, and saw about a 6 to 7 percent improvement in times with the new drivers. And the 384.76 drivers implement at least a preliminary form of OpenCL 2.0, which may be of interest to some projects, maybe even here at some point. As for no work, it is no mystery. It happens every summer. Check the beaches at Majorca. |
©2025 Universitat Pompeu Fabra