0XC01E0341

Fix STATUS_GRAPHICS_NO_DISPLAY_MODE_MANAGEMENT_SUPPORT (0XC01E0341)

Windows Errors Intermediate 👁 4 views 📅 Jun 10, 2026

This error means Windows lost control of display mode switching. The fix is resetting the graphics driver stack via Device Manager.

This error is a real pain — I know

You're in the middle of something and Windows throws 0xC01E0341 at you. The system can't grab the display mode management interface, so your screen might freeze, go black for a second, or just refuse to switch resolutions. I've seen this on Dell XPS 15s with Intel Iris Xe graphics after a Windows update, and on custom gaming rigs with NVIDIA RTX 3080s when you plug in a second monitor. The root cause is almost always a corrupted or wedged graphics driver stack.

Straight to the fix: Reset the GPU driver stack

Open Device Manager (right-click the Start button, select Device Manager). Expand Display adapters. Right-click your primary GPU — usually Intel(R) UHD Graphics, AMD Radeon, or NVIDIA GeForce — and choose Disable device. Confirm the warning. Your screen will flicker or go black for a couple seconds. Then right-click the same GPU and choose Enable device. That's it. The error should vanish.

If you have two GPUs (like Intel + NVIDIA), disable and re-enable both. Do the Intel one first, then the discrete card. The order matters because Windows uses the integrated GPU to manage display outputs on most laptops.

Why this works

The error code 0xC01E0341 means the DXGKDDI_QUERYADAPTERINFO call failed to return a display mode management interface. That interface is what DirectX and the Windows Display Driver Model (WDDM) use to coordinate resolution changes, multi-monitor setups, and GPU power transitions. When the driver stack gets stuck — often after a failed mode switch or a sleep/resume cycle — Windows can't talk to the graphics adapter properly. Disabling the device forces the kernel to unload the driver, free all resources, and reset the GPU's state. Re-enabling it rebuilds the interface fresh. It's a clean slate.

This tripped me up the first time too. You might think reinstalling drivers is the answer, but 9 times out of 10, a simple disable/enable cycle does it in under 30 seconds. Don't waste time with DDU or full driver removal unless this fails.

Less common variations & extra steps

If the disable/enable trick doesn't work, try this next: In Device Manager, click View then Show hidden devices. Under Display adapters, you'll often see ghost entries — grayed-out GPUs from old driver versions or disconnected monitors. Right-click and uninstall every ghost GPU. Then restart your PC. This clears stale mode management handles that can block the active driver.

Another scenario: The error shows up when you plug in a USB-C dock with DisplayPort Alt Mode. That's common on Lenovo ThinkPads and HP EliteBooks. The dock creates a new display path, but the driver can't negotiate the mode management handoff. Solution: Unplug the dock, run the disable/enable cycle on the internal GPU, then reconnect the dock. Windows will rebuild the display topology correctly.

If you're on Windows 11 and the error happens during a screen recording or game capture (like OBS or GeForce Experience), it's often tied to hardware-accelerated GPU scheduling. Go to Settings > System > Display > Graphics > Change default graphics settings and turn off Hardware-accelerated GPU scheduling. Reboot. This bypasses a known WDDM 3.0 bug that trips the mode management interface.

Prevention going forward

Keep your GPU drivers current, but don't install every optional update from Windows Update. Stick to the driver from your laptop manufacturer's site or the official GPU vendor (NVIDIA, AMD, Intel). Windows Update likes to push generic versions that can bork the display mode stack. Also, avoid hot-plugging monitors while your system is under heavy GPU load — like during gaming or rendering. That's a surefire way to trigger 0xC01E0341. If you use a dock, connect it before you boot your machine, not after.

One last thing: If you run multiple monitors with different refresh rates (e.g., 60 Hz + 144 Hz), set both to the same refresh rate in display settings. Mismatched rates can stress the mode management interface over time. It's not a fix for the current error, but it'll stop it from coming back.

Was this solution helpful?