STATUS_GRAPHICS_VIDPN_SOURCE_IN_USE (0xC01E0342) Fix

What triggers this error

You plug in a second monitor, switch to Extend mode, and instead of seeing your desktop you get a black screen or a "No signal" message. Check Device Manager or Event Viewer and you find STATUS_GRAPHICS_VIDPN_SOURCE_IN_USE (0xC01E0342).

This error pops up most often on laptops running Windows 11 22H2 or Windows 10 21H2 with Intel Iris Xe or UHD graphics, especially after waking from sleep or when you've been hot-plugging monitors without restarting. The core problem: the display source (the video output from the GPU) is already assigned to another display path and won't release for the new one.

Fix 1: Restart the graphics driver (works 60% of the time)

Don't restart the whole computer. Just restart the graphics driver. This forces Windows to release and reallocate all video sources.

1. Press Win + Ctrl + Shift + B at the same time.
2. You'll hear a short beep and the screen will go black for about 1-2 seconds.
3. After the screen comes back, your second monitor should wake up and show your desktop.

What to expect: If the error was just a stuck allocation, the hotkey restarts the driver cleanly and your second monitor snaps on. If your second monitor still shows "No signal" after 5 seconds, move on to Fix 2.

Fix 2: Disable and re-enable the display adapter (works 25% of the time)

When the hotkey doesn't cut it, do this in Device Manager.

1. Right-click the Start button and select Device Manager.
2. Expand Display adapters. You'll see one or two entries there. If you have Intel + NVIDIA or Intel + AMD, you'll see both.
3. Right-click your integrated graphics (usually Intel UHD or Iris Xe) and select Disable device.
4. A warning pops up — click Yes. Your screen might flicker or go black for 3-5 seconds.
5. Click Yes again on any confirmation dialogs.
6. Once the screen settles, right-click the same adapter and select Enable device.
7. Your screen flashes again. After it comes back, check your second monitor.

Why this works: Disabling the adapter forces Windows to release all resources attached to that GPU. Re-enabling it rebuilds the entire display pipeline from scratch. This clears the stuck VIDPN_SOURCE_IN_USE flag.

Fix 3: Update or roll back the graphics driver (works 15% of the time)

If the first two fixes didn't help, the driver itself is likely buggy. Here's how to handle both scenarios.

Scenario A — you're on an old driver (2023 or earlier)

Old Intel drivers have a known bug where the source-to-target mapping gets corrupted after a few display hot-plugs. Update to the latest version from Intel's site, not from Windows Update.

1. Go to Intel Driver & Support Assistant.
2. Download and run the installer. It will scan your system and find the correct driver.
3. Install the latest driver — reboot when prompted.
4. After reboot, the error should be gone.

Scenario B — you're on a recent driver (2024 or newer)

Sometimes a new driver introduces the bug. Roll back to a previous version.

1. Open Device Manager and expand Display adapters.
2. Right-click your Intel graphics and choose Properties.
3. Go to the Driver tab and click Roll Back Driver.
4. If the button is grayed out, you don't have a previous driver saved. In that case, download the driver from Intel's archive (choose a version from 3-6 months ago).
5. Install that older driver manually — choose Clean Installation if prompted.
6. Reboot and test.

Real example: I had a Dell Latitude 5430 with Intel Iris Xe that threw 0xC01E0342 every time I docked and undocked twice. Rolling back from driver 31.0.101.4255 to 31.0.101.4032 fixed it completely.

Quick-reference summary table

Start with Fix 1. If that fails, go straight to Fix 2. Only touch the driver if the first two don't work. Most people are back up and running in under 5 minutes.