Message boards :
Number crunching :
SETI@home crashes Windows 10
Message board moderation
Author | Message |
---|---|
LtCmdrData Send message Joined: 12 Sep 05 Posts: 1 Credit: 34,569 RAC: 0 |
Running Win10 x64 on Intel 5930k and nVidia's GeForce 1060 with the latest drivers, 376.33 and SETI@home crashes the OS whether GPU processing is enabled or not. BOINC is latest, 7.6.33. If GPU is suspended, the PC reboots (I don't know if with a BSOD or not). Examining the windows logs after the reboot I see a BugCheck log stating The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xffff98801fbfb638, 0x0000000000000002, 0x0000000000000000, 0xfffff8001415b1ed). A dump was saved in: C:\WINDOWS\MEMORY.DMP If GPU is not suspended I get a BSOD in nvlddmkm.sys, which appears to be part of the nVidia drivers. These Windows crashes only occur when SETI@home is actively processing, and no other time. The nVidia drivers are freshly installed, with a 'clean' installation (even though I just got the card and I never had nVidia drivers installed on this PC) |
Grant (SSSF) Send message Joined: 19 Aug 99 Posts: 13736 Credit: 208,696,464 RAC: 304 |
I'm running Win10 Pro on an i7 2600 with 2 GTX 1070s using 368.81 drivers with no issues. I'd suggest disabling the Auto restart on errors to see what the BSOD is and if there is more information there than what is in the Windows log. Unfortunately weird errors such as these, while they are occurring when Seti starts to run, can often be caused by problem hardware/software such as wireless hardware drivers. Grant Darwin NT |
©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.