STATUS_GRAPHICS_PRESENT_MODE_CHANGED (0xC01E0005) — Fix in 2 Minutes
Annoying DirectX error when game or app detects display mode changed mid-render. Real fix is disabling fullscreen optimizations.
Yeah, this one's annoying as hell. You're in the middle of a game or running some fullscreen app, and bam — it either crashes to desktop or just freezes. And the error log says nothing helpful. But I've seen this dozens of times. Here's the fix.
The Fix: Kill Fullscreen Optimizations
Windows 10 and 11 have this feature called "Fullscreen Optimizations" that tries to blend fullscreen and windowed modes. For most modern games it's fine. But for anything using older DirectX or certain rendering pipelines, it causes exactly this error. The fix is simple.
- Right-click the .exe file of the game or app that's crashing. Go to Properties.
- Click the Compatibility tab.
- Check the box that says Disable fullscreen optimizations.
- Click Apply, then OK.
- Launch the app again. Should work.
Had a client last month whose entire art department couldn't run a 3D visualization tool because of this. One checkbox fix. Two minutes. That's it.
Why This Works
The error 0xC01E0005 (STATUS_GRAPHICS_PRESENT_MODE_CHANGED) means DirectX was told to present a frame, but between when the app asked for the swap chain and when it actually submitted the frame, someone — usually Windows' compositor — changed the display mode. That messes up the buffer chain, and DirectX throws this error as a hard fail.
Fullscreen optimizations are the biggest culprit because they let Windows inject its own compositing between the app and the GPU. Disabling them forces the app to run in true exclusive fullscreen mode, where it owns the display pipeline completely. No mode changes mid-frame, no error.
Less Common Variations
Multiple Monitors
If you run the app on a secondary monitor with different refresh rate or resolution scaling, this error can pop. Same fix: disable fullscreen optimizations on that app's .exe. Also check that all monitors use the same scaling setting (100% is safest).
Game Mode Interference
Windows Game Mode can trigger this too. Turn it off in Settings > Gaming > Game Mode. Set it to Off. Game Mode sometimes overrides display settings mid-session, especially if you alt-tab.
NVIDIA/AMD Driver Overlays
GeForce Experience overlay, AMD Adrenalin overlay, Discord overlay — all can cause this. Disable overlays one by one to find the culprit. For NVIDIA: open GeForce Experience, click the gear icon, toggle "In-Game Overlay" off. For AMD: open Adrenalin, click the gear, go to General, toggle "In-Game Overlay" off.
Windows 11 HDR Auto Switch
Windows 11's Auto HDR can trigger a display mode change when a game starts. Turn off Auto HDR in Display Settings > HDR > Auto HDR = Off. Also disable "Automatically manage color for apps" in the same screen.
Prevention
- Keep your GPU driver updated. Old drivers don't handle mode changes well. But don't update mid-session; do it cleanly after a reboot.
- Avoid messing with resolution or refresh rate while an app's running. I've seen people try to hot-swap monitors and this error is the result.
- Run the app as administrator. Sometimes Windows denies the app exclusive mode access. Right-click the .exe, Properties, Compatibility, check "Run this program as an administrator".
- Use borderless windowed mode instead of fullscreen. This avoids the mode change entirely. Only do this if disabling fullscreen optimizations doesn't work — borderless can add input lag.
Bottom line: this error is almost always Windows trying to be clever with your display. Turn off the cleverness. Done.
Was this solution helpful?