Clock Watch Dog Time Out BSOD

R

RobCharles1981

Member
Hi all I'm wondering if you can help me with this problem?


I've basically gone ahead and upgraded my Computer with this:


AMD Ryzen 5 2600
MSI B450 Gaming Plus (Latest Bios)
Corsair 16gig 3200 Memory


I've installed Windows 10 and the motherboard drives and graphics ect.


But after sometime my system freezes with no reason, and then I get a BSOD with "Clock Watchdog Timeout Ryzen"


Any idea what this means and how can I fix this?


Thanks
Rob
 
Watchdog timers just check whether or not a system has froze and triggers a BSOD/reset if so, I'm afraid that BSOD message won't be much use in finding the cause of the freezing on its own.

Chipset/CPU drivers are a good place to start though(Might need a reinstall or similar), if you're on latest Win10 build already.
 
Last edited:
I can't verify if that's Samsung or Hynix.

Download CPUZ, go to SPD and look at this and see what it says.

R1YL7zk.jpg


99.9% of the issues with Ryzen are memory related.
 
Really hard to diagnose this one
The Ram is Hynix and is not on the compatibility list from what I can see for that board, however that should not mean it is unusable.

Try the following
  • setting your ram to its normal JDEC i.e turn off XMP
  • Open device manager and expand Computer right click ACPI x64 > Select update driver and search auto
  • Do this again with the following devices
    [*]Display adapters
    [*]monitors
    [*]network adaptors > Realtek​

I have a feeling that lower Ram speeds will be what fixes it though
 
Another Update - I asked in another forum who told me to download an an application "Who Crashed" this is the report that it's given me......


[FONT=Segoe UI, Arial]On Sun 17/03/2019 08:42:40 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031719-8796-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x14CC20)
Bugcheck code: 0x101 (0x10, 0x0, 0xFFFFD00160DD8180, 0xA)
Error: [FONT=Segoe UI, Arial]CLOCK_WATCHDOG_TIMEOUT[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. [/FONT]
 
All that means is that the timing in your kernel got waffy dude. It could have been for many reasons, but mostly CPU and RAM speed. I've had Watchdog errors on boggy stock rigs.

I would surmise it is your RAM causing the issue, as 3200mhz non Samsung is pushing it. Try tweaking it back to around 2900 and see what happens then.
 
Yeah an easy PSU check is to find the readouts for 12V, 5V & 3.3V lines via your motherboards software or hwmonitor or something similar, if they're(12V in particular) consistently below their ratings or drops quite heavily under load then that's a bit of a warning sign its on the way out, or it's overloaded (But that shouldn't be the case with your hardware stock if you've still got that 750W model and it still works at its ratings)

Drivers are also a common one for this with Ryzen, make sure you use drivers from online rather than discs, and make sure any drivers you've installed are fairly recent and meant for Windows 10 post Anniversary update.
 
I'd check the PSU still just incase it's faulty, another place to check from there would be the SSD/HDD (SMART & sector checks) that has your page file(s) on it(Likely your boot drive but you can check if Windows has allocated any more from "Adjust the appearance and performance of Windows"), have you tried disabling/removing your sound card maybe to check if the issue lies there? Often this problem can be caused by "peripheral" devices too besides the main components, more or less anything could be causing this one even USB drivers.
 
Last edited:
Arne Saknussemm said:
Do you have an old PSU about to try with...maybe give that a go

And if you leave RAM at 2133 defaults(BIOS stock)...does the BSOD happen?
Click to expand...




I don't have a spare PSU


it still blue screens.....


This is the Error Message what I'm getting when I run "Who Crashed":


[FONT=Segoe UI, Arial]On Sun 17/03/2019 17:32:36 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031719-23703-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x14CC20)
Bugcheck code: 0x101 (0x10, 0x0, 0xFFFFD00054A95180, 0xB)
Error: [FONT=Segoe UI, Arial]CLOCK_WATCHDOG_TIMEOUT[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. [/FONT]
 
Arne Saknussemm said:
Is it a fresh OS install on the new system?

Have you tried F5 defaults in BIOS?
Click to expand...




Yep its a fresh install - I downloaded the Windows 10iso from Microsoft burned it to disk and used this in the past and was able to activate when it did it's own thing.


When I installed it - It couldn't activate for some reason and even tried speaking to the clueless support on this matter.


F5 does nothing tried it.
 
Win 10 is tied to your hardware IDs these days so a new PC will mean activation problems of some sort...

But that shouldn't mean the install is off

You could run "sfc /scannow" in an administrator command prompt...check system files are all OK

Maybe remove one stick of RAM...really barebones the PC at F5 defaults

Reseat power cables

Not sure what else...unless you try another fresh OS install with minimal driver...just chipset direct from AMD
 
Did you make this Windows 10 disc recently? Ryzen chipset drivers will often throw out this error on pre-Anniversary edition installs of Windows 10
 
You must log in or register to reply here.

Similar threads

D
Full display black screen/game hangs on 2080 ti.
Replies
4
Views
9K
DwarfAdigginAhole
D
AlienALX
Wub Wub, time for something different.
4 5 6
Replies
111
Views
14K
AlienALX
AlienALX
D
Crashes in any game I play except LoL or Second Life.
Replies
17
Views
11K
looz
looz
D
b450 with a 1700x, will I have ram issues?
Replies
6
Views
1K
NeverBackDown
N
NickOmega
Ryzen 2600X - Opinions?
Replies
0
Views
7K
NickOmega
NickOmega
Back
Top