How to Fix Alt Tab Crashes in Older Games: Easy Steps (2026)

Alt tab crashes in older games happen because the game loses its graphics device the moment Windows moves focus away from an exclusive fullscreen window, and a legacy engine has no code left to rebuild its textures afterwards. The fix is almost always to stop using exclusive fullscreen and then remove the overlays and settings that interfere with the switch.

That is the short version of how to fix alt tab crashes in older games. The longer version is that alt-tabbing is not an edge case for PC players. You answer a Discord message, check a wiki, alt-tab to a launcher, or move a window off the second monitor and you expect the game to sit there patiently. Older titles frequently do not. They crash to desktop on the way out, come back as a black screen, or freeze forever while audio keeps playing.

The good news is that this is nearly always a software problem, and nearly always one of a small number of them. You will not have to replace your power supply. This guide walks through the checks in the order worth trying, cheapest and least risky first, for players running older PC games on a modern machine.

What You Need

You do not need new hardware, a new Windows install, or a toolkit of utilities. You need five things lined up before you start, and having them ready is what stops people from changing six settings at once and learning nothing.

• A way back into Windows. If the whole system hangs, Ctrl+Alt+Delete then Sign out is faster than a restart and saves your unsaved work in most cases.
• The real game executable. Not the desktop shortcut. Right-click the game in your library, choose Manage, then Browse local files, and find the .exe that launches the game rather than the launcher.
• Administrator access. Compatibility mode, fullscreen optimization, and some driver steps all need it.
• Access to your graphics driver. Know whether you run NVIDIA GeForce, AMD Radeon or Intel Arc, and which version you have installed right now.
• A list of what is running. Write down every overlay and mod: Discord, Steam, GeForce Experience, AMD Software, Xbox Game Bar, OBS, ReShade, Script Extender, ENB, trainers.

If you use two monitors, note the refresh rate of each. A 144 Hz main panel next to a 60 Hz laptop screen is one of the most common and most under-reported triggers there is.

Step-by-Step: How to Fix Alt Tab Crashes in Older Games

Work through these in order and stop at the first one that makes the crash disappear. Each step is listed roughly by cost and risk, so the easy toggles come before anything that touches your driver.

Identify the Crash Pattern First

Crashing on the way out and crashing on the way back are different bugs with different fixes, and ten minutes of pattern-finding saves you an afternoon of guessing. Note whether the game dies before the other window appears, whether it dies when you switch back, and whether it survives the trip if you wait for a loading screen to finish first.

What you see	Most likely cause	Start with
Crash to desktop the instant you switch away	Exclusive fullscreen losing the graphics device on focus loss	Borderless windowed
Black screen when you switch back, audio still playing	Focus returned but textures were never rebuilt after device loss	Windowed mode, then a driver check
Freeze for a few seconds or forever on return	Overlay hook or driver timeout during the display mode change	Overlays off, then Hardware Accelerated GPU Scheduling
Resolution, aspect ratio or 4:3 stretch resets every switch	Display mode renegotiation on a second monitor or mixed refresh rate	Single-monitor test, then match refresh rates
Desktop flashes and sound cuts, game is gone	GPU timeout reset, also called TDR	Overlays off, then a clean driver install
System freezes hard or reboots	Driver crash or an unstable overclock rather than the game alone	Stability test, then hardware triage

One test narrows this down further. Alt-tab out during gameplay versus alt-tab out during a loading screen, since loading is a heavy and half-finished state where resources are still being created. Games in that class tend to fail on both.

Disable Overlays and Background Apps

Overlays inject themselves into the game’s rendering process and hook the swap chain, so they are present at exactly the moment focus changes. They are the second most common cause after fullscreen mode and the first thing to rule out.

• Steam overlay: Right-click the game in your Steam library, choose Properties, open the General tab, and untick Enable overlay on game start.
• NVIDIA overlay: Open NVIDIA App or GeForce Experience, go to Settings, find In-game overlay, and switch it off. Restart the app so it takes effect.
• AMD overlay: Open AMD Software, go to Settings, then Gaming, and turn off the in-game overlay and Instant Replay.
• Discord overlay: User Settings, App Settings, then Overlay, and turn off the in-game overlay and hardware acceleration.
• Xbox Game Bar: Press Win+G, open Settings, and turn off capturing. To stop it launching at all, go to Settings, Gaming, and turn Game Bar off.
• Microsoft Game Mode: Settings, Gaming, Game Mode, off. This one has a confirmed fix history, with a Windows 11 reader reporting that turning Game Mode off ended their alt-tab crashes on every game.

Close OBS and any recording tool completely rather than leaving the tray icon running. Then test the alt-tab that previously crashed.

A test result that counts: if the crash stops with every overlay closed but returns when you reopen Discord, you have found it and you can re-enable the rest.

Update or Reinstall the Correct Graphics Driver

Only change the driver if the overlay step changed nothing, and never install a different vendor driver on top of an existing one. Download from the GPU vendor directly, not from a driver updater utility, which tends to install a generic build that performs worse.

