BSOD Clock Watchdog Timeout

[Leoplate25]

Hi, i'm facing some issues. I was setting my Windows and out of the sudden a BSOD occured. I tried to run Prime95 SmallFFT and after 20 minutes, i got the same BSOD. I had the CPU undervolted by -0.050v offset for 2 months and nothing happened. Now, i'm running Prime95 again, without UV the CPU and it's fine... For now. I have an 11600K on an ASUS TUF WiFi Z590, 4x8GB Corsair Vengeance RGB Pro at 3200MHz, an H115i RGB PRO XT, a SATA SSD Samsung EVO 860 1TB, two NVMe, one is a WD SN750 SE 500GB PCIe 4.0 and another is a WD SN550 1TB. My PSU is a Seasonic GX850 and the GPU that i could afford was the 3060 12GB GDDR6.
Could it be the -0.050v offset UV or what? Thanks in advance.

Microsoft says this: The CLOCK_WATCHDOG_TIMEOUT bug check has a value of 0x00000101. This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.

Bug Check using BlueScreen Viewer:

 

[RJARRRPCGP]

I wouldn't be surprised if that's just Microsoft's way of saying that a worker died. That is very likely with too low of Vcore.

Albeit, for me, for some reason, it's always been WHEA_UNCORRECTABLE_ERROR with "Cache Hierarchy Error" as the reason, including the Vcore being too low when running Cinebench.

Seems like Ryzens are more likely to give "Cache Hierarchy Error" WHEAs. As with my Vermeer, even when not known to be faulty, gives the same WHEA error type as my Matisse with unstable VRAM.

I know that in the past, it was common for me to get 0x0000000A (IRQL_NOT_LESS_OR_EQUAL) BSODs for not enough Vcore.

 

[Leoplate25]

I wouldn't be surprised if that's just Microsoft's way of saying that a worker died. That is very likely with too low of Vcore.

Albeit, for me, for some reason, it's always been WHEA_UNCORRECTABLE_ERROR with "Cache Hierarchy Error" as the reason, including the Vcore being too low when running Cinebench.

Seems like Ryzens are more likely to give "Cache Hierarchy Error" WHEAs. As with my Vermeer, even when not known to be faulty, gives the same WHEA error type as my Matisse with unstable VRAM.

I know that in the past, it was common for me to get 0x0000000A (IRQL_NOT_LESS_OR_EQUAL) BSODs for not enough Vcore.

Hi, and thanks for your answer. I just run an hour and a half of Prime95 and 3 rounds of CB and now it seems stable.

 

[RJARRRPCGP]

Hi, and thanks for your answer. I just run an hour and a half of Prime95 and 3 rounds of CB and now it seems stable.

CTR 2.1 RC5 reports golden sample for my Ryzen 5 5600X, but the diagnose option still sets the Vcore too low, because Windows 10 crashed out when running Cinebench.

 

[Leoplate25]

CTR 2.1 RC5 reports golden sample for my Ryzen 5 5600X, but the diagnose option still sets the Vcore too low, because Windows 10 crashed out when running Cinebench.

Hi, man, sorry for the late reply but i was testing the CPU. I lowered the offset from -0.050v to 0.025v and i ran Prime95 for 2 sesions of 1 and a half hour with no issues. When i had the offset at -0.050v, the BSOD occurs in 20 minutes aproximately.

EDIT: the hottest core reached 53, and the lowest core 48 C. An average of 49-50 C. Prime95 SmallFFTs no AVX (more realistic test).