STATUS_GRAPHICS_TRY_AGAIN_LATER (0xC01E0104) Fix

1. A running app or overlay locked the GPU display pipeline

This is the most common cause. What's actually happening here is that another process — typically a game, video player, or desktop recording tool — has acquired exclusive ownership of the display adapter or a swap chain. When you (or another app) try to change the resolution, refresh rate, or color depth, Windows returns 0xC01E0104 because the resource is busy.

I've seen this most often with:

• Razer Cortex or MSI Afterburner overlays locking the frame buffer.
• OBS Studio with game capture running in the background.
• Discord's hardware acceleration or overlay.
• A stuck fullscreen game that didn't release the swap chain on alt-tab.

The fix: Kill the offending process. Don't guess — use the built-in tool. Open a Command Prompt as admin and run:

tasklist /m dxgi.dll

This lists every process currently holding the DirectX Graphics Infrastructure (DXGI) lock. You'll see something like obs64.exe or Discord.exe. Kill them with:

taskkill /f /im obs64.exe

Swap in the actual process name from your list. Then try your display change again. Nine times out of ten, this clears it without a reboot.

Why step 3 works: DXGI is the Windows component that manages swap chains and mode changes. If a process has an active swap chain, Windows won't let another process touch the adapter. Killing the process forces a release.

2. Corrupted or stale graphics driver state

If no process shows up in the DXGI lock list, the next suspect is the kernel-mode driver hanging onto a resource. This happens after a driver update that didn't fully clean up, or after a Timeout Detection and Recovery (TDR) event — that's the Windows mechanism that resets a hanging driver. But sometimes the reset leaves the device in a broken state.

I've hit this on both Nvidia and AMD systems. On Nvidia, the nvlddmkm.sys driver can get stuck after a TDR. On AMD, amdkmdag.sys is the culprit.

The fix: Force a driver reset without rebooting. The most reliable way is with Device Manager:

1. Press Win + X and select Device Manager.
2. Expand Display adapters, right-click your GPU, and choose Disable device.
3. Wait 10 seconds, then right-click again and Enable device.

This triggers a clean driver reload. The display will flicker once — that's normal. After it comes back, the error should be gone.

If you're on a laptop with switchable graphics (Intel + Nvidia/AMD), also disable and re-enable the integrated GPU. That resets the power-management handoff that sometimes causes the conflict.

Don't bother with the "roll back driver" option — that only helps if the error started right after a driver update. In most cases it's a transient state, not a version problem.

3. Multiple monitors with incompatible refresh rates or HDR conflicts

This one sneaks up on people. When you have two or more monitors running at different refresh rates — say a 144Hz gaming display and a 60Hz secondary — Windows sometimes fails to negotiate a common display mode across all outputs. The error comes back when an app tries to change the primary display's mode and the driver can't lock all outputs simultaneously.

I see this most often when:

• You plug in a second monitor while a game is running fullscreen.
• You toggle HDR on one display while another is playing protected content (like Netflix in Edge).
• You use Nvidia Surround or AMD Eyefinity spanning multiple monitors — those setups are fragile.

The fix: Temporarily disconnect the secondary monitor. Physically unplug the cable or use Win + P to select PC screen only. Change the display mode on the primary monitor, then plug the secondary back in.

If that's not practical, match the refresh rates. Set both monitors to 60Hz in Settings > System > Display > Advanced display. Then try your resolution change. Once it succeeds, you can bump the primary back to 144Hz.

For HDR specifically: Turn off HDR in Windows before changing the resolution. HDR adds metadata negotiations that can lock the display pipeline. Turn it back on after the mode change sticks.

Quick-reference summary table

Of the three, start with #1. It's the quickest to test and the most common cause I've seen across Windows 10 22H2 and Windows 11 23H2. If that doesn't work, move to the driver reset. The multi-monitor issue only applies if you actually have more than one display connected — don't waste time on it if you're on a single monitor.