Identify your card first with DirectX Diagnostic Tool or Device Manager under Display adapters. Then pick the current stable driver for that card. For an older game specifically, try one step back: drivers from the last couple of years fixed a lot of legacy D3D9 and D3D11 titles that the newest drivers broke.

Install cleanly rather than over the top. In the NVIDIA installer choose Custom and tick Perform a clean installation. In AMD Software choose the factory reset option during install. Restart Windows afterwards, then confirm the game still launches and still crashes the same way, because a driver change alone frequently does not fix an exclusive fullscreen bug.

Run the Game in Compatibility Mode

Compatibility mode changes how Windows presents the window to the game, and for titles that were built for older Windows display behavior it is often the whole fix.

1. Open the game folder and locate the executable, not the launcher.
2. Right-click it and choose Properties.
3. Open the Compatibility tab.
4. Tick Run this program in compatibility mode, then pick Windows 8 or Windows 7 from the dropdown. Windows 7 is the right first guess for DirectX 9 era titles.
5. Apply, then run the game as administrator using the Run this program as an administrator checkbox on the same tab.

A test result that counts: compatibility mode fixes this when the crash is a window-management bug rather than a rendering one. If it does nothing, untick it before moving on, because a pile of speculative settings makes the next test meaningless.

Disable Fullscreen Optimization and Change Display Mode

This is the highest-value step and it is the one most people skip. Windows 10 and Windows 11 quietly wrap old exclusive fullscreen games in a compatibility shim called fullscreen optimizations, and games that break on focus change can break inside that shim too.

1. Right-click the executable and open Properties.
2. Open the Compatibility tab.
3. Tick Disable fullscreen optimizations, or leave it unticked to test the difference.
4. Apply, then launch and alt-tab.

On Windows 11 you can also let the system handle windowed games: Settings, System, Display, Graphics, then find the game, choose Options, and turn on the windowed game optimisations for the game executable. It is worth trying both directions, since it helps some titles and hinders others.

If the game has a graphics menu, set Display Mode to Borderless Windowed or Windowed. If it has no graphics menu at all, the config file method below is the one that matters for you.

Here is why the mode matters. Borderless windowed and windowed mode are different from exclusive fullscreen, and old engines treat them differently.

Display mode	Alt-tab crash risk	Performance	Works on very old games
Exclusive fullscreen	Highest, the swap chain is destroyed on focus loss	Best frame pacing and lowest latency	Yes, but it is where the bug lives
Borderless windowed	Very low, Windows owns the swap chain	Slight cost in frame pacing	Usually yes
Windowed	Lowest	Highest cost, windowed render paths are slower	Yes, the safest fallback

If a player on a Steam thread isolated the cause by disabling a second display in Windows display settings and the crashes stopped, that is the same mechanism: the game was renegotiating its display output mid-switch. Multi-monitor setups get their own coverage below.

Disable Mods and Verify Original Game Files

Move your mods out of the way rather than deleting them. Rename the mod folder to something the game does not read, launch once, and alt-tab. Mod frameworks frequently inject their own DLLs and can crash on focus change, and a base-game crash means you are looking at the wrong list of fixes.

Then verify the files. In Steam, right-click the game, choose Properties, Local files, then Verify integrity of game files. GOG has the same function under Verify or Repair. A missing or damaged DirectX DLL is a real cause of crashes that look random.

For games with no graphics menu, edit the config instead. Source engine titles keep a file called config.cfg in the game’s own cfg folder under steamapps, and GoldSrc titles keep valve and hl files in the game root. GameMaker and RPG Maker saves usually live under AppData, with the folder name matching the engine version. In any of these you will find lines for fullscreen, width and height that you can set by hand.

Many older titles also accept launch options in the same Properties window, or in the Play section of GOG. Useful ones include -windowed, -noborder, -borderless and -fullscreen. Try -windowed first, since it is the most widely supported and the most likely to leave a legacy engine alone.

Repair Conflicting Windows Settings

Change one setting, run the alt-tab test, then decide. Turning four things off at once means that if the crash stops you still do not know which one did it, and you end up keeping four changes you did not need.

Hardware Accelerated GPU Scheduling lives in Settings, System, Display, Graphics, Default graphics settings. Turning it off changes how Windows schedules GPU work, and it is a documented trigger for alt-tab freezes in games that were never built around it. It requires a restart.

Game Mode is in Settings, Gaming. It prioritises the running game over background work, and disabling it fixed one reader’s crashes across every game on Windows 11.

Background apps: Settings, Apps, Installed apps, then turn off background permissions for your launcher and anything else that scans saves or talks to the game while it runs.

If you are on Windows 11, check Windows Update too. The 24H2 release shipped an alt-tab regression that affected any fullscreen app, and the fix arrived as a cumulative update rather than a setting.

Reinstall or Reapply the Game’s Required Components

Only touch the runtime libraries when the game tells you it is missing one, because reinstalling DirectX or Visual C++ redistributables on a healthy machine wastes an evening and changes nothing.

