Where this error actually shows up
You won't see this error on your screen as a popup. It shows up in Event Viewer under Windows Logs > System, usually as a warning or error from source Display with event ID 0. The exact error code is 0xC01E032C. You'll see it after you plug in a second monitor, switch display inputs, or right after a graphics driver update. The system doesn't crash, but sometimes the second monitor stays black or your display settings reset to single monitor.
What's actually happening here
The error code comes from the Windows DirectX graphics kernel subsystem (dxgkrnl.sys). It means some piece of code—either a driver or a system service—tried to access a monitor descriptor (an EDID block) that isn't part of the descriptor set the kernel has cached for that monitor. Normally, each monitor has one or more EDID blocks that describe its capabilities (resolution, refresh rate, color depth). The kernel keeps a list of these. If something asks for descriptor index 2 but the kernel only stored indices 0 and 1, you get this error.
The reason this happens is almost always a stale descriptor set: the physical monitor was disconnected or changed, but the driver or a user-mode component (like the NVIDIA control panel or the Windows display topology manager) is still holding a reference to the old descriptor set. When that component tries to query or apply a mode that depends on that old descriptor, the kernel says "nope, that descriptor doesn't exist in the current set."
The fix: clear the stale descriptor cache
There's no registry key or settings toggle for this. The fix is to force the graphics stack to rebuild its descriptor sets from scratch.
- Disconnect all external monitors. Unplug HDMI, DisplayPort, USB-C, and any docking station connections. If you're using a laptop, unplug the power adapter too—some docks draw power and keep the monitor detection alive.
- Restart the computer with only the built-in display active. This forces the kernel to discard all cached EDID data. Windows 10 and 11 both re-enumerate displays at boot, so the descriptor set is rebuilt fresh.
- Reconnect your monitors one at a time. Plug in the first monitor, wait 10 seconds for detection, then check if it's working (Settings > System > Display should show it). Then plug in the second. Don't hot-plug all at once—the kernel processes each EDID sequentially, and doing them in rapid succession can cause races that recreate the stale set.
- If the error persists after step 2, do a full graphics driver reinstall. Use Display Driver Uninstaller (DDU) in Safe Mode. Boot into Safe Mode, run DDU to wipe the current driver, then reboot and install the latest driver from the manufacturer's site (NVIDIA, AMD, or Intel). Don't use Windows Update—it sometimes installs generic drivers that don't handle descriptor sets correctly, especially for high-refresh-rate monitors.
- For laptops with hybrid graphics (Intel + NVIDIA/AMD), also update the Intel integrated graphics driver. The Windows Display Driver Model (WDDM) uses the integrated GPU to manage display outputs even if the discrete GPU renders frames. If the Intel driver is old or corrupted, it can pass bad descriptor indices to the kernel.
Why step 4 works
DDU removes not just the driver files but also the driver store and the registry entries that cache display configuration. When you reinstall, the kernel enumerates the monitors fresh, reads their EDIDs from the physical hardware (via I²C on the video cable), and builds a descriptor set from scratch. No chance of stale indices.
If it still fails
Three things to check:
- Monitor EDID corruption. Some monitors (especially older ones or those using KVM switches) have flaky EDID EEPROMs. Try a different cable—bad shielding can corrupt the I²C signal. If that doesn't help, test the monitor on another PC. If the error follows the monitor, the monitor's EDID chip is damaged. A firmware update from the monitor manufacturer (if available) can fix it.
- Docking station issues. Dell and Lenovo docks sometimes don't expose EDID correctly on all firmware versions. Update the dock firmware. Also try plugging the monitor directly into the laptop's HDMI/DP port instead of through the dock—if the error goes away, blame the dock.
- Windows display topology bug. In rare cases, the Windows Display Switch (Win+P) leaves the kernel in a confused state. Press Win+P, select "PC screen only," then wait 5 seconds, then press Win+P and select "Extend." This triggers a topology rebuild that doesn't require a reboot.
If nothing above works, grab a MonitorInfoView dump of the problematic monitor. Check if the number of EDID blocks reported matches what the kernel should see. If the raw EDID dump shows only one block but the system expects two, you've found the hardware cause.