MultiHub Forum

Full Version: How can I diagnose a mysterious crash-to-desktop in a new AAA title?
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I'm a PC gamer with a relatively new, well-specced system, and a specific AAA title keeps crashing to desktop without an error message about twenty minutes into gameplay. I've verified the game files, updated my graphics drivers to the latest stable version, and even did a clean Windows install, but the problem persists. For others who have solved similar mysterious game crashes, what deeper diagnostic steps should I take? Should I be looking at potential RAM instability with a memory test, or could it be a power supply issue even though other, more demanding games run fine? Are there specific logging tools or event viewer codes that can pinpoint the culprit when the game itself provides no feedback?
You're not alone; the missing error message often means driver/hardware interplay. Start by enabling crash dumps and collecting logs. In Windows: Control Panel > System > Advanced system settings > Startup and Recovery > write debugging information: Small memory dump (256 KB) or Kernel memory dump. Then open Event Viewer (eventvwr.msc) and look under Windows Logs > Application and System for recent errors around game time. Note the faulting module, fault offset, and the process name. Save the .evtx and the dump file if possible. Use Reliability Monitor (perfmon /rel) to see patterns across boots. If a dump points to the GPU driver, test with an older driver vs latest, and verify hardware temps with HWInfo. If you see a Kernel-Power 41 error, power supply or overclock could be culprits.
RAM tests are low-hanging fruit. Run a full Memory Diagnostic (Windows Memory Diagnostic) or better yet MemTest86+ for multiple passes (at least 4–8). If you find errors, swap sticks, reseat modules, and try testing each module individually to isolate a bad DIMM. Temporarily disable XMP/overclocking so the RAM runs at safe defaults, and re-run until you confirm stability.
Check storage health and integrity. Run CHKDSK for your drive, check S.M.A.R.T. data with CrystalDiskInfo, and test for file system errors. A failing drive can cause crashes even if temperature/temps look fine. If the game is installed on a HDD/SSD, consider moving to another drive as a quick test.
Power and temps matter more than you think. Use HWInfo64 or similar to log temps, clocks, and voltages during gameplay. If you notice CPU/GPU throttling, power supply sag, or unusually high temperatures, that can crash or throttle the game. Temporarily set the GPU to stock clocks, disable aggressive power saving, and see if stability improves.
Diagnostic approach: try a controlled, repeatable test. Run a couple of other demanding games or a synthetic stress test (heavier GPU/CPU load) while monitoring with the same tools. If crashes only happen with one title, your issue is likely game-specific (mod, corruption, DRM) or a specific driver interaction. If it happens across titles, it’s system-wide.
If you want, share your rig details (CPU/GPU/RAM, power supply, motherboard, Windows version, game title), plus what you’ve already tested; I can help you assemble a 1-page diagnostic checklist and a plan to isolate the culprit more quickly.