Random BSOD with CLOCK_WATCHDOG_TIMEOUT error

Hi, I have had my PC for 3 years now.

This is the following specs:
Motherboard: ASRock AB350M Pro4 AM4
CPU: AMD RYZEN 5 1600 6-Core 3.2 GHz (3.6 GHz Turbo)
RAM: 32 GB
Power Supply: SeaSonic G Series SSR-550RM 550W ATX12V
OS: Windows 10 Pro Build 19041.329

Ever since sometime last year, I would infrequently get a BSOD every once a while involving a CLOCK_WATCHDOG_TIMEOUT. I wasn't able to figure much out but it didn't occur often enough to really bother me. However, recently I have noticed that it occurred more frequently. Another side note that I've also noticed is that when I restart my computer or shut it down and reboot, it will sometimes be much slower than usual and will stay that way until I've performed another shut down + reboot / restart.

Here is a dump file I got recently.

Anyone got any idea why this is happening?

Thanks!

Means unstable CPU core(s) But only normal with overclocking core(s) with not enough Vcore or need to back off on the CPU overclock, according to overclockers.com. IIRC, it's bugcheck code 0x00000101.

I never received that one, interestingly, but the meaning of the error code appears to be very clear-> A core dropped out.

Jacee, that site is sketchy, seems to prey on people who don't know much about computers.
(some spam text before the decent article) (not your fault, I apologize)
Albeit I saw some decent information. But this is a CPU hardware error, from what I gather. Never heard of dropped-out GPUs causing this, most likely, that'll be 0x00000116, for "VIDEO_TDR_FAILURE", which is probable, if the video card pops out of the PCI-E slot while Windows is running. I had that happen! Yikes!

Thanks for the reply RJARRRPCGP.

That would be really weird as I don't have any of my CPUs overclocked. So would that point towards a faulty core or something like that instead then?

lazukr said:

So would that point towards a faulty core or something like that instead then?

Possibly, especially if you have a good PSU and still get that bugcheck code. It looks like Windows' way of saying that it timed out on a CPU core, because a CPU core failed to respond.