Step-By-Step: Deciphering BIOS beep codes

Each time a user turns on his or her computer, the BIOS gathers information about the major system components and performs a special test called the Power On Self Test (POST) to make sure that each component is functioning correctly. If the test identifies a hardware problem, the BIOS will display an error message on the monitor. But, if the failure occurred before the BIOS could access the video card, the BIOS will issue special beep codes to alert the user to the problem.

In this article, I’ll take a detailed look at the beeps that are issued by various BIOS manufacturers, and I’ll provide you with a resource for more detailed information. Understanding these noises will allow you to troubleshoot a multitude of hardware problems.

Annoying noises, flashing lights
During a POST session, your computer has several ways to communicate: Either through flashing indicator lights, the computer’s speaker, or via the monitor. Since the monitor is not initialized until later in the process, early failures are communicated by red or absent status lights, such as the power and hard drive activity lights, or by sound in the form of beeps.

POST diagnostic cards

Another option is to purchase a POST diagnostic card to intercept POST errors at their source via the ISA or PCI bus. Cards are available for either bus and typically contain one or two digital readouts that present the codes, as well as LEDs for monitoring the power supply. Since POST codes are more numerous than beep codes (there may be 10 beep codes to 256 POST codes), a diagnostic card can help you track the progress of the POST and see more detail about what caused a failure or warning.

An ISA card is preferred, as it’s possible that a PCI card may not report all the POST codes. Because the ISA bus is initialized first, the PCI bus only receives the codes generated after the ISA bus is initialized. In addition, ISA busses connect to the South Bridge chip, so damaged motherboards may not be able to send codes to the PCI bus at all.

You can obtain more information on POST diagnostic cards from manufacturers such as Xetal Systems Inc., makers of POSTmortem; Microsystems Development Technologies Inc.’s Post Code Master, or by running a Web search.

Heard any good beeps lately?
Naturally, if the speaker is damaged or disconnected, you’ll have no way of knowing what ails your hardware without a diagnostic card. At the conclusion of a successful POST, the computer should beep once or twice. These beeps inform you that your hardware is in good working order. If you don’t hear this “all’s well” beep, here are a few things to check:

Are external speakers connected? On many computers, the computer speaker is disabled when a jack is connected.
Is the volume too low? Use the function keys indicated by the manufacturer to increase the volume.
Did someone disconnect the speaker? People do this occasionally because the beeps bother them. Reconnect the leads to the motherboard jumpers.
Is the onboard speaker disabled in the BIOS? Re-enable the speaker in the BIOS setup program. Note: It’s also a good idea to include a small speaker mounted to a motherboard with some standard leads as part of your troubleshooting kit.

To create unique error messages, codes emit combinations of long and short beeps, similar to Morse code. Instead of letters, however, each unique sequence indicates a different problem with components. As you might have guessed, in contrast to a universal standard such as Morse code, each BIOS manufacturer creates its own beep sequences.

POST time
Below are audible codes for several common BIOSs that I obtained from The BIOS Companion. The Companion excels in presenting almost every BIOS setting that can be configured. It also contains tables of POST codes. It can be purchased online (as a PDF file) for $15 or printed for $49.95, or it can be acquired as part of a larger set, called The PC Engineer’s Reference Book. You’ll want to check this out if you support many different PC types, including legacy equipment. For more information on these and other reference books, see Electrocution Technical Publishers.

American Megatrends Inc. BIOS
Standard beep codes for computers using American Megatrends Inc. (AMI) BIOSs are listed in Table A.

Table A

American Megatrends Inc. BIOS beep codes

Award BIOS
Award BIOSs only have one beep code: One long beep, followed by two short beeps, indicates that the BIOS is unable to initialize the video screen.

Compaq BIOS
Standard beep codes for Compaq computers with no text and error message are shown in Table B.

Table B

Other Compaq beeps are associated with specific text messages on the video screen.

Dell BIOS
Beep codes for Dell computers (Phoenix BIOS) are listed in Table C. (All are short beeps separated by pauses.)

Table C

To view screen messages that accompany beep codes, make sure the Phoenix QuietBoot feature is disabled by pressing [Esc] during boot. This will display POST messages.

IBM beep codes
IBM personal computers (Thinkpads and Desktops) use a Phoenix-based BIOS. An extensive amount of information can be gleaned from the beep codes of Phoenix BIOSs. Since 1994, Phoenix has used a four-part system: four bursts of short beeps separated by pauses. For example, in Table D below, a value such as 4-2-3-1 (shutdown error), means four short beeps, pause, two short beeps, pause, three short beeps, pause, one short beep. While the codes in the table below will apply in general, to be sure, always check the specification for your particular model. The beep codes for IBM computers are listed in Table D. (All are short beeps separated by pauses.)
Table D

