Gaming PC Won't POST: Reading the Startup Sequence

What POST actually is

Power-On Self-Test is the firmware's checklist: detect the processor, train the memory, find a graphics output, enumerate storage, then hand over to the boot device. If any step fails, the machine stops there. Nothing about Windows is involved yet, which is why reinstalling the operating system cannot help.

• Fans spin, no image, no drive activity, no keyboard lights — a likely POST failure.
• Machine powers on for a few seconds then cycles off and on repeatedly — a boot loop, usually memory training or a power fault.
• You reach a BIOS screen or a "no bootable device" message — POST succeeded; the problem is storage or boot configuration.

Reading the indicators

Start with what changed

Most no-POST machines that come to us stopped posting right after something happened. If you can name the change, you have narrowed the field enormously.

• New build that has never posted — seating, standoffs shorting the board, front panel wiring, missing EPS power, or a CPU the board needs a firmware update to run.
• Memory or CPU just installed — compatibility and firmware version first, then seating.
• BIOS update applied — a failed or wrong update; many boards have a recovery or flashback feature.
• Overclock or memory profile applied — clear CMOS.
• Machine was moved — a card or stick shaken loose, or a cooler that shifted.
• Nothing changed at all — more likely a component that has genuinely failed, or the power supply.

Safe checks

1. 1

   Confirm both power connectors

   The 24-pin and the 8-pin CPU connector at the top of the board both need to be fully seated. A missing EPS cable is one of the most common no-POST causes on new builds.

2. 2

   Clear CMOS

   Use the board's button or jumper with the machine unplugged. This reverses settings that stop the board from posting.

3. 3

   Reduce to minimum

   One memory stick in the slot the manual names, no extra drives, no USB devices, no extra cards. Add parts back one at a time.

4. 4

   Reseat memory and graphics card

   Firmly, until the clips engage. Then try the other stick alone, and the other slots.

5. 5

   Look at the board itself

   Check for a standoff under a spot with no mounting hole, bulging capacitors, scorch marks, or a front-panel power switch wired to the wrong header.

6. 6

   Check the board's supported CPU list

   If the processor is newer than the board, it may need a BIOS update — and some boards can do that with no CPU installed via a flashback port.

What each result may indicate

• Posts after clearing CMOS — settings were the cause, most often a memory profile the board could not train.
• Posts with one stick, not the other — memory or a slot; confirm by swapping the working stick into the suspect slot.
• Boot looping with the DRAM light — memory training is failing repeatedly; some boards need a long first-boot training period, but minutes, not hours.
• No change with minimum configuration — CPU, board or power supply, which needs substitution to separate.
• BOOT light lit — the hardware is fine and the problem is the drive or the boot configuration, which is a much better outcome.

About your files

When to stop

Stop if you see bent socket pins, physical damage or scorch marks, or if the board powers on and off repeatedly without your input. Stop as well once the only path forward is buying a CPU, board or power supply speculatively — three guesses cost far more than a diagnosis.

When it's a bench job

Separating CPU, board and power supply requires known-good spares in each of those positions. That is routine bench work for us and impossible to do properly at home. New builds that have never posted are especially worth bringing in with all the parts and boxes — the answer is often compatibility or a wiring detail rather than a faulty component.