What fixes should I try for a newly released AAA game crashing after 20 minutes?
#1
I'm trying to play a newly released AAA game on my PC, but it keeps crashing to desktop without an error message about twenty minutes into any session. My system meets the recommended specs, I've updated my graphics drivers, and I've verified the game files through the launcher. For others who have dealt with similar game crash fixes, what troubleshooting steps should I try next? Should I be looking at Windows event logs, adjusting in-game settings like DirectX version, or could it be a background application conflict? I'm also wondering if a clean Windows install is a realistic last resort or if there are more targeted solutions I haven't considered yet.
Reply
#2
Here's a practical triage you can run this weekend to pin down what's causing the crashes. Start with some quick, low-friction checks and then move into deeper diagnostics if needed:
- Gather basics: confirm you’re on the latest game patch, the latest GPU driver, Windows updates installed, and you’ve got at least a couple of hours of stable power supply (no power-save quirks).
- Try a clean boot: disable non-essential startup programs and services, then launch the game to see if the crashes keep happening. If they stop, re-enable items one by one to identify the culprit.
- Check in-game settings: test with DirectX 11 vs DirectX 12, disable ray tracing where present, and switch off overlays (Steam/Discord/NVIDIA). Set to fullscreen or borderless fullscreen to see if one mode is more stable.
- Temperature and power: monitor GPU/CPU temps during play and ensure the notebook/desktop isn’t thermal throttling. Also check your power plan in Windows (High Performance) and make sure your PSU is delivering enough wattage for peak usage.
- Logs and dumps: open Event Viewer (Windows + X → Event Viewer) and look under Windows Logs → Application and System for errors around the crash time. Note the faulting module name and an Event ID (common IDs are 1000, 1002). If you see a crash dump, grab the minidump file in C:\Windows\Minidump and consider using a viewer (BlueScreenView or WinDbg) for a quick read.
- Reliability Monitor: type Reliability in the Start menu, find the crash entry, and drill into details to see what happened prior to the crash. This can reveal a repeating software or driver issue.
- Memory and disk health: run Windows Memory Diagnostic or MemTest86 for RAM health, and run CHKDSK or vendor tooling to check storage health. If you’re on an SSD, check SMART data for signs of impending failure.
- Optional but powerful: temporarily swap to a different GPU if you have one or test the game on another drive to rule out a faulty install.

If you still crash after this, move to a targeted fix. The next steps depend on what you see in logs and diagnostics.
Reply
#3
If you want a more guided log analysis, here’s how to interpret common crash signals in Event Viewer. Look for: 1) Faulting application name (the game) and faulting module (e.g., dxgi.dll, nvwgf2umx.dll, or a .dll loaded by the game). 2) The stack trace or fault offset; these hint whether the crash is GPU, memory, or CPU-related. 3) The time stamp aligns with a driver update or Windows update.
Export the relevant events (Action > Save All Events As…) and share the details if you want a second look. Also note if there’s a crash dump: Minidump (*.dmp) or Memory.dmp; if you don’t have dumps enabled, you can enable them in System Properties > Advanced > Startup and Recovery > Write debugging information (set to Small or Kernel memory dump).
If you can grab a frame of the game’s log (some games write their own crash logs in AppData or My Documents), include that too. A lot of issues boil down to a mismatch between DX version and GPU drivers, or a peripheral/overlay clash.
Reply
#4
Background apps and overlays bite a lot of players. Try this sequence if you’re not sure where the conflict lies:
- Disable overlays (Steam Overlay, Discord Overlay, GeForce Experience, etc.). Run the game with all overlays off.
- Do a clean boot (as above) and test with only essential software running.
- If you’re using antivirus or security software, temporarily disable it for a test (don’t game without protection, but you’re isolating the issue here).
- Check for background software that streams/recording: that can spike GPU/CPU usage or cause driver timeouts.
- Verify game/game launcher isn’t forcing a conflicting DirectX mode or a runtime package; repair or reinstall runtimes if needed (DirectX End-User Runtime, Visual C++ redistributables).
- If a crash occurs after a specific event (like loading a new area or starting a mission), try disabling assets like ray tracing or a particular shader feature (if the game exposes it) to confirm.
Document results and revert to your baseline configuration after testing.
Reply
#5
Deeper checks you might do if the above doesn’t help: run a memory test (MemTest86) and monitor RAM ages. Check disk health and SMART status. Confirm you have a clean install of the game on an SSD if possible, and consider a re-install of the GPU driver—sometimes a clean install fixes stubborn driver conflicts. If you’re comfortable, try a Windows repair install (in-place upgrade) to fix corrupted system files without removing your apps; otherwise a fresh Windows reinstall is a last resort.
For Windows, run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth to repair OS components. If you’re using a laptop, ensure battery/power management isn’t throttling performance during gaming.
If you still crash, gather your data (logs, temps, settings) and bring it to a game-specific forum/thread; the developers or other players with the same hardware often pinpoint obscure driver or game-specific conflicts."],

"Almost-last-resort route: last path is a repair install of Windows or a clean Windows reinstall if nothing else works. Before you go there, exhaust the other options: confirm you have a recent full backup, create a bootable USB with the latest Windows image, and run the repair install (in-place upgrade) from inside Windows to preserve apps and data. A full reset is too drastic unless you have no other choice. Be prepared for a reinstall of some drivers and apps, and you’ll want to re-check the game settings and potential driver conflicts after the repair.
Reply


[-]
Quick Reply
Message
Type your reply to this message here.

Image Verification
Please enter the text contained within the image into the text box below it. This process is used to prevent automated spam bots.
Image Verification
(case insensitive)

Forum Jump: