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
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) |
bcc92c88 fffff802
1203ab42 : 0000000000000101 00000000
0000000c 0000000000000000 ffff9281
bc995180 : nt!KeBugCheckExbcc92c90 fffff802
11e7541d : 0000000000000000 ffff9281
bcc40180 0000000000000246 00000000
000022cf : nt!KeAccumulateTicks+0x1c8942bcc92cf0 fffff802
11e759c1 : 0000000000002100 00000000
000014bf ffff9281bcc40180 00000000
00000001 : nt!KiUpdateRunTime+0x5dbcc92d40 fffff802
11e6f833 : ffff9281bcc40180 00000000
00000000 fffff80212831a58 00000000
00000000 : nt!KiUpdateTime+0x4a1bcc92e80 fffff802
11e781f2 : ffffd20bdbd8f090 ffffd20b
dbd8f110 ffffd20bdbd8f100 00000000
0000000c : nt!KeClockInterruptNotify+0x2e3bcc92f30 fffff802
11f27f55 : 000000005320c6ae ffffc101
68ecb380 ffffc10168ecb430 00000000
00000000 : nt!HalpTimerClockInterrupt+0xe2bcc92f60 fffff802
11ff76fa : ffffd20bdbd8f110 ffffc101
68ecb380 0000000000000001 00000000
00000000 : nt!KiCallInterruptServiceRoutine+0xa5bcc92fb0 fffff802
11ff7c67 : 000000001bd73585 ffff9281
bcc40180 0000000000000002 ffff9281
bcc43130 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfadbd8f090 fffff802
11e93686 : 0000000000000000 00000000
00000000 0000000000000002 ffffc101
6ee10000 : nt!KiInterruptDispatchNoLockNoEtw+0x37dbd8f220 fffff802
11e93498 : 0000000000000000 ffffe4f2
00000000 ffffc10175c9bb00 fffff802
11e2f08a : nt!KeFlushMultipleRangeTb+0x166They 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 fffff802
1203ab42 : 0000000000000101 00000000
0000000c 0000000000000000 ffff9281
bc995180 : nt!KeBugCheckEx
ffff9281bcc92c90 fffff802
11e7541d : 0000000000000000 ffff9281
bcc40180 0000000000000246 00000000
000022cf : nt!KeAccumulateTicks+0x1c8942
ffff9281bcc92cf0 fffff802
11e759c1 : 0000000000002100 00000000
000014bf ffff9281bcc40180 00000000
00000001 : nt!KiUpdateRunTime+0x5d
ffff9281bcc92d40 fffff802
11e6f833 : ffff9281bcc40180 00000000
00000000 fffff80212831a58 00000000
00000000 : nt!KiUpdateTime+0x4a1
ffff9281bcc92e80 fffff802
11e781f2 : ffffd20bdbd8f090 ffffd20b
dbd8f110 ffffd20bdbd8f100 00000000
0000000c : nt!KeClockInterruptNotify+0x2e3
ffff9281bcc92f30 fffff802
11f27f55 : 000000005320c6ae ffffc101
68ecb380 ffffc10168ecb430 00000000
00000000 : nt!HalpTimerClockInterrupt+0xe2
ffff9281bcc92f60 fffff802
11ff76fa : ffffd20bdbd8f110 ffffc101
68ecb380 0000000000000001 00000000
00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffff9281bcc92fb0 fffff802
11ff7c67 : 000000001bd73585 ffff9281
bcc40180 0000000000000002 ffff9281
bcc43130 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffd20bdbd8f090 fffff802
11e93686 : 0000000000000000 00000000
00000000 0000000000000002 ffffc101
6ee10000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffd20bdbd8f220 fffff802
11e93498 : 0000000000000000 ffffe4f2
00000000 ffffc10175c9bb00 fffff802
11e2f08a : 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
NO picture attached I can see?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.
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![]()
Oh i can see. Here is the picture: https://1drv.ms/u/s!AgsDYwxM32yCvkGtvNDmNgSTBthf?e=M5LIdf
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
![]()
Yee okay. But you have no idea what i can do to fix the error?think it was just confused and showed that for every thread in CPU. IT could see core count but it didn't know what it is. Clearly they need to update something.