CLOCK_WATCHDOG_TIMEOUT ERROR NEED HELp

maoo1

Distinguished
Apr 18, 2011
14
0
18,510
I can only use the PC for ONE task at a time, for example: if i run a movie and copy some files in the background or run/install/uninstall a program or browse the internet my computer freezes restarts and this error shows up before the PC restarts CLOCK_WATCHDOG_TIMEOUT. i have also updated my BIOS version to no effect. Need help on how to resolve this. Thanks!

Here are my specs:

AMD RYZEN 7 SERIES OCTA CORE PROCESSOR 1700 - WITH WRAITH SPIRE COOLING SOLUTION (AM4 SOCKET, 20MB CACHE, UP TO 3.7 GHz)

MSI Gaming AMD Ryzen B350 DDR4 VR Ready HDMI USB 3 ATX Motherboard (B350 PC MATE)

Corsair Vengeance RGB LED 16GB (2x8GB) DDR4 3000 (PC4-24000) C15 - Intel 100/200 Series PC Memory (CMR16GX4M2C3000C15)

Zotac Amp Edition GeForce GTX 1060 6GB DDR5 PCI-e Graphics Card with IceStorm Cooling

Corsair RMx Series RM750x 750W Fully Modular Power Supply 80 PLUS Gold Certified

COOLER MASTER LIQUID COOLER - MASTERLIQUID LITE 120

Samsung 850 EVO 250GB 2.5-Inch SATA III Internal SSD (MZ-75E250BW)

Seagate Barracuda 2TB SATA 6Gb/s 64MB Cache 3.5-Inch Internal Bare Drive with 7200 RPM (ST2000DM006)

Arctic MX-4 Thermal Compound
 
Solution
I highly doubt that the CPU is to blame. There are numerous reports of people having the same issue in Windows, or even much worse, after buying Ryzen. The most common cause was that the platform was simply too new for Windows 10 build they used, and they had to redownload the latest ISO, and install it. It contains many fixes and patches which were unavailable just a few months ago.


Apart from that do you have any clue whether the processor can be faulty?
 
I highly doubt that the CPU is to blame. There are numerous reports of people having the same issue in Windows, or even much worse, after buying Ryzen. The most common cause was that the platform was simply too new for Windows 10 build they used, and they had to redownload the latest ISO, and install it. It contains many fixes and patches which were unavailable just a few months ago.
 
Solution