Fix ERROR_FULLSCREEN_MODE (0X000003EF) on Windows

Yeah, that error is a nasty one — you're in a game or a full-screen video, you hit Alt+Tab or try to snap a window, and boom, the screen freezes or throws ERROR_FULLSCREEN_MODE (0X000003EF). I've hit this on Windows 11 with a 30-series Nvidia card, but it can happen on any modern GPU driver stack.

The Direct Fix

Here's the order I'd try. Do them in sequence, test after each one. The first step works for most people.

Kill the hanging process — Press Ctrl+Shift+Esc to open Task Manager. Find the full-screen app (usually the game or video player). Right-click it, select End task. If you can't see it because the screen is black, use Win+Tab to create a new desktop, then Task Manager from there. The reason this works: the error means the app holds an exclusive full-screen swap chain that the Desktop Window Manager (DWM) can't release.
Reset the display driver stack — Press Win+Ctrl+Shift+B. You'll hear a beep and the screen flickers. This restarts the GPU driver without rebooting. If the error came from a driver hang (common on 0x000003EF), this clears the stuck state.
Switch to borderless window — If you can get back into the app's settings (maybe it's still responding on a second monitor), change the display mode from Full Screen to Borderless Window or Windowed. Most games support this. Windows handles borderless windows through DWM compositing, which doesn't require the exclusive full-screen mode that triggers this error.

Why This Happens

What's actually happening here is a conflict between the app's request for exclusive full-screen access and the window manager's ability to fulfill it. On Windows, full-screen mode goes through a swap chain managed by DirectX (or Vulkan). The ERROR_FULLSCREEN_MODE (error code 1007) is the OS telling you, I can't switch the display to the requested full-screen state right now.

The root causes are usually one of these three:

Hung GPU driver — A previous command from the app is stuck, so new mode changes fail.
DWM deadlock — Desktop Window Manager is waiting for the app to release the swap chain, but the app is waiting for DWM — a circular wait.
Multiple displays with mismatched refresh rates — Windows 11 struggles with exclusive full-screen when one monitor runs at 60 Hz and another at 144 Hz. The OS tries to synchronize them and fails.

The reason step 3 (borderless window) works permanently is that it bypasses the entire exclusive full-screen mechanism. DWM composites every window, and the app renders to a regular window that just happens to be sized to the screen. No mode switches, no swap chain conflicts.

Less Common Variations

Sometimes 0x000003EF shows up in non-obvious places:

Video players — VLC or MPC-HC can throw this when you try to take a screenshot while a video is playing in full screen. The screenshot tool tries to capture the exclusive surface and can't. Fix: pause the video first, or set the video output to Direct3D11 instead of automatic in VLC's preferences.
Remote Desktop — If you're connected via RDP, full-screen apps on the remote machine can trigger this when you minimize the RDP window. The remote DWM gets confused about the screen resolution change. Fix: reduce the remote display resolution to match the local one, or run the remote app in windowed mode.
Windows Sandbox — Older builds of Windows 10 Sandbox would lock up with this error if you tried to full-screen an app inside the sandbox. Microsoft fixed it in 20H2, but if you're running an older build, you'll need to update.

Preventing It Long-Term

This isn't a hardware failure — it's a software state issue. You can avoid it with these habits:

Update your GPU driver — Nvidia and AMD have fixed several full-screen mode bugs over the last two driver branches. Use DDU (Display Driver Uninstaller) in Safe Mode to clean the old driver first, then install the latest from the vendor site — not Windows Update.
Set your primary display as the main boot monitor — Go to Settings > System > Display > Advanced display. Make sure the monitor you game on is set as the primary display (it'll have a 1 label). Windows prefers the primary display for exclusive full-screen.
Disable hardware-accelerated GPU scheduling — Some users report this error goes away after turning off HAGS in Settings > System > Display > Graphics > Change default graphics settings. The feature is still buggy with certain game engines (especially Unreal Engine 4).
Use borderless window for problematic games — If a game consistently triggers this when you Alt+Tab, just leave it in borderless window mode. The performance hit is negligible on modern hardware (maybe 1-2% FPS loss).
Match monitor refresh rates — If you run multiple monitors, set them all to the same refresh rate if possible. You can do this in the Nvidia Control Panel > Display > Change resolution > Customize > Create custom resolution. Even 60 Hz across the board prevents the timing mismatch that sometimes triggers this error.

Bottom line: 0x000003EF is a symptom of a stuck or mismatched display state. Kill the process, reset the driver, and move on. If it keeps coming back, switch to borderless window — it's the most reliable workaround until Microsoft or GPU vendors sort out the exclusive full-screen mess.