Quick answer: Reinstall your graphics driver. If it still fails, delete the monitor's driver from Device Manager and reboot.
This error is a graphics stack failure, not a hardware problem. Windows tried to read the monitor's EDID (the data block that tells the GPU what resolutions and timings the monitor supports) and got garbage back. The culprit here is almost always a corrupted driver extension or a leftover monitor profile from an old monitor. I've seen it after Windows updates, after switching between integrated and discrete GPUs, and after plugging the same monitor into a different port. Don't bother reseating cables — that rarely helps.
Fix 1: Reinstall your graphics driver
The easiest fix. This resets the entire display stack, including any bad monitor descriptors cached in memory.
- Open Device Manager (Win+X, select Device Manager).
- Expand Display adapters.
- Right-click your GPU (e.g., NVIDIA GeForce RTX 3060, AMD Radeon RX 6700 XT) and select Uninstall device.
- Check the Delete the driver software for this device box if it appears (on Windows 10/11 it usually does).
- Click Uninstall. Don't reboot yet.
- Go to Action menu, select Scan for hardware changes. Windows will reinstall a basic driver automatically.
- Reboot. Windows will pick up the monitor again and re-read the EDID.
Almost always this clears it. If you're running a custom driver from NVIDIA or AMD, you might want to do a clean install with their installer (check the “Clean installation” box). But the built-in driver works fine for most cases.
Fix 2: Delete the monitor's driver
If the graphics driver reinstall didn't work, the monitor driver itself is corrupted. This is common when you've used a custom monitor profile or the monitor's PnP INF file got mangled.
- Open Device Manager again.
- Expand Monitors.
- You'll see something like Generic PnP Monitor or the actual brand name (e.g., Dell U2720Q, LG UltraGear).
- Right-click it, select Uninstall device. Don't check the delete driver box (though you can, it doesn't matter).
- Reboot. Windows will re-detect the monitor and install a clean descriptor.
Fix 3: Clear the EDID cache in the registry
If you're still stuck (rare, but happens), the bad EDID might be cached in the registry. This is a bit more hands-on but still safe.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Configuration- Open Regedit as admin.
- Navigate to that key. You'll see subkeys with long names (copies of your monitor's configuration).
- Delete the entire Configuration key. Don't worry — Windows rebuilds it on next boot.
- Reboot and see if the error is gone.
Also check HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\ScaleFactors — if it exists, delete it too. That's another common cache location.
Alternative: Update motherboard BIOS / GPU firmware
If the error appeared after a hardware change (new GPU, new monitor), a BIOS update sometimes helps. The EDID is read through the GPU's firmware, and a buggy firmware can misread it. Check your motherboard manufacturer's site (e.g., ASUS, MSI, Gigabyte) for the latest BIOS. Also update the GPU firmware if the vendor provides it — NVIDIA and AMD rarely do, but it exists for some cards.
Prevention tips
- When unplugging monitors, use the Disconnect option in Windows (Settings > System > Display > Disconnect this display) instead of just yanking the cable. It sends a clean EDID release signal.
- If you switch between different monitors often, don't let Windows install vendor-specific monitor drivers. Generic PnP Monitor works for 99% of users and avoids conflicts.
- Keep your GPU driver up to date, but don't install every release — stick to stable versions, not beta or hotfix builds.
That's it. Reinstall the driver, nuke the monitor profile, and you're back in business. I've never seen this error survive all three steps. If it does, you're looking at a hardware-level EDID issue — check if your monitor has a firmware update (DSLR monitors like BenQ and Eizo do this).