STATUS_GRAPHICS_NO_ACTIVE_VIDPN 0XC01E0336 Fix

This error is frustrating, I know. Let's cut to the fix.

You're seeing STATUS_GRAPHICS_NO_ACTIVE_VIDPN (0XC01E0336) in your system logs, often when you connect or disconnect an external monitor, or wake your PC from sleep. The VidPN (Video Present Network) manager is the part of the Windows display driver that maps out which display goes where. When it says it doesn't have an active VidPN, it means the handshake between your GPU and monitor failed. The result: a black screen, or your monitor showing "no signal," or Windows forgetting your second screen.

The fix that works in 90% of cases is a clean graphics driver reset. Here's how I do it on Windows 10 and 11.

Try this first: the driver reset

1. Press Win + Ctrl + Shift + B all at once. This is the Windows magic key combo that resets the graphics driver stack without a reboot. You should hear a short beep and see the screen flicker once. If your screen stays black for more than 3 seconds, move to step 2.
2. Still broken? Open Device Manager. The fastest way: press Win + X and select Device Manager from the menu.
3. Find Display adapters and expand it. You'll see your GPU listed there — something like NVIDIA GeForce RTX 3060, AMD Radeon RX 6700, or Intel UHD Graphics 620.
4. Right-click your GPU and choose Disable device. A warning pops up saying disabling will cause the display to go black. Click Yes. The screen will go black for a few seconds, but it'll come back. If it doesn't, wait 10 seconds — the fallback driver kicks in.
5. Right-click the same GPU again and choose Enable device. After clicking enable, you should see the screen flicker once more. That's the driver reloading.
6. Now test your display. Plug in your external monitor if you have one, or just check the primary screen. The error should be gone.

Why this works: disabling the device forces Windows to unload the entire display driver stack, including any broken VidPN state. Re-enabling it reloads the driver fresh, and the VidPN manager starts from scratch. It's like turning the display adapter off and on again, but without shutting down your PC.

If the reset didn't work: DDC/CI and monitor driver

Sometimes the problem isn't your GPU driver — it's the monitor itself not reporting its capabilities correctly. Many monitors use DDC/CI (Display Data Channel Command Interface) to tell the GPU what resolutions and timings they support. If that gets corrupted, the VidPN manager can't build a valid path.

1. Unplug your monitor from the PC. Wait 15 seconds.
2. Press the monitor's physical power button to turn it off. Wait 30 seconds.
3. Turn the monitor back on.
4. Reconnect the cable — HDMI, DisplayPort, or whatever you're using. After reconnecting, Windows should detect it as a new device and renegotiate the EDID.
5. If that fails, go to Device Manager again. Look under Monitors (not Display adapters). Right-click your monitor and choose Uninstall device. Check the box that says "Delete the driver software for this device" if it appears.
6. Unplug and replug the monitor cable. Windows will reinstall the generic monitor driver. That often fixes corrupted EDID data.

The less common fix: registry tweak for high refresh rates

I've seen this error hit when you set a monitor to a refresh rate it can't actually sustain over the cable length or bandwidth. For example, a 4K 144Hz monitor over a 1.4 DisplayPort cable that's too long — the signal degrades, and the VidPN manager fails to lock the timing. Here's the registry fix to force a safe fallback:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers

1. Press Win + R, type regedit, and hit Enter.
2. Navigate to that key.
3. Create a new DWORD (32-bit) value called TdrDelay. Set it to decimal 8.
4. Create another called TdrDdiDelay. Set it to 10.
5. Close regedit and restart your PC. After restart, the GPU gets more time to negotiate the display link before giving up with a VidPN error.

This isn't a permanent fix — it's a workaround for flaky cables. Replace the cable if you see the error again.

Prevention for down the road

• Update your GPU driver from the manufacturer's site, not Windows Update. Go to NVIDIA.com, AMD.com, or Intel.com directly. Windows Update often pushes older driver versions that have known VidPN bugs.
• Use the same cable type for both ends. Don't use a DisplayPort-to-HDMI adapter unless you absolutely must. Passive adapters can cause EDID handshake failures.
• Avoid daisy-chaining monitors with DisplayPort MST (Multi-Stream Transport) unless your GPU explicitly supports it. Some GPUs drop the VidPN when MST negotiation times out.
• Set your monitor to a standard refresh rate if you're overclocking it. I've seen 75Hz monitors set to 120Hz throw this error constantly. Reset to the monitor's rated spec.

That covers it. If you still see 0xC01E0336 after trying all this, it's likely a hardware issue — either the GPU's video output port is failing, or the monitor's EDID chip is fried. Try a different GPU port or a different monitor to isolate it.