When was the last time it happened, and what did you do to try resolving it?
Generally, when there's no beep, it's either, your power supply's busted, or it's the system board. If you need to narrow down the culprit, you would have to remove every removable component, (RAM, Video Card, Sound Card, PCI Cards) except the coin type battery and the power supply connector, and at least, the hard-drive.
Remember, use an Anti-static wrist-guard to protect you and your computer from static electricity.
Gradually, reseat one component at a time, while booting the computer and listening for beeps until you can determine which component it is.
If there are still no beeps, have a spare power supply unit handy and install it. Sometimes, the Power Supply can only make fans running, without having enough juice to power-up the whole system. If after changing power supplies, and still no beeps, try changing the CMOS coin type battery (CR32), it could be that your CMOS has no power from the battery, thus couldn't run the puter properly.
If all still fail, consider buying a new motherboard. That's the last option you'll have. I know it hurts, but that's just it.
2007-01-30 13:00:16
·
answer #1
·
answered by KenMikaze 3
·
0⤊
0⤋
Assuming the PC speaker is plugged in, no BIOS beep on power up is a fried BIOS or a short somewhere. You sound like you have some idea whats up, so I'll just simply suggest you make sure the memory and the video card are firmly inserted on the motherboard, and check the hard drive and cd-rom connections to the motherboard. I find that the first generation SATA cables will fall off the drive or the board pretty easily...
I think, but don't know, that blown memory chips would result in a BIOS error. I know I've been memory parity errors before, the point being that if the error is displayed on the monitor, the BIOS is working. A bad video card would cause no video BUT the bios would give you one beep unless the card was missing or not inserted properly which would cause a series of beeps (depends on BIOS).
2007-01-30 11:50:37
·
answer #2
·
answered by dug 4
·
1⤊
1⤋
That's a tough one. It could be your memory or motherboard. Have you tried removing a memory chip and restarting?
2007-01-30 11:46:53
·
answer #3
·
answered by Colin M 3
·
0⤊
0⤋