Computer Beep Codes: Complete BIOS Diagnostic Guide (2026)

Computer beep codes are your motherboard's POST (Power-On Self-Test) error signals: a specific pattern of beeps before the operating system loads maps to a specific hardware failure. Understanding them correctly means knowing which BIOS standard your board uses, because AMI, Award, Phoenix, and OEM systems all use different codes for the same number of beeps. This guide covers every major beep code standard, modern UEFI hex debug displays, and the real-world diagnostic workflow IT technicians actually follow — including the single most important fact most guides miss: on the majority of modern motherboards, you will not hear any beeps at all unless you plug in a separate PC speaker.

What Beep Codes Are (and Why Your Board Might Be Silent)

During power-on, the BIOS or UEFI firmware runs a Power-On Self-Test that checks core hardware before handing off to the operating system. If a critical component fails this test and no display output is available to show an error message, the firmware signals the failure through the PC speaker as a pattern of beeps. Each pattern maps to a specific hardware component or failure category.

The problem on modern hardware: PC speakers are not included in most cases or motherboard packages sold since approximately 2015. The 4-pin speaker header exists on nearly every motherboard, but nothing is connected to it by default. Beep codes fire into silence. If you are diagnosing a machine that won't POST and hear nothing, the absence of sound is not diagnostic information — it means you need to plug in a POST speaker (a small component available for under 5 USD) before beep codes become useful.

On mid-range and high-end motherboards from 2018 onward, a 2-digit hexadecimal POST code display has largely replaced audio beep codes as the primary diagnostic tool. These LED displays (ASUS Q-Code, MSI Dr. Debug, Gigabyte Debug LED, ASRock Dr. Debug) show real-time POST progress codes and are far more precise than beep patterns. The beep code sections below remain essential for older hardware, budget boards, and any machine without a debug display. Section 5 covers modern UEFI hex codes.

For a broader framework on hardware failure diagnosis, see our complete PC troubleshooting and hardware diagnostics guide.

How to Identify Your BIOS

Beep codes are not universal. The same number of beeps means completely different things across BIOS standards. Identifying your BIOS before looking up codes is not optional.

On the first POST screen: AMI BIOS displays "American Megatrends" or the AMI logo. Award BIOS displays a version string in the bottom-left corner ("Award Modular BIOS v6.00"). Phoenix BIOS displays the Phoenix logo or version. If the screen clears too fast, press Pause/Break to freeze it.

From the motherboard manual or box: The BIOS brand is always listed. For consumer motherboards from ASUS, Gigabyte, MSI, and ASRock purchased since 2008, the firmware is AMI-based UEFI — even if the interface looks different across brands.

For OEM systems: Dell, HP, and Lenovo use proprietary firmware that does not follow AMI/Award/Phoenix codes. Use the Dell, HP, or Lenovo sections below directly.

AMI BIOS Beep Codes

AMI (American Megatrends) is the dominant firmware on consumer and business motherboards. The codes below apply to classic AMI BIOS and AMI UEFI firmware.

Critical accuracy note: One beep in AMI BIOS means a DRAM refresh failure — it does not mean POST passed successfully. The "one beep = all clear" behavior belongs to Phoenix BIOS. This is one of the most widely repeated errors in online beep code guides. In most AMI implementations, a successful POST produces no beep.

Beep Pattern	Meaning	Component to Check
1 short	DRAM refresh timer error	RAM — reseat or replace
2 short	Memory parity circuit failure	RAM — reseat, test individually
3 short	Base 64KB RAM read/write failure	RAM — most common AMI code
4 short	Motherboard timer failure	Motherboard or expansion card
5 short	CPU / processor error	CPU failure or unseated CPU
6 short	Gate A20 / keyboard controller failure	Keyboard controller or motherboard
7 short	Virtual mode exception error	CPU or motherboard failure
8 short	Display memory read/write failure	GPU / video card
9 short	BIOS ROM checksum failure	BIOS chip corruption
10 short	CMOS shutdown register error	Motherboard / southbridge
11 short	L2 cache memory failure	CPU or motherboard
1 long + 3 short	Conventional/extended memory failure	RAM beyond base 64KB
1 long + 8 short	Video adapter test failure	GPU not detected or failed
Continuous	Power supply or RAM completely unseated	PSU or RAM

The three codes you will encounter most often in real-world diagnostics: 3 short (RAM), 5 short (CPU), and 8 short or 1 long + 8 short (GPU/video).

Award BIOS Beep Codes

