Read the motherboard debug LED first, then reduce the machine to one stick of memory and the parts POST requires. Check every CPU power connector, clear CMOS, and verify the installed BIOS supports the installed processor. A light that stays on is a starting point, not a verdict, and swapping parts before the board identifies the stage wastes money.
At a glance
- Class
- PC Hardware
Provenance
- Nov 16, 2026Published
A no-POST machine is the most misdiagnosed failure in PC building, because the symptom is so unhelpful. The fans spin, the lights glow, and nothing appears. People respond by buying a power supply, then memory, then a motherboard, and often end up with a working machine and three spare parts.
The board is already trying to tell you where it stopped. You just have to read the indicator and then work the checks in an order that removes the cheap possibilities before the expensive ones.
No POST is a specific failure, not a general one
I keep four states separate, because they lead to completely different pages:
- No power: nothing spins, nothing lights.
- No POST: the machine powers on but never completes its firmware hardware check.
- No boot: POST completed but no operating system loads.
- No video: the machine boots but the display shows nothing.
This page is the second one. If nothing happens at all, the computer won’t turn on guide is the right starting point, because the checks split almost immediately. If the machine reaches Windows and the screen is blank, that is a display fault and the no signal guide covers it.
A useful confirmation: connect a monitor to the output the machine should be using and watch for the firmware logo. No logo, no beep, no handoff, and the board’s own indicator lit is a POST failure. That is the machine telling you which stage it could not clear.
Read the board’s own diagnostic light
Most modern boards carry four status LEDs for the stages that matter. ASUS calls them Q-LEDs, and the Q-LED troubleshooting article names them plainly: CPU, DRAM, VGA, BOOT. A light that stays lit means that stage did not clear.
The board manual for the ROG STRIX B650-A Gaming WiFi adds the colour coding, which is handy when the inside of the case is dark and the labels are small:
| LED | Colour on this board | What ASUS says a lit LED means |
|---|---|---|
| CPU | Red | No CPU detected, or a CPU fault |
| DRAM | Yellow | No memory detected, or a memory fault |
| VGA | White | No graphics card detected, or a graphics fault |
| BOOT | Yellow-green | No boot device detected, or a boot device fault |
One sentence in that manual matters more than the table: the LEDs “provide the most probable cause of an error code as a starting point for troubleshooting,” and “the actual cause may vary from case to case.” A lit CPU LED is a direction, not a replacement order. The processor is one of the last things I suspect, not the first.
The same board has a second indicator worth knowing about. A separate LED marked PLUG_8PIN_PWR lights up when the 8-pin CPU power plug is not connected. If that one is on, you have found the problem without opening anything else.
Build the minimum configuration first
Once you know which stage is failing, reduce the machine to the parts POST actually requires. ASUS’s No Power / No Boot / No Display article walks through this in order: power supply, CPU, memory, graphics card, monitor, then minimal components, Clear CMOS, and the Q-LEDs again.
The minimum set is the board, the CPU with its cooler installed and connected, one memory module in the slot the manual specifies for single-module operation, and power. Remove the graphics card if the processor has integrated graphics, and disconnect every drive and every external device.
Two rules I do not bend. The CPU cooler stays installed and powered, because POST will not complete with a processor that has no thermal path. And you change one thing at a time, so that when the symptom changes you know which change did it.
Before any of that, count the power connectors. ASUS’s article calls out that some boards carry an 8-pin EATX12V_1, a 4-pin EATX12V_2 and the 24-pin EATXPWR, and recommends connecting all of them. A missing auxiliary CPU connector produces a machine that lights up and never POSTs, and it is one of the most common causes I see.
Ordered checks, cheapest first
Work down the list and stop when the symptom changes.
- Confirm the state. Firmware logo on screen or no? Listen for a beep, watch the keyboard lights, and note which LED stays lit. Write it down before you touch anything.
- Check every power connector. 24-pin, 8-pin CPU, and the 4-pin auxiliary if the board has one. Seat both ends on a modular supply until the latches click.
- Clear CMOS exactly as the manual describes. A settings problem, particularly after a memory change or a failed overclock, can stop POST with every part healthy.
- Reduce to one memory module. Use the slot named for single-module operation in the manual, then rotate modules and slots one change at a time. If a module is not on the board’s qualified list, that is a suspect rather than proof.
- Remove the graphics card and use integrated video. A card that is not seated, or a slot that is not receiving power, can hold the VGA stage indefinitely.
- Recheck CPU power and cooler mounting. A cooler that is not tightened evenly, or a CPU power connector that is only half seated, will stop the machine before any other test matters.
- Reseat the processor only after the above. ASUS’s Q-LED article lists reinstalling the CPU, checking for dirt or damaged pins, and trying another processor as the CPU-side steps. Bent pins are easy to create and hard to fix, so this is not a first move.
- Verify the firmware supports the processor. Check the CPU support list and required BIOS version for your exact board. If the board will not start at all, USB BIOS FlashBack can reflash from a USB drive without a processor installed; ASUS’s FlashBack article specifies a USB drive of at least 1 GB in FAT16 or FAT32 with an MBR partition.
- Substitute a power supply only with its own cable set. Corsair’s guidance is blunt: “never try to use one brand’s cables with another brand’s PSU,” because each maker wires the supply end differently. A borrowed supply with borrowed cables is not a controlled test.
- Try the board outside the case. A misplaced standoff or loose metal can short the board and stop POST. This is the last free check, and it is a deliberate one.
If the machine repeatedly shuts down rather than sitting at a lit LED, the fault is different. Corsair’s PSU protections explainer describes short-circuit protection tripping when the 3.3 V, 5 V, or 12 V rails short to another rail or to ground, and over-power protection tripping between 115% and 135% of rated output. A supply that trips and resets is protecting itself from something. Stop provoking it and find the short.
What survives a reboot, and what does not
This distinction saves a lot of wasted effort, because most of the evidence in a no-POST diagnosis is live and disappears the moment you power down.
Does not survive a reboot: the lit LED itself, a beep pattern, and the exact moment the machine stopped. These are live states. If you power off to reseat a cable, the evidence is gone. Photograph the LED pattern or write it down first.
Survives a reboot: the installed BIOS version, the memory configuration you left in place, a jumper or Clear CMOS result, and anything you saved to a file or a note. That is why I keep a sheet of paper next to the machine and record each change with the symptom that followed it.
Survives a reboot and is also a hardware fact: whether the PLUG_8PIN_PWR LED is lit with the supply connected and switched on. That is a wiring state, not a transient reading.
The practical upshot: change one thing, note the LED, power down, change the next thing. The note is the only part of that loop that persists.
When to stop
Stop when the free checks are exhausted, because the next step stops being free.
- A pop, a spark, or a burning smell. Unplug the machine and leave it off. Corsair’s article explains what the supply is protecting against; it does not make repeated retries safe.
- The same LED after a correct minimum configuration. At that point the board, the CPU, and the firmware are the suspects, and separating them needs known-good spares. That is a technician job, not a shopping spree.
- A BIOS FlashBack that will not complete on a board that will not start. Check the USB format and the exact port from the manual once, then stop. Repeated failed flashes on a dead board do not improve with volume.
- A machine that will not POST with a processor the board’s support list does not cover. That is a compatibility problem, not a fault, and the answer is firmware, not hardware.
- Anything involving a prebuilt with a proprietary board. The maker decides which checks are user-serviceable. Ask before opening it.
If you get as far as documenting the LED stage, the power connections, and the BIOS version, you already have more than most repair tickets contain. The POST time census tracks how long boards take to clear training on healthy systems, which is useful context when a machine feels slow rather than dead. And the diagnostic workbench lets you record each step and result so the next person starts where you stopped.
Frequently asked questions
What does it mean if my PC powers on but won’t POST?
What do the CPU, DRAM, VGA and BOOT LEDs mean?
Should I reseat the CPU first when the CPU LED stays on?
Why does my PC not POST after a BIOS update?
Can a bad RAM stick stop a PC from POSTing?
Is it safe to test a PC outside the case?
How many power connectors does the motherboard need?
When should I stop and take the PC to a shop?
Sources and corrections
- Last updated
- Methodology
- See our methodology for research and review standards. It draws on 7 cited sources, listed below, each checked against the original page on the date above. Debug LED behaviour, header requirements, and recovery procedures verified November 16, 2026 against ASUS’s official Q-LED troubleshooting article, ASUS’s No Power/No Boot/No Display article, ASUS’s USB BIOS FlashBack article, the ROG STRIX B650-A Gaming WiFi hardware manual, the UEFI Forum’s ACPI 6.5 hardware specification, and Corsair’s power-supply documentation. I describe LED behaviour as ASUS documents it and do not claim measurements from a machine of mine.
- Sources
- ASUS: Motherboard troubleshooting via Q-LED indicators (CPU, DRAM, VGA, BOOT) accessed 2026-11-16
- ASUS: Motherboard troubleshooting - No Power / No Boot / No Display accessed 2026-11-16
- ASUS: How to use USB BIOS FlashBack accessed 2026-11-16
- ASUS: ROG STRIX B650-A GAMING WIFI user manual (Q-LED colour table, 8-pin power LED, system panel header) accessed 2026-11-16
- UEFI Forum: ACPI Specification 6.5, section 4.8.2.2.1, power button override accessed 2026-11-16
- Corsair: Power Supply Protections Explained (short-circuit and over-power protection) accessed 2026-11-16
- Corsair: Are PSU Cables Universal? (never mix modular cables across brands) accessed 2026-11-16
- Corrections
- Spotted an error? Email a correction with the affected line and what you found. The draft includes this page’s address. Verified changes are recorded here. Contact details.