[SOLVED] Clock watchdog timeout: Error code

Mar 7, 2021
9
0
10
0
I get bsod on Windows 20h2, with error code: clock watchdog timeout, it happens when I try to open Noxplayer and it has started after I switched to a ryzen 7 5800x, msi b550 gaming plus and 32 gb 3600mhz ram
 

Colif

Win 10 Master
Moderator
well, we can look at hardware and see if its okay, as perhaps cause isn't CPU but instructions it is getting that are causing the stuck. I don't see many of these BSOD so I don't have a plan of action

CPU - Ryzen 7 5800X 8-Core Processor - Passes Prime 95
RAM - 32gb Corsair 3600mhz CMK32GX4M2Z3600C18
MB - MPG B550 GAMING PLUS - latest bios (No real tests for MB)
what else is in PC? I know there is more. what make model ssd/hdd?
What PSU?

have you had any more BSOD?

try running memtest on your ram
Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. Memtest is created as a bootable USB so that you don’t need windows to run it

only tests for GPU are benchmarks and really, I don't need the results, we just run them to see if you crash during them. Don't run both at once.

https://geeks3d.com/furmark/
https://benchmark.unigine.com/heaven
 

Colif

Win 10 Master
Moderator
if you did clean install
Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

Open Windows File Explorer
Navigate to C:\Windows\Minidump
Copy the mini-dump files out onto your Desktop
Do not use Winzip, use the built in facility in Windows
Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
Then post a link here to the zip file, so we can take a look for you . . .

Do you have newest chipset drivers? - https://www.amd.com/en/support/chipsets/amd-socket-am4/b550
latest bios? newest is a Beta that came out on 5th - https://www.msi.com/Motherboard/support/MPG-B550-GAMING-PLUS
 
Mar 7, 2021
9
0
10
0
if you did clean install
Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

Open Windows File Explorer
Navigate to C:\Windows\Minidump
Copy the mini-dump files out onto your Desktop
Do not use Winzip, use the built in facility in Windows
Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
Then post a link here to the zip file, so we can take a look for you . . .

Do you have newest chipset drivers? - https://www.amd.com/en/support/chipsets/amd-socket-am4/b550
latest bios? newest is a Beta that came out on 5th - https://www.msi.com/Motherboard/support/MPG-B550-GAMING-PLUS
I did a fresh install. But when i try to compres the file it says "The file was not found or there are no read rights."?
 

Colif

Win 10 Master
Moderator
the steps above should be all you need to copy it, I got them direct from Microsoft and include all the steps you need.

if you did a clean install since the bsod, they won't be there as you deleted them with the clean install.

set PC up to create minidumps just in case it happens again.
 

gardenman

Distinguished
Moderator
I ran the dump files through the debugger and got the following information: https://jsfiddle.net/7vnkhgcz/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.
File information:031021-21625-01.dmp (Mar 10 2021 - 10:19:10)
Bugcheck:CLOCK_WATCHDOG_TIMEOUT (101)
Probably caused by:memory_corruption (Process: ExpressVPNNotificationService.exe)
Uptime:0 Day(s), 0 Hour(s), 01 Min(s), and 23 Sec(s)

File information:030921-21796-01.dmp (Mar 9 2021 - 15:19:00)
Bugcheck:CLOCK_WATCHDOG_TIMEOUT (101)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 02 Min(s), and 19 Sec(s)

File information:030921-20750-01.dmp (Mar 9 2021 - 15:06:28)
Bugcheck:CLOCK_WATCHDOG_TIMEOUT (101)
Probably caused by:memory_corruption (Process: explorer.exe)
Uptime:0 Day(s), 0 Hour(s), 00 Min(s), and 45 Sec(s)

File information:030921-19281-01.dmp (Mar 9 2021 - 09:50:51)
Bugcheck:CLOCK_WATCHDOG_TIMEOUT (101)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 03 Min(s), and 43 Sec(s)

File information:030921-19281-02.dmp (Mar 9 2021 - 14:54:44)
Bugcheck:CLOCK_WATCHDOG_TIMEOUT (101)
Probably caused by:memory_corruption (Process: NoxVMHandle.exe)
Uptime:0 Day(s), 0 Hour(s), 01 Min(s), and 23 Sec(s)
Possible Motherboard page: https://www.msi.com/Motherboard/MPG-B550-GAMING-PLUS
You have BIOS 1.4 installed. The latest stable version is 1.5. We usually recommend avoiding Betas (1.6). Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Reactions: Jonas7782

Colif

