Monitor 'Signal Not Found' when waking from sleep

Hardware – Monitors Beginner 👁 13 views 📅 May 27, 2026

Fix that black 'No Signal' screen when your monitor won't wake from sleep. Most people try cables, but the real fix is usually a power setting or GPU driver trick.

You step away from your desk for a meeting, come back, and move your mouse. The PC wakes up—you hear fans spin—but your monitor stays black, showing that dreaded "No Signal" or "Check Cable" message. This happens on Windows 10 and 11, with both HDMI and DisplayPort cables, and on monitors from Dell, LG, Samsung, and ASUS. I've seen it trigger most often after the monitor has been asleep for more than 30 minutes, or when you have multiple monitors and only one wakes up.

What's actually going on?

The root cause isn't a dead cable or a dying monitor—most of the time. It's a handshake failure between your graphics card and the monitor's power management. When the monitor goes into deep sleep (VESA's DPMS standard), it drops the signal line. Your GPU doesn't realize the monitor is awake again, so it doesn't re-send the video signal. This is especially common with DisplayPort, which uses a more aggressive link training protocol than HDMI.

The fix that works 90% of the time

Skip the cable-swapping dance. Here's what actually fixes it.

Step 1: Force a full power cycle

  1. Unplug the monitor's power cable from the wall or surge protector.
  2. Press and hold the monitor's power button for 15 seconds. This drains any residual charge in the capacitors.
  3. Wait 30 seconds, then plug it back in and power it on.

I know that sounds like the IT guy's "turn it off and on again" cliché. But in this case, it forces the monitor to re-initiate the EDID handshake from scratch. Works on Dell U2719D and Samsung Odyssey G7 models I've fixed.

Step 2: Change Windows power plan settings

  1. Open Control Panel > Power Options.
  2. Click Change plan settings next to your active plan.
  3. Click Change advanced power settings.
  4. Expand PCI Express > Link State Power Management.
  5. Change the setting to Off for both On battery and Plugged in.

This stops Windows from cutting power to your GPU's PCIe link when the monitor sleeps. The trade-off is a tiny power draw increase—maybe a few dollars a year. Worth it to stop the black screen.

Step 3: Disable fast startup (Windows 10/11)

  1. Open Control Panel > Power Options.
  2. Click Choose what the power buttons do.
  3. Click Change settings that are currently unavailable.
  4. Uncheck Turn on fast startup (recommended).
  5. Click Save changes and restart.

Fast startup is a hybrid shutdown that can mess up GPU driver state. I turn it off on every machine I set up—it's the first thing I check when someone says "monitor won't wake."

If it's a specific graphics card: Nvidia or AMD

For Nvidia users

  1. Right-click desktop > Nvidia Control Panel.
  2. Under Display, click Set up multiple displays.
  3. Check the box for your monitor if it's greyed out—sometimes Windows marks it as off.
  4. Open Nvidia Control Panel > Manage 3D settings > Power management mode and set it to Prefer maximum performance.

For AMD users

  1. Open AMD Radeon Software.
  2. Go to Settings > Display.
  3. Disable Display Overclocking if enabled.
  4. Switch Power Saving features to Off.

If it still fails: Check the cable

I said skip cable-swapping, and I meant it—until after you try the steps above. If the black screen persists, use your monitor's menu (the physical buttons) to manually switch the input source from HDMI to DisplayPort and back. Sometimes the monitor is just sitting on the wrong input. Also, try a different cable—specifically, a certified DisplayPort cable (they're stricter about bandwidth). A plain HDMI 1.4 cable can cause this issue on 4K monitors. I've had luck with Club3D's CAC-1085 DisplayPort 1.4 cable.

One last check: Monitor firmware

Some monitors got firmware updates that fixed sleep wake issues. Check your manufacturer's support site: Dell has a firmware updater for the S2721D series, LG has one for the 27GP850. If you're on an older firmware, updating can solve the handshake problem entirely. It's rare, but I've seen it work.

Was this solution helpful?