Number of beeps	Description
1-1-1-3	Verify real mode
1-1-2-1	Get CPU type
1-1-2-3	Initialize system hardware
1-1-3-1	Initialize chipset registers with initial values
1-1-3-2	Set in POST flag
1-1-3-3	Initialize CPU registers
1-1-4-1	Initialize cache to initial values
1-1-4-3	Initialize I/O
1-2-1-1	Initialize power management
1-2-1-2	Load alternative registers with initial POST values
1-2-1-3	Jump to UserPatch0
1-2-2-1	Initialize timer initialization
1-2-3-1	8254 timer initialization
1-2-3-3	8237 DMA controller initialization
1-2-4-1	Reset Programmable Interrupt Controller
1-3-1-1	Test DRAM refresh
1-3-1-3	Test 8742 Keyboard Controller
1-3-2-1	Set ES segment register to 4GB
1-3-3-1	Autosize DRAM
1-3-3-3	Clear 512K base memory
1-3-4-1	Test 512K base address lines
1-3-4-3	Test 51K base memory
1-4-1-3	Test CPU bus-clock frequency
1-4-2-1	CMOS RAM read/write failure (This commonly indicates a problem on the ISA bus such as a card not seated.)
1-4-2-4	Reinitialize the chipset
1-4-3-1	Shadow system BIOS ROM
1-4-3-2	Reinitialize the cache
1-4-3-3	Autosize the cache
1-4-4-1	Configure advanced chipset registers
1-4-4-2	Load alternate registers with CMOS values
2-1-1-1	Set initial CPU speed
2-1-1-3	Initialize interrupt vectors
2-1-2-1	Initialize BIOS interrupts
2-1-2-3	Check ROM copyright notice
2-1-2-4	Initialize manager for PCI Options ROMs
2-1-3-1	Check video configuration against CMOS
2-1-3-2	Initialize PCI bus and devices
2-1-3-3	Initialize all video adapters in system
2-1-4-1	Shadow video BIOS ROM
2-1-4-3	Display copyright notice
2-2-1-1	Display CPU type and speed
2-2-1-3	Test keyboard
2-2-2-1	Set key click if enabled
2-2-2-3	Enable keyboard
2-2-3-1	Test for unexpected interrupts
2-2-3-3	Display prompt “Press F2 to enter setup”
2-2-4-1	Test RAM between 512K and 640K
2-3-1-1	Test expanded memory
2-3-1-3	Test extended memory address lines
2-3-2-1	Jump to UserPatch1
2-3-2-3	Enable external and CPU caches
2-3-2-3	Configure advanced cache registers
2-3-3-1	Enable external and CPU caches
2-3-3-2	Initialize SMI handler
2-3-3-3	Display external cache size
2-3-4-1	Display shadow message
2-3-4-3	Display nondisposable segments
2-4-1-1	Display error messages
2-4-1-3	Check for configuration errors
2-4-2-1	Test real-time clock
2-4-2-3	Check for keyboard errors
2-4-4-1	Set up hardware interrupt vectors
2-4-4-3	Test coprocessor if present
3-1-1-1	Disable onboard I/O ports
3-1-1-3	Detect and install external RS232 ports
3-1-2-1	Detect and install external parallel ports
3-1-2-3	Reinitialize onboard I/O ports
3-1-3-1	Initialize BIOS Data Area
3-1-3-3	Initialize Extended BIOS Data Area
3-1-4-1	Initialize floppy controller
3-2-1-1	Initialize hard disk controller
3-2-1-2	Initialize local bus hard disk controller
3-2-1-3	Jump to UserPatch2
3-2-2-1	Disable A20 address line
3-2-2-3	Clear huge ES segment register
3-2-3-1	Search for option ROMs
3-2-3-3	Shadow option ROMs
3-2-4-1	Set up power management
3-2-4-3	Enable hardware interrupts
3-3-1-1	Set time of day
3-3-1-3	Check key lock
3-3-3-1	Erase F2 prompt
3-3-3-3	Scan for F2 keystroke
3-3-4-1	Enter SETUP
3-3-4-3	Clear in-POST flag
3-4-1-1	Check for errors
3-4-1-3	POST done—prepare to boot operating system
3-4-2-1	One beep
3-4-2-3	Check password (optional)
3-4-3-1	Clear global descriptor table
3-4-4-1	Clear parity checkers
3-4-4-3	Check virus and backup reminders
4-1-1-1	Try to boot with INT 19
4-2-1-1	Interrupt handler error
4-2-1-3	Unknown interrupt error
4-2-2-1	Pending interrupt error
4-2-2-3	Initialize option ROM error
4-2-3-1	Shutdown error
4-2-3-3	Extended Block Move
4-2-4-1	Shutdown 10 error
4-2-4-3	Keyboard Controller failure (most likely problem is with RAM or cache unless no video is present)
4-3-1-3	Initialize the chipset
4-3-1-4	Initialize refresh counter
4-3-2-1	Check for Forced Flash
4-3-2-2	BIOS ROM is OK
4-3-2-4	Do a complete RAM test
4-3-3-1	Do OEM initialization
4-3-3-2	Initialize interrupt controller
4-3-3-3	Read in bootstrap code
4-3-3-4	Initialize all vectors
4-3-4-2	Initialize the boot device
4-3-4-3	Boot code was read OK

Keep in mind that IBM-labeled hardware contains components made by OEMs. These companies may modify their versions of the Phoenix BIOS.

Do they really help?
If a system error is occurring before video initialization, interpreting the BIOS beep codes is your last line of defense when something is troubling your system. All you need to do is listen closely to the sequence of beeps for your specific BIOS and simply look up the corresponding error description. Then, you can focus your troubleshooting efforts on that particular problem instead of wasting time with guesswork.

Step-By-Step: Deciphering BIOS beep codes

michaeljackman