Question BSoD In Normal Mode Clock_Watchdog_Timeout

[GetYaArmour]

My PC BSoDs when running in normal mode and Clean Boot mode but not in Safe Mode.

Error Message: Clock_Watchdog_Timeout

BlueScreenView is pointing at: ntoskrnl.exe

If you need more info just ask

Specs:
CPU: Ryzen 5 2600
GPU: GTX 1650
Motherboard: MSI A320M-A Pro Max
RAM: 16GB (2x8GB) DDR4
SSD: 1TB SSD
PSU: CV550

Thanks in advance,
GetYaArmour

 

[Roland Of Gilead]

Hey there,

There can be a number of reasons for this. It can be a driver related issues, where a driver sends a request to the CPU and it does not respond in time. It can also be hardware related, as in a fault with the CPU.

Try updating all your system drivers, and bios to latest agesa version to make sure it's not some bug. Prob worth clearing out CMOS if you do update the bios, or even if you haven't still reset CMOS. You can find instructions in your mobo manual on how to do this.

Let us know how you get on.

On a side note, your PSU isn't the best. If you are running any OC's, take them off, and run at stock, and see if that makes a difference. It can do.

It can also be indicative of a ram issue. Are you running a matched kit? Or are the mixed DIMMS?

Sadly that clock watchdog timeout, can be a number of things, that present as that error code. It's a tough one to diagnose.

 

[GetYaArmour]

Hey there,

There can be a number of reasons for this. It can be a driver related issues, where a driver sends a request to the CPU and it does not respond in time. It can also be hardware related, as in a fault with the CPU.

Try updating all your system drivers, and bios to latest agesa version to make sure it's not some bug. Prob worth clearing out CMOS if you do update the bios, or even if you haven't still reset CMOS. You can find instructions in your mobo manual on how to do this.

Let us know how you get on.

On a side note, your PSU isn't the best. If you are running any OC's, take them off, and run at stock, and see if that makes a difference. It can do.

It can also be indicative of a ram issue. Are you running a matched kit? Or are the mixed DIMMS?

Sadly that clock watchdog timeout, can be a number of things, that present as that error code. It's a tough one to diagnose.

Drivers all appear to be up to date

Have already reset cmos and that doesn't seem to have helped

Currently not running any OC

Both ram sticks are the same

Tried quite a lot but having left it in safe mode for a while to check if it crashes in safe mode and just now switched back to normal mode it seems to doing OK but could crash at any moment (edit: just did).

 

[GetYaArmour]

Hey there,

There can be a number of reasons for this. It can be a driver related issues, where a driver sends a request to the CPU and it does not respond in time. It can also be hardware related, as in a fault with the CPU.

Try updating all your system drivers, and bios to latest agesa version to make sure it's not some bug. Prob worth clearing out CMOS if you do update the bios, or even if you haven't still reset CMOS. You can find instructions in your mobo manual on how to do this.

Let us know how you get on.

On a side note, your PSU isn't the best. If you are running any OC's, take them off, and run at stock, and see if that makes a difference. It can do.

It can also be indicative of a ram issue. Are you running a matched kit? Or are the mixed DIMMS?

Sadly that clock watchdog timeout, can be a number of things, that present as that error code. It's a tough one to diagnose.

New issue, 8 just tried loading into safe mode and it BSoD'd with Critical_Process_Died
Is my entire system now screwed?

 

[Bob.B]

New issue, 8 just tried loading into safe mode and it BSoD'd with Critical_Process_Died
Is my entire system now screwed?

See if you can boot and run a copy of memtest86.