If your computer fails the power-on self-test, cut power, reseat parts, clear CMOS, and test one component at a time to find the fault.
Nothing on screen, no keyboard lights, maybe a fan burst, then silence. That means the system never completes the power-on self-test. The good news: with a simple plan you can spot bad connections, mismatched parts, or a failing device fast. This guide shows quick checks first, then deeper steps that solve most no-POST headaches at home.
No POST On A Desktop: Quick Checks That Fix Most Builds
Start with electricity, then seating, then bare-minimum boot. Work from outside in so you don’t miss an easy win. Keep the wall outlet switched off while you touch hardware, and touch metal to discharge static before every step.
Step-By-Step Triage
- Shut the switch on the power supply, then unplug the cord. Hold the case power button for ten seconds to drain residual charge.
- Plug only the monitor into the graphics output you intend to use. For new CPUs with integrated graphics, use the motherboard HDMI/DP; for a discrete card, use the card’s port.
- Seat the 24-pin ATX and the CPU 8-pin (sometimes 4+4). Missed EPS power is a classic no-boot cause.
- Install one memory module in the slot the manual marks for single-DIMM. Press until both latches click.
- Remove all storage and extras: no SSDs, no USB hubs, no case RGB controllers, no add-in cards.
- Connect the case power-switch header correctly, or bridge the two power pins with a screwdriver for a moment to start the board.
Fast Signal Guide
Many boards show beep codes, two-digit POST codes, or labeled LEDs. Use the signal you see to pick the next step.
| What You See Or Hear | Likely Area | Next Move |
|---|---|---|
| No display, fans spin once | Power delivery | Check 24-pin and CPU 8-pin; try a known-good outlet |
| Repeating short beeps | Memory | Boot with one DIMM; try other slot; reseat |
| One long, two short beeps | Graphics | Move cable to GPU; reseat card; try onboard video |
| CPU/DRAM/VGA/BOOT LED lit | Board debug cue | Follow the labeled LED to target part |
| Two-digit code halts | POST checkpoint | Look up code in the board manual |
| Fans run, no beeps, no lights | Stuck before POST | Clear CMOS; try bench test outside case |
Why Power-On Self-Test Fails
POST is firmware running checks on the CPU, memory, graphics path, and basic interfaces. A halt can come from power issues, an unsupported CPU, bent socket pins, a shorted standoff under the board, a RAM mismatch, a GPU that needs extra power, or corrupted firmware. Knowing which area fits your symptoms trims hours off the hunt.
Power And Ground First
Loose power leads stop everything. The 24-pin and CPU EPS plugs must seat fully. Some graphics cards need one or two PCIe power plugs; missing one leaves you staring at a blank panel. If your supply has a rear switch, set it to I for on. If nothing spins at all, one option is the classic paperclip jump: bridge the PS_ON green wire to any black ground on the 24-pin to see if the PSU fan starts. Do this with the PSU disconnected from the PC and from the wall, and follow a vendor sheet like SilverStone’s paperclip safety steps.
Memory Seating And Compatibility
Two DIMMs not clicked home is a top culprit. Boot with one stick in the preferred slot, then swap to test the other module and slot. Check the board’s QVL list and the CPU’s supported speeds. Over-tightened cooler pressure can also skew memory training; loosen a quarter turn and try again.
Graphics Path
Many boards default to integrated video when present. Try HDMI/DP on the motherboard first with the card removed. If you need the card, make sure it is in the top x16 slot and powered, and try a second output and cable.
CPU And Socket
If debug lights park on CPU, check the 8-pin EPS lead, remove and reseat the processor, and inspect for bent pins in the socket. On LGA sockets, one bent pin can block memory initialization, which looks like a RAM fault at first glance.
Firmware Corruption Or Unsupported CPU
A new processor on an older board may need a BIOS update before it can run. Many boards offer USB Flashback or similar so you can update firmware without a working system. If a recent tune pushed the system too far, a full CMOS reset returns safe defaults.
Clear CMOS The Right Way
Resetting setup values wipes unstable memory timings and failed overclocks. Use the board’s clear-CMOS button or jumper when present. If you don’t have those, remove AC power, pop the coin cell for a few minutes, then reinstall it and power back on. Vendor guides show exact jumper positions and safe handling. A clear, brand-specific walk-through like Dell’s BIOS/CMOS reset guide outlines common methods that also apply broadly across desktop boards.
Use Board Debug Lights And Beeps
Modern boards ship with CPU/DRAM/VGA/BOOT LEDs or a tiny two-digit display. When one light stays on, chase that part. If you hear a beep pattern from a tiny case speaker, check the code table for your firmware vendor and model. These cues point you straight to the bad actor. Pages like ASUS Q-LED indicators explain what each light means so you can act in the right order.
Build A Minimal Test Bed
Pull the motherboard from the case and place it on a box. Install CPU with cooler, one DIMM, and either onboard video or a known-good GPU. Connect the PSU’s 24-pin and 8-pin. Short the power pins to start. This bench test removes case shorts and narrows the suspect list in minutes.
Order Of Swap Testing
- PSU: try another unit of adequate wattage.
- RAM: test each module alone; try slow JEDEC speed.
- GPU: try onboard, then a spare card.
- Motherboard: inspect for burn marks or swollen caps.
- CPU: last in line; borrow a supported chip if possible.
Common Scenarios And Fixes
New Build, Fans Spin, No Video
Recheck EPS power, seat the card, and move the display cable to match the active output. Boot with one DIMM. If the board offers a BIOS update from USB, apply the release that adds CPU compatibility.
Old System Sat For Months
Pop the coin cell to clear setup values, reseat memory, and try a fresh power lead. Dust can block contacts; pull and press parts back in to wipe oxide from pins.
Boot Loop
Many boards retry memory training a few times, then power cycle. Set RAM to stock JEDEC, clear CMOS, and update firmware. If lights stick on DRAM, try a single module and test the other channel.
Lights On CPU LED
Check the backplate standoffs for a misplaced screw under the socket area. Confirm the cooler backplate isn’t shorting traces. Reseat the chip and inspect the socket with a bright light.
No Beep Codes
Many modern cases skip a speaker. Add a cheap buzzer to the front-panel header to hear beeps. The pattern points straight to memory or graphics in many fails.
Safety Notes For Power Testing
Never short pins on a live motherboard. If you choose to jump a power supply for a spin test, disconnect it from the PC and from the wall before moving clips. A PSU that spins isn’t fully proven; it only shows standby logic and a fan response. Full load checks need proper tools.
When To Suspect Each Part
| Symptom | Suspect First | Why That Part |
|---|---|---|
| Instant off after start | PSU or short | Protection trips from a short or bad rail |
| DRAM light locked | Memory or CPU pins | Training fails due to seating or IMC issue |
| VGA light locked | GPU or monitor path | Card lacks power or cable/port mismatch |
| Code 00 on display | CPU/board | Board can’t hand off to CPU |
| Beeps repeat forever | RAM | POST can’t pass basic memory test |
| No lights, fans run | Firmware | NVRAM values block init |
Firmware Updates And CPU Compatibility
Match the motherboard’s CPU list page to your exact processor stepping. If the CPU needs a newer firmware, use the vendor’s offline flashing tool when available. Keep a spare USB drive with the file at the root, named exactly as the vendor asks.
Ground Rules For Assembly That Prevent No-POST
- Install only the standoffs that match holes; extras cause shorts.
- Click both memory latches; look for equal height on the ends.
- Plug PCIe power leads into the card; don’t daisy chain if the vendor asks for separate cables.
- Route front-panel headers by the manual, not guesswork.
- Add the tiny speaker so you can hear beeps next time.
Small Tools That Pay Off
- POST code reader for older boards without built-in displays.
- Known-good PSU and HDMI cable.
- USB stick for firmware files.
- Isopropyl wipes for contacts.
- Bright flashlight to check socket pins.
What To Do After It Finally Boots
Load setup defaults, set RAM to the advertised profile only after a few stable restarts, and update to a stable firmware. Keep a change log so the next time a tune goes sideways you can roll back fast.
Helpful Vendor Guides
Board makers publish solid pages on debug lights and reset methods. Bookmark a page for your hardware so you can cross-check LEDs and beeps during the next build.
Run a memory test overnight once stable to catch flaky modules early, too.