Crashing to the desktop (CTD) is one of the most frustrating PC gaming problems because Windows may not show an error message at all. A game can close because of corrupted files, unstable hardware settings, driver conflicts, overlays, missing runtime components, or a problem with the save/configuration data. The fastest solution is not to reinstall everything immediately: isolate whether the crash is tied to one game, one driver change, one Windows component, or system-wide instability.
This guide uses reversible checks first, so you can identify the cause without creating new problems or losing saves. The menu names below apply to current Windows 11 builds in 2026; some labels may differ slightly by GPU driver version.
Most Common Causes
| Cause | Symptom | Likelihood |
|---|---|---|
| Corrupted or missing game files | One game crashes at launch, during loading, or after an update | High |
| GPU driver issue or bad shader cache | Crashes during gameplay, scene changes, cutscenes, or shader compilation | High |
| Overlays, injectors, mods, or monitoring tools | Crash after opening an overlay, using a hotkey, or starting a protected multiplayer game | High |
| Unstable GPU, CPU, RAM, or XMP/EXPO overclock | Several demanding games crash, freeze, reboot, or show display-driver errors | Medium to high |
| Damaged settings, save files, or local cache | Crash happens when loading one save, entering one area, or applying graphics settings | Medium |
| Low free storage, page-file issue, or memory pressure | Crash after extended play, loading large areas, or compiling shaders | Medium |
| Missing Windows or Microsoft runtime components | Immediate launch failure, DLL message, or crash before a splash screen | Medium |
| Failing drive, RAM, GPU, power supply, or overheating | Worsening crashes across applications, file corruption, artifacts, shutdowns, or reboots | Low to medium |
Diagnose Step by Step
1. Establish the crash pattern
Write down the exact point of failure: launch, main menu, loading screen, specific save, multiplayer match, cutscene, or 15 to 30 minutes into play. Test one other demanding game and one non-game application. If only one title crashes, prioritize game files, mods, game settings, and its local cache. If multiple games crash, investigate drivers, overlays, temperatures, RAM stability, and power delivery.
2. Check Windows reliability history
Press Win + R, type perfmon /rel, and press Enter. Reliability Monitor displays failures by date. Select a red X associated with the game and choose View technical details. Note the “Faulting module name” and exception code. A module such as nvwgf2umx.dll, atidxx64.dll, or amdxc64.dll points toward the graphics stack; repeated ntdll.dll or KERNELBASE.dll entries are less specific and require further testing.
3. Remove variables before changing drivers
Close monitoring and tuning utilities, including MSI Afterburner, RivaTuner Statistics Server, GPU Tweak, Intel XTU, Ryzen Master, and motherboard RGB suites. Disable Discord, Steam, NVIDIA, AMD, Xbox Game Bar, and Overwolf overlays temporarily. If the crash stops, re-enable one item at a time rather than leaving everything disabled permanently.
4. Verify the game and test a clean configuration
Use the launcher’s repair tool, then rename—not delete—the game’s settings folder in %LOCALAPPDATA%, %APPDATA%, or Documents\My Games. On the next launch, the game should generate new default settings. Back up save folders first, especially if saves are stored alongside configuration files.
5. Check temperatures, storage, and available memory
Keep at least 20 GB free on the Windows drive and enough free space for the game’s updates and shader cache. Open Task Manager with Ctrl + Shift + Esc, select Performance, and watch Memory, Disk, and GPU usage while reproducing the problem. A full system freeze, abrupt restart, or black screen is more likely a stability or hardware issue than a normal game-file problem.
Fixes by Cause
Corrupted or missing game files
What causes it: Interrupted updates, antivirus quarantine, disk errors, or altered files can make a game crash during startup or loading.
How to check: If the issue affects one game after a patch or power interruption, file corruption is a strong possibility. In Steam, open Library, right-click the game, choose Properties > Installed Files > Verify integrity of game files. In the Epic Games Launcher, select the three dots beside the game, then choose Manage > Verify.
What to do: Run verification, restart the launcher, and test without mods. Check Windows Security > Virus & threat protection > Protection history for quarantined game files. Restore only files you recognize as belonging to the game, then add the game’s installation folder as an exclusion only if you trust its contents.
How to undo: Remove any exclusion from Windows Security > Virus & threat protection > Manage settings > Exclusions. Re-enable mods only after confirming the unmodified game is stable.
GPU driver conflict or corrupted shader cache
What causes it: A driver update, damaged shader cache, or game-specific driver profile can cause CTDs when rendering effects, compiling shaders, or changing display modes.
How to check: Look in Reliability Monitor for a graphics-driver module. Also test whether the game crashes with ray tracing disabled, frame generation disabled, and the frame-rate cap set to 60 FPS.
What to do: Install the latest stable driver from your GPU manufacturer using its normal installer. Choose a clean-install option if offered, but avoid third-party driver removal tools unless ordinary reinstalling has failed. Then clear the DirectX shader cache: go to Settings > System > Storage > Temporary files, select DirectX Shader Cache, and choose Remove files. The first launch afterward may stutter while shaders rebuild.
How to undo: If the crash began immediately after a driver update, open Device Manager > Display adapters > [your GPU] > Properties > Driver and select Roll Back Driver when available. Restore your previous in-game graphics options after stability is confirmed.
Overlay, mod, ReShade, or monitoring conflict
What causes it: Overlays and injectors hook into the game’s rendering process. Anti-cheat systems and some newer graphics APIs can reject or conflict with those hooks.
How to check: Disable Steam Overlay through Steam > Settings > In Game > Enable the Steam Overlay while in-game. In Discord, use User Settings > Game Overlay > Enable in-game overlay. Exit RTSS completely from the notification area, not just its window.
What to do: Start the game with all overlays off. Remove ReShade files from the game folder only after backing them up; common files include dxgi.dll, d3d11.dll, dinput8.dll, and ReShade.ini. Disable mods through the game’s manager or move mod files outside the installation folder. Test for at least one full play session.
How to undo: Restore backed-up mod and ReShade files one group at a time. Re-enable only the overlay you actually use, then retest.
Unstable overclock, undervolt, XMP, or EXPO profile
What causes it: A system can appear stable in everyday use but fail under a game’s particular CPU, RAM, and GPU load pattern. GPU undervolts, memory profiles, and automatic motherboard boosting are common contributors.
How to check: If several games crash, display artifacts appear, or the PC restarts, return the GPU core clock, memory clock, power limit, CPU tuning, and RAM settings to defaults. Note that a crash without artifacts can still be RAM instability.
What to do: In your GPU tuning tool, select Reset or set core and memory offsets to 0 MHz. In UEFI/BIOS, load optimized defaults or disable XMP/EXPO temporarily; save and reboot. Test the same crash location. Run Windows Memory Diagnostic by pressing Win + R, typing mdsched.exe, and choosing Restart now and check for problems.
How to undo: Reapply only previously stable settings, one change at a time. If disabling XMP/EXPO fixes the crash, do not assume the memory kit is defective; update the motherboard BIOS and use a lower validated memory speed before replacing parts.
Broken game settings, cache, or save data
What causes it: A bad graphics option, obsolete configuration value, damaged shader cache, or corrupted save can crash a game repeatedly at the same point.
How to check: Test a new game or a different save. If only one save fails, copy it elsewhere before further troubleshooting. Search %LOCALAPPDATA%, %APPDATA%, and Documents\My Games for the game’s folder.
What to do: Rename the folder by adding .backup to its name, for example GameName to GameName.backup. Launch the game to create fresh settings. If the game starts, copy saves back in small batches rather than restoring the entire old folder. Set display mode to borderless or windowed temporarily and disable ray tracing, frame generation, and custom launch options.
How to undo: Delete the newly created settings folder, then rename GameName.backup back to its original name. Keep separate copies of working saves.
When to Replace or Reinstall
Reinstall the game only after verification, clean settings, and mod removal fail. Uninstall through the launcher, manually check that the old installation folder is gone, restart Windows, and reinstall to a drive with adequate free space. Do not delete cloud saves unless you have a separate backup.
Consider hardware replacement or professional diagnosis when crashes spread across games and applications, Windows reports disk errors, the PC restarts under load, or visual artifacts appear before the crash. Run chkdsk /scan in an elevated Command Prompt for the affected drive. Replace a drive if it reports persistent errors or cannot reliably read/write files. Suspect the power supply, GPU, RAM, or cooling when the system loses power, reboots, or produces artifacts; a normal CTD alone does not prove that any one component has failed.
FAQ
Why does my game crash to desktop with no error message?
Many games handle a fatal error by closing their process without showing a dialog. Reliability Monitor is usually more useful than the absence of an on-screen message. Check perfmon /rel immediately after the crash and correlate the time with driver, Windows, or game updates.
Should I reinstall Windows for game crashes?
Usually no. Reinstalling Windows is a last resort after testing clean drivers, default stability settings, game verification, storage health, and multiple games. If only one game crashes, a Windows reinstall is especially unlikely to be the efficient fix.
Can low RAM cause a game to crash to desktop?
Yes. Low available memory can cause crashes during large loads or extended sessions, particularly if the page file is disabled. Leave the page file system-managed: open System Properties > Advanced > Performance Settings > Advanced > Virtual memory, then enable Automatically manage paging file size for all drives.
Is it safe to disable antivirus to test a crash?
Prefer checking Protection History and using a temporary, specific exclusion for a verified game folder. Fully disabling real-time protection creates unnecessary risk and is rarely required. If antivirus is involved, the affected file or quarantine record should provide evidence before you change protection settings.