When a game does need them, use the official sources. Microsoft’s DirectX End-User Runtime installer, known as the June 2010 DirectX 9 runtime, adds the legacy DirectX 9 DLLs that Windows 10 and 11 no longer include, which is what most DirectX 8 and DirectX 9 titles still ask for. The Visual C++ Redistributable from Microsoft’s site covers the 2005, 2008, 2010, 2013 and 2015 runtimes, and old titles often need the 2005 and 2008 ones.

After installing, launch the game and repeat the exact alt-tab sequence that used to crash it. That is the only way to know whether the runtime was the missing piece.

If the title ships with a third-party launcher such as a GoldSrc launcher, reinstall that launcher too and let it point at the game folder. It usually offers a windowed mode checkbox that saves you editing config files.

Test the Final Configuration

Run the exact sequence that used to fail, not a different one. Alt-tab during gameplay, alt-tab during a loading screen, alt-tab twice in quick succession, and if you have two monitors, alt-tab to a window on the second screen. Do it at least three times each.

Then work backwards and remove what is no longer needed. If turning off the Discord overlay fixed it, leave the NVIDIA overlay off for a week and see whether anything actually breaks. Keeping a minimal, understood configuration is what makes the next crash diagnosable.

Write down the winning combination. Six weeks later when something else misbehaves you will not remember that Game Mode was the setting that mattered.

Common Mistakes to Avoid When You Fix Alt Tab Crashes

• Changing five settings at once. You learn nothing, and you leave four changes you cannot justify.
• Downloading drivers or DirectX packages from third-party sites. Driver updater utilities and mirror sites are a common source of malware and of drivers that break old games.
• Testing with mods still enabled. A mod crash and a base-game crash look identical from the outside.
• Ignoring overlays because the game runs fine in single player. Discord and Steam overlays only activate when something else launches or a hotkey fires, which is exactly your alt-tab moment.
• Applying compatibility settings to the launcher instead of the executable. The launcher is the window you see; the settings that matter belong on the .exe that creates the fullscreen surface.
• Installing a third-party borderless tool first. These can cause post-alt-tab freezes and crashes of their own, which makes the original problem harder to diagnose.
• Replacing the power supply or RAM on the first bad evening. Users on hardware forums keep landing on this expensive dead end. An alt-tab crash that reproduces every single time, with a clean pattern, is software until proven otherwise.

Quick Reinstall Checklist

Copy this onto paper before you start, and fill it in rather than working from memory. It takes two minutes and it stops you from repeating a step you already tried three times ago.

• Game name, edition and store it came from
• Path to the actual game executable, not the shortcut or launcher
• Windows version and build number, typed from winver
• Graphics card model and current driver version
• Overlays currently running
• Mods or injected frameworks currently active
• Display mode the game is set to, and whether the toggle exists at all
• Monitor setup: one screen or two, and the refresh rate of each
• Whether the crash happens on tab out, tab back, or both
• Result of the alt-tab test after each change

If you ever reinstall Windows or move to a new drive, that sheet is the difference between a twenty-minute setup and an evening of rediscovering everything.

When to Stop Troubleshooting and Report a Crash

Stop when you have a clean reproduction and nothing left in the checklist. A crash that reliably happens on the third alt-tab of a specific game, after overlays are off and files verify, is not a configuration problem you will solve by toggling another Windows checkbox.

Collect the error information before you post. Open Event Viewer, go to Windows Logs, Application, and look for the faulting module and exception code at the moment of the crash. Reliability History, reachable from Reliability Monitor in Windows, gives a cleaner timeline of what died and when. The exception code tells you a lot: a faulting module of d3d11.dll or the game’s own d3d9 wrapper points at rendering, while a module inside the Steam or Discord client points at an overlay.

A report that gets answered needs five things: the exact game and version, your Windows build, your GPU and driver version, your monitor setup, and the reproduction steps written as “alt-tab out during gameplay, wait two seconds, alt-tab back in, freezes.” Include whether it happens on tab out or tab back, since those are different bugs. Per-title forum threads get faster answers than general ones because the fix is already confirmed against your exact game.

On the hardware question players keep asking: bad RAM causes crashes across many programs, blue screens, and failures that follow no pattern, not a crash that reproduces only on the fourth alt-tab. A hard freeze or reboot during a display mode change is worth a stability test, but check your overclock and any undervolt first, since those break exactly this kind of transition. Diagnose the software before the hardware.

One recovery trick worth memorizing. If the whole system hangs with the frozen game still in the foreground, press Ctrl+Alt+Delete, then choose Sign out, then sign back in. On a Windows 10 or 11 machine that is often faster than waiting through a restart, and it preserves your open applications.

Frequently Asked Questions

Start with the display mode. If you have not already put the game into windowed or borderless windowed, that is the single highest-value change on this page, and for a DirectX 9 era title it is usually the whole fix. After that, close every overlay and turn off Game Mode before you touch a driver.

If the game ships no graphics menu, use the launch option or the config file, because the advice you have read everywhere else simply does not apply to you yet. And if a clean test still reproduces the crash every time, stop buying parts and start writing the report.