Award BIOS was acquired by Phoenix Technologies in 1998. Boards sold under the Award name retain Award-style codes; do not assume Phoenix grouped codes apply to a board labeled "Award BIOS."

Award officially documents only a small number of codes. The 1 long + 2 short pattern is by far the most encountered in practice.

Beep Pattern	Meaning
1 short	POST passed (successful boot)
2 short	Non-fatal CMOS error — look for on-screen message
1 long + 1 short	RAM or motherboard failure
1 long + 2 short	Video card failure — GPU not seated or failed
1 long + 3 short	GPU failure (alternate)
1 long + 9 short	BIOS ROM checksum error
Continuous long	RAM not correctly installed
Repeating short	Power supply failure

If you are getting 1 long + 2 short on an Award system, reseat the GPU first. If a second GPU is available, swap it. On systems with integrated graphics, remove the discrete GPU and connect to the motherboard output.

Phoenix BIOS Beep Codes

Phoenix BIOS uses grouped patterns separated by pauses. A "1-3-3" code means one beep, pause, three beeps, pause, three beeps — not seven consecutive beeps. This distinction is critical: Phoenix codes written as X-X-X notation are completely different from the consecutive counts used by AMI.

Pattern	Meaning
1-1-3	CMOS write/read failure
1-1-4	BIOS ROM checksum failure
1-2-1	Programmable interval timer failure
1-2-2	DMA initialization failure
1-2-3	DMA page register read/write failure
1-3-1	RAM refresh verification failure
1-3-3	First 64KB RAM chip/data line failure
1-3-4	First 64KB RAM odd/even logic failure
2-x-x	First 64KB RAM failure (various sub-tests)
3-1-1	Slave DMA register failure
3-3-4	Screen initialization / video memory failure
3-4-1	Screen retrace test failure
4-2-1	Timer tick interrupt failure
4-2-3	Gate A20 failure
4-2-4	Unexpected interrupt in protected mode
4-3-1	RAM test failure above address 0FFFFh
4-4-3	Math coprocessor failure

For Phoenix 4.x, the format expands to 4 groups (X-X-X-X). The code 1-3-3-1 in 4-group Phoenix notation means extended memory failure and is commonly seen on Lenovo ThinkCentre machines.

Dell, HP, and Lenovo Beep Codes

OEM systems use proprietary codes that share no relationship with AMI/Award/Phoenix. Citing a generic beep code table for a Dell or HP system will give you wrong results.

Dell (OptiPlex, Precision, Vostro, XPS)

On post-2012 Dell desktops, the primary beep code is 1-3-2 (one beep, three beeps, two beeps) indicating memory failure. This is the code IT technicians encounter most in fleet support — it almost always means a DIMM is unseated or has failed. Reseat first; replace if reseating does not resolve it.

On newer OptiPlex models (7010+) and XPS systems, Dell replaced audio codes with amber/white LED blink sequences on the power button. The number of amber blinks indicates the failure category; white blinks indicate the specific fault. Always check the model-specific support page at support.dell.com — a single universal Dell beep code table does not exist reliably across generations.

HP (EliteDesk, ProDesk, EliteBook, Pavilion)

HP's modern business desktops (2013+) use a combined beep + power LED blink system. The number of beeps indicates the failure category (example: 2 beeps = memory). The number of power LED blinks following the beeps indicates the specific fault within that category. Beep sequences repeat 5 times then stop; LED blinks continue until power-off.

Older HP systems with simple beep codes: 1 short + 1 long = memory failure, 1 long + 2 short = video error, 3 long = keyboard error. Model-specific codes are documented at HP's support site — a generic HP table is unreliable across product generations.

Lenovo (ThinkCentre, ThinkPad)

ThinkCentre desktops use beep codes; ThinkPad laptops rely more heavily on on-screen error messages ("Error 0271: Date and time error", "Error 0200: Failure Fixed Disk"). The most common ThinkCentre POST failure code is 1-3-3-1 (Phoenix 4-group pattern) indicating memory not detected or failed — reseat DIMMs as the first step.

Modern UEFI Debug Codes: Q-Code, Dr. Debug, EZ Debug

On modern consumer and enthusiast motherboards, the 2-digit hexadecimal POST display is the primary diagnostic tool. These displays follow the UEFI Platform Initialization (PI) specification, meaning many codes are shared across ASUS, MSI, Gigabyte, and ASRock boards. Vendor-specific codes exist at the low and high ends of the hex range.

The most important codes to know:

