Computer Turns On But No Display? How to Diagnose a No-POST Fault Before You Assume the Worst
There's a particular kind of dread that comes with pressing the power button, seeing the fans spin up and the lights come on — and then getting nothing on the screen. No error message, no login prompt, just a blank display. It feels worse than a computer that simply won't turn on at all, because everything looks like it's working, which makes it harder to guess what's actually wrong.
The good news is that "turns on but no display" is one of the more diagnosable faults a PC or laptop can have, and it doesn't automatically mean the motherboard has failed. It's worth working through calmly before assuming the worst — or before buying a replacement machine you might not have needed.
What "no POST" actually means (and how it's different from no power at all)
POST stands for Power-On Self-Test — the quick internal check a computer runs every time it starts, before handing control over to Windows (or whatever's installed). If POST completes successfully, you'll usually see a manufacturer logo, a BIOS/UEFI screen, or at least some sign of life on the monitor. If it doesn't complete, the system can sit there indefinitely with the fans running and the power light on, but nothing ever reaches the display.
That's a meaningfully different problem to a machine that shows no signs of power at all — no fans, no lights, nothing — which points toward the power supply or a motherboard power-delivery fault, the scenario we covered in our recent article on desktops that won't turn on at all. A no-POST fault, by contrast, means the machine is getting power and attempting to start — the problem is somewhere between "powered on" and "showing you anything."
The safe checks worth trying first
Reseat the RAM and listen or watch for beep/LED codes. Loose or poorly seated RAM is one of the single most common causes of a no-display fault, and it's also the easiest to rule out. With the machine powered off and unplugged, reseating the memory modules (removing them and firmly clicking them back into place) fixes a surprising number of these faults outright. Many motherboards also give a diagnostic clue if you know where to look — a series of beeps from an internal speaker, or a small row of debug LEDs on the board itself — and the motherboard manufacturer's own support documentation is the right place to decode what a given beep pattern or LED colour means for that specific board (ASUS Support, "Motherboard Troubleshooting — No Power/No Boot/No Display").
Rule out the display itself. Before assuming it's the computer, try a different monitor or TV, a different video cable, and a different port on the graphics card or motherboard if more than one is available. It sounds obvious, but a faulty cable or a monitor that's woken up on the wrong input source causes a fair share of "my computer is broken" calls that turn out not to be.
Notice what else is (or isn't) happening. Are the case fans spinning at full speed the whole time, or do they settle down normally? Does the hard drive or SSD activity light flicker at all? Does the machine attempt to restart itself on a loop? These small details help narrow down whether the system is getting stuck very early (often RAM or a motherboard fault) or slightly later in the startup process (more often graphics-related).
What usually causes a no-POST fault
RAM seating or a failed module. As above — this is the first thing to check, and the most common fix. If a machine has multiple RAM sticks, testing with one at a time in different slots can also help isolate a single failed module rather than a slot problem.
A dislodged or failing graphics card. On desktops with a separate graphics card, a card that's worked loose from its slot (sometimes simply from the machine being moved) is a common and easy-to-check cause. Reseating the card, and checking that any PCIe power cables are firmly connected, resolves this more often than people expect.
Motherboard-level faults. When RAM, the graphics card and the display itself have all been ruled out, the remaining possibilities sit on the motherboard: a failed DIMM slot, a fault in the voltage regulation feeding the CPU or memory, or — less commonly — a corrupted BIOS chip. These are genuine hardware faults, but even here, the scope of the repair varies enormously depending on exactly what's failed, which is why a proper diagnostic matters rather than guessing.
Laptops are a different story
Everything above applies conceptually to a Windows laptop too, but the practical checks look different, because you generally can't reseat internal RAM or a graphics card on a modern thin laptop the way you can on a desktop. Laptop RAM is frequently soldered directly to the motherboard (we explain why in our guide to soldered RAM versus LPCAMM2), and there's no separate graphics card to check in most models. A laptop that powers on with no display more often points to a display-cable connection issue (the ribbon cable between the screen and the motherboard, which flexes every time the lid opens and closes), a failed backlight, or — again — a motherboard-level fault. External-monitor testing (plugging the laptop into an external screen via HDMI or USB-C) is one of the most useful checks a laptop owner can do themselves: if an image appears on the external display but not the laptop's own screen, that points toward the internal screen or its cable rather than the motherboard.
Why "it powered on, so it can't be the motherboard" is a myth
It's a reasonable assumption — surely if the board were dead, nothing would happen at all? In practice, a motherboard can power up perfectly normally and still fail to complete POST, because "getting power" and "successfully initialising every component" are two different jobs the board has to do. A machine with a healthy power supply and a genuinely faulty motherboard will often look identical, from the outside, to one with a simple RAM-seating issue — which is exactly why the checks above matter, rather than assuming either extreme.
When it's time to bring it in
If you've reseated the RAM, tried a different display and cable, and (on a desktop) reseated the graphics card, and you're still getting nothing, it's a reasonable point to stop self-diagnosing. Continuing to swap parts without proper testing equipment risks further damage, particularly on laptops where getting inside the case safely takes the right tools. Macrotech Solutions offers hands-on diagnostics for no-display and no-POST faults on both custom-built and pre-built desktops and Windows laptops at our Carrum Downs workshop, with component-level and microsoldering capability on-site for cases that do turn out to be motherboard-level. We'll identify exactly which part of the system has failed before any repair work begins, so you know the scope of the job upfront. We look after customers across Carrum Downs, Frankston, Cranbourne, Lyndhurst, Langwarrin, Seaford, Skye and Patterson Lakes — see our desktop and laptop repair pages.
Frequently Asked Questions
My computer beeps a few times when I turn it on — what does that mean?
Beep codes vary by motherboard manufacturer, so the exact pattern (number and length of beeps) needs to be checked against that specific board's documentation, but a beep pattern of any kind usually means the board is detecting a fault with a specific component (often RAM) rather than the board itself being dead.
Is a no-POST fault always cheaper to fix than a total no-power fault?
Not necessarily — it depends entirely on the actual cause. A RAM-seating issue costs nothing to fix; a genuine motherboard-level fault can be a significant repair either way. That's exactly why a proper diagnostic is worth doing before assuming either outcome.
Can dust cause a no-display fault?
Yes — a heavy buildup of dust can interfere with connections and airflow enough to cause intermittent or persistent startup faults, which is one of the reasons a routine clean-out (especially heading into a Melbourne summer) is genuinely useful preventative maintenance, not just cosmetic.
Will Safe Mode help me fix this?
No — Safe Mode is a Windows startup option, and a no-POST fault happens before Windows (or any operating system) even begins to load, so there's nothing on the software side to select yet.
What if my laptop shows an image on an external monitor but not its own screen?
That strongly suggests the fault is in the internal display, its backlight, or the cable connecting it to the motherboard, rather than a motherboard fault itself — a smaller and generally more affordable repair.
Powers on but nothing on screen? Get it diagnosed before you replace anything.
Book a DiagnosticMacrotech Solutions is an independent repair centre and is not affiliated with any computer or component manufacturer.