Win 10 Master
Moderator
They are all the same process, I don't understand windows processes fully (loi) enough to understand what it was trying to do but since all 5 are the same BSOD, I can guess.
Error Description
An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval. This indicates that the specified processor is hung and not processing interrupts.
the below text is from the error, I don't expect you to understand it (as I am not sure myself). It is in first in, last out order, meaning the things at bottom were the 1st entries

ffff9281bcc92c88 fffff8021203ab42 : 0000000000000101 000000000000000c 0000000000000000 ffff9281bc995180 : nt!KeBugCheckEx
ffff9281bcc92c90 fffff80211e7541d : 0000000000000000 ffff9281bcc40180 0000000000000246 00000000000022cf : nt!KeAccumulateTicks+0x1c8942
ffff9281bcc92cf0 fffff80211e759c1 : 0000000000002100 00000000000014bf ffff9281bcc40180 0000000000000001 : nt!KiUpdateRunTime+0x5d
ffff9281bcc92d40 fffff80211e6f833 : ffff9281bcc40180 0000000000000000 fffff80212831a58 0000000000000000 : nt!KiUpdateTime+0x4a1
ffff9281bcc92e80 fffff80211e781f2 : ffffd20bdbd8f090 ffffd20bdbd8f110 ffffd20bdbd8f100 000000000000000c : nt!KeClockInterruptNotify+0x2e3
ffff9281bcc92f30 fffff80211f27f55 : 000000005320c6ae ffffc10168ecb380 ffffc10168ecb430 0000000000000000 : nt!HalpTimerClockInterrupt+0xe2
ffff9281bcc92f60 fffff80211ff76fa : ffffd20bdbd8f110 ffffc10168ecb380 0000000000000001 0000000000000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffff9281bcc92fb0 fffff80211ff7c67 : 000000001bd73585 ffff9281bcc40180 0000000000000002 ffff9281bcc43130 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffd20bdbd8f090 fffff80211e93686 : 0000000000000000 0000000000000000 0000000000000002 ffffc1016ee10000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffd20bdbd8f220 fffff80211e93498 : 0000000000000000 ffffe4f200000000 ffffc10175c9bb00 fffff80211e2f08a : nt!KeFlushMultipleRangeTb+0x166

the only parts that aren't typical of hardware errors is the Update Time line that I haven't seen before. the dump text is mostly the same in all 5, process starting it off might be new but end result is same. No indication of any drivers.

The cause appears to be a core in your processor gets stuck and isn't processing requests (system calls them interrupts)

You appear to have latest AMD chipset drivers, the beta bios might actually help since you on a 5800X

I would suggest running Prime 95 and test CPU
https://www.mersenne.org/download/
Prime 95 How to Guide: http://www.playtool.com/pages/prime95/prime95.html
 
Mar 7, 2021
9
0
10
0
They are all the same process, I don't understand windows processes fully (loi) enough to understand what it was trying to do but since all 5 are the same BSOD, I can guess.
Error Description
An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval. This indicates that the specified processor is hung and not processing interrupts.
the below text is from the error, I don't expect you to understand it (as I am not sure myself). It is in first in, last out order, meaning the things at bottom were the 1st entries

ffff9281bcc92c88 fffff8021203ab42 : 0000000000000101 000000000000000c 0000000000000000 ffff9281bc995180 : nt!KeBugCheckEx
ffff9281bcc92c90 fffff80211e7541d : 0000000000000000 ffff9281bcc40180 0000000000000246 00000000000022cf : nt!KeAccumulateTicks+0x1c8942
ffff9281bcc92cf0 fffff80211e759c1 : 0000000000002100 00000000000014bf ffff9281bcc40180 0000000000000001 : nt!KiUpdateRunTime+0x5d
ffff9281bcc92d40 fffff80211e6f833 : ffff9281bcc40180 0000000000000000 fffff80212831a58 0000000000000000 : nt!KiUpdateTime+0x4a1
ffff9281bcc92e80 fffff80211e781f2 : ffffd20bdbd8f090 ffffd20bdbd8f110 ffffd20bdbd8f100 000000000000000c : nt!KeClockInterruptNotify+0x2e3
ffff9281bcc92f30 fffff80211f27f55 : 000000005320c6ae ffffc10168ecb380 ffffc10168ecb430 0000000000000000 : nt!HalpTimerClockInterrupt+0xe2
ffff9281bcc92f60 fffff80211ff76fa : ffffd20bdbd8f110 ffffc10168ecb380 0000000000000001 0000000000000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffff9281bcc92fb0 fffff80211ff7c67 : 000000001bd73585 ffff9281bcc40180 0000000000000002 ffff9281bcc43130 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffd20bdbd8f090 fffff80211e93686 : 0000000000000000 0000000000000000 0000000000000002 ffffc1016ee10000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffd20bdbd8f220 fffff80211e93498 : 0000000000000000 ffffe4f200000000 ffffc10175c9bb00 fffff80211e2f08a : nt!KeFlushMultipleRangeTb+0x166

