CLOCK_WATCHDOG_TIMEOUT error occurred, now I cannot boot up at all

Toggle sidebar Toggle sidebar
A

AeJayEm

Honorable
Jul 2, 2013
13
0
10,510
I have a system (details at the bottom) that got the CLOCK_WATCHDOG_TIMEOUT BSoD today. When I shut down and rebooted the computer would power on, but nothing would go. Screens wouldn't display, the CMOS "good" beep did not happen, no BIOS, nothing. I did get two short beeps from my MoBo which it says means CMOS setting error.

Troubleshooting steps:

1. Take out every USB - nothing except one monitor and power are plugged in at startup
2. Clear the CMOS - two different ways
3. Power off and unplug, and let it sit for a few hours
4. Take out GPU and reseat it - (MoBo has no onboard plug for monitor)

None of these steps made any difference. I still cannot boot up at all. I am starting to suspect a faulty processor, but that would really kill me - I have no money for a new MoBo and CPU.

System Specs:

Intel(R) Core™ i7-960 3.20 GHz 8M Intel Smart Cache LGA1366
GigaByte GA-X58A-UD3R Intel X58
12GB (2GBx6) Memory
1TB SATA-III HDD (non-system)
120GB System SSD
AMD ASUS R9 290 GPU
650W Antec Power Supply

As I said I cannot boot into BIOS or Windows, nothing works so I cannot post dump files or do a system restore. I feel like I am out of options. Any help is appreciated.



 
Sort by date Sort by votes
A

AeJayEm

Honorable
Jul 2, 2013
13
0
10,510


Just to check I did replace the battery and it still does not work. It did initially have a different "beep" code but it then went back to the two short "beeps".

I have "beeps" like that because they are actually more like ticks coming from the MoBo, not beeps. Pretty sure they have the same meaning though.
 
Upvote 0 Downvote
A

AeJayEm

Honorable
Jul 2, 2013
13
0
10,510


Unfortunately nothing changes - still doesn't POST - still two beeps

I don't see any physical damage to the MoBo or CPU. Very doubtful its somehow heat related. Nothing has changed with the Memory or any other part for that matter. This came out of the blue. I suppose it is possible that the OS could have somehow failed (Seen from other's CLOCK_WATCHDOG_TIMEOUT) but in that case I would still be able to POST and get into BIOS.
 
Upvote 0 Downvote
A

AeJayEm

Honorable
Jul 2, 2013
13
0
10,510
I appreciate all the comments. Tomorrow I will be trying to get my hard drive to boot on a completely different system. Hopefully it will rule out any OS issue.
 
Upvote 0 Downvote
gamerk316

gamerk316

Glorious
Jul 8, 2008
13,234
131
44,840
Only time I've ever seen this BSOD occur is when the CPU shuts down due to overheating, so that's the first thing I'd verify. After that, you're down to swapping components, but the fact you can't even post points toward a mobo/CPU side issue (and I almost NEVER consider a CPU failure, since it's so rare).
 
Upvote 0 Downvote
A

AeJayEm

Honorable
Jul 2, 2013
13
0
10,510
The problem was the Wireless Network Card I had hooked up via PCI. I have no explanation why. I disconnect it and the computer boots up.

Freakin computers man.....
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom