The quick answer
To fix a game that keeps crashing on PC, start with the simple, safe steps: restart the PC, update or clean-reinstall your graphics driver, verify the game’s files through its launcher, close overlays and background apps, and remove any mods. If crashes continue, return any overclocks or RAM profiles to stock settings, check temperatures, and look in Windows’ error logs for clues.
The order matters. First work out what kind of crash you have, because that tells you where to look.
First, identify the kind of crash
| What happens | What it usually points to |
|---|---|
| Game closes to the desktop (CTD), PC keeps running | The game, its mods, drivers or overlays |
| Game freezes and you have to force-close it | Drivers, memory pressure, storage or the game itself |
| Screen goes black or the driver “recovers” | Graphics driver, GPU overclock or GPU stability |
| Whole PC freezes, reboots or shows a blue screen | Drivers, hardware, power or temperatures |
| Only one game crashes | Usually that game’s files, settings or mods |
| Many games crash | Usually drivers, Windows or hardware |
| Crashes after a set time of play | Often heat, memory leaks or power delivery |
Note when the crash happens (at launch, in menus, while loading, or after a period of play) and whether it started after a change such as a driver update, Windows update, new hardware or new mod.
Quick fixes to try first
- Restart the PC fully. Use Restart rather than Shut down, since Windows’ fast startup means a shutdown doesn’t always fully reset the system.
- Update Windows and restart again.
- Update the graphics driver from NVIDIA, AMD or Intel directly. Avoid third-party “driver updater” tools.
- Close overlays and background apps, such as recording overlays, monitoring tools, RGB software and chat overlays, then test.
- Lower graphics settings temporarily to see whether the crash is load-related.
- Check free disk space. Games need room for caches and updates.
Fixes for crashes in one game
- Verify or repair game files. In Steam, verify integrity of game files. In the Xbox app and other launchers, use the repair option.
- Remove mods and add-ons. Move them out rather than deleting them, test, then add them back in small groups to find the cause.
- Reset the game’s settings by renaming its settings file so the game creates a fresh one.
- Install required runtimes. Some games need Microsoft Visual C++ Redistributables or DirectX components. Get them from Microsoft’s official site or the game’s own installer.
- Check the game’s official forums for known issues after a recent patch, and any official workaround.
- Reinstall only once the steps above have failed.
Fixes for crashes in every game
- Clean-install the graphics driver. Use the driver installer’s clean install option. Some users also use Display Driver Uninstaller (DDU) in Safe Mode to fully remove old drivers first. If crashes began after a driver update, try the previous version.
- Repair Windows system files. Open Command Prompt as administrator and run
sfc /scannow, thenDISM /Online /Cleanup-Image /RestoreHealthif problems are reported. - Do a clean boot to start Windows with only Microsoft services, then re-enable startup items gradually to find a conflict.
- Check the page file. If you’ve disabled Windows virtual memory or set it very small, set it back to system-managed. Many games rely on it, especially on PCs with 16 GB of RAM or less.
- Review security software. Third-party antivirus can occasionally interfere with games. Temporarily disabling it for a test is fine, but turn it back on afterwards. Built-in Windows Security is generally sufficient for most users.
Check temperatures, power and overclocks
Hardware stability is behind many “random” crashes:
- Temperatures: use a monitoring tool such as HWiNFO or your GPU vendor’s overlay to watch CPU and GPU temperatures while playing. If temperatures are very high or clocks drop sharply, clean dust from fans and filters and check airflow. Safe limits vary by component, so compare against the manufacturer’s specifications.
- Overclocks and undervolts: return the CPU, GPU and RAM to stock settings for testing. Factory-overclocked GPUs can occasionally benefit from a small clock reduction using the vendor’s tool.
- RAM profiles (XMP/EXPO): these are a common hidden cause. Disable the profile in the BIOS to test. If crashes stop, the memory may need a BIOS update, a less aggressive setting or a check that it is a supported kit.
- Power: an ageing or undersized power supply can cause crashes or reboots under heavy load. Laptop users should play on mains power with the performance power mode.
Read the error logs
Windows records crash details that can point to the cause:
- Event Viewer: open it, go to Windows Logs > Application, and look for an Error entry at the time of the crash. “Application Error” entries list the faulting application and faulting module, which might be a graphics driver file, a mod or a system library. Check Windows Logs > System too, particularly for full-system crashes.
- Reliability Monitor: search for “View reliability history” for an easier timeline view of crashes.
- Minidumps: after a blue screen, dump files are usually saved in
C:\Windows\Minidump. These can be analysed with tools such as WinDbg, or shared on support forums. - Windows Memory Diagnostic: a built-in test that checks RAM for obvious faults.
Search the faulting module name or stop code along with the game’s name. Others have often hit the same problem.
Extra steps for flight simulators
Flight simulators push PCs harder and for longer than most games, and they have add-on ecosystems that create extra failure points:
- Add-ons first. Outdated or incompatible add-ons are the leading cause of sim crashes after an update. In Microsoft Flight Simulator, empty the Community folder for testing. Our guide on installing add-ons in the MSFS Community folder shows where it is.
- Memory pressure. Large scenery packages, high settings and long flights use a lot of RAM and VRAM. Keep the page file enabled and reduce texture or scenery settings if crashes happen in dense areas.
- Caches. Corrupted scenery caches can cause failures. Clearing a sim’s rolling cache is a reasonable step if you see corrupted or missing scenery.
- Controllers and USB devices. Unplug non-essential peripherals to rule out a problem device.
- External tools. Utilities that connect to the sim, such as trackers, replay tools and panel software, should be updated after sim updates.
For a detailed MSFS walk-through, including DLSS and frame generation settings that affect stability, see our MSFS performance and crash-fix guide.
When it’s probably hardware
Suspect a hardware fault when:
- Crashes happen across many games, with clean drivers and stock settings
- The whole PC reboots or shows blue screens with varied stop codes
- Memory tests report errors
- Problems get worse with heat or heavy load
At that point, testing parts one at a time (for example, one RAM stick at a time) or contacting the manufacturer or a repair service is the sensible route. If the PC is under warranty, avoid opening it in ways that might affect coverage, and contact the seller or manufacturer first.