SRBase causing CLOCK_WATCHDOG_TIMEOUT
log in

Advanced search

Message boards : Number crunching : SRBase causing CLOCK_WATCHDOG_TIMEOUT

Author Message
Profile rebel9
Send message
Joined: 4 Jul 15
Posts: 3
Credit: 1,426,607
RAC: 158
Message 2321 - Posted: 31 Jan 2016, 8:58:11 UTC
Last modified: 31 Jan 2016, 8:59:39 UTC

Hi,

SRBase is causing CLOCK_WATCHDOG_TIMEOUT BSOD errors within seconds on my brand new, professionally overclocked, 4-core hyperthreaded, Windows 10 machine. I've disabled it for now. Temps don't look excessive in the brief time I have to check before the machine reboots, which it does every time. I have safeguards in place to prevent overtemping, anyway. This error is said to happen when a CPU core times out waiting for another thread. Could something not be playing nice here? I did see a couple of WUs that had completed but didn't see which type they were, I'm afraid, so it may be one particular type of WU that's causing the issue.

Cheers.
____________

Profile rebirther
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 2 Jan 13
Posts: 3466
Credit: 22,879,153
RAC: 0
Message 2322 - Posted: 31 Jan 2016, 14:46:04 UTC - in response to Message 2321.

Hi,

SRBase is causing CLOCK_WATCHDOG_TIMEOUT BSOD errors within seconds on my brand new, professionally overclocked, 4-core hyperthreaded, Windows 10 machine. I've disabled it for now. Temps don't look excessive in the brief time I have to check before the machine reboots, which it does every time. I have safeguards in place to prevent overtemping, anyway. This error is said to happen when a CPU core times out waiting for another thread. Could something not be playing nice here? I did see a couple of WUs that had completed but didn't see which type they were, I'm afraid, so it may be one particular type of WU that's causing the issue.

Cheers.


This only happened on a heavy OC system, I had bluescreens before with OC 4GHz but the temps were still ok, with 3.8Ghz its ok now. The llr app is using all the power of the CPU so you will have some trouble.

Profile rebel9
Send message
Joined: 4 Jul 15
Posts: 3
Credit: 1,426,607
RAC: 158
Message 2325 - Posted: 31 Jan 2016, 21:19:27 UTC - in response to Message 2322.

Any suggestions as to BOINC settings I could use for this project to avoid the problem?

Thanks.
____________

Profile Conan
Avatar
Send message
Joined: 7 Dec 14
Posts: 20
Credit: 3,375,790
RAC: 0
Message 2326 - Posted: 1 Feb 2016, 10:52:10 UTC

This project is a similar to PrimeGrid, so as is often stated on their forums, disable Hyperthreading if you have it turned on it chews up resources and reduces performance on "llr" type work units.

If you already have this option turned off then I don't know what would be causing your issue.

llr work units don't use a lot of memory so it maybe as rebirther has said your CPU is being pushed a bit too hard.

Conan

frederikhk1
Send message
Joined: 25 Aug 15
Posts: 5
Credit: 124,108
RAC: 0
Message 2327 - Posted: 1 Feb 2016, 11:43:44 UTC

Turn down your OC and see if this solves your problem.

Profile rebel9
Send message
Joined: 4 Jul 15
Posts: 3
Credit: 1,426,607
RAC: 158
Message 2339 - Posted: 9 Feb 2016, 17:33:56 UTC - in response to Message 2327.

I'm not prepared to do any of those things for a project. The worst case is that I'd just not run it on this machine. I think I have it under control, though. I created an app_config.xml file and limited each app to 1 concurrent instance. It seems OK so far so, if that continues, I'm happy with that solution.

Thanks for the suggestions, folks.
____________


Post to thread

Message boards : Number crunching : SRBase causing CLOCK_WATCHDOG_TIMEOUT


Main page · Your account · Message boards


Copyright © 2014-2018 BOINC Confederation / rebirther