Code	Stage	Meaning	Most Likely Cause
00	Early	CPU not detected or microcode failure	CPU not seated, dead CPU
0d	CPU	Microcode update failed	CPU incompatible with current BIOS
55	Memory	Memory not installed or not detected	RAM not seated, wrong slot, incompatible RAM
C0	CPU/Memory	CPU or memory initialization error	RAM failure, CPU issue
C1	Memory	Memory initialization: SPD data not loading	RAM failure or incompatible kit
62	PCIe	PCIe enumeration	GPU-related, usually transient
A2	Boot	IDE/storage detect	Disconnected drive, failed NVMe, wrong boot order
A9	Boot	SATA enumeration in progress	Normal transitional code
D6	Boot	No console output device found	GPU not seated, GPU dead, PCIe issue
D7	Boot	No console input device	Keyboard controller failure
FF	Done	POST complete, handing to bootloader	Successful POST

Two codes that cause the most confusion:

A2 means "IDE Detect" in the UEFI PI specification — the board is searching for storage devices. A machine stuck at A2 has completed CPU and RAM initialization successfully; the problem is with storage (disconnected SATA cable, failed NVMe drive, mechanical drive slow to respond). It does not indicate a GPU problem. This is one of the most frequently misidentified codes online.

D6 means "No Console Output Device" — the UEFI found no GPU to display output. Causes: GPU fully unseated, dead GPU, PCIe slot damage, or (on systems with integrated graphics) iGPU disabled in BIOS with no discrete GPU present. D6, not A2, is the code that points to a GPU problem.

ASUS Q-LED banks: Many ASUS boards include four LED indicators labeled CPU, DRAM, VGA, and BOOT. The LED that remains lit after attempted POST indicates the failing component category. A stuck DRAM LED means RAM initialization failed. A stuck VGA LED means GPU initialization failed. These LEDs are faster to read than the hex display for initial triage.

MSI Dr. Debug, Gigabyte Debug LED, ASRock Dr. Debug follow the same UEFI PI codes. Gigabyte-specific note: code 00 briefly appearing at power-on before transitioning is normal on some boards; only persistent 00 indicates a CPU issue.

"Computer Beeps But No Display" — Step-by-Step Fix

This is the most common POST failure scenario: the machine powers on, produces beep(s) or a debug code, and the monitor shows nothing. Work through these steps in order.

1. Verify the monitor and cable first. Test the monitor with a phone or laptop. Try a different cable. Confirm the monitor is set to the correct input source. This resolves a surprising number of "no display" calls.

2. Check the CPU power connector. The 8-pin (or 4+4-pin) CPU power connector on the top-left of the motherboard is the single most commonly missed connection in new builds and reassembly jobs. A machine can power on with only the 24-pin ATX connector, but it will never POST. Confirm this connector is fully seated.

3. Reseat the GPU. Remove the GPU, clear dust from the PCIe slot, reseat firmly until the latch clicks. On systems with integrated graphics, remove the discrete GPU entirely and connect the monitor to the motherboard video output.

4. Reseat RAM. Remove all sticks. Boot with a single stick in the primary slot (check your motherboard manual — it is usually the slot labeled A2 or DIMM_A2, not the slot closest to the CPU). Test each stick individually. If the board has Q-LED indicators, watch the DRAM LED.

5. Clear CMOS. Remove the CMOS battery for 30 seconds (CR2032 coin cell, typically near the PCIe slot), or use the CLRTCMOS jumper if present. This resets BIOS settings to defaults and resolves failures caused by a corrupted overclock profile or incompatible XMP setting.

6. Strip to minimum components. Remove all drives, USB devices, and extra RAM. Boot with only CPU, one RAM stick, and PSU. If the board has onboard video, remove the GPU too. A machine that POSTs in this configuration has a problem with one of the removed components.

7. Check for BIOS compatibility. If a CPU was recently upgraded, the current BIOS version may not support it. Some boards support BIOS recovery without a working CPU (ASUS BIOS Flashback, MSI Flash BIOS Button, Gigabyte Q-Flash Plus) — these allow flashing from USB using only PSU power.

When Beep Codes Are Misleading

Beep codes identify the component class that failed during POST — but they do not always identify the actual defective component. Three scenarios catch technicians regularly.

RAM beep code caused by a bent CPU pin. The memory controller lives inside the CPU on modern Intel and AMD processors. If a CPU socket pin is bent or damaged, the memory controller cannot initialize — which triggers a RAM failure code. Before condemning a RAM kit, inspect the CPU socket (or CPU bottom, on AMD platforms) under magnification. This is especially important after any CPU removal or installation.

