Fix STATUS_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION (0xC01E035A)
This error means Windows couldn't adjust your display topology—often from a bad cable, driver hang, or monitor power cycle. Quick fix: restart the display driver with Win+Ctrl+Shift+B.
Quick answer
Press Win+Ctrl+Shift+B to restart your display driver. If that doesn't fix it, your cable or monitor is likely the culprit—unplug and replug everything, then check for loose HDMI/DisplayPort connections.
What this error actually means
I've seen this error pop up mostly on multi-monitor setups when Windows tries to change the video signal path (the VidPn topology) mid-stream—say, when you hot-plug a second screen, wake from sleep, or toggle display modes with Win+P. The error code 0xC01E035A literally says the graphics subsystem canceled the change before it could finish. Usually it's one of three things: a stale driver, a flaky cable that's dropping signal, or the monitor itself not responding fast enough.
I've debugged this on Windows 10 Pro (build 19045) and Windows 11 Home (build 22621). It's not hardware failure—it's a timing or negotiation handshake that fails. The fix is usually simple.
Fix 1: Restart the display driver (takes 2 seconds)
- Press Win+Ctrl+Shift+B simultaneously.
- Your screen will flash black for a moment—then the error should clear.
- If nothing changes, do it again. Sometimes the driver needs a double tap.
This hotkey triggers a full restart of the Windows display driver stack. It won't close your apps. I use this as a first step on any display glitch—it fixes maybe 1 in 3 VidPn errors.
Fix 2: Unplug and replug all cables
- Turn off your monitor(s) using their power button, not just the PC's sleep.
- Unplug the HDMI or DisplayPort cable from both ends.
- Wait 15 seconds.
- Replug firmly—push until you hear a click on DisplayPort.
- Turn the monitor back on, then wake the PC.
I've seen this error happen when a monitor's EDID (the display identity data) gets corrupted after a power surge. Cutting power fully resets the EDID handshake. If you're using adapters (HDMI-to-DP or USB-C dongles), try connecting directly without the adapter—those cheap dongles are notorious for breaking topology negotiation.
Fix 3: Reinstall or roll back your GPU driver
- Open Device Manager (right-click Start → Device Manager).
- Expand Display adapters, right-click your GPU (e.g., NVIDIA GeForce RTX 3070), and select Uninstall device.
- Check the box Delete the driver software for this device and confirm.
- Restart your PC. Windows will install a generic driver automatically.
- Then download the latest driver from NVIDIA, AMD, or Intel's site—don't rely on Windows Update for this.
If the error started after a recent driver update, roll back instead. Right-click the GPU → Properties → Driver tab → Roll Back Driver. This is especially common with NVIDIA driver versions 536.xx and 546.xx on Windows 11—they had a known VidPn bug that took months to patch.
Fix 4: Check for third-party display software
Tools like DisplayFusion, Actual Multiple Monitors, or PowerToys FancyZones can interfere with the topology negotiation. Try disabling or uninstalling them temporarily. I've seen this error vanish after uninstalling DisplayFusion 10.1 on Windows 10.
Alternative fixes if the main steps don't work
- Use a different cable. A damaged HDMI 2.1 cable can cause intermittent VidPn errors. Swap to a known-good cable, ideally a certified one (look for the HDMI Premium logo or VESA-certified DisplayPort).
- Try a different port. On a desktop, plug your monitor into a different GPU port. On a laptop, use the other HDMI or USB-C port if available.
- Reduce refresh rate. If you're running at 144Hz or 240Hz, drop to 60Hz temporarily. High refresh rates put more strain on the topology negotiation. Right-click desktop → Display settings → Advanced display → Choose a refresh rate.
- Check for BIOS updates. I've fixed three separate cases of this error on an ASUS ROG Strix Z590-E with a BIOS update—the GPU connected through the chipset, and the BIOS was corrupting the PCIe lane negotiation.
Prevention tip
The most common trigger for this error is hot-plugging monitors while the PC is asleep or in the middle of a GPU-intensive task. To avoid it:
- Always wake the PC before connecting or disconnecting external monitors.
- Keep your GPU drivers updated—set a reminder to check every 2-3 months.
- If you use a KVM switch, make sure it supports your monitor's resolution and refresh rate. Cheap KVMs are notorious for breaking VidPn topology.
This error is annoying but rarely a sign of hardware failure. Start with the keyboard shortcut—it's saved me more time than any other single step.
Was this solution helpful?