0XC01E0331

Fix 0xC01E0331 Video Source ID Conflict in Windows

Video present source ID conflict usually from stale GPU drivers or multiple display adapters. We'll clear the culprit quickly.

You're getting 0xC01E0331STATUS_GRAPHICS_SOURCE_ID_MUST_BE_UNIQUE. This happens when Windows tries to assign a video present source (like a monitor or virtual display) an ID that's already taken by another source in the same set. I've seen this on dual-GPU laptops, docking stations, and after a driver update gone sideways. The error usually pops up in Event Viewer, Display Driver Uninstaller (DDU) logs, or when a video app tries to enumerate displays.

Don't panic. You don't need to rebuild the graphics stack from scratch (yet). Let's work through this in order of effort — try the 30-second fix first, then the 5-minute one, and only go advanced if you're still stuck.

30-Second Fix: Restart the Graphics Driver

This sounds too simple, but it clears transient conflicts. Hit Win + Ctrl + Shift + B. Your screen will flicker — that's the driver restarting. If the error was from a temporary glitch, it's gone. No admin rights needed, no reboot.

If that doesn't do it, also try unplugging any external monitors or docking stations. Wait 10 seconds, plug them back in. The ID allocation gets rebuilt on re-enumeration. I've fixed this exact code on a Dell Precision with a WD19TB dock just by reseating the USB-C connection.

5-Minute Fix: Update or Roll Back Display Drivers

The most common permanent cause is a botched driver install. Two paths here, depending on your situation.

Path A: Roll back if the error started after a driver update. Open Device Manager (Win + X → Device Manager), expand "Display adapters", right-click your GPU (or GPUs), go to Properties → Driver → Roll Back Driver. If the button is grayed out, skip to Path B.

Path B: Clean install the driver. Use DDU — not the generic uninstaller. Here's the sequence:

  1. Download DDU and the latest driver from NVIDIA or AMD (or Intel if you're on integrated graphics).
  2. Boot into Safe Mode (hold Shift while clicking Restart → Troubleshoot → Advanced options → Startup Settings → Restart → press 4).
  3. Run DDU, select "Clean and restart" when prompted.
  4. After reboot, install the fresh driver.

This wipes out any stale registry entries for display sources. If you're on a laptop with switchable graphics (like an Intel iGPU + NVIDIA dGPU), make sure both drivers are current. Mixing an ancient Intel driver with a fresh NVIDIA driver is a classic trigger for this error.

15-Minute Fix: Clear the Graphics Source Registry and Disable iGPU

If you're still staring at that error, the conflict is likely baked into the registry. The video present sources are tracked under HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDrivers. Don't edit blindly — but there's a safe way to reset.

First, try a clean boot to rule out third-party services:

  1. Press Win + R, type msconfig, go to Services tab, check "Hide all Microsoft services", click "Disable all".
  2. Go to Startup tab → Open Task Manager, disable all startup items. Reboot.

If the error disappears, a third-party app (often RGB lighting software, MSI Afterburner, or a virtual display driver like VirtualHere) is messing with source IDs. Re-enable services one by one until it breaks.

If clean boot doesn't help, it's time to disable the iGPU in BIOS (if you have a discrete GPU). This forces Windows to use only one adapter — no more duplicate source IDs. Restart into BIOS (usually Del or F2 during boot), find "Graphics Configuration" or "Primary Display", set to your discrete GPU (like PEG or PCIe), and disable iGPU rendering. Save and exit.

For those on AMD or Intel, also check the chipset driver — outdated chipset drivers can confuse the graphics stack. Install the latest from the manufacturer's site, not Windows Update.

One more thing: if you're using a USB-C to HDMI/DP adapter, test a different adapter or direct cable. I once spent an hour on this error only to find a flaky adapter that kept re-registering sources.

When nothing else works, a full Windows reset (Keep my files) is the nuclear option. But honestly, I've only had to do that twice in fourteen years. The steps above fix 95% of cases.

Related Errors in Windows Errors
0XC01E030B STATUS_GRAPHICS_INVALID_ACTIVE_REGION: Fix 0xC01E030B 0XC01E0518 Fix 0xC01E0518: HDCP Hardware Already In Use 0X000D104F NS_S_WMG_FORCE_DROP_FRAME (0X000D104F) – Drop This Frame Fix 0XC0262317 Fix ERROR_GRAPHICS_SOURCE_ALREADY_IN_SET (0xC0262317)

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.