Clock Watchdog Timeout, screen freeze, Thread Stuck in device driver

TechiGamer

Distinguished
Aug 3, 2013
381
0
18,790
Hi,

I've been having some issues with my pc in the past week or so, and I can't seem to find the problem, so I was hoping someone would help out. These are my specs:

CPU: i5-4670k (1.5 years old)
Motherboard: MSI Gaming 5 (2.5 years old)
RAM: Patriot 8gb 2133Mhz (4 years old)
GPU Crossfire: r9 280x and 7970 (2 and 4 years old respectively)
Power Supply: Antec 850W High current pro (4 years old)
Storage: 850 evo and 1tb WD blue (2 days and 4 years old respecitvely

I have not done any overclocking on my system. Temperatures are fine (33 C)

So basically, my system has been freezing alot, including BSOD, black screens, and straight up screen freeze. Its also been randomly crashing. I had an m4 crucial SSD as my boot, and I tried doing a clean install, after which it would be fine, but would consistently get worse and worse as I would be rebooting and installing my programs until I can pretty much no longer get into the system.
After checking the health of the ssd with crystal disk info, I noticed quite a few errors, and also lots of people were reporting very similar issues with the m4 line of ssds. Since mine was refurbished as well, I thought this was definitely the issue. So I bought the 850 evo .

However, even with the new ssd, its very difficult even to just install windows and all the programs. The issue starts when I start installing windows 10, and after the computer reboots for the first time, it starts to load and shows different things like "checking devices" at the screen displaying the motherboard manufacturer icon and this picture starts to shift upward and downward etc. and black text boxes appear.
There are 2 versions to what happens after this:

1. System with GPU installed: black screen without cursor or anything else.

2. System without GPU and processor doing screen output: "Clock Watchdog Timeout" Bsod.
The led debug indicator displayed "39"


After this, I have to click the reset button which after boot always takes me straight to the windows 10 setup screen. This happened with both gpu installed and uninstalled.

After Windows 10 is installed, it was completely fine, and I only start noticing issues after I install most of the programs, drivers, and updates and after I had been rebooting several times. So the problems that I encounter then is mainly screen freezes, but the 3 or 4 times that BSOD occurred, the error message was "Thread Stuck in Device Driver". Sometimes in these situations, the computer wouldn't respond even when I clicked the reset button. I needed to either unplug the computer or hold the power button down for about 10 seconds.

I tried both connecting to wifi and leaving it disconnected during the windows setup before installing the drivers and programs. I read that windows 10 sometimes automatically downloads drivers for devices that do not have it installed yet, so that is why I skipped the wifi for one of the installations, but no difference in the end result.

I have seen quite a few BSODs since the problem started, but I only started writing down the name of the error in the past few attempts. They have all been either "Clock Watchdog Timeout" or "Thread stuck in device driver".

Also, every single time, I usually install my chipset drivers first, but when I do this, before it completes installing, I get a BSOD with the error: Clock Watchdog Timeout. The BSOD does not disappear until I click reset our manual power cycle the computer. After it has been rebooted, it installs just fine.

Any suggestions would be appreciated. Thank you !
 
Solution
Your manual indicates that debug code 39 is "Early North Bridge Initialization"

  • ■ Try with a single stick of RAM in the first slot
    ■ Try re-seating the CPU and inspect the socket for bent or broken pins

HamBown81

Commendable
Aug 3, 2017
917
0
1,360
Your manual indicates that debug code 39 is "Early North Bridge Initialization"

  • ■ Try with a single stick of RAM in the first slot
    ■ Try re-seating the CPU and inspect the socket for bent or broken pins
 
Solution

TechiGamer

Distinguished
Aug 3, 2013
381
0
18,790

Thanks. It was actually one of the RAM modules that no longer functions properly.