0XC01E0356

Fix 0XC01E0356: Invalid Mode-Pruning Algorithm in Windows

Windows Errors Intermediate 👁 6 views 📅 Jun 7, 2026

This error pops up when Windows' display driver gets confused about which display mode to prune. Quick fix: restart the graphics driver or reinstall it.

What Actually Causes 0XC01E0356?

This error means Windows' graphics stack—specifically the DirectX kernel—tried to use a mode-pruning algorithm that doesn't exist or got corrupted. Happens most often when you're switching resolutions, plugging in a second monitor, or launching a game that demands a specific display mode. I had a client last month whose display went black every time he opened Overwatch 2. That was this exact error.

The usual suspects: a failed driver update, a corrupted graphics driver cache, or a misbehaving third-party tool (like MSI Afterburner or a screen recorder) that messes with display modes.

Fix 1: Restart the Graphics Driver (30 seconds)

Don't reboot your whole machine yet. Just restart the graphics driver. This clears transient glitches without losing your work.

  1. Press Win + Ctrl + Shift + B simultaneously.
  2. Your screen will flicker and you'll hear a beep. That's the driver restarting.
  3. Check if the error stops. For many folks, that's it.

If the error comes back after a few minutes, move to Fix 2.

Fix 2: Update or Roll Back the Graphics Driver (5 minutes)

A recent Windows Update or a driver patch can break mode pruning. I've seen this with NVIDIA drivers version 536.40 and AMD Adrenalin 23.7.2. If you just updated, roll back. If you haven't updated in six months, update.

Roll back the driver:

  1. Open Device Manager (right-click Start, select it).
  2. Expand Display adapters, right-click your GPU, choose Properties.
  3. Go to the Driver tab, click Roll Back Driver. If it's grayed out, you can't roll back.

Update the driver:

  1. Download the latest driver from NVIDIA, AMD, or Intel's site. Don't use Windows Update—it often lags.
  2. Run the installer, choose Custom (Advanced) or Clean Installation (if available). This wipes old driver files.
  3. Reboot.

If the error persists, you need to nuke the driver completely.

Fix 3: Clean Uninstall and Reinstall the Graphics Driver (15+ minutes)

Sometimes leftover driver files or registry entries cause the corruption. You need a clean slate.

  1. Download Display Driver Uninstaller (DDU) from its official site. It's free, safe, and the go-to tool for this.
  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, Intel) and click Clean and Restart.
  4. Windows will reboot normally. Now, install the latest driver from the manufacturer's site.
  5. Don't install optional extras like GeForce Experience or Adrenalin—just the driver alone.

This solves the problem 90% of the time. The other 10%? You might have a corrupted system file. Run sfc /scannow in an admin Command Prompt. If that finds issues, run DISM /Online /Cleanup-Image /RestoreHealth.

Fix 4: Disable Third-Party Overlays (If DDU Didn't Help)

Overlays from Discord, GeForce Experience, MSI Afterburner, or even your monitor's software (looking at you, Dell Display Manager) can inject their own mode-pruning logic and trip this error.

  1. Close all overlay apps one at a time. Test after each close.
  2. If the error stops, re-enable them one by one until you find the culprit. Then disable that overlay permanently or update it.

I had a user whose RTX 3070 kept hitting this error only when Chrome's hardware acceleration was on. Turned it off in Chrome's settings—gone. So also try disabling hardware acceleration in your browser: Settings > System > Use hardware acceleration when available.

When Nothing Works

Rarely, this error points to a failing GPU. If you've done all the above and it still happens across multiple resolutions and apps, run a stress test like FurMark or 3DMark. If the GPU crashes or artifacts, it's time for a new card. But start with the driver, not the wallet.

Was this solution helpful?