Fix STATUS_GRAPHICS_INVALID_MONITOR_SOURCE_MODE 0xC01E0322

When This Error Shows Up

You're plugging in a second monitor—maybe a Dell U2723QE or an LG 27GP850—and your screen goes black. Or you're trying to set a custom resolution in NVIDIA Control Panel or AMD Adrenalin, and you get hit with STATUS_GRAPHICS_INVALID_MONITOR_SOURCE_MODE (0xC01E0322). It happens most often after a Windows Update (22H2 is notorious for this) or a GPU driver upgrade. I've seen it on both NVIDIA GeForce RTX 30-series and AMD Radeon RX 6000 cards. The error means Windows can't apply the source mode you're requesting—either the refresh rate, resolution, or timing is borked.

What's Actually Wrong

Under the hood, Windows uses something called the Display Config API. When you change a monitor's mode, it checks the EDID (Extended Display Identification Data) from your monitor. If the requested mode—like 1440p at 165 Hz—doesn't match any valid source mode listed in the EDID, it throws this error. Common triggers: a bad EDID override from a tool like Custom Resolution Utility (CRU), a driver that's half-corrupted, or a monitor that reports weird timing values. It's not your hardware failing—it's the software handshake that's off.

How to Fix 0xC01E0322

Step 1: Roll Back the GPU Driver

This is the fix that works 80% of the time. Open Device Manager (right-click Start), go to Display Adapters, double-click your GPU, click the Driver tab, and select Roll Back Driver. If that's greyed out, you'll need to uninstall the current driver completely. Use DDU (Display Driver Uninstaller) in Safe Mode, then install an older driver—like NVIDIA 546.65 for RTX 30-series or AMD 23.12.1 for RX 6000-series. Avoid the latest drivers for a week or two after a major Windows update—they often clash.

Step 2: Reset Monitor EDID

If the driver rollback didn't help, the EDID might be corrupted or overridden. Unplug your monitor completely. Wait 10 seconds. Plug it back in. Windows will re-read the EDID from the monitor's firmware. This clears any bad custom modes you might've added via CRU or other tools. If you used CRU, open it and click Reset All, then restart.

Step 3: Clear Custom Resolutions

For NVIDIA: Open NVIDIA Control Panel, go to Display > Change Resolution > Customize. Delete any custom modes that match the failing resolution.
For AMD: Open AMD Adrenalin, go to Gaming > Display > Custom Resolutions. Remove the problematic mode.
For Intel: Open Intel Graphics Command Center > Display > Custom Resolutions. Same deal.

After clearing, restart your PC and try setting the mode again from scratch.

Step 4: Change Display Timing Manually (Advanced)

This is for folks who need a specific resolution that the monitor supports but Windows won't let you set. Download CRU. Before you do anything, back up your current EDID by clicking Export in the main window. Then add a new detailed resolution with the exact horizontal and vertical timing from your monitor's spec sheet. For example, for 2560x1440 at 144 Hz, set the total horizontal pixels to 2720 and vertical lines to 1481. Save, run restart64.exe, and reboot. If it fails, restore the backup and try different timing values.

Check This If It Still Fails

If you've done all four steps and the error persists, try a different cable. HDMI 2.1 and DisplayPort 1.4 are picky—bad cables can mess up EDID communication. Also test the monitor on another PC to rule out a firmware issue. On Samsung Odyssey monitors, you sometimes need to update the monitor's firmware itself. Finally, check your motherboard BIOS for any GPU-related settings like "ReBAR" or "Above 4G Decoding"—turning them off can resolve weird display handshake errors. If nothing works, a clean install of Windows 10 or 11 (keeping your files) will flush any corrupted display subsystem files that refuse to go away. I've had to do that twice in six years—it's a last resort, but it works.