Fix STATUS_GRAPHICS_MODE_NOT_IN_MODESET (0XC01E034A) Error

I know this error is infuriating

You're staring at a black screen or a crash, and Windows just threw STATUS_GRAPHICS_MODE_NOT_IN_MODESET (0XC01E034A) in your face. It happens most often when you try to switch to a custom resolution in a game or app, or when a monitor wakes from sleep and the GPU driver can't find the mode in its internal list. The good news: you don't need to reinstall Windows. Let's fix it.

The real fix: reset the display driver's mode cache

This error means the driver's mode set—the list of supported resolutions and refresh rates—got corrupted or out of sync with your monitor's EDID (the data your monitor sends about what it supports). The fastest way to clear that cache is a full driver reinstall using DDU (Display Driver Uninstaller). Skip the normal uninstall—it leaves junk behind.

1. Download DDU from Guru3D (the official source).
2. Boot Windows into Safe Mode—hold Shift while clicking Restart, then go to Troubleshoot → Advanced Options → Startup Settings → Restart, then press 4 for Safe Mode.
3. Run DDU. Select your GPU vendor (NVIDIA, AMD, or Intel) and choose Clean and restart.
4. After the reboot, Windows will install a generic driver. Don't let it—use the NVCleanInstall option for NVIDIA or the manufacturer's clean install option for AMD. This strips all leftover registry entries and mode lists.
5. Install the latest driver from your GPU vendor's site. Don't use Windows Update here—it's often outdated.

This works because DDU wipes the HKLM\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318} registry branch completely, which is where Windows stores corrupted mode sets. I've seen this fix the error on Windows 10 22H2 and Windows 11 23H2 after a single clean pass.

Why it worked (the technical bit)

The error code 0xC01E034A maps to STATUS_GRAPHICS_MODE_NOT_IN_MODESET in the DirectX graphics kernel (dxgkrnl.sys). When you request a mode—say 1920x1080 at 144Hz—the graphics stack checks the monitor's EDID and the driver's cached mode list. If those don't match (e.g., the driver has stale entries from a previous monitor or an overclocking tool like CRU), the API returns this error. Resetting the driver forces a fresh enumeration of the monitor's EDID and rebuilds the mode list from scratch.

Less common variations of the same issue

Sometimes the driver isn't the culprit—the monitor itself sends a bad EDID. Here's how to spot that:

• Custom Resolution Utility (CRU) leftovers: If you've used CRU to add custom modes, removing the driver won't clear those. Run CRU, click Reset-all, then reboot.
• Bad HDMI/DP cable: A flaky cable can corrupt EDID reads. Try a different cable—DisplayPort 1.4 or HDMI 2.1 certified cables are safer.
• Multiple monitors with mismatched timings: If you extend to a second monitor with different specs, the GPU driver may fail to build a combined mode set. Disconnect the extra monitor, fix the primary, then reconnect.
• Virtual monitor software: Apps like Moonlight or Parsec can inject fake modes. Uninstall them temporarily to test.

If none of those work, check the Windows Event Viewer under System logs for Display source events. You'll often see an event ID 4101 or 0 before the error hits—that's the GPU crashing and resetting the mode set.

How to prevent this from coming back

Three things stop this error cold:

1. Never use Windows Update to install GPU drivers. Always grab them from NVIDIA, AMD, or Intel. Windows Update often pushes older builds that don't match your monitor's EDID.
2. If you use CRU, always back up the original EDID before editing. One corrupted override and you're back to square one.
3. Set a fixed resolution in your game's config file instead of relying on in-game mode switches. For example, in %LOCALAPPDATA%\YourGame\Settings\config.ini, set ResolutionX=1920 and ResolutionY=1080 manually—this bypasses the mode set API entirely.

That's it. You've got your display back. If this didn't work, your GPU hardware might be failing—try swapping in a known-working card to isolate it. But 9 times out of 10, DDU does the job.