Most crash-fix guides tell you to reinstall your GPU driver, verify your game files, and hope. That only works when the game itself is the actual problem — because a driver crash, a RAM fault, and an overheating VRM all produce the exact same symptom (the game vanishes to your desktop) but need completely different fixes. Windows already recorded which one happened to you. You just have to open the log before you start reinstalling things at random.
This guide starts with the 3-minute diagnostic step every other guide skips, then routes you to the fix that actually matches your crash type — single game, multiple games, or full system freeze/reboot. Diagnostic steps and menu paths below are verified current on Windows 11 24H2/25H2 as of September 2026; Event Viewer and Reliability Monitor themselves have been part of Windows since Vista and haven’t changed structurally in years, so this applies to Windows 10 as well. If your PC runs games without crashing but the frame rate itself is the problem, see our complete guide to optimizing PC game settings for better FPS.
Quick Start: Diagnose Your Crash in 3 Minutes
Do this before touching a single setting. It takes less time than one driver download.
- Press Win + R, type
perfmon /rel, hit Enter — this opens Reliability Monitor directly. - Find the red X on the day your game crashed, click it, and note the exact application name and time in the report below.
- Press Win + X > Event Viewer > expand Windows Logs > click Application.
- Sort by date, find the red Error entry matching your crash timestamp.
- Double-click it and read the Faulting module name and Exception code fields — write both down.
- Match what you found against the decision tree and exception code table below.
If Reliability Monitor shows nothing for that day, the crash likely wasn’t logged as an application fault — skip to the freeze/reboot/BSOD section, since that usually means a harder failure than a clean crash-to-desktop.
The Crash-Type Decision Tree
Your fix depends on which of these three patterns you’re actually seeing — not on a generic top-10 list.
- Only one specific game crashes, every other game and app is fine → the problem is scoped to that game’s files, its driver interaction, or software conflicting with it. Go to Fixing a Single Game.
- Multiple unrelated games crash to desktop at random times → the problem sits underneath the games, in your driver stack, memory, or Windows itself. Go to Fixing System-Wide Crashes.
- The whole PC freezes, reboots on its own, or blue-screens → this is a hardware or power-delivery symptom, not a software one. Go to Fixing Freezes, Reboots, and Blue Screens.
The exception code you found in Event Viewer narrows it further. This table covers the codes that show up most often in game-crash reports [6]:
| Exception Code | What It Means | Most Likely Cause |
|---|---|---|
| 0xc0000005 | Access violation — the game tried to read/write memory it wasn’t allowed to touch | Corrupt game files, bad GPU driver, faulty RAM, or an unstable overclock |
| 0xc0000374 | Heap corruption — a program broke its own memory bookkeeping | Driver or DLL conflict, often paired with 0xc0000005 in the same crash cluster |
| 0xc000001d / 0xc000001e | Illegal or invalid instruction | CPU instability — check overclocks and voltages first |
| No entry in Application log at all | Nothing was logged before the failure | Hard hang, reboot, or BSOD — treat as a hardware/thermal issue, not a software one |
A single sourced number here matters more than the table itself: in one documented Microsoft support case, one user hit both 0xc0000005 and 0xc0000374 across three completely unrelated games (an MMO, a survival game, and a racing sim) with the same ntdll.dll faulting module every time [5] — proof that the exception code, not the game, tells you where to look.
Fixing a Single Game That Keeps Crashing
Verify the game’s files first — it’s the single highest-hit-rate fix for one misbehaving game. On Steam: right-click the game in your Library, open Properties, go to Installed Files, and select Verify integrity of game files [3]. Steam re-downloads anything corrupted; a few “failed” local config files in the result are normal and not a problem. Epic Games Store and EA App have the equivalent under a “Verify” or “Repair” button in the game’s settings.
If that doesn’t fix it, update your GPU driver from the manufacturer directly, not Windows Update — Windows Update frequently ships an older build than NVIDIA, AMD, or Intel’s own driver page. See our graphics driver update guide for the exact steps per vendor.
Then check overlays. Discord, GeForce Experience/NVIDIA App, the Steam overlay, Xbox Game Bar, and MSI Afterburner/RivaTuner all inject code into the game’s process to draw their UI on top of it — that injection is a common, well-documented source of crashes in exactly one game while everything else is stable. Disable them one at a time and relaunch to isolate which one is conflicting, rather than turning all of them off at once and never finding out which one was the culprit.
Fixing System-Wide Crashes Across Multiple Games
ntdll.dll as the faulting module across different, unrelated games points to something beneath all of them, not a bug in any one title [5]. Work through this order — it mirrors what actually resolved a real multi-game ntdll.dll case reported to Microsoft support, after the easy fixes (driver update, game verification) had already failed:
Check your page file next if you’re also seeing “out of memory” errors despite having RAM free. Windows’ automatic page-file sizing can grow too slowly to keep up with a game’s memory requests, producing a false out-of-memory crash even on a system with plenty of headroom [1]. Microsoft’s own fix: open System Properties (Win + Pause/Break) > Advanced system settings > Performance Settings > Advanced tab > Change, under Virtual Memory. Uncheck “Automatically manage paging file size,” select Custom size, and set the Initial size to 1.5x your installed RAM in MB — if you still see the error afterward, increase the Initial size further [1]. If you’re consistently pushing your GPU’s VRAM limit rather than system RAM, our VRAM allocation guide covers the game-side settings that reduce that pressure.
If the driver update alone didn’t hold, do a clean reinstall with Display Driver Uninstaller (DDU) instead of just running the installer again. A standard driver update leaves old configuration files behind, and those leftovers — not the new driver itself — are frequently the actual source of the instability [4]. Download your new driver first, boot into Safe Mode (driver files can’t be fully removed while Windows has them loaded), run DDU, then install the fresh driver and confirm the card shows up correctly in Device Manager [4].
If crashes continue after a clean driver reinstall, test your RAM with MemTest86 before assuming it’s a software problem. MemTest86 stresses memory, CPU cache, and motherboard together, so a failure doesn’t isolate the exact faulty part — but it does confirm whether the hardware layer is stable at all, since unreliable memory causes exactly this kind of intermittent, hard-to-reproduce crash [2]. Run at least a full first pass (it’s deliberately shorter, built to catch serious faults fast); if it comes back clean but crashes persist, the instability is likely environmental (heat, voltage) rather than a dead RAM stick [2].
Fixing Freezes, Reboots, and Blue Screens
If Reliability Monitor showed nothing and Event Viewer has no matching Application error, the failure happened at a level below what Windows could log cleanly — that’s a hardware or power symptom, not a driver bug. Heat is the most common cause: as a GPU or CPU approaches its thermal limit, its voltage regulation destabilizes before the chip actually shuts down, and that instability is what crashes the game — not the temperature number itself. Our thermal throttling guide covers exact safe-temperature ranges and how to check them.
Any active overclock or undervolt — CPU, GPU, or RAM (including XMP/EXPO memory profiles, which are a factory overclock even though they don’t feel like one) — should be reverted to stock before you spend money on anything else. If the freezes stop, the “safe” overclock your specific chip was running wasn’t actually stable under a sustained gaming load. See our GPU overclocking guide and RAM overclocking guide for how to identify and roll back an unstable profile rather than reverting everything to default and losing the performance you tuned for elsewhere.
If You Are…
The right first move depends on how much time and risk you’re willing to spend, not just on the crash type.
| Player Type | Start Here | Why |
|---|---|---|
| New player, first crash | Verify game files, then update GPU driver from the manufacturer | Clears up the most common single-game crash causes in under 10 minutes, no risk of breaking anything else |
| Casual player, wants it fixed once | Run the full DDU clean driver reinstall directly, skip the plain driver update | Saves a second round trip if the plain update doesn’t hold — worth the extra 15 minutes upfront |
| Hardcore / overclocker | Revert every non-stock voltage/clock/timing first, before touching drivers | An unstable overclock produces identical symptoms to a bad driver, and you’re the player most likely to have one running |
| Completionist / troubleshooting for someone else | Read the exact exception code and faulting module before recommending any fix | Guessing wastes the other person’s time; the log already narrows it to one of three categories |
The Fail-Safe Escalation Ladder
If you’ve worked through the relevant section above and the crash is still happening, don’t jump straight to reinstalling Windows — that’s the last step, not the first. A real Microsoft support case worked through this exact order before finding a fix: Windows Update (including optional updates), GPU driver update, BIOS update, sfc /scannow, DISM repair, MemTest86, a storage health scan, chipset driver update, and a temperature check — all before the actual fix (re-registering the ntdll.dll system file) resolved it [5]. If every step here fails, a clean Windows reinstall is the documented next step, not a panic move [5].
Frequently Asked Questions
Should I just reinstall Windows if a game keeps crashing?
No — reinstalling Windows fixes a genuinely corrupted system, but it wastes hours if your actual problem is one bad overlay or an unstable RAM overclock, both of which survive a Windows reinstall untouched. Read the exception code first; only escalate to a full reinstall after driver, memory, and thermal checks have all failed [5].
I verified my game files and it still crashes — now what?
Verification only catches corrupted or missing files; it does nothing for a driver conflict, a RAM fault, or an overheating component, which is why it clears up some crash reports but leaves plenty of others untouched. If verification didn’t help, the faulting module and exception code in Event Viewer tell you which of the other categories you’re actually dealing with.
How do I tell if it’s my GPU driver or my RAM causing the crash?
If only one specific game crashes and everything else on your PC is rock-solid, suspect the driver or that game’s files first. If multiple unrelated games and even non-gaming apps crash at random, or Reliability Monitor shows unrelated errors on the same days, suspect RAM or the page file — test with MemTest86 before spending more time on driver reinstalls [2].
Sources
- Microsoft. Memory allocation errors can be caused by slow page file growth. Microsoft Learn
- PassMark Software. MemTest86 Troubleshooting Guide. MemTest86
- Valve Corporation. Verify Integrity of Game Files. Steam Support
- NZXT. Clean Install GPU Drivers with DDU: Step by Step. NZXT
- Microsoft Q&A community. All games randomly crashing to desktop, event viewer: ntdll.dll. Microsoft Learn
- Microsoft Q&A community. Exception code: 0xc0000005 error when playing games. Microsoft Learn
I've been playing video games for over 20 years, spanning everything from early PC titles to modern open-world games. I started Switchblade Gaming to publish the kind of accurate, well-researched guides I always wanted to find — built on primary sources, tested in-game, and kept up to date after patches. I currently focus on Minecraft and Pokémon GO.