STATUS_GRAPHICS_INVALID_VIDEO_PRESENT_SOURCE_MODE (0xC01E0310) Fix

Cause #1: Corrupt or mismatched graphics driver

This is the big one. About 8 out of 10 times I've seen this error, it's because Windows Update pushed a bad driver, or you tried to force a resolution your monitor doesn't support. The error code 0xC01E0310 literally means the video present source mode is invalid – Windows is trying to use a display mode that doesn't match what your graphics card or monitor can handle.

You'll see this error when you launch a game, plug in a second monitor, or wake your PC from sleep. The screen might go black for a second, then you get a pop-up with the error number. Or it just crashes the app with no message.

Fix: Clean uninstall graphics driver with DDU

Don't just reinstall the driver – that leaves leftover junk. Use Display Driver Uninstaller (DDU). It's free, safe, and the only way to really reset things.

1. Download DDU from Guru3D. Save it to your desktop.
2. Unplug your internet cable or turn off Wi-Fi. This stops Windows from auto-installing a driver while you work.
3. Restart your PC into Safe Mode. Hold Shift while clicking Restart in the Start menu. On the blue screen, pick Troubleshoot > Advanced Options > Startup Settings > Restart. Then press 4 for Safe Mode.
4. Run DDU. It should open automatically. If not, find it on your desktop and double-click it.
5. In DDU, pick your GPU type from the dropdown on the right – NVIDIA or AMD (Intel for integrated graphics). Then click "Clean and restart."
6. Wait. Your screen will flicker a few times, then your PC restarts. After restart, you should be in normal mode with a super-low resolution (like 800x600). That's normal.

Now plug your internet back in. Windows Update will likely grab a basic driver automatically. That's fine for now. Test if the error is gone by opening the app that crashed before. If it works, great – but you probably want the full driver from NVIDIA or AMD's website for best performance.

After this fix, the error disappeared for most people I've helped. If it hasn't, move to the next cause.

Cause #2: Monitor EDID data is corrupted or incompatible

EDID is basically your monitor's ID card. It tells the graphics card what resolutions and refresh rates it supports. If that data gets scrambled – maybe from a bad cable, a power surge, or some weird sleep/wake cycle – Windows gets confused and tries to use a mode the monitor can't do. That throws error 0xC01E0310.

You'll notice this especially after your PC goes to sleep and wakes up. Or when you connect a monitor that's been used with a different computer recently. The error pops up randomly, not just when launching specific apps.

Fix: Reset monitor EDID through registry

This is more advanced, but it works when drivers don't help. Make a system restore point first – just in case.

1. Press Win + R, type regedit, hit Enter.
2. Go to this key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\DISPLAY
3. Under DISPLAY, you'll see folders with names like DELA123 or MON1234. Each is a monitor you've connected. Click each one.
4. Inside each monitor folder, look for subfolders like "5&..." – there's usually one per connection type (HDMI, DP, etc.). Click that subfolder.
5. Look on the right side for a value called EDID. Right-click it and choose Delete. Confirm yes.
6. Repeat for every monitor subfolder you see. Don't skip any – even ones you think are gone.
7. Close Registry Editor. Restart your PC.

When Windows boots, it can't find the old EDID. So it re-detects your monitor fresh, re-reading the correct data from the monitor itself. This clears any bad mode info. After restart, check if the error is gone.

One warning: on some laptop with built-in displays, the EDID is in a different registry location and you shouldn't delete it. But for external monitors, this is safe and effective.

Cause #3: Multiple monitor setup with mismatched refresh rates

Here's a sneaky one. You have two monitors – one running at 60 Hz, another at 144 Hz. Windows sometimes tries to use the same refresh rate for both, or swaps to a mode that only one can handle. The error triggers when you move a window between screens or when the GPU tries to sync both.

You'll see this in games that use exclusive fullscreen mode. Or when you connect a second monitor while a game is running. The error might only happen on the second monitor, not the main one.

Fix: Set both monitors to the same refresh rate and resolution

This isn't ideal for gaming, but it proves the point. If the error goes away, you know the mismatch caused it.

1. Right-click your desktop, choose Display Settings.
2. Scroll down to Advanced Display.
3. Click on each monitor at the top. Under "Choose a refresh rate," pick the same number for both – usually 60 Hz if one is 60 and other is 144.
4. Also set the same resolution for both. If one is 1920x1080 and other is 2560x1440, drop the higher one to 1920x1080 temporarily.
5. Click Keep Changes when prompted. Restart the app that crashed.

If the error doesn't come back, you've found your culprit. Long-term fix: keep both at 60 Hz, or get a monitor that matches. Or play games in borderless windowed mode – that avoids the mode switching problem entirely.

Some users report that just unplugging the extra monitor works too. But that's a workaround, not a fix.

Quick reference: What to try first

Start with the driver reinstall – it fixes the most cases. If that doesn't work, try the EDID reset. The refresh rate thing is more of a test than a permanent fix, but it tells you what's wrong. Good luck.