How to Fix a PC That Turns On But Shows No Display

A PC that turns on but shows no display most often fails because the monitor is set to the wrong input or the graphics card is not seated, sending no signal to the screen. When the fans spin and the lights come on but the monitor stays black and reports no signal, power has reached the system and the fault sits in the display path or the power-on self-test rather than the power supply. This article lists the causes of a no-signal PC in order of probability, then walks through step-by-step solutions ordered from the fastest check to the deeper hardware tests.

The fixes cover selecting the monitor input and testing the cable, plugging into the graphics card rather than the motherboard, reseating the graphics card and connecting PCIe power, reseating and testing one RAM stick, reading POST beeps and motherboard debug LEDs, trying onboard graphics or another card, and clearing the CMOS. Each solution states what it resolves and gives the exact procedure.

What Causes a PC to Turn On But Show No Display?

A PC turns on but shows no display because the monitor receives no usable signal, most commonly from the wrong monitor input, a cable plugged into the wrong port, or a graphics card that is not seated. Power reaches the system, so the fault sits in the display path or the power-on self-test. The common causes are listed below, most frequent first:

• Wrong monitor input leaves the screen waiting on a source the PC is not using, such as HDMI 2 while the cable runs to HDMI 1.
• A dead or wrong cable carries no signal, or a DisplayPort-to-HDMI mismatch fails to handshake.
• A graphics card not seated or without power outputs nothing, since the card needs full slot contact and its PCIe power cables.
• The cable plugged into the motherboard instead of the graphics card sends no signal when a discrete card is installed.
• Bad or unseated RAM halts the power-on self-test before the system can output video.
• A failed graphics card powers on but produces no image, isolated by testing another card or onboard video.
• A BIOS or POST issue from corrupted firmware or incompatible hardware stops the system before display initialization.

The distinction that matters is that the system has power: fans spin and lights show, which separates this problem from a fully dead machine covered in the computer that will not turn on guide. A screen that shows the manufacturer logo and then freezes is a boot problem covered in the computer stuck on the boot screen guide rather than a no-signal fault.

Select the Correct Monitor Input and Test the Cable

Selecting the correct monitor input and testing the cable resolves a no-signal screen caused by the monitor watching the wrong source or a failed cable. A monitor with several inputs stays on the last source until changed, and a damaged cable carries no picture.

This check comes first because it requires no tools. Follow these steps:

1. Press the monitor’s source or input button and cycle through HDMI 1, HDMI 2, and DisplayPort until the screen matches the connected port.
2. Reseat the video cable at both ends, since a partly inserted DisplayPort or HDMI plug breaks the handshake.
3. Swap the cable for a known-good one, because a damaged cable is a frequent and inexpensive cause of no signal.
4. Test the monitor on another device, such as a laptop or console, to confirm the monitor itself displays an image.

If the monitor shows an image from another device on the same cable and input, the monitor and cable are confirmed working and the fault returns to the PC’s graphics output. A monitor that stays black on every input and every source has a display fault of its own.

Plug Into the Graphics Card, Not the Motherboard

Plugging the monitor into the graphics card rather than the motherboard resolves a no-signal screen on a system with a discrete graphics card installed. When a dedicated graphics card is present, the motherboard’s video ports are usually disabled, so a cable in the motherboard port produces no image.

The card’s outputs sit lower on the rear panel, oriented horizontally. Follow these steps:

1. Locate the graphics card’s outputs, the HDMI and DisplayPort connectors on the horizontal card lower on the rear of the case.
2. Move the video cable from the motherboard ports, grouped with the USB ports higher up, to the graphics card outputs.
3. Confirm the image appears once the cable connects to the card, which indicates the motherboard ports were disabled by the discrete card.
4. Enable onboard graphics in BIOS only if the build intends to use the motherboard outputs alongside the card.

The motherboard ports work only when the processor has integrated graphics and no discrete card overrides them, so most gaming systems output solely through the graphics card. This single mistake accounts for many no-signal reports on newly built systems.

Reseat the Graphics Card and Connect PCIe Power

Reseating the graphics card and connecting its PCIe power resolves a no-signal screen caused by a card that lost slot contact or lacks supplemental power. A card that vibrated loose or sits unseated outputs nothing, and a card without its required 6-pin or 8-pin PCIe power cables cannot initialize. Follow these steps:

1. Power off and unplug the system, then release the PCIe slot latch and the rear bracket screw holding the card.
2. Reseat the card firmly in the top x16 slot until the latch clicks, because a card seated on one edge makes no contact.
3. Connect the PCIe power cables, the 6-pin or 8-pin plugs, since a card starved of power runs its fans but outputs no signal.
4. Confirm the cables are PCIe, not EPS, because the 8-pin CPU EPS connector does not fit the graphics card correctly.

A graphics card whose fans spin without producing an image often lacks its PCIe power or sits unseated, so both points need confirming together. How the power supply delivers the rails the card draws appears in the explanation of how power supplies work, and a card that exceeds the unit’s capacity ties to the guide to PSU wattage.

