A PC game that keeps crashing can point to a damaged game file, an unstable driver, limited system resources, overheating, or a conflict with another program.
Work through these checks in order to narrow down the cause without making unnecessary changes to your PC.
Start with the crash pattern
Note when the crash happens: during startup, while loading a particular save, after several minutes of play, or only in multiplayer.
Also note whether the game closes to the desktop, freezes, restarts the PC, or displays an error message.
These details help distinguish a game-specific problem from a wider system or hardware issue.
- Crashes before the main menu: Check the game’s requirements, launch options, installed files, and security software.
- Crashes during demanding scenes: Check temperatures, graphics settings, power, and driver stability.
- Only one save or area crashes: Try another save or a new game; the affected file or game data may be damaged.
- Several games crash: Look first at shared causes such as drivers, memory, heat, or background software.
Write down the exact error text before dismissing it.
If the problem started after a game update, Windows update, driver change, or new hardware installation, include that in your notes.
Check the game’s requirements and updates
Compare your PC with the game’s minimum requirements on its official store page or support site.
Check the operating system, processor, graphics card, available memory, and storage space.
Minimum requirements indicate a baseline, not a guarantee that every setting or resolution will run reliably.
A system close to the minimum may need lower graphics settings and fewer programs open.
Install updates for the game through the launcher or store where you own it.
If the game uses a separate launcher, check that it is also updated.
Restart the PC after a major update, then launch the game again.
If a crash began immediately after an update, check the game’s official status page or support announcements for known issues before changing system settings.
Verify or repair the game files
Launchers often provide a check that compares installed files with the current version and replaces missing or damaged data.
The wording and location vary by launcher, so use its current help documentation if you cannot find the option.
For example, Steam’s official guidance on verifying game files explains the process for Steam installations.
After verification finishes, restart the launcher and try the game.
If the game still crashes, note whether the check found and reacquired files.
Avoid deleting folders manually unless the game’s support instructions tell you to; saved games, configuration files, and screenshots may be stored near game data, and their locations differ by title.
Update or roll back the graphics driver carefully
Graphics drivers affect how a game communicates with the GPU.
Download drivers from the official support page for your graphics hardware: NVIDIA, AMD, or Intel.
Confirm your exact graphics model and Windows version before installing.
If the crash started after a driver update, check the manufacturer’s release notes and consider returning to a known stable driver using the manufacturer’s instructions.
Install one driver change at a time and restart when prompted.
Avoid driver-download sites that bundle installers or claim to update every component automatically.
If you have both integrated and dedicated graphics, confirm that the game is using the intended GPU through Windows graphics settings or the graphics vendor’s official software.
Reduce overlays and background conflicts
Overlays, recording utilities, performance monitors, RGB-control tools, and third-party antivirus features can conflict with some games.
Close nonessential applications, then test the game.
If that resolves the crash, re-enable programs one at a time until the conflict returns.
This gives you a specific application to investigate rather than leaving essential software disabled.
Temporarily turn off optional overlays from the game launcher, chat application, or graphics software if the game’s support team recommends it.
Do not disable Windows security protections or allow a game through the firewall without a specific reason.
If security software reports that a game file is suspicious, check the game publisher’s support guidance and verify the installation before changing any security setting.
Check temperatures, power, and system stability
A game may crash when a CPU or GPU becomes too hot, especially if crashes happen after a consistent amount of play.
Check temperatures with a reputable monitoring tool from the hardware manufacturer or a well-established utility, and compare readings with the device maker’s published operating limits.
Make sure desktop vents are clear, fans can turn freely, and a laptop is used on a hard surface with unobstructed airflow.
Clean dust only using the device maker’s safety instructions.
If the PC shuts down or restarts rather than only closing the game, treat that as a broader stability issue.
Check that power cables are seated correctly and that the power supply meets the requirements of the installed hardware.
Remove any CPU, GPU, or memory overclock temporarily, including profiles applied by tuning software.
An unstable overclock can cause crashes even when other games appear to work.
Free memory and storage space
Close applications that use substantial memory, such as browsers with many tabs, video editors, virtual machines, or other games.
Use Task Manager to see whether memory or disk use is near capacity while the game runs.
Keep adequate free space on the drive containing both the game and Windows; updates and temporary files may need additional room.
If crashes occur when loading large areas or switching levels, check whether the PC meets the game’s recommended memory requirements.
Do not change the Windows paging file as a first step.
Let Windows manage it unless the game publisher or PC manufacturer provides a specific reason and instructions to adjust it.
Try lower graphics settings and reset custom configurations
Lower demanding settings such as texture quality, resolution, ray tracing, and frame rate, then test the same scene.
If the game becomes stable, raise one setting at a time to identify a likely pressure point.
A frame-rate cap can also reduce load on the GPU, especially when an uncapped game pushes hardware continuously.
If the game crashes before settings can be changed, use its official support instructions to reset configuration files or start with default settings.
Back up configuration files and saves first, and avoid downloading replacement files from unofficial sites.
Mods and custom reshade tools can also cause crashes after an update; temporarily remove them using the mod manager’s instructions, then test a clean game installation.
Use Windows repair tools and crash details
Install pending Windows updates, restart, and try the game again.
If multiple applications are also failing, use Windows’ built-in system file repair guidance from Microsoft: System File Checker and DISM instructions.
These tools check Windows system files; they do not repair a game’s own installation.
For more clues, open Event Viewer and look under Windows Logs > Application for an error at the time of the crash.
The faulting application, module, and code can help game support identify the problem, but a module name alone does not prove the cause.
Record the game version, Windows version, GPU model, driver version, crash time, and steps that reproduce the issue.
When to contact game or hardware support
Contact the game publisher if only that title crashes after file verification, updates, and a clean test without mods or overlays.
Send the exact error, relevant crash log, and a concise list of steps already tried.
Use the game’s official support channel and avoid posting personal account details or full diagnostic files publicly.
Contact the PC or hardware manufacturer if several games crash, the computer restarts, artifacts appear, or diagnostic tools report memory or storage errors.
For a useful final check, reproduce the crash once with default game settings, no mods, and nonessential overlays closed, then save the error text and timestamp for the support report.