Monitor 'Out of Range' Fix After Resolution Change

Out of Range means your GPU is sending a signal your monitor can't handle. Here's how to get back to a working resolution, including the no-display trick.

You bumped the resolution to 2560x1440 or nudged the refresh rate up to 144Hz, the screen went black, and now the monitor's OSD is flashing "Out of Range" or "Signal Out of Range." Sometimes it's the opposite — you plugged a laptop into a conference room display and Windows auto-picked a mode the panel can't take. Either way the machine boots fine, you just can't see anything. The good news: your GPU and monitor are probably both healthy. Someone just asked one of them for a mode the other won't do.

What 'Out of Range' Actually Means

The monitor has a tiny controller chip that scans the incoming signal and checks two things: the horizontal/vertical frequency (kHz/Hz) of the timing, and the pixel clock (MHz). If any value falls outside what the panel's EDID advertises as supported, the controller shuts off the panel and throws the OSD warning. It's a protection mechanism, not a failure.

Windows, meanwhile, doesn't always care about EDID. It'll happily let you pick a mode from the generic list, or a game will set a fullscreen exclusive mode the panel can't lock onto, or a KVM switch will strip EDID and the GPU falls back to something weird. Result: the GPU outputs a valid signal that the monitor simply refuses.

Get Your Display Back First

You can't fix this from the normal desktop because you can't see it. Force Windows into a safe, low-resolution mode.

Hard power off. Hold the power button for 10 seconds. Don't just hit restart — the GPU state needs to clear.
Boot into Low-Resolution Video mode. Power on and immediately start tapping F8 (Win 7/older) or, for Windows 10/11, interrupt the boot three times in a row by holding the power button during the spinning-dots phase. That gets you to the Recovery Environment.
In WinRE pick Troubleshoot → Advanced options → Startup Settings → Restart. When the list appears, press 3 or 4 to enable Low-resolution video or Safe Mode.
Once you're on the desktop at 640x480 or 800x600, right-click the desktop → Display settings. Drop the resolution to something conservative like 1920x1080 at 60Hz. Apply, then reboot normally.

If you can't get to Safe Mode — say the POST screen never appears either — try a different cable first. DisplayPort and HDMI sometimes negotiate differently than DVI, and a passive DP-to-HDMI adapter can flat-out lie to the GPU about EDID.

Reset the Driver's Stored Mode

Windows remembers your last display config per monitor. If you keep getting dumped back into the bad mode, nuke it.

Boot into Safe Mode as above.
Open Device Manager → Display adapters → right-click your GPU → Uninstall device. Tick "Delete the driver software for this device."
Reboot. Windows installs the basic Microsoft Display Adapter at 1024x768. Now you're safe.
Reinstall the proper GPU driver (NVIDIA Studio/Game Ready, AMD Adrenalin, or Intel Arc/Iris). Don't grab it from Windows Update — go to the vendor.

For NVIDIA specifically, you can also force a mode from the driver using nvidia-smi or by editing the CustomResolutionUtility (CRU) profile — but only do that once you can see the screen.

If You Can Boot Normally But Only in VGA Mode

Sometimes the machine boots fine to a working desktop and the problem is only after the driver loads. That points to a bad EDID handshake. Two things to try:

Unplug and replug the monitor's video cable with both devices powered on. This forces a fresh EDID read.
Get a cheap EDID emulator (like an EVGA or Monoprice dongle) if you're running through a KVM. KVMs are the #1 cause of this in enterprise environments — they cache stale EDID and the GPU never learns the real panel's limits.

Prevent It Next Time

Before you go jacking the refresh rate to 165Hz on a panel rated for 144, check the monitor's spec sheet or the OSD's Info menu — it usually lists the exact supported modes. Also stop using "Generic PnP Monitor" as the display name in Device Manager. If Windows shows that instead of your actual model, EDID isn't being read and you're flying blind. Install the manufacturer's INF or just replace the cable with a proper VESA-certified one.

Still Out of Range?

If you've reset the driver, tried both HDMI and DisplayPort, booted into Safe Mode, and it still throws the error, the panel is either failing or the controller board inside is toasted. Displays do fail this way — the backlight stays on, the OSD works, but the timing decoder dies. Test the monitor on another PC. If it errors there too at known-good settings, replace it. Don't waste a Saturday chasing a GPU issue when the panel is the problem.