the only parts that aren't typical of hardware errors is the Update Time line that I haven't seen before. the dump text is mostly the same in all 5, process starting it off might be new but end result is same. No indication of any drivers.

The cause appears to be a core in your processor gets stuck and isn't processing requests (system calls them interrupts)

You appear to have latest AMD chipset drivers, the beta bios might actually help since you on a 5800X

I would suggest running Prime 95 and test CPU
https://www.mersenne.org/download/
Prime 95 How to Guide: http://www.playtool.com/pages/prime95/prime95.html
That core is stuck sounds pretty likely. Tried updating BIOS to 16.1 now. But still no luck ... Here's a picture of my Speccy. "AMD K19" must be the cores that stuck. Any idea what to do?
 

Colif

Win 10 Master
Moderator
Here's a picture of my Speccy. "AMD K19" must be the cores that stuck. Any idea what to do?
NO picture attached I can see?
AMD K19 seems to appear if software is out of date, whether its Speccy or CPU-Z or even HWINFO. Appears linked to be another name for the 5000 series. I seen it linked to your CPU and 5950x

did you try Prime95?

Clock Watchdog is a hardware error so its possible you might need to rma CPU as I don't know of anyway to unstick a CPU. Its why I suggest Prime as it will test CPU and maybe show fails there you can show AMD.
 
Mar 7, 2021
9
0
10
0
NO picture attached I can see?
AMD K19 seems to appear if software is out of date, whether its Speccy or CPU-Z or even HWINFO. Appears linked to be another name for the 5000 series. I seen it linked to your CPU and 5950x

did you try Prime95?

Clock Watchdog is a hardware error so its possible you might need to rma CPU as I don't know of anyway to unstick a CPU. Its why I suggest Prime as it will test CPU and maybe show fails there you can show AMD.
Oh i can see. Here is the picture: https://1drv.ms/u/s!AgsDYwxM32yCvkGtvNDmNgSTBthf?e=M5LIdf
And i will try the Prime95 now. It just looket confusing :)
 
Mar 7, 2021
9
0
10
0
This is what Prime95 shows in "results" folder. After been running for 1 hour and 30 minuts:


