PC Turns On But No Display? Read the Motherboard Before You Buy Anything (2026)

By LK Wood IV · 2026-07-10 · ~8 min read · St. Louis County, MO

Some retailer links below are Amazon affiliate links; if you buy through them TechFuel HQ may earn a small commission at no extra cost to you. As an Amazon Associate I earn from qualifying purchases. Commissions never influence what gets recommended — see our disclosure.

The fans spin. The RGB lights up. Maybe the graphics card fans turn too. But the monitor sits there black — “No Signal” — and you have no idea which of the dozen parts inside is the problem. So you start guessing, and guessing gets expensive fast.

(If pressing power gets you nothing at all — no fans, no lights, no sound — that’s a different problem: the PC isn’t powering on in the first place, which is a power-on-path fault. Start with Power Button Not Working on Your PC? and come back here once it’s spinning up.)

Here’s a true story that plays out in build-help forums every single day: someone with this exact symptom buys a whole new motherboard, installs it, gets the same black screen — and then realizes they’d never plugged both PCIe power cables into the graphics card. A five-second fix cost them a motherboard. The reason it happened is that they skipped the one step that would have told them where to look: the motherboard is already reporting which component failed. You just have to read it.

This guide is built around that step. Don’t reseat anything, don’t order parts, and definitely don’t RMA a working board until you’ve done the two-minute check and read the debug LED.

The whole troubleshoot fits on one page. Here it is as a map — the entire decision, start to fix, before you touch a screwdriver:

Step 1: The two-minute “is it even broken?” check

Roughly half of “no display” posts are not hardware failures at all. Clear these before you open the case, because they take seconds:

• Monitor input. Press the monitor’s Source/Input button and cycle through its inputs. A monitor set to HDMI 1 will show “No Signal” all day while your PC happily outputs on HDMI 2 or DisplayPort.
• Cable in the graphics card, not the motherboard. This is the single most common self-inflicted one. If your PC has a dedicated graphics card (a horizontal card lower on the back panel), the video cable must go into that, not the motherboard’s HDMI/DisplayPort ports up near the USB stack. On most desktops with a discrete GPU, the motherboard’s video outputs are disabled — plug into them and you get nothing.
• Try the other everything. A different cable, a different monitor, a different port on the card. Cheap cables die, and a bad DisplayPort cable produces an identical black screen to a dead GPU.
• Both GPU power cables fully seated. Modern cards use one or two PCIe power connectors (or a 12VHPWR/12V-2×6 plug). If even one isn’t clicked in, the card powers its fans and RGB but never outputs video — exactly the trap that costs people a new motherboard.

If the screen is still black after those, the machine genuinely isn’t completing POST (the power-on self-test that runs before Windows). Now the motherboard earns its keep.

One fork before you dig in: was it working yesterday?

The single most useful question — and the one most guides never ask — is whether this is a brand-new build that has never posted, or a machine that worked fine and then suddenly went black. Same symptom, different odds, so it’s worth naming which one you’re in:

• New build, never displayed. The prime suspects are seating and compatibility: RAM not fully clicked in, a GPU not seated, an EPS or PCIe power cable never plugged, standoffs shorting the board against the case, or a BIOS too old for a brand-new CPU. Work the debug LED below — this is exactly what it’s for.
• It was working, then suddenly nothing. Seating rarely un-does itself, so the odds shift toward things that drift or wear: a GPU power cable that worked loose (especially a 12VHPWR/12V-2×6 plug that was never fully latched), a power supply beginning to fail so voltages sag under load, an XMP/EXPO memory profile that was always marginal and finally tipped over, a dead CR2032 coin cell that lost your BIOS settings, or a graphics card that’s genuinely dying (often after a spell of visual artifacts first). The good news: the debug LED reads these out too, so the procedure is the same — you just start suspicious of cables and the PSU rather than seating.

If you moved, bumped, or cleaned the PC right before it went dark, treat it as the “suddenly” case with a loose cable at the very top of the list — reseat every power connector before anything else.

Step 2: Read the debug LED — the step almost every guide skips

Nearly every motherboard sold in the last several years has a small cluster of diagnostic LEDs labeled CPU, DRAM, VGA, BOOT (sometimes shown as a single two-digit code). When you power on, they light in that sequence as the board initializes each subsystem, then go out once POST completes. The one that stays lit is the stage that failed — that’s your answer. Manufacturers just brand them differently:

One important detail: on boot it’s normal for the LEDs to flash through the sequence quickly. Only when one stays lit for roughly a minute (or a code stops changing) should you treat it as the failure point. On AM5 / DDR5 systems especially, the DRAM light can sit on for several minutes during memory training on a first boot or after a CMOS reset — that’s expected, so give it time before you panic.

No debug LEDs at all, and nothing on screen? That’s its own signal. If the board never lights any diagnostic LED, it may not be getting power correctly, or something is shorting it — jump to the bench test in Step 4.

About beep codes: the classic POST beeps (one long + two short for a GPU error, a repeating tone for RAM) only work if you have the small PC speaker installed — and most modern cases and boards don’t ship one. No beep usually means “no speaker,” not “no problem.” If you do have a speaker, treat the pattern as a hint (they vary between AMI, Award, and Phoenix BIOS versions) and trust the debug LED where you have one.

Step 3: Fix by whichever LED is stuck (in hit-rate order)

There’s a reason to work these in order rather than jumping to the scariest one. Across the thousands of “no display” build-help threads that all look identical, the causes are wildly lopsided: the top of the list is free and common, the bottom is expensive and rare. Reading the debug LED tells you which branch; this tells you how much to worry.