Reseat and Test One RAM Stick

Reseating and testing one RAM stick resolves a no-display condition caused by memory that fails the power-on self-test. A system that cannot detect working memory halts before video output, often with a beep code or a memory debug LED.

Testing a single known-good stick isolates a faulty module or slot. Follow these steps:

1. Power off and open the retention clips on each RAM slot to release the modules.
2. Reinsert one stick in the primary slot the motherboard manual names, usually the second slot from the CPU (A2 or DIMM_A2).
3. Attempt to post with the single stick, then test each module and slot in turn to find the failing part.
4. Clean the module contacts with a soft eraser if a stick is detected intermittently, since oxidized contacts cause dropouts.

A system that displays an image only with a particular stick or slot has isolated the fault to the excluded module or slot. The correct slot order for single and dual-channel memory appears in the guide to installing RAM, which prevents a board from failing to post with memory in the wrong slots.

Read POST Beeps and Motherboard Debug LEDs

Reading POST beeps and debug LEDs identifies the component that halts the power-on self-test before display output. The motherboard signals the failed stage through a speaker beep code or a row of debug LEDs labeled CPU, DRAM, VGA, and BOOT.

The indicator that stays lit names the stalled component. Follow these steps:

1. Watch the debug LEDs at power-on, since the LED that remains lit, CPU, DRAM, VGA, or BOOT, marks where the POST stopped.
2. Install a case speaker if the board lacks debug LEDs, because the beep code conveys the same diagnosis through sound.
3. Count the beep pattern and match it to the motherboard manual, where one long and two short beeps commonly signals a graphics fault.
4. Act on the indicated stage, reseating RAM for a DRAM light, the graphics card for a VGA light, or the processor for a CPU light.

A debug LED stuck on VGA points to the graphics card, while one stuck on DRAM points to memory, giving a precise target rather than guesswork. A board that hangs on the BOOT LED has passed hardware initialization and reached a storage problem closer to the no bootable device error.

Try Onboard Graphics or Another Graphics Card

Trying onboard graphics or another card isolates a no-signal fault to a failed graphics card. Switching the video source to the processor’s integrated graphics or to a different card determines whether the original card has failed. Follow these steps:

1. Remove the discrete graphics card and connect the monitor to the motherboard video port if the processor includes integrated graphics.
2. Power on with onboard graphics, since an image through the motherboard port confirms the discrete card has failed.
3. Install a known-good graphics card in place of the original if the processor has no integrated graphics.
4. Test the suspect card in another system to confirm the fault travels with the card rather than the slot or power supply.

A system that displays correctly on integrated graphics or a different card has confirmed the original card as the fault. A processor without integrated graphics, common on many desktop chips, requires a working discrete card to display anything, so a spare card is the only test available.

Clear the CMOS to Reset BIOS Settings

Clearing the CMOS resolves a no-display condition caused by a BIOS setting or failed overclock that blocks video output. A memory overclock such as an unstable XMP profile, a disabled primary display setting, or corrupted firmware can stop the system before it sends an image.

Clearing the CMOS restores safe defaults. Follow these steps:

1. Unplug the power supply and press the case power button to drain residual charge from the board.
2. Use the CLR_CMOS jumper or button identified in the motherboard manual, holding or bridging it for ten seconds.
3. Remove the CR2032 battery for several minutes as an alternative if the board has no clear jumper.
4. Reconnect power and boot, then re-enter BIOS to confirm the primary display and memory settings before re-applying any overclock.

A system that displays an image only after a CMOS clear had a firmware setting blocking output, often an aggressive memory profile. A board that boots to the firmware screen but then stalls loading the operating system moves to the Windows stuck on loading screen procedure rather than a no-signal fault.

Key Takeaways

• Confirm the monitor input and cable first, since the wrong source or a dead cable is the most common no-signal cause.
• Plug into the graphics card, not the motherboard, because a discrete card disables the board’s video ports.
• Reseat the graphics card and connect PCIe power, as a card without power spins its fans but outputs nothing.
• Reseat and test one RAM stick, because failed memory halts the power-on self-test before video.
• Read POST beeps and debug LEDs to identify the exact component stalling the system.
• Test onboard graphics or another card, then clear the CMOS to isolate a failed GPU or a blocking BIOS setting.

Last Thoughts on a PC With No Display

A PC that turns on but shows no display has power, so the fix targets the display path and the power-on self-test: confirm the monitor input and cable, plug into the graphics card rather than the motherboard, reseat the card and connect PCIe power, test one RAM stick, read the POST beeps and debug LEDs, try onboard or another card, and clear the CMOS. The debug LEDs and beep codes name the failed stage and save guesswork. Readers can continue with the fix for a computer that will not turn on, the fix for a PC stuck on the boot screen, or the hub of common PC problems for related faults.