[Wed Mar 17 00:13:58 2021]
Self-test 384K passed!
Self-test 384K passed!
Self-test 384K passed!
Self-test 384K passed!
Self-test 384K passed!
Self-test 384K passed!
Self-test 384K passed!
Self-test 384K passed!
Self-test 384K passed!
Self-test 384K passed!
Self-test 384K passed!
Self-test 384K passed!
Self-test 384K passed!
Self-test 384K passed!
Self-test 384K passed!
Self-test 384K passed!
[Wed Mar 17 00:20:33 2021]
Self-test 4K passed!
Self-test 4K passed!
Self-test 4K passed!
Self-test 4K passed!
Self-test 4K passed!
Self-test 4K passed!
Self-test 4K passed!
Self-test 4K passed!
Self-test 4K passed!
Self-test 4K passed!
Self-test 4K passed!
Self-test 4K passed!
Self-test 4K passed!
Self-test 4K passed!
Self-test 4K passed!
Self-test 4K passed!
[Wed Mar 17 00:26:45 2021]
Self-test 400K passed!
Self-test 400K passed!
Self-test 400K passed!
Self-test 400K passed!
Self-test 400K passed!
Self-test 400K passed!
Self-test 400K passed!
Self-test 400K passed!
Self-test 400K passed!
Self-test 400K passed!
Self-test 400K passed!
Self-test 400K passed!
Self-test 400K passed!
Self-test 400K passed!
Self-test 400K passed!
Self-test 400K passed!
[Wed Mar 17 00:32:15 2021]
Self-test 5K passed!
Self-test 5K passed!
Self-test 5K passed!
Self-test 5K passed!
Self-test 5K passed!
Self-test 5K passed!
Self-test 5K passed!
Self-test 5K passed!
Self-test 5K passed!
Self-test 5K passed!
Self-test 5K passed!
Self-test 5K passed!
Self-test 5K passed!
Self-test 5K passed!
Self-test 5K passed!
Self-test 5K passed!
[Wed Mar 17 00:40:17 2021]
Self-test 448K passed!
Self-test 448K passed!
Self-test 448K passed!
Self-test 448K passed!
Self-test 448K passed!
Self-test 448K passed!
Self-test 448K passed!
Self-test 448K passed!
Self-test 448K passed!
Self-test 448K passed!
Self-test 448K passed!
Self-test 448K passed!
Self-test 448K passed!
Self-test 448K passed!
Self-test 448K passed!
Self-test 448K passed!
[Wed Mar 17 00:46:26 2021]
Self-test 6K passed!
Self-test 6K passed!
Self-test 6K passed!
Self-test 6K passed!
Self-test 6K passed!
Self-test 6K passed!
Self-test 6K passed!
Self-test 6K passed!
Self-test 6K passed!
Self-test 6K passed!
Self-test 6K passed!
Self-test 6K passed!
Self-test 6K passed!
Self-test 6K passed!
Self-test 6K passed!
Self-test 6K passed!
[Wed Mar 17 00:55:29 2021]
Self-test 480K passed!
Self-test 480K passed!
Self-test 480K passed!
Self-test 480K passed!
Self-test 480K passed!
Self-test 480K passed!
Self-test 480K passed!
Self-test 480K passed!
Self-test 480K passed!
Self-test 480K passed!
Self-test 480K passed!
Self-test 480K passed!
Self-test 480K passed!
Self-test 480K passed!
Self-test 480K passed!
Self-test 480K passed!
[Wed Mar 17 01:01:26 2021]
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!
[Wed Mar 17 01:09:28 2021]
Self-test 512K passed!
Self-test 512K passed!
Self-test 512K passed!
Self-test 512K passed!
[Wed Mar 17 01:14:52 2021]
Self-test 512K passed!
Self-test 512K passed!
Self-test 512K passed!
Self-test 512K passed!
Self-test 512K passed!
Self-test 512K passed!
Self-test 512K passed!
Self-test 512K passed!
Self-test 512K passed!
Self-test 512K passed!
Self-test 512K passed!
Self-test 512K passed!
Self-test 560K passed!
Self-test 560K passed!
[Wed Mar 17 01:20:04 2021]
Self-test 560K passed!
Self-test 560K passed!
Self-test 560K passed!
Self-test 560K passed!
Self-test 560K passed!
Self-test 560K passed!
Self-test 560K passed!
Self-test 560K passed!
Self-test 560K passed!
Self-test 560K passed!
Self-test 560K passed!
Self-test 560K passed!
Self-test 560K passed!
Self-test 560K passed!
[Wed Mar 17 01:25:42 2021]
Self-test 10K passed!
Self-test 10K passed!
Self-test 10K passed!
Self-test 10K passed!
Self-test 10K passed!
Self-test 10K passed!
Self-test 10K passed!
Self-test 10K passed!
Self-test 10K passed!
Self-test 10K passed!
Self-test 10K passed!
Self-test 10K passed!
Self-test 10K passed!
Self-test 10K passed!
Self-test 10K passed!
Self-test 10K passed!
[Wed Mar 17 01:33:09 2021]
Self-test 576K passed!
Self-test 576K passed!
Self-test 576K passed!
Self-test 576K passed!
Self-test 576K passed!
Self-test 576K passed!
Self-test 576K passed!
[Wed Mar 17 01:38:17 2021]
Self-test 576K passed!
Self-test 576K passed!
Self-test 576K passed!
Self-test 576K passed!
Self-test 576K passed!
Self-test 576K passed!
Self-test 576K passed!
Self-test 576K passed!
Self-test 576K passed!
Self-test 12K passed!
Self-test 12K passed!
Self-test 12K passed!
Self-test 12K passed!
Self-test 12K passed!
[Wed Mar 17 01:44:28 2021]
Self-test 12K passed!
Self-test 12K passed!
Self-test 12K passed!
Self-test 12K passed!
Self-test 12K passed!
Self-test 12K passed!
Self-test 12K passed!
Self-test 12K passed!
Self-test 12K passed!
Self-test 12K passed!
Self-test 12K passed!
Self-test 640K passed!
Self-test 640K passed!
Self-test 640K passed!
[Wed Mar 17 01:50:17 2021]
Self-test 640K passed!
Self-test 640K passed!
 
Last edited by a moderator:

Colif