DRAM light stuck — start here, it’s the most common

Memory that isn’t detected is the number-one reason a PC powers on but won’t POST. In order:

1. Reseat the RAM. Power off, unclip each stick, and press it firmly back in until both clips snap. A stick that looks seated but isn’t fully clicked is a classic culprit.
2. Test one stick, in the right slot. Pull all but one, and put that one in the slot your manual specifies for single-stick operation (usually the second slot from the CPU, labeled A2 or DIMM2). If it POSTs, add sticks back one at a time to find the bad one or the bad slot.
3. Wait out memory training. On DDR5, give a fresh configuration several minutes before concluding it’s dead.
4. Clear CMOS. A bad memory setting (an unstable XMP/EXPO profile) can hang POST; clearing CMOS resets it. Use the board’s Clear CMOS button/jumper, or pull the CR2032 CMOS battery for a minute with the power unplugged.

VGA light stuck — the graphics card

1. Reseat the GPU in its slot, and re-check both power cables (the mistake from the intro).
2. Try the integrated graphics if your CPU has them: pull the GPU, plug the monitor into the motherboard, and see if you get a picture. If you do, the problem is the card or its slot, not the rest of the PC.
3. Try a different PCIe slot if the board has one.
4. The older-card gotcha: genuinely old GPUs (GeForce GTX 600/700-era cards and older, before UEFI GOP video BIOSes became standard) can hang on the VGA light on a brand-new board until you enable CSM / Legacy boot mode in BIOS — which is a chicken-and-egg problem you may need a newer card or the iGPU to solve first. Worth knowing if you paired an old card with a new motherboard. If the card POSTs elsewhere but not here, that’s the pattern.

If it does eventually POST and boot but the card is missing inside Windows, that’s a different problem — see graphics card not detected.

CPU light stuck — usually not a dead CPU

1. Check the 8-pin EPS power at the top-left of the board. An unplugged CPU power cable produces a dead, no-POST board that looks exactly like a fried processor. This is far more common than an actual dead CPU.
2. Reseat the CPU and inspect the socket for bent pins under good light.
3. BIOS too old. If you just dropped a newer CPU into an older board, the BIOS may predate support for it. Use the board’s BIOS Flashback feature (often with an older, supported CPU) to update. Do not cut power or reset the machine while the flash runs — an interrupted BIOS update can leave the board unable to boot, which is why ASUS’s own flashing instructions say to back up first and not to shut down or reset mid-update.
4. Only then suspect the CPU itself — confirmed by swapping in a known-good chip. A new CPU that never POSTs on a compatible, updated board can be DOA, but prove it with a swap before spending.

BOOT light stuck

By this point the board has POSTed and you likely have a display — this is a storage/boot-device issue, not a no-signal one, so it’s outside this guide’s scope.

No LED lights at all, or a red “power” light with nothing else

Suspect a short or a power problem. The most common short is an extra motherboard standoff under the board, or a case screw contacting the wrong spot — a genuinely frequent cause that forum veterans spot immediately. Also confirm the power supply is actually delivering; if the system won’t stay on or cycles power, work through PC keeps restarting. And if the board never POSTs even stripped to CPU, one RAM stick, and a known-good PSU, work through the exclusion ladder in motherboard failure symptoms.

Step 4: The barebones bench test (when the LED won’t localize it)

If the debug LED is ambiguous or absent, strip the build down to the absolute minimum and test it outside the case, on the motherboard box or a sheet of cardboard, to rule out a case short:

• Power supply
• Motherboard
• CPU + cooler
• One stick of RAM
• Monitor plugged into the iGPU if available, otherwise the GPU

Nothing else — no extra drives, no case fans on the headers, no front-panel USB, no second GPU. Power it on by briefly bridging the two power-switch pins with a screwdriver — this is done on a live board, so touch only those two pins, briefly, and keep the blade clear of the 24-pin and EPS connectors, since a screwdriver dragged across the header or the board can short something you did not intend. If it POSTs like this, add components back one at a time until the black screen returns; the part you just added is the fault. If it still won’t POST bare, with CMOS cleared and a known-good CPU and RAM, then you’ve genuinely narrowed it to a failed motherboard or CPU — and even that is a part swap, not a “bricked” machine.

A quick note on the word bricked: a PC that powers on but won’t display is almost never actually dead. Real bricking is rare. Nine times out of ten this is a reseat, a repower, a cleared CMOS, or a single loose cable — which is exactly why reading the board before buying parts saves the most money.

The quick version

1. Rule out the dumb stuff (2 min): monitor input, cable in the GPU not the motherboard, spare cable/monitor, both GPU power cables seated.
2. Read the debug LED (ASUS Q-LED / MSI EZ Debug / Gigabyte Status LEDs / ASRock Dr. Debug). The light that stays lit — CPU, DRAM, VGA, or BOOT — is the failed stage. Give DDR5 memory training a few minutes first.
3. Fix that stage: DRAM → reseat / single stick in slot 2 / clear CMOS. VGA → reseat GPU + both power cables / try iGPU / CSM for old cards. CPU → check 8-pin EPS / reseat / BIOS update / swap-test last.
4. No LEDs at all → suspect a standoff short or power fault; bench-test outside the case.
5. Barebones bench test to isolate the culprit, then add parts back one at a time.

Read the board before you reach for your wallet. The motherboard spent a full second at power-on telling you exactly which component didn’t wake up — and the difference between a $0 reseat and a needless new part is whether you looked.