Game Keeps Crashing to Desktop? A Fix Checklist

The worst crash is the polite one: no error box, no freeze, just the game silently gone and the desktop sitting there where your raid, your ranked match, or your save file used to be. Crash-to-desktop (CTD) feels random, but it almost always leaves a signature — Windows writes down what died, in which module, and at what moment. Read that signature first and the checklist below stops being guesswork; skip it and you will reinstall drivers for days while a misbehaving memory profile is the actual culprit.

Step 1: Read the Crash Signature in Event Viewer

After the next crash (do it while the moment is fresh), press Win + X and open Event Viewer, then go to Windows Logs → Application and look at the timestamps around the crash. Two entry types matter:

• Application Error — the game process itself died. The "Faulting module name" line is the fingerprint: the game's own executable points at game files or mods; ntdll.dll often means memory instability; a graphics driver DLL (names containing nvlddmkm, amdwddmg, or similar) points at the GPU driver stack.
• Display / LiveKernelEvent entries under Windows Logs → System — these indicate the driver reset or the GPU fell over, which is the territory covered in our guide to GPU driver timeout crashes; the fix list there (clean driver reinstall, stock clocks) is the one to run.

One crash proves little; a pattern proves a lot. Note whether crashes cluster at load screens (streaming assets — often storage or memory), in combat (load spikes — power or thermals), or after a fixed number of minutes (heat buildup). That pattern is half your diagnosis already.

Step 2: Reset the GPU Driver Stack Properly

Because most CTDs eventually finger the display driver, do this one correctly rather than by feel: download the latest driver directly from NVIDIA, AMD, or Intel, then run their clean-install option (both NVIDIA and AMD installers offer it) or use a third-party utility like DDU in Safe Mode for a truly fresh start. An "upgrade install" keeps the old settings and can carry a corrupted shader cache forward — the exact thing you were trying to remove. After reinstalling, let the first few game launches be slow; rebuilding shader caches is normal and stutter-heavy first launches do not mean the fix failed.

Step 3: Disable Overlays and Injectors

Anything that hooks itself into the game's rendering pipeline is a crash suspect, and they multiply silently: Discord's in-game overlay, GeForce Experience or Adrenalin overlays, MSI Afterburner with RivaTuner, RGB and fan-control software, screenshot tools, and game-bar widgets. Turn all of them off at once, play a session, and only re-enable them one at a time if the crashes stop. Yes, this is tedious; it is also how you catch the single RGB utility that has been killing one specific game since last month's update. While you are at it, close background launchers you are not using — some integrate overlays deep enough to matter.

Step 4: Take the Hardware Off Its Overclock

If the GPU, CPU, or RAM is overclocked — factory "OC buttons" and one-click BIOS profiles count — return everything to stock and retest. Memory instability deserves special attention: an XMP/EXPO memory profile can pass benchmarks for months and still crash one particular game, because games stress memory in different patterns than stress tests do. Set the RAM to its default JEDEC speed in BIOS as a test, not just the CPU. If stock settings make the crashes vanish, you have your answer: run stock, or re-tune the overclock with more conservative voltages and much longer stability testing.

Step 5: Verify Game Files and Runtime Libraries

Corrupted or half-updated game files crash at exactly the same spot every run — that fixed repetition is the tell. On Steam, right-click the game → Properties → Installed Files → Verify integrity of game files; other launchers have an equivalent repair or verify option in the game's settings page. Let it replace what it finds, then test. If verification finds nothing but the crash repeats identically, reinstall the redistributables the game shipped with — look in the game folder's _CommonRedist, DirectX, or Redist folders and run the installers inside; a corrupted Visual C++ runtime is a classic silent killer that file verification never touches.

Step 6: Check Memory Pressure and the Page File

Modern games allocate enormous amounts of RAM, and a system with a disabled or shrunken page file crashes when a game asks for memory the physical sticks cannot supply — often with exactly the silent CTD we are discussing. If you (or an "optimization guide") ever disabled the page file, set it back to System managed under Settings → System → About → Advanced system settings → Performance → Advanced → Virtual memory. While there, watch actual usage during play: if RAM sits pinned near capacity with the game plus a browser open, close the browser mid-session as a test. More background memory pressure means more allocation failures at the worst moment.

Step 7: Heat and Power — the Late-Session Crashers

Crashes that arrive after a predictable number of minutes, or only in summer, or only in graphically dense scenes, point at thermals and power. Check temperatures with a monitoring overlay during a surviving session: sustained GPU or CPU junction temps in the 90s Celsius invite driver resets and shutdowns. Clean the case filters and heatsinks, and confirm fans actually spin up under load. On the power side, a PSU that is old, underrated, or allocated a single cable for a hungry GPU can brown out during brief load spikes — the PC keeps running but the GPU momentarily starves and the driver dies. If the machine also randomly reboots under load, the PSU moves up the suspect list fast.

Step 8: Mods, Configs, and Anti-Cheat

Modded games crash in modded ways. Remove all mods (not just the obvious ones — patch files and replacers count), then restore a clean config by renaming the game's documents-folder settings directory so the game rebuilds it. If crashes began immediately after a game update, check the community's mod compatibility notes before blaming your hardware. Finally, anti-cheat services occasionally break their own games after updates: verify files (step 5), make sure the anti-cheat service is running, and check the game's official status page — if everyone is crashing, your PC is fine and patience is the fix. Frame rates behaving oddly before the crash? Our guide to fixing game stuttering overlaps with several of these causes and is worth a pass too.

Event Viewer names the culprit more often than any hunch: the game's own files, ntdll memory pressure, or the GPU driver module. Match the fix to the signature and the checklist shrinks from eight steps to two.

Work it in order, one change per test session, and keep notes — "crashed at 8:40, again at 12:05, none after driver clean install" is the kind of log that ends these investigations quickly. More troubleshooting guides live in the blog index, and the maintenance checklists that prevent the next round are on our tools page.