Open desktop PC with a graphics card removed during diagnosis
Computer Repair Guide10 min read

PC Turns On but No Display? What to Check First

Start with the monitor, cable, and video port. Then use startup clues to tell a display problem from a PC that cannot complete POST.

· Updated

Written by Ken, NorthCore Computing Solutions Founder and Technician.

Quick Answer

Why does my PC turn on but show no display?

First check the monitor's input, cable, and the video port on the PC. If those work, watch for a startup logo and record any motherboard debug light or beep code. Fans and lights alone cannot tell you whether the computer completed its startup checks.

Request no-display computer diagnosis in Davis

A PC can light up and spin its fans without sending a picture to the monitor. Start with the checks you can make without opening the case:

  • Confirm the monitor is on and set to the input used by the cable.
  • Reseat the cable at both ends and, if possible, try a cable or monitor you know works.
  • If the PC has a graphics card, connect the monitor to that card rather than assuming the motherboard video port is active.
  • Note whether you ever see a startup logo. Record any debug light or beep pattern that remains after the PC starts.

If a logo appears and the screen goes dark only when Windows loads, start with display settings, drivers, or Windows. If there is no image from power-on, the monitor connection or the PC's hardware startup is more likely. The sections below show how to narrow those possibilities without replacing parts at random.

First Identify Which Startup Failure You Have

Failure typeWhat you observeWhat it suggests
No powerNo fans, lights, sound, or response from the power buttonPower source, switch, cabling, front-panel connection, power supply, or motherboard
No POSTFans or lights may run, but the system never completes its hardware checks or shows a startup logoRAM, CPU, graphics, motherboard, firmware, compatibility, or power delivery
No videoThe computer may complete POST or even load Windows, but nothing reaches the displayMonitor, input, cable, port, graphics output, display configuration, or GPU
No bootThe system displays POST or firmware information but Windows does not loadStorage, boot configuration, Windows, encryption, or another operating-system problem

These categories can look similar from across the room. Diagnostic LEDs, beep patterns, keyboard response, startup sounds, and whether any logo ever appears help separate them. Dell also distinguishes no power, no POST, no video, and no boot in its official startup troubleshooting because each category leads to different checks.

Start With the Monitor, Cable, Input, and Port

Before opening the computer, confirm that the monitor has power and is set to the input matching the connected cable. Test one display at a time, reconnect both ends of the cable, and try a known-good cable or monitor when available. A monitor can correctly report No Signal even though the fault is the selected input or the computer output.

  • Confirm the monitor's power light is on and select the exact HDMI, DisplayPort, DVI, or USB-C input in use.
  • Connect directly to the computer during testing rather than through a dock, switch, adapter chain, or capture device.
  • Try one known-good display and cable instead of changing several unknown items together.
  • Inspect connectors for damage and make sure the cable is fully seated without forcing it.
  • If the computer has a dedicated graphics card, check whether the display cable belongs in that card rather than the motherboard panel.

The Motherboard Video Port May Not Produce an Image

Motherboard HDMI or DisplayPort connectors require a processor and firmware configuration that support integrated graphics. Some desktop processors have no integrated graphics at all. Intel, for example, notes that processors with an F suffix require a separate graphics card. Other processor families use different naming, so verify the exact model rather than assuming every motherboard port is active.

For a system with a dedicated graphics card, connect the monitor to an output on that card for the initial test. If integrated graphics are confirmed for the processor and the motherboard supports them, testing the motherboard output can help isolate the display path after the system is powered down and the configuration is understood.

Record Debug Lights, POST Codes, and Beep Patterns

Many motherboards provide diagnostic LEDs labeled CPU, DRAM, VGA, and BOOT, a numerical POST-code display, or beep patterns through a connected speaker. A light may appear briefly during a normal startup. The useful clue is the indicator that remains lit or the pattern that repeats when the failure occurs.

Write down the exact label, color, number, or beep sequence and check the manual for that motherboard or computer model. Codes are not universal. A DRAM light directs attention toward the memory stage, for example, but it does not prove that buying new RAM will solve the problem; seating, slot choice, compatibility, firmware, processor contact, and the motherboard can all affect memory initialization.

Take a short video of the lights from power-on through the point where they stop changing. That preserves a repeatable clue and is more useful than reporting that every light flashed.

Reverse the Most Recent Change First

If the computer worked before a new graphics card, RAM kit, processor, BIOS update, cable change, cleaning, or move, begin with that timeline. Verify compatibility and installation, then return to the last known-working configuration when practical. Intel's no-boot guidance similarly recommends reverting recent hardware changes before expanding the diagnosis.

A newly built computer adds compatibility questions: whether the motherboard firmware supports the processor, whether the memory is installed in the recommended slot, whether the CPU and PCIe power connectors are present, and whether the case standoffs or front-panel connections are correct. A previously working computer that suddenly fails calls for a different emphasis, including loose connections, failed hardware, and power quality.

Why RAM Is a Common No-POST Check

