Desktop

Ask something
Discussion Locked

Troubleshooting home built PC

0 helpful
7 replies

by samcorp

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a PC that I have built and is now giving me fits. It ran great for about 6 months and now I can't even get it to boot. I have an EPOX 8K7A+ motherboard, Athlon Thunderbird 1.333Ghz processor, Crucial 256MB DDR memory. When I power up I get ononboard BIOS code of C1 which according to EPOX is a memory issue. However, I have gone to Crucial and replaced the memory. Then after talking with EPOX I replaced the BIOS chip. Then after replacing the BIOS chip I replaced the motherboard. Next I went to AMD and they replaced my processor. It worked for about a day or two. Now it just gives me continuous beeps on boot up. Could the power supply be causing these problems? I can yank EVERYTHING off the M/B (video, NIC, HD) and I still get the same error code. I am totally stumped. Any suggestions?

7 replies

by thechas

It sounds like your video card has gone now too!

From the list of problems, this sounds like ESD dammage to me.

If you did not use proper ESD (static) precautions when assembling, and re-assembling this system, that is at the root of your problems.

If you did use a good ground strap, and an ESD mat when assembling the system, then, I suspect a voltage surge is the root cause.
I would have a thourough bench test run on the power supply at both light, and full loads.

Chas

by dmiles

A continous beep code can mean the Power Supply or Motherboard failure

If you have a volt meter available check the voltage on the power supply to see if you can get a reading in the range of 12V,then check power supply has the ample amount of wattage to supply the system to run

Power supply problems will cause any number of the above mention and very difficult to determine,it may very well be the cause,also make sure that you have connectors to the motherboard secured properly

by kentward

I had this exact problem on a Soyo MBoard. It turned out to be the V.92 modem. I had to step down to a V.90 and presto the problem went away. Yes I moved PCI slots with the V.92 to no avail, but a v.90 in the same slot and everything worked. I put the V.92 in a Tyan MBoard and it works fine, so it was a compatibility issue.

This discussion is closed to new replies.