GPU power draw triggering spurious memory codes. A high-end GPU that draws excessive current during PCIe initialization can cause voltage instability that the POST firmware interprets as a memory error. If you receive a memory beep code on a system with a high-TDP GPU (RTX 4090, RTX 3090, RX 7900 XTX), test by temporarily installing a lower-power GPU. Also confirm the PCIe power cable is fully seated at both ends.

CMOS battery failure causing recurring startup beeps. The CR2032 battery on the motherboard maintains BIOS settings and the real-time clock when the system is unplugged. A dead battery (typically after 3 to 7 years) causes the BIOS to report a checksum error on every boot, often accompanied by a beep and a "CMOS checksum error" or "Date/Time not set" message. This is extremely common in business PC fleets. A CR2032 cell costs under 5 USD and resolves the issue in two minutes. It is one of the most overlooked maintenance items on machines in this age range.

For a deeper look at the RAM failure patterns that precede these POST errors, our guide to RAM failure signs and how to test memory covers the full diagnostic process including MemTest86 interpretation.

From POST Failure to Proactive Monitoring

A machine that fails POST rarely fails without warning. Beep codes are hardware in crisis mode — the firmware cannot initialize a component that was already degrading. In the weeks before a POST failure, the symptoms are there in the sensor data: RAM voltage instability, rising memory error counts under load, temperature spikes that cause the system to cut power before completing initialization, or a drive going offline intermittently.

The difference between catching a problem at the sensor stage versus the POST failure stage is the difference between a scheduled maintenance window and an emergency onsite visit. Modern hardware monitoring agents read the sensor channels that surface these pre-failure signals — RAM voltage, memory error event logs, CPU thermal behavior — and generate alerts before the machine reaches the point of beeping at you.

Our guide to hardware monitoring alert thresholds covers the specific sensor values that indicate a machine is approaching failure, well before it stops booting.

Frequently Asked Questions

What does it mean when my computer beeps on startup?

A beep on startup means your motherboard's POST (Power-On Self-Test) detected a hardware failure before it could load the operating system. The number and pattern of beeps indicates which component failed, but the code table varies by BIOS brand. Identify your BIOS manufacturer (AMI, Award, Phoenix, or the OEM brand for Dell/HP/Lenovo) before looking up the specific pattern.

Why is my computer beeping 3 times?

Three short beeps in AMI BIOS indicates a base 64KB RAM read/write failure — this is one of the most common beep codes in the field. Start by reseating all RAM sticks, then test with a single stick in the primary slot. If three beeps persist with each stick individually, the RAM kit has likely failed. Note: three beeps can also trace to a bent CPU socket pin that prevents the memory controller from initializing, so inspect the socket if RAM swaps do not resolve it.

My computer beeps but the screen is black — what do I do?

Work through these in order: confirm the monitor and cable are working (test with another device), check that the 8-pin CPU power connector is seated, reseat the GPU and try with onboard video if available, reseat RAM with a single stick in the primary slot, clear CMOS. If the board has a debug LED display, check that code first — D6 means no GPU detected, 55 or C0 means RAM initialization failed, A2 means storage is not found.

Do modern computers still use beep codes?

Modern UEFI firmware still generates beep codes, but most current boards ship without a PC speaker installed. The speaker header exists but nothing is plugged into it, so beeps fire silently. Mid-range and enthusiast boards from roughly 2018 onward have replaced audio beep codes with 2-digit hexadecimal POST code displays (ASUS Q-Code, MSI Dr. Debug, Gigabyte Debug LED) that are more precise and always visible. Budget boards and many OEM desktops still rely on beep codes as the primary fallback signal.

What does ASUS Q-Code A2 mean?

A2 in the UEFI PI specification means "IDE Detect" — the system has successfully completed CPU and RAM initialization and is now searching for storage devices. A machine stuck at A2 has a storage problem: a disconnected SATA or NVMe cable, a failed drive, or a slow-to-respond mechanical hard disk. It does not indicate a GPU problem. The GPU-related code is D6 ("No Console Output Device"). This distinction is widely misreported in online forums.

Why isn't my PC making any beep sounds during POST?

Almost certainly because no PC speaker is connected to the motherboard's speaker header. Most modern cases do not include a POST speaker, and most motherboard packages do not either. The 4-pin speaker header (labeled SPEAKER on the board) is present but empty. Purchase a motherboard speaker — a small component for under 5 USD — and connect it to the header. Without it, beep codes fire into silence and you will need to rely on the debug LED display (if present) or visual inspection to diagnose POST failures.