BOINC crashes Windows 10

Message boards : Questions and problems : BOINC crashes Windows 10
Message board moderation

To post messages, you must log in.

AuthorMessage
Dewde

Send message
Joined: 28 Dec 16
Posts: 3
Romania
Message 74990 - Posted: 28 Dec 2016, 17:18:01 UTC
Last modified: 28 Dec 2016, 17:18:19 UTC

Running Win10 x64 on Intel 5930k and nVidia's GeForce 1060 with the latest drivers, 376.33 and Boinc crashes whether GPU processing is enabled or not, on SETI@HOME.

How can I go about debugging this? Which logs should I provide?
ID: 74990 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15477
Netherlands
Message 74992 - Posted: 28 Dec 2016, 17:59:35 UTC - in response to Message 74990.  

Which BOINC version?
The title of the thread says Windows 10 crashes due to BOINC, the post suggests otherwise, so please clarify?
What, if any, is the error you get?
'latest drivers' are which exactly? Installed by you from the Nvidia site or by Windows?
ID: 74992 · Report as offensive
Dewde

Send message
Joined: 28 Dec 16
Posts: 3
Romania
Message 74998 - Posted: 28 Dec 2016, 21:56:12 UTC - in response to Message 74992.  
Last modified: 28 Dec 2016, 21:57:42 UTC

Which BOINC version?
latest one from the site, 7.6.33[/quote]

The title of the thread says Windows 10 crashes due to BOINC, the post suggests otherwise, so please clarify?
how does the post suggest otherwise?

What, if any, is the error you get?
there is no error, the PC reboots. 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


'latest drivers' are which exactly? Installed by you from the Nvidia site or by Windows?
like I stated, the latest GPU drivers offered by nVidia and installed by me from their site, version 376.33
ID: 74998 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15477
Netherlands
Message 74999 - Posted: 28 Dec 2016, 22:34:56 UTC - in response to Message 74998.  
Last modified: 28 Dec 2016, 22:36:45 UTC

The title of the thread says Windows 10 crashes due to BOINC, the post suggests otherwise, so please clarify?
how does the post suggest otherwise?
Running Win10 ... and Boinc crashes... <> BOINC crashes Windows 10

there is no error, the PC reboots.
A reboot isn't necessarily the same as a crash. A crash is the program stopping and showing an error message or error number or silently stopping and disappearing. In the case of Windows a crash is stopping and showing one of its myriad of infamous and difficult to read blue screens of death. Here the reboot can happen after the BSOD. But normally when a program crashes, that is all, Windows won't reboot.

Seeing the bugcheck and following it through a search, 0x0000000a is IRQL_NOT_LESS_OR_EQUAL
An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses.

'Drivers' can mean any drivers of hardware in your system, from the motherboard chipset drivers, via keyboard/mouse, to audio, video, monitor, network, printer, scanner, camera, microphone, external drives, etc. Depends on what's in and on your system really. Therefore you may want to check the memory dump with Windbg (Windows Debug), part of the Debugging Tools for Windows. It can yield more information.

like I stated, the latest GPU drivers offered by nVidia and installed by me from their site, version 376.33
Yes, sorry, you did say the driver version. Not that it was from Nvidia though, just that your GPU is an Nvidia. I asked specifically as Windows installed drivers can lack components required to do things, like OpenCL calculations. I'll leave it to any passing Nvidia guru to check if those drivers are stable enough for the GPU in question. Not all are.
ID: 74999 · Report as offensive
Dewde

Send message
Joined: 28 Dec 16
Posts: 3
Romania
Message 75007 - Posted: 29 Dec 2016, 15:33:33 UTC

Also got 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.
ID: 75007 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15477
Netherlands
Message 75009 - Posted: 29 Dec 2016, 16:53:15 UTC - in response to Message 75007.  

Well, best ask at the Seti forums then. And when you do, report which of the applications the GPU is using, perhaps that that's of importance as well.
ID: 75009 · Report as offensive
robsmith
Volunteer tester
Help desk expert

Send message
Joined: 25 May 09
Posts: 1283
United Kingdom
Message 75010 - Posted: 29 Dec 2016, 17:15:06 UTC

One critical thing that can cause problems when NOT done is performing a "Clean" installation of new Nvidia drivers.
This will completely remove any residual bits of earlier versions. Sometimes one can get away without doing this, but I've had the sort of problems you are describing when not using the clean installation, this option is normally somewhat buried under the "advanced", or "options" tab that appears during the installation, the exact wording of the tab, and the button to enable the clean installation varies from version to version.
ID: 75010 · Report as offensive
Coleslaw
Avatar

Send message
Joined: 23 Feb 12
Posts: 198
United States
Message 75033 - Posted: 30 Dec 2016, 19:54:17 UTC

My team hasn't posted results with BOINC, but there were several that had issues with Folding@Home. You can read about it here: https://hardforum.com/threads/nvidia-375-drivers.1918384/

Try version 376.48 which is a hotfix here: https://nvidia.custhelp.com/app/answers/detail/a_id/4288
otherwise try downgrading to a 373 version.
ID: 75033 · Report as offensive

Message boards : Questions and problems : BOINC crashes Windows 10

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.