CLOCK_WATCHDOG_TIMEOUT for a week old built computer

Justbender

Reputable
Jun 21, 2014
8
0
4,510
the specs of my computer are
Intel core i5-4670k processor
msi z97 gaming 5
asus geforce gtx 770
Samsung ssd 840 evo
WD 1 TB mainstream hard drive
8 GB crucial ballistix sport ddr3 RAM

It's been a week since I built the compute and everything was working Good. today i was playing assassin Creed black flag when the game froze and the blue screen and the CLOCK_WATCHDOG_TIMEOUT error appeared. I waited for the computer to restart but it never did. I restarted the computer manually but it didn't booted up.
and now it nothing appears in the monitor just a black screen.
what can I do?
 
CLOCK_WATCHDOG_TIMEOUT is basically the system asks a piece of hardware to do something and sets a timer. if the timer goes off before the hardware responds the system calls a bugcheck because it thinks you have a hardware failure.

you will want to start by reseting your BIOS to defaults, since you have no video you will have to use jumpers or a switch on your motherboard. In particular you want to make sure your PCI bus is not over clocked. It should be set to 100Mhz. if you don't have a switch on your motherboard, try moving your graphics card to another slot to get the BIOS to detect a change and update.

failing this you will want to check your power to your graphics card, and the graphics card itself for failures.

(most likely you just have a slightly overclocked PCI bus)
 



I did everything you said but still not working. i am guessing is the processor. i forgot to mention this i am using a HYPER 212 EVo CPU COOLER from COOLER MASTER. I removed the video card and unplugged the hard drives and mouse and keyboar but i didnt hear a beep sound. the fans are working. i have no clue what the problem is.
 
generally you would get this error when the CPU does not get a response from a external hardware device.
(ssd, usb, network driver, graphics card) I recall looking at this error with a SSD where the drive was kind of backed up because the TRIM commands were not called. That seems to happen, with the older SSD drives with firmware bugs and on old versions of windows like windows 7. it also happens using "ghost" type programs that drop images on to SSD drives.

overall, you end up looking at the memory dump to see what driver failed to respond, then you have to figure out why it did not respond before the timeout period. Oh, some times if it is your SSD causing the problem you can boot into BIOS and leave the machine running for a few hours on the BIOS screen and the SSD internal garbage collection routines will clean up the drive and it will start working again. tends to happen more often as the drive starts to fill up. ( you want to have plenty of free space on the drive to allow the drive to do its clean up)