Monitor Says No Signal: 3 Fixes That Actually Work

Most 'No Signal' errors come from a dead cable, a wrong input, or a driver glitch. Here's how to fix each in minutes.

1. The Cable Is Loose or Dead (The Real Culprit)

Before you touch any settings, unplug both ends of the video cable — HDMI, DisplayPort, DVI, whatever you're using. Wait two seconds. Plug them back in. Push firmly until you hear the click.

Loose cables are the #1 cause of "No Signal" on monitors, especially after someone bumped the desk or moved the PC case. I've seen it a hundred times: the HDMI connector looks seated, but it's half a millimeter out. That's enough to kill the handshake between the GPU and the display.

If re-seating doesn't do it, swap the cable. Don't bother testing it with a multimeter — just grab a known-good cable. HDMI and DisplayPort cables fail more often than people think, particularly the cheap ones. If you're running a 144Hz or 4K setup, make sure the cable is rated for that bandwidth. A cable that's fine for 1080p60 can flake out at higher refresh rates and show random dropouts that look like a GPU problem.

Quick check for bent pins

For VGA or DVI cables, inspect the pins. One bent pin and you'll get no signal or a corrupted image. I've fixed more than one "dead" monitor by straightening a pin with a small flathead screwdriver. If you see any bent pins, don't try to bend them back — replace the cable. The connector is already damaged.

2. The Monitor Is on the Wrong Input

This sounds dumb, but it's the second most common cause. Most modern monitors have multiple ports — HDMI 1, HDMI 2, DisplayPort, maybe VGA. If you're plugged into HDMI 1 but the monitor is showing HDMI 2, you get nothing but a black screen with "No Signal" or "HDMI 2 No Signal" in the corner.

Press the Input or Source button on the monitor's bezel or remote. Cycle through the options. Watch the screen. When it hits the right input, the image pops up immediately.

Some monitors let you rename inputs. I've seen people rename HDMI 1 to "PC" and then forget which physical port that actually maps to. Don't do that. Leave them as defaults.

Also — if you're using a KVM switch or a docking station, that's another layer of input routing. Unplug the KVM/dock and connect the monitor directly to the PC. If it works, the KVM is the problem. I've had KVMs where the EDID handshake fails after the PC sleeps, and the monitor just sits there with no signal until you power-cycle the KVM.

3. The Display Driver Crashed (The Sneaky One)

If the cable and input are fine, the next suspect is the graphics driver. This happens more on Windows 10 and 11 than people admit. The driver can glitch out during a game or after waking from sleep, leaving the screen black with no signal. The PC is still running — you can hear fans, maybe music — but the monitor's dead.

The fast fix is a hard reset of the driver. Press Win + Ctrl + Shift + B. That forces the GPU to reinitialize. You'll hear a beep and the screen should flicker back on. It works about 60% of the time.

If that doesn't do it, reboot the PC. But here's the thing — a full shutdown and cold boot is different from a restart on Windows. Restart does a real hardware reset. Shutdown with "Fast Startup" only does a partial reset. So always test with a proper restart.

Still happening? Then update or roll back the driver. If this started after a recent Windows update or a GPU driver update, roll back the driver first. In Device Manager, find your GPU under Display Adapters, right-click, go to Properties, then Driver tab, and click Roll Back Driver. If that's grayed out, download the previous driver from the GPU vendor's site (NVIDIA, AMD, or Intel). Don't bother with a generic driver from Windows Update — those are rarely the fix.

Also check if you've got two displays running. Sometimes the monitor's EDID is misread after a driver crash, and the GPU thinks the monitor is a different resolution. If you've got a second monitor, plug it in, then set the primary monitor's resolution to its native one and unplug the second.

Quick Reference Table

CauseDiagnosisFix
Loose or bad cableMove the cable, screen flickers or drops outRe-seat or replace the cable
Wrong input selectedMonitor shows "No Signal" on one input but not othersPress Input/Source button to cycle
Driver crashPC is on but screen went black after sleep or gameWin+Ctrl+Shift+B, then restart, then update/rollback driver

That's the whole playbook. Work through these in order and you'll fix 95% of no-signal issues. If none of these help, you're into deeper territory — try a different monitor, test the GPU in another slot, or start suspecting the motherboard. But don't start there. The cable and input fixes are free and take two minutes.

Related Errors in Hardware – Monitors
Monitor flickers on macOS Sequoia after sleep wake cycle Monitor 'No Signal' Error — Quick Fixes That Actually Work Monitor flickers when HDR is turned on — real fix Monitor keeps going black for a few seconds – fix that actually works

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.