Questions and Answers :
GPU applications :
Cuda initialisation failure, temporary exit - every time on every GPU task - what is the problem
Message board moderation
Author | Message |
---|---|
cwancyk Send message Joined: 4 Jan 01 Posts: 4 Credit: 542,322 RAC: 0 |
Hi Recently I updated BOINC and my Nvidia drivers, after this update I can't run any GPU tasks. It runs to about 10 to 17 % and then stops and I have this message: 2017-02-11 16:45:28 | SETI@home | task postponed 180.000000 sec: Cuda initialisation failure, temporary exit I reinstalled BOINC, installed the older version, reinstalled Nvidia drivers. Nothing worked I have a GTX 980ti with the newest 378.49 drivers. Anyone can help? |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
CUDA is a part of your GPU, and is activated by the drivers. It being seen as missing or unable to initialize is a problem with the drivers. Reinstalling BOINC won't help in this as BOINC itself doesn't use your GPU, nor does it add any functions to your GPU. Reinstalling drivers is the only thing you can do, and if newer drivers don't fix the problem or even cause the problem, then you'll have to try to install older drivers. Also install drivers from the GPU manufacturer, Nvidia in this case. Do not let Windows install them. Try to install the drivers with a clean install. This is an option in the driver installer, so do a custom installation and read all the screens. |
cwancyk Send message Joined: 4 Jan 01 Posts: 4 Credit: 542,322 RAC: 0 |
CUDA is a part of your GPU, and is activated by the drivers. It being seen as missing or unable to initialize is a problem with the drivers. Reinstalling BOINC won't help in this as BOINC itself doesn't use your GPU, nor does it add any functions to your GPU. clean install didn't help, but installing older drivers solved the problem, thanks |
Colin Haig Send message Joined: 18 May 99 Posts: 3 Credit: 8,346,058 RAC: 5 |
I'm experiencing same thing with the new nvidia drivers as well. I sentr them feedback, hopefully they will resolve. |
Colin Haig Send message Joined: 18 May 99 Posts: 3 Credit: 8,346,058 RAC: 5 |
To add a bit more detail, it has a problem on machine with a pair of 980ti 's and setiathome v8 8.0 (cuda 42). Other machine with a pair of 770's runs setiathome v8 8.0 (cuda 32) fine. So its specific to cuda 42 on the 980ti and the new driver.. |
Colin Haig Send message Joined: 18 May 99 Posts: 3 Credit: 8,346,058 RAC: 5 |
NVidia has produced a hotfix driver that appears to fix the problem on 980Ti and other high end nvidia cards. Details here: https://forums.geforce.com/default/topic/994534/geforce-drivers/announcing-geforce-hotfix-driver-378-72/ http://nvidia.custhelp.com/app/answers/detail/a_id/4405 I've installed it, and many CUDA based seti@home work is underway again without postponement or other errors. Will let you know if I run into other issues. Cheers! |
©2024 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.