Computer won't post

jeffro29 · Feb 3, 2006, 07:31 PM

I was wondering if anybody could help me? I have a abit AV8 third eye with an 3500 amd64 processor and 1gb of corsair 3200C2 2226 timings and the video card is an X800XTPE all running on Windows XP Home Edtion. My problem is when i power on the system all you hear is the fans running and the system won't post all i hear is beeping. I've tested the memory, video card, power supply is a 485 watt enermax, in anouther system with an AMD 2600XP moblie processor and an abit NF7-S Rev 2.0 board and it all works fine. I don't under stand whats wrong!!!!!! does anybody have any ideas what could be wrong?

niceguyrichy · Feb 3, 2006, 07:33 PM

have you swapped out the hdd yet?

jeffro29 · Feb 3, 2006, 07:36 PM

Yes i have i tried that in the other system also. Both systems had a fresh install of the OS on them.

Dyre Straits · Feb 4, 2006, 06:22 PM

Pull out the CMOS battery from the motherboard and disconnect the power cord from the system for a minute or two. This will restore the motherboard to its native state.

Then replace the CMOS battery, hook up the power cord and see if it will boot. Sometimes this works if all that was the problem is bad settings or conflicts.

jeffro29 · Feb 4, 2006, 08:19 PM

I tried what you said and still nothing it does the same thing could it be the CPU is bad thats why it's not posting?

davidnsibs · Feb 4, 2006, 08:33 PM

hmm, what were you doing the last time it worked? same thing happened to me on my mobo when i was overclocking - i managed to fry my bios chip so needed to get a replacement. were you overclocking your fsb at all?

jeffro29 · Feb 4, 2006, 09:24 PM

It was overclocked not buy much thou it was like at 225fsb the processor was at 2475mhz from the factory setting of 2204 204fsb. How could it be the bios chip?

davidnsibs · Feb 4, 2006, 09:32 PM

well, when i pushed my board to 195fsb (its 166fsb default) it crashed, and then wouldnt boot, although fans would spin (bit like yours) i did a bit of reading on forums and stuff and found similar issues with other people, not quite sure why, but pushing the fsb too high meant sometimes the bios would get corrupted irreversibly, i ordered another from asus for £5, put it in, and voila, a working pc again (i had treied wiping the bios with no effect previously). anyway, doubt its the case for you if it was only a small overclock, not too sure what it could be though ??

EDIT: When resetting the bios you normally have to move a jumper across (should say in the mobo manual) as well as removing the battery like Dyre Straits mentioned, would be worth trying that again

niceguyrichy · Feb 4, 2006, 09:34 PM

the cpu tells the comp to look for all the other bits, so if it's still beeping then there's a good chance that your cpu is still ok and it's something else that's borked, probably the mobo from what you've described.

if you can test the cpu in another comp, and the mobo with a known working cpu then you can't really go wrong.
otherwise I'd rma the mobo and hope for the best

Tipstaff · Feb 5, 2006, 12:48 AM

It'd would help if you could post the beep codes. By that I mean the number of beeps, and length of beeps. For instance 1 long, and 2 short beeps can indicate a video error. This can mean that the video card isn't properly seated, isn't recognized by the motherboard, or is faulty.

I should point out that beep codes can depend on the bios manufacturer though as each one uses different tones to indicate errors. The one I described would be a common one used with Award bioses which is what your motherboard uses (this tone is also used with AMI bioses too). So, again, it would be helpful if you could post the beep errors your getting.

Also, you can take a look at THIS page which is for the Award bioses. For other bioses see the "Bios Beep Codes" menu on the right.