Memory must initialize before the computer can complete POST. A module that is loose, in the wrong slot for a one-module test, incompatible, or unstable can leave the system running fans without producing video. Some systems also spend longer than expected training memory after new RAM or a firmware reset, so consult the board manual before interrupting that process repeatedly.

If you are comfortable working inside the PC, shut it down, switch off and unplug external power, and follow the motherboard manual for a one-module test in the recommended slot. Change one item at a time and record the result. Never install or remove memory while the system is powered, and never force a module that does not align with the slot.

Check the Graphics Path Without Assuming the GPU Is Dead

A graphics card can fail to initialize because it is not fully seated, required power is missing, the display is connected to the wrong output, firmware compatibility is involved, or another component prevents the system from reaching the graphics stage. GPU fans are not a reliable pass-or-fail test because many cards intentionally stop their fans at low temperature.

  • Power the PC down before checking whether the card and its power connectors are fully seated.
  • Use only the power cables and connections specified for that power supply and graphics card.
  • Test another output on the card and one known-good cable or monitor.
  • If the exact processor supports integrated graphics, use the motherboard output as a controlled isolation test when the hardware configuration permits it.
  • Use a known-good graphics card only when its power needs and compatibility are understood, then retest the same startup condition.

Fans Spinning Does Not Clear the Power Supply

A power supply has several outputs and must remain stable while the motherboard, processor, and graphics hardware initialize. It can power lights or fans while a missing CPU-power connector, incorrect cable, weak rail, protection event, or internal fault prevents POST. Visual activity therefore does not prove that every required voltage is present and stable.

Check external power, the rear switch, and the motherboard, processor, and graphics power connections with the PC shut down. CPU/EPS and PCIe connectors can look similar while serving different purposes. Modular power-supply cables are not universally interchangeable, even when they fit the socket. Use only cables approved for the exact power-supply model, and never open the power-supply enclosure because hazardous charge can remain inside.

Use a Minimal Configuration and Change One Variable

When basic checks do not expose the cause, reduce the computer to the parts required to reach POST: the motherboard, compatible processor and cooler, one memory module in the documented slot, suitable graphics output, and a known-good power source. Disconnect nonessential USB devices, storage, expansion cards, and accessories. Reconnect one item at a time only after the core system behaves consistently.

This process is useful because it turns a broad symptom into controlled evidence. Swapping RAM, graphics, power, and motherboard parts all at once may produce a working computer without identifying the cause. It can also introduce a second installation problem that hides the first one.

Treat Firmware and CMOS Reset as Later Steps

A firmware version may not support a newly installed processor, and unstable tuning or incorrect settings can prevent startup. Clearing CMOS can restore motherboard defaults, but the exact jumper, button, battery procedure, and required waiting time depend on the board. Follow the model's manual instead of a generic pin layout.

Record customized settings before a reset when possible. If Windows uses BitLocker or device encryption, locate the recovery key before changing firmware, Secure Boot, TPM, or boot settings. Microsoft documents that hardware and pre-boot configuration changes can trigger BitLocker recovery. A CMOS reset should not become a new data-access problem after the display is restored.

A Common Real-World No-Display Question

A recent Reddit user described a PC whose fans ran but whose monitor, keyboard, and mouse showed no response. The computer had first power-cycled and later remained on without displaying anything. They had already reseated the RAM and graphics card and cleared CMOS, yet the symptom remained.

The useful next question is not which expensive part to buy. It is which startup stage fails and what the motherboard reports while it fails. The exact board model, debug indicators, processor graphics capability, power connections, recent changes, and results from known-good parts can separate memory, graphics, power, motherboard, processor, and firmware causes. The original discussion is linked below.

Avoid These No-Display Troubleshooting Mistakes

  • Do not replace the graphics card solely because the monitor says No Signal.
  • Do not assume RGB lighting or spinning fans prove the power supply and motherboard are healthy.
  • Do not connect modular cables from a different power-supply model unless the manufacturer explicitly confirms compatibility.
  • Do not reseat or swap internal components while power remains connected.
  • Do not flash firmware or clear CMOS repeatedly without the exact board procedure and an accessible BitLocker recovery key.
  • Do not bend socket pins, open the power supply, or force connectors while trying random fixes.

How NorthCore Diagnoses a PC With No Display

NorthCore starts by reproducing the symptom and identifying whether the system has no power, no POST, no video, or a Windows boot failure. We record debug indicators, inspect relevant connections and recent changes, confirm the display path, and reduce the computer to a controlled configuration when needed.

The next tests follow the evidence and can include known-good memory, graphics, and power components; compatibility and firmware review; processor and socket inspection; or storage and Windows checks after POST is restored. The goal is to recommend the part or repair supported by the test results rather than treating every black screen as a failed graphics card.

When requesting service, include the motherboard, processor, graphics card, memory, and power-supply models; whether the PC ever worked; the last hardware or firmware change; and a photo or video of debug lights and beep patterns. Bring the complete desktop and its relevant power cable rather than only the suspected part.

If the PC still will not reach POST or produce a display, NorthCore offers local computer repair.