Your laptop runs fine for browsing and office work, then blue-screens twenty minutes into a game. That pattern is a diagnostic gift: gaming stresses the GPU, CPU, RAM, thermals, and power delivery simultaneously, which narrows the suspects dramatically.
Game-only crashes are almost always the graphics driver, overheating, unstable RAM, or the power supply sagging under load. Our gaming crash reference has the background; the steps below isolate which one is yours. Start at Fix 1.
Why this happens
An unstable or corrupted GPU driver crashing under 3D load.
GPU or CPU overheating — gaming heat that desktop use never produces.
RAM instability that only shows when games fill memory and stress the controller.
An underpowered or aging power supply/charger sagging under gaming load.
Overclocked GPU, CPU, or RAM (including factory overclocks) failing under sustained load.
Corrupted DirectX or Visual C++ redistributables the game depends on.
How to fix it
Work through these in order, starting with Fix 1. Most of these crashes are resolved by one of the first three fixes, so don’t skip ahead.
Fix 1: Note the stop code and suspect file
Game crashes still leave the usual evidence. Capture it before changing anything.
Photograph the blue screen, noting the stop code and any .sys file named.
After rebooting, check Event Viewer > Windows Logs > System for the BugCheck entry.
Common gaming culprits: nvlddmkm.sys / amdkmdag.sys (GPU driver), 0x00000116 (VIDEO_TDR_FAILURE).
If it’s VIDEO_TDR_FAILURE, the GPU driver is suspect number one — continue below.
Fix 2: Clean-reinstall the GPU driver
Standard driver updates leave remnants behind. A true clean install with DDU is the real fix for driver-caused gaming crashes.
Download Display Driver Uninstaller (DDU) and the latest GPU driver (NVIDIA: official download page ; AMD: AMD driver page ).
Boot into Safe Mode and run DDU to remove the GPU driver completely.
Restart normally and install the fresh driver, choosing Custom > Clean installation if offered.
Test with the game that crashed — give it a full session, not five minutes.
Fix 3: Monitor temperatures while gaming
Heat is the second-biggest gaming crash cause. Measure it instead of guessing.
Install HWiNFO and enable logging, or watch GPU-Z / Core Temp on a second monitor.
Play until just before the usual crash point and note peak GPU and CPU temps.
Sustained 90°C+ on the GPU or 95°C+ on the CPU means thermal trouble.
Clean vents with compressed air, use a cooling pad, and cap framerates to reduce load. Repasting helps chronic cases.
Fix 4: Test the RAM
Games fill RAM and hammer the memory controller — marginal sticks crash here while passing desktop use.
Press Win + R, type
mdsched.exe, and run the Windows Memory Diagnostic.For certainty, run MemTest86 from USB for 2+ passes.
If your RAM runs XMP/EXPO, disable it in BIOS and retest — gaming is where unstable memory overclocks die.
Replace faulty sticks; no driver tweak fixes bad RAM.
Fix 5: Check power delivery
Gaming can double a laptop’s power draw. A weak charger or battery causes crashes that look like GPU failures.
Game with the original manufacturer charger plugged in — not a third-party or underpowered one.
In Control Panel > Power Options, use High performance (not Power saver).
If the laptop only crashes on battery, the battery can’t sustain gaming load — that’s normal; game plugged in.
Try a known-good charger of the correct wattage if crashes persist.
Fix 6: Repair DirectX and Visual C++ runtimes
Corrupted shared gaming components crash games and sometimes the display driver with them.
Download the DirectX End-User Runtime from Microsoft and install it.
In Settings > Apps, repair or reinstall the Microsoft Visual C++ Redistributables (both x86 and x64, all years).
Verify game files through Steam > Properties > Installed Files > Verify integrity (or the equivalent in your launcher).
Retest. Full DirectX guidance is on Microsoft’s Windows support pages .
Fix 7: Undo overclocks and test at stock
GPU/CPU/RAM overclocks — including manufacturer ‘OC mode’ utilities — are a top cause of load-only crashes.
Reset any GPU overclock in MSI Afterburner or similar to defaults.
Disable XMP/EXPO in BIOS and set any performance utility to Balanced.
Test the game at completely stock settings.
If crashes stop, your overclock was unstable — re-tune conservatively or leave it stock. Our WHEA guide covers hardware-error crashes that often accompany this.
Fix 8: Isolate the subsystem with separate stress tests
Instead of guessing between GPU and CPU, stress them independently. Whichever test crashes tells you which half of the machine to focus on — fifteen minutes each, definitive answer.
Download FurMark and run its GPU stress test for 15 minutes, watching temperatures.
If FurMark crashes or artifacts, the GPU side (driver, thermals, or card) is the problem.
Next, download Prime95 and run Small FFTs for 15 minutes to hammer the CPU and RAM.
If Prime95 crashes it, suspect CPU thermals, RAM, or power delivery — not the graphics driver.
If both pass but the game still crashes, it’s driver- or game-specific: clean-reinstall the GPU driver and verify game files.
Note peak temperatures from both tests — a crash at 97C and a crash at 70C are completely different diagnoses.
Closing
Blue screens that only happen while gaming are the most diagnosable kind: the trigger is load, so the suspects are the GPU driver, heat, RAM, and power. Clean-reinstall the GPU driver with DDU, watch your temperatures, and test the RAM — that trio resolves the overwhelming majority of gaming crashes on Windows 10. And once it’s stable, keep the GPU driver current but skip day-one ‘game ready’ releases unless the game you play needs them; a driver that’s been out for two stable weeks beats a shiny new one that blue-screens. Stress-testing the GPU and CPU separately is the fastest way to split ‘graphics problem’ from ‘system problem.’ Note your peak temperatures during the tests too — the numbers make the difference between a heat issue and a driver issue obvious, and they tell a repair shop exactly where to look if it comes to that.
