Phoenix BIOS beep codes

description

Beep sequence What's Wrong
1-1-3 Your computer can't read the configuration information stored in the CMOS. Replace the motherboard.
1-1-4 Your BIOS needs to be replaced.
1-2-1 You have a bad timer chip on the motherboard; you need a new motherboard.
1-2-2 The motherboard is bad.
1-2-3 The motherboard is bad.
1-3-1 The motherboard is bad.
1-3-3 Same as AMI BIOS 2 beeps. Replace the motherboard.
1-3-4 The motherboard is bad.
1-4-1 The motherboard is bad.
1-4-2 Some of your memory is bad.
2-_-_ Any combination of beeps after two means that some of your memory is bad, and unless you want to get real technical, you should probably have the guys in the lab coats test the memory for you. Take your computer to the shop.
3-1-_ One of the chips on your motherboard is broken. You'll likely need to get another board.
3-2-4 Same as AMI BIOS 6 beeps: keyboard controller failure.
3-3-4 Your computer can't find the video card. Is it there? If so, try swapping it with another one and see if it works.
3-4-_ Your video card isn't working. You'll need to replace it.
4-2-1 There's a bad chip on the motherboard. You need to buy another board.
4-2-2 First, check the keyboard for problems. If there are none, you have a bad motherboard.
4-2-3 See 4-2-2.
4-2-4 One of the cards is bad. Try taking out the cards one by one to isolate the culprit. Replace the bad one. The last possibility is to buy another motherboard.
4-3-1 Replace the motherboard.
4-3-2 See 4-3-1
4-3-3 See 4-3-1
4-3-4 Time of day clock failure. Try running the setup program that comes with the computer, and check the date and time. If that doesn't work, replace the battery. If that doesn't work, replace the power supply. You may have to replace the motherboard, but that is rare.
4-4-1 Your serial ports are acting up. Reseat or replace the I/O card. If the I/O is on the motherboard itself, disable it with a jumper (consult your manual to know which one) and then add an I/O card.
4-4-2 See 4-4-1
4-4-3 Your math coprocessor is malfunctioning. Run a test program to double-check it. If it is indeed bad, disable or replace it. Disabling is fine, because you probably don't need it anyway.