Lastly, some common beep errors can occur because of bad keyboard/mouse, bad or improperly seated ram (try only one stick at a time), improperly seated video card (remove it, then reseat it), and overheating CPU (check that the heatsink is properly seated). One commonly overlooked problem is the bios settings for fan control. If the CPU or case fans are running too slow the system will alert you (this depends again on the bios and it's settings). It could be that the system is just simply alerting you to that fact, and will not post as a precautionary measure so you don't fry your system. You could try unplugging all your case fans (not the CPU one though), and try booting again.

niceguyrichy · Feb 5, 2006, 01:02 AM

Quote:

Originally Posted by Tipstaff

It'd would help if you could post the beep codes. By that I mean the number of beeps, and length of beeps. For instance 1 long, and 2 short beeps can indicate a video error. This can mean that the video card isn't properly seated, isn't recognized by the motherboard, or is faulty.

I should point out that beep codes can depend on the bios manufacturer though as each one uses different tones to indicate errors. The one I described would be a common one used with Award bioses which is what your motherboard uses (this tone is also used with AMI bioses too). So, again, it would be helpful if you could post the beep errors your getting.

Also, you can take a look at THIS page which is for the Award bioses. For other bioses see the "Bios Beep Codes" menu on the right.

Lastly, some common beep errors can occur because of bad keyboard/mouse, bad or improperly seated ram (try only one stick at a time), improperly seated video card (remove it, then reseat it), and overheating CPU (check that the heatsink is properly seated). One commonly overlooked problem is the bios settings for fan control. If the CPU or case fans are running too slow the system will alert you (this depends again on the bios and it's settings). It could be that the system is just simply alerting you to that fact, and will not post as a precautionary measure so you don't fry your system. You could try unplugging all your case fans (not the CPU one though), and try booting again.

yeah, if you get "beeep, beb beb beep beep" (say it out loud to yourself) it's mem or vid card.

Feb 3, 2006, 07:31 PM	#1
jeffro29 DriverHeaven Lover Join Date: Oct 2003 Location: Nebraska Posts: 109 Rep Power: 0	Computer won't post I was wondering if anybody could help me? I have a abit AV8 third eye with an 3500 amd64 processor and 1gb of corsair 3200C2 2226 timings and the video card is an X800XTPE all running on Windows XP Home Edtion. My problem is when i power on the system all you hear is the fans running and the system won't post all i hear is beeping. I've tested the memory, video card, power supply is a 485 watt enermax, in anouther system with an AMD 2600XP moblie processor and an abit NF7-S Rev 2.0 board and it all works fine. I don't under stand whats wrong!!!!!! does anybody have any ideas what could be wrong? __________________ A good stable OC is a good steal in speed.

Feb 3, 2006, 07:36 PM	Thread Starter #3
jeffro29 DriverHeaven Lover Join Date: Oct 2003 Location: Nebraska Posts: 109 Rep Power: 0	Yes i have i tried that in the other system also. Both systems had a fresh install of the OS on them. __________________ A good stable OC is a good steal in speed.

Feb 4, 2006, 08:19 PM	Thread Starter #5
jeffro29 DriverHeaven Lover Join Date: Oct 2003 Location: Nebraska Posts: 109 Rep Power: 0	I tried what you said and still nothing it does the same thing could it be the CPU is bad thats why it's not posting? __________________ A good stable OC is a good steal in speed.

Feb 4, 2006, 08:33 PM	#6
davidnsibs 9500pro Forever Join Date: Oct 2003 Location: Bath, UK Posts: 273 Rep Power: 0	hmm, what were you doing the last time it worked? same thing happened to me on my mobo when i was overclocking - i managed to fry my bios chip so needed to get a replacement. were you overclocking your fsb at all? __________________ Goodbye 9500pro, you've been a faithful servant through Half life, Deus Ex, Unreal 2, Max Payne 1+2, Nolf 1+2, CoD, Far Cry, Civ IV, F.E.A.R and many more

Feb 4, 2006, 09:24 PM	Thread Starter #7
jeffro29 DriverHeaven Lover Join Date: Oct 2003 Location: Nebraska Posts: 109 Rep Power: 0	It was overclocked not buy much thou it was like at 225fsb the processor was at 2475mhz from the factory setting of 2204 204fsb. How could it be the bios chip? __________________ A good stable OC is a good steal in speed.

Feb 4, 2006, 06:22 PM	#4
Dyre Straits HH Old Fuddy Duddy Join Date: May 2002 Location: Georgia, USA Posts: 14,196 Rep Power: 216 System Specs	Pull out the CMOS battery from the motherboard and disconnect the power cord from the system for a minute or two. This will restore the motherboard to its native state. Then replace the CMOS battery, hook up the power cord and see if it will boot. Sometimes this works if all that was the problem is bad settings or conflicts.

Feb 4, 2006, 09:32 PM	#8
davidnsibs 9500pro Forever Join Date: Oct 2003 Location: Bath, UK Posts: 273 Rep Power: 0	well, when i pushed my board to 195fsb (its 166fsb default) it crashed, and then wouldnt boot, although fans would spin (bit like yours) i did a bit of reading on forums and stuff and found similar issues with other people, not quite sure why, but pushing the fsb too high meant sometimes the bios would get corrupted irreversibly, i ordered another from asus for £5, put it in, and voila, a working pc again (i had treied wiping the bios with no effect previously). anyway, doubt its the case for you if it was only a small overclock, not too sure what it could be though ?? EDIT: When resetting the bios you normally have to move a jumper across (should say in the mobo manual) as well as removing the battery like Dyre Straits mentioned, would be worth trying that again __________________ Goodbye 9500pro, you've been a faithful servant through Half life, Deus Ex, Unreal 2, Max Payne 1+2, Nolf 1+2, CoD, Far Cry, Civ IV, F.E.A.R and many more Last edited by davidnsibs; Feb 4, 2006 at 11:57 PM.

Feb 5, 2006, 12:48 AM	#10
Tipstaff HardwareHeaven Extreme Member Join Date: Jul 2002 Location: Real capital of Canada: Torauna Posts: 6,773 Rep Power: 190 System Specs	It'd would help if you could post the beep codes. By that I mean the number of beeps, and length of beeps. For instance 1 long, and 2 short beeps can indicate a video error. This can mean that the video card isn't properly seated, isn't recognized by the motherboard, or is faulty. I should point out that beep codes can depend on the bios manufacturer though as each one uses different tones to indicate errors. The one I described would be a common one used with Award bioses which is what your motherboard uses (this tone is also used with AMI bioses too). So, again, it would be helpful if you could post the beep errors your getting. Also, you can take a look at THIS page which is for the Award bioses. For other bioses see the "Bios Beep Codes" menu on the right. Lastly, some common beep errors can occur because of bad keyboard/mouse, bad or improperly seated ram (try only one stick at a time), improperly seated video card (remove it, then reseat it), and overheating CPU (check that the heatsink is properly seated). One commonly overlooked problem is the bios settings for fan control. If the CPU or case fans are running too slow the system will alert you (this depends again on the bios and it's settings). It could be that the system is just simply alerting you to that fact, and will not post as a precautionary measure so you don't fry your system. You could try unplugging all your case fans (not the CPU one though), and try booting again. __________________ Portal: The Flash Version _________________________________ Brain: So, you sacked the cocky khaki Kicky Sack sock plucker? Mr. Sackett: The second cocky khaki Kicky Sack sock plucker I've sacked since the sixth sitting sheet slitter got sick. Last edited by Tipstaff; Feb 5, 2006 at 12:57 AM.