Win 10 Master
Moderator
I should have said this by now but anymore dumps you get while we look into this may reveal more of the problem and save testing if you can give them to us as we go.

So that Prime95 test is a pass. I had a sneaking suspicion it wouldn't be that obvious.

Well, that isn't at all useful is it. and its showing K19 for every core so its not showing stuck ones at all. Your PC wouldn't work if all were stuck - Speccy wouldn't know that info anyway.

It seems Speccy just doesn't know your CPU, it doesn't know what CPU I have (exactly) but it at least guesses, and it doesn't show every core by itself but that is likely cause it thought it knew what I had but it was close enough.

Speccy must see the package temp as I don't show those temps on the CPU, I track another sensor which is far more accurate. But I digress.
I don't know what you were actually looking for in it. If you want to track actual sensor scores, I would use HWINFO as its more accurate (See spoiler below)
download HWINFO - https://www.hwinfo.com/download/
when you open app, click the box next to show sensors only and click run
in the next window, click on the gear icon in bottom right
On General tab, under polling period, set it to 500 and click the set button next to it, and click OK. this reduces the amount of time between sensors updating so its more accurate and you can watch CPU fall and rise all day.
i used tips from this video to set up icons in toolbar to track two temps but not the ones he chooses, I went with CPU CCD1instead of the package temp
CPU CCD1 is average temp of all cores and ignores the constant spike of a core being woken up every second or so.
If you want to know actual speed of CPU at any one time, the best to watch is Average Effective Clock
Another thing I did in HWINFO was right click the 2 sensors (in the main sensors window) I mentioned in the last 2 sentences and clicked show graph so I can see what CPU is doing at any time on screen, which much of the time isn't a lot
 
Last edited:
Mar 7, 2021
9
0
10
0
I should have said this by now but anymore dumps you get while we look into this may reveal more of the problem and save testing if you can give them to us as we go.

So that Prime95 test is a pass. I had a sneaking suspicion it wouldn't be that obvious.



Well, that isn't at all useful is it. and its showing K19 for every core so its not showing stuck ones at all. Your PC wouldn't work if all were stuck - Speccy wouldn't know that info anyway.

It seems Speccy just doesn't know your CPU, it doesn't know what CPU I have (exactly) but it at least guesses, and it doesn't show every core by itself but that is likely cause it thought it knew what I had but it was close enough.

Speccy must see the package temp as I don't show those temps on the CPU, I track another sensor which is far more accurate. But I digress.
I don't know what you were actually looking for in it. If you want to track actual sensor scores, I would use HWINFO as its more accurate (See spoiler below)
download HWINFO - https://www.hwinfo.com/download/
when you open app, click the box next to show sensors only and click run
in the next window, click on the gear icon in bottom right
On General tab, under polling period, set it to 500 and click the set button next to it, and click OK. this reduces the amount of time between sensors updating so its more accurate and you can watch CPU fall and rise all day.
i used tips from this video to set up icons in toolbar to track two temps but not the ones he chooses, I went with CPU CCD1instead of the package temp
CPU CCD1 is average temp of all cores and ignores the constant spike of a core being woken up every second or so.
If you want to know actual speed of CPU at any one time, the best to watch is Average Effective Clock
Another thing I did in HWINFO was right click the 2 sensors (in the main sensors window) I mentioned in the last 2 sentences and clicked show graph so I can see what CPU is doing at any time on screen, which much of the time isn't a lot

Just used speccy because I wanted to see if everything looked fine in there. Seems so weird with all the "AMD K19". Just thought it meant the kernels were stuck.

Have been inside and set temprature up in HWiN now.
 

Colif

Win 10 Master
Moderator
well, we can look at hardware and see if its okay, as perhaps cause isn't CPU but instructions it is getting that are causing the stuck. I don't see many of these BSOD so I don't have a plan of action

CPU - Ryzen 7 5800X 8-Core Processor - Passes Prime 95
RAM - 32gb Corsair 3600mhz CMK32GX4M2Z3600C18
MB - MPG B550 GAMING PLUS - latest bios (No real tests for MB)
what else is in PC? I know there is more. what make model ssd/hdd?
What PSU?

have you had any more BSOD?

try running memtest on your ram
Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. Memtest is created as a bootable USB so that you don’t need windows to run it

only tests for GPU are benchmarks and really, I don't need the results, we just run them to see if you crash during them. Don't run both at once.

https://geeks3d.com/furmark/
https://benchmark.unigine.com/heaven
 

ASK THE COMMUNITY