CPU not booting - no POST message

DLam

Junior Member
Mar 5, 2004
3
0
0
I'm trying to build my first computer. It booted the first time and I went into bios to change the boot from floppy to CD-ROM. I rebooted with Windows XP in the DVD drive and it began loading. However, it stalled and gave me a message that loading is stopped to prevent "damage to the computer", something along those lines, I don't remember exactly what it said. I rebooted it and the post message was "system failed due to overclocking". I turned it off and on again
but now it won't even beep and I can't get into bios. I took out the mobo, like an earlier thread suggested, and powered up just with the mobo + cpu + 1 stick of RAM but I still can't get it to beep.
Anybody has any thoughts on what's fried and how to go around fixing it?

These are the components (all new): Asus A7N8X-E Dlx, Athlon XP-M 2500, TT Purepower 420W PSU, Corsair 512mb 3200 LLPT RAM. Other hardware that I put together in the case: ATI 9700 Pro, Sony DVDROM, Nec 2500 DVDRW, Seagate 120gb ATA HD (and no floppy drive).

I don't understand the "overclocking" message because everything was set at default (except the boot drive).
Edit: The CPU fan works upon power up and I'm using Thermalright ALX-800 with Arctic silver 5 TIM.
 

DLam

Junior Member
Mar 5, 2004
3
0
0
I just cleared the CMOS. It didn't make any difference. Still the fan spinning round and round, but nothing else.
 

minendo

Elite Member
Aug 31, 2001
35,560
22
81
Originally posted by: DLam
I just cleared the CMOS. It didn't make any difference. Still the fan spinning round and round, but nothing else.

Reseat the motherboard to ensure it is not shorting out.
 

DLam

Junior Member
Mar 5, 2004
3
0
0
Yah, I have it sitting on an antistatic bag, outside the case, on the table. I thought it was a short too, so I took it out. I'm beginning to think that the chip or the mobo is fried, but before I take drastic (and expensive) measures , I wanna be able to rule everything out. :(
 

minendo

Elite Member
Aug 31, 2001
35,560
22
81
With no beep codes, I would lean towards it being a mobo issue.