PC Crashes or Blue Screens When Gaming? Find the Cause (Windows 11 & 10)

When a PC crashes or blue-screens only while gaming, the cause is almost always one of five things: the graphics driver, overheating, unstable memory or overclocks (including XMP/EXPO memory profiles), the power supply, or the game's own files or overlays. Games push the GPU, CPU, memory and power supply harder than anything else, so they expose weaknesses that everyday use never touches. Start by noting the stop code and checking Reliability Monitor (perfmon /rel). Then clean-install the latest GPU driver, watch temperatures while playing, turn off overclocks and XMP to test, and update the BIOS. Verify the game files and turn off overlays. That order fixes the large majority of gaming crashes.

Ethan's son saved for months for a gaming PC, and two weeks after it arrived it started shutting off in the middle of matches, sometimes with a blue screen, sometimes with no warning at all. Ethan feared the new PC was faulty. Jake asked for one evening with it. Reliability Monitor showed a pattern of "hardware error" events, temperature monitoring showed the graphics card running hot, and the power cable to the card was not fully seated in its socket. One firm push on the connector, a clean graphics driver install and a dusting of the intake filter later, the PC ran a three-hour session without a hiccup. This page follows the same method: read what Windows recorded, then test the likely causes in order.

Work through the steps in order and change one thing at a time, testing with the same game between changes. That is the only way to know which fix worked.

Crash, freeze, blue screen or shutdown: what each points to

The last two rows are the most useful split. A problem in one game is usually software; a problem across many demanding games is usually hardware stress, which is where heat, power and stability come in.

Disconnects are not crashes

In online games, a sudden return to the menu with a connection error is a network disconnect, not a crash, and the fixes are different: check your internet connection, use a wired connection where possible, and check the game's server status. Our network troubleshooting guides cover Wi-Fi and connection problems. Telling the two apart early avoids reinstalling drivers for a problem that lives in the router.

The same goes for a game that freezes for a few seconds and then resumes: that is usually a network hiccup or a background task, such as an antivirus scan or update download, rather than a hardware fault, and it shows up as a spike in network or disk activity in Task Manager rather than as a crash in Reliability Monitor.

Many games log disconnects separately in their own crash or log folders, which support teams can use to tell the difference.

Read what Windows recorded

Windows keeps a record of every crash, and reading it first saves hours of guessing. On the stop screen, note the stop code, such as VIDEO_TDR_FAILURE or WHEA_UNCORRECTABLE_ERROR, and any file name shown. Recent Windows 11 versions show a simpler stop screen, black rather than the classic blue, but the stop code is still there. If the screen flashed by too quickly, Windows records it afterwards.

1. Press Windows + R, type perfmon /rel and press Enter to open Reliability Monitor.
2. Find the days with red crosses and select each one.
3. Look for Windows stopped working, Shut down unexpectedly and Hardware error entries, and the game's own crash entries.
4. Select View technical details to see the stop code and the driver or module involved.
5. Open Event Viewer, eventvwr.msc, and look in Windows Logs > System for Kernel-Power event 41, WHEA-Logger events and BugCheck events at the crash times.

Kernel-Power 41 alone means the PC lost power or stopped without shutting down cleanly, which points toward power or a hard freeze. WHEA-Logger events mean the hardware itself reported an error, often CPU, memory or PCIe related. A BugCheck entry contains the stop code. Our guide to reading Event Viewer logs explains filtering.

If the PC restarts so quickly that you never see the stop screen, turn off automatic restart: in System Properties > Advanced > Startup and Recovery > Settings, uncheck Automatically restart. The stop screen then stays visible until you restart, giving you time to note the code.

Export a Reliability Monitor report with Save reliability history at the bottom of its window if you plan to ask for help; it captures every event in one file.

Common gaming stop codes and what they mean

• VIDEO_TDR_FAILURE or VIDEO_SCHEDULER_INTERNAL_ERROR: the graphics driver stopped responding. Driver, GPU overclock, heat or power. Our guide to VIDEO_TDR_FAILURE covers it in depth.
• WHEA_UNCORRECTABLE_ERROR: a hardware error, most often CPU or memory instability from overclocks, XMP, voltage or a faulty part.
• MEMORY_MANAGEMENT and PAGE_FAULT_IN_NONPAGED_AREA: memory problems, unstable XMP or a failing RAM stick, sometimes a driver.
• IRQL_NOT_LESS_OR_EQUAL and DRIVER_IRQL_NOT_LESS_OR_EQUAL: usually a faulty driver; the details often name it.
• CLOCK_WATCHDOG_TIMEOUT: a CPU core stopped responding, typically CPU instability.
• DPC_WATCHDOG_VIOLATION: a driver or storage device took too long; check storage and chipset drivers.
• KERNEL_SECURITY_CHECK_FAILURE: often driver or memory corruption.

Stop codes narrow the search but rarely name the cause outright. Treat them as a starting direction, then confirm with the tests below.

If the details name a file ending in .sys, search for that file name: it usually belongs to a specific driver, such as the graphics driver, a network driver or an antivirus product, which tells you exactly what to update or remove.

Clean-install the graphics driver

The graphics driver is the most common cause of gaming crashes, especially after a game update that expects a newer driver, or after a Windows update replaces the driver with an older one. A clean install removes leftovers that a normal update can leave behind.

1. Download the latest driver for your graphics card from NVIDIA, AMD or Intel, and keep the installer ready.
2. Disconnect from the internet briefly, so Windows Update does not install its own driver in the middle of the process.
3. Uninstall the current driver from Settings > Apps > Installed apps, or use the installer's clean or factory reset option where offered.
4. Restart, install the downloaded driver, then reconnect to the internet.
5. Test with the game that crashed.

Many enthusiasts use Display Driver Uninstaller, a free third-party tool run in Safe Mode, for a deeper clean when ordinary uninstalling is not enough. If the newest driver is the problem, roll back to the previous version and wait for the next release; our guides to uninstalling a driver and stopping Windows reinstalling it cover both. If the screen goes black and recovers with a message, see our page on "Display driver stopped responding".

Graphics drivers come in two flavors from NVIDIA and AMD: the latest feature releases and more conservative studio or recommended releases. If the newest game-ready driver crashes, the recommended or studio branch is a sensible fallback.

Check temperatures while gaming

Overheating causes crashes, sudden shutdowns and throttling that feels like stutter. Components protect themselves: a CPU or GPU that gets too hot slows down, and if it keeps rising, the system shuts off. Gaming is when temperatures peak.

Use a monitoring tool that logs temperatures, such as the GPU maker's overlay, Task Manager's GPU temperature on supported cards, or a free hardware monitor that shows CPU and GPU sensors. Play for twenty minutes and note the maximums. As a rough guide, modern CPUs commonly run up to the 80s and 90s Celsius under load and throttle near their limit, around 95 to 100 °C on many models; GPUs usually run in the 60s to 80s, with a separate hotspot reading that runs higher. Consistent readings at the limit, or rising until a crash, point to cooling.

Fixes are usually simple: clean dust from filters, fans and heatsinks; make sure case fans blow in the right directions; give a laptop space to breathe and use it on a hard surface; and, on older PCs, replace dried-out thermal paste. Ethan's son's PC had a dust filter already clogged after two weeks in a carpeted room.

Laptops reach higher temperatures by design and are built to tolerate them; what matters is whether they stay steady during play or climb until a shutdown.

Fan curves and case airflow

Desktop cases need a clear airflow path: cool air in at the front or bottom, warm air out at the back and top. Fans fitted backwards, a front panel with no intake, or cables blocking the path can raise temperatures by many degrees. Check each fan's direction, which is usually shown by arrows on its frame. In the BIOS or the motherboard maker's software, set fan curves so fans speed up as temperatures rise, rather than staying quiet under load. Many graphics cards also let you set a more aggressive fan curve in their software.

Room temperature matters too: a PC in a warm room or a closed cabinet runs hotter, and summer crashes that disappear in winter are a classic sign of marginal cooling.

For laptops, the equivalent is a clean intake and exhaust, and never gaming on a bed or sofa, where fabric blocks the vents underneath.

Gaming laptops: extra checks

Gaming laptops pack hot components into a thin case, so heat and power deserve extra attention. Game plugged in with the original charger, since many laptops limit performance or behave erratically on battery and lower-wattage chargers. Use the maker's control app to choose a performance mode and check that fan profiles are not set to silent. Raise the back of the laptop or use a stand so the bottom intakes are not blocked, and clean the vents every few months.

Laptops with both integrated and dedicated graphics switch between them; occasionally a game runs on the wrong one or the switch misbehaves. In Settings > System > Display > Graphics, set the game to High performance. Some laptops have a MUX switch in the maker's app or BIOS that connects the display directly to the dedicated GPU; switching modes and restarting can fix crashes tied to graphics switching.

Laptop makers also release BIOS and embedded controller updates that change fan behavior and power limits; install them from the maker's support page or app, especially if the laptop is a recent model.

On battery, many gaming laptops reduce GPU power sharply by design, so a game that runs on the charger but crashes on battery may simply be hitting that limit.

Overclocks, XMP and BIOS updates

Overclocking, whether you did it or the PC came with it, is a major cause of crashes that appear only under heavy load. That includes GPU overclocks in tools like MSI Afterburner, factory-overclocked graphics cards, CPU overclocks and automatic boost settings, and memory profiles called XMP on Intel systems and EXPO on AMD, which run RAM faster than its default speed.

To test, return everything to defaults: reset GPU tuning tools, and in the BIOS, load optimized defaults or turn off XMP or EXPO. Play as before. If crashes stop, the overclock or memory profile was unstable; you can then re-enable it with slightly lower speeds or leave it off. The performance difference from XMP is real but smaller than people expect, and a stable PC is always faster than one that crashes.

Update the BIOS as well. Motherboard makers release updates that fix memory compatibility and CPU stability. Some Intel 13th and 14th generation desktop processors had a well-documented instability problem, causing crashes in games, that Intel addressed with microcode updates delivered through BIOS updates in 2024; if you have one of those processors, a current BIOS is essential. Follow the motherboard maker's instructions carefully, and do not interrupt the update.

Older PCs: wear and age

Components age. Thermal paste between the CPU or GPU and its cooler dries out over several years, raising temperatures; fans slow and collect dust; and power supplies lose some capacity as their parts age. An older PC that ran a game fine two years ago may crash with the same game today, especially after an update made the game more demanding. Fresh thermal paste, clean fans and, if the power supply is old or was marginal from the start, a new quality power supply often restore stability. These are routine maintenance, not signs the PC is finished.

On older PCs, also check that the BIOS is not years out of date, since later versions often improve memory compatibility with newer modules added during upgrades.

Undervolting and power limits

The opposite of overclocking can fix crashes too. Undervolting runs a CPU or GPU at slightly lower voltage, reducing heat and power draw, often with no performance loss, and it is popular on gaming laptops. Lowering the power limit in GPU software has a similar effect. If a PC crashes from heat or power spikes, a modest power limit reduction is a quick, reversible test. Undervolting too far causes its own instability, so change in small steps and stress test each one. On some laptops, makers lock voltage controls; their performance modes are the safe alternative.

Undervolting settings live in tools from the CPU or GPU maker and in the BIOS; note your original values before changing anything, so you can return to them.

Test the memory

Faulty or mismatched memory produces random crashes and stop codes that change each time. Windows has a built-in test: press Windows + R, type mdsched.exe, choose Restart now and check for problems, and let it run. Results appear after Windows restarts, or in Event Viewer under MemoryDiagnostics-Results. For a more thorough test, bootable tools such as MemTest86 run for hours and catch subtle errors.

If errors appear, test sticks one at a time to find the faulty one. Make sure mixed kits are not the problem: RAM bought separately, even of the same model, does not always run reliably together at XMP speeds. Reseating the sticks in their slots, as the motherboard manual recommends, also fixes surprising numbers of problems.

Memory errors can also come from the memory controller in the CPU rather than the sticks themselves, which is one more reason to test at default speeds before concluding a stick is bad.

Stress tests: reproducing the crash on purpose

A crash that happens once an evening is hard to troubleshoot, so enthusiasts use stress testing tools that load the CPU, GPU, memory or all of them at once, recreating the stress of gaming in minutes. A GPU benchmark loop shows whether the graphics card is stable; a CPU stress test shows CPU and cooling stability; a combined test loads the power supply heavily. If a stress test crashes the PC quickly, you have a reliable way to check each fix. If it passes for an hour while the game still crashes, the cause is more likely software.

Watch temperatures during stress tests and stop if anything approaches its limit; the goal is to find instability, not to damage hardware.

Run each stress test separately first, CPU alone and GPU alone, before a combined test; a crash on one narrows the search far more than a crash on both at once.

Power supply and connectors

A PC that switches off instantly during gaming, with no blue screen and a Kernel-Power 41 event, often has a power problem. Modern graphics cards draw large, very brief spikes of power under load, and a power supply that is too small, old or of poor quality may shut down to protect itself. Check that your power supply's wattage meets the graphics card maker's recommendation, and that it comes from a reputable brand.

Check the cables too. High-end graphics cards use a 12VHPWR or 12V-2x6 connector that must be pushed fully into the socket; a partly seated connector can cause instability and, in rare cases, overheating of the connector itself. Use separate cables from the power supply for each power socket on the card rather than one daisy-chained cable where the manufacturer advises it. Laptops should be gamed on their original charger; a weaker charger can cause shutdowns under load.

Power settings can help too: lowering the GPU's power limit slightly in its software, or capping the frame rate, reduces those spikes. If either stops the shutdowns, the power supply is struggling, and replacing it with a higher-rated, quality unit is the lasting fix.

New prebuilt PCs: check for shipping issues

Prebuilt gaming PCs travel by courier, and rough handling can loosen parts. If a new PC crashes from the start, open the side panel, remove any foam packing inside the case, which manufacturers add to protect the graphics card in transit and expect you to take out, and check that the graphics card is fully seated in its slot and screwed to the case, that every power connector is pushed fully home, and that memory sticks are clicked in. This takes five minutes and solves a surprising share of new-PC crashes, as Ethan's son discovered. If you are not comfortable opening the case, the maker's support can talk you through it without affecting the warranty.

Also check that the graphics card's support bracket, if one was included, is installed; heavy modern cards can sag over time, stressing the slot and sometimes causing intermittent problems.

Verify the game files and settings

When only one game crashes, start with the game. Every major launcher can check and repair game files: in Steam, right-click the game, choose Properties > Installed Files > Verify integrity of game files; the Epic Games launcher, the Xbox app and others have similar Verify or Repair options. Corrupted files after an interrupted update are a common cause of crashes at launch or when loading a level.

Next, lower settings that stress the GPU, such as ray tracing, very high texture quality on cards with limited video memory, or frame generation features, and test. If the game is new, check its official forums or patch notes for known crash issues; many launch-week crashes are fixed by the developer within days. Deleting the game's shader cache, so it rebuilds, fixes stutters and some crashes after driver updates.

Mods are another common cause: if you use mods, disable them all and test the unmodded game, then re-add them one at a time after a game update, since mods often break when the game changes.

Storage and game installs

Modern games stream large amounts of data from storage while you play, and some use DirectStorage to load assets directly from fast SSDs. A game installed on an old hard drive or a nearly full, worn SSD can stutter badly and crash when loading. Install demanding games on an SSD, keep some free space, and check the SSD's health in its maker's tool. If a game crashes only in particular areas or while loading, moving it to a different drive is a quick test.

Game launchers can move installed games between drives without redownloading them, which makes this test quick.

Keep the SSD's firmware current as well; makers fix stability and performance issues in firmware, and a few firmware bugs have caused drives to drop out under heavy load.

Runtimes older games need

Games depend on shared components such as Microsoft Visual C++ Redistributables, .NET runtimes and DirectX. Modern games install what they need, but older games sometimes rely on legacy parts, especially older DirectX 9 components that Windows does not include by default. Installing Microsoft's DirectX End-User Runtime adds those legacy files and fixes many "missing DLL" errors and crashes at launch in older titles. Reinstalling the Visual C++ Redistributables from Microsoft repairs corrupted ones. For very old games, compatibility mode in the game's shortcut Properties can help as well.

Store and Game Pass versions of games handle runtimes through the Xbox app, which has its own repair option in the game's settings.

Reinstalling a game cleanly, after deleting its leftover folder in Documents or AppData, also resets corrupted settings files that verification does not touch.

Displays, cables and refresh rates

Some "crashes" are actually the display losing signal: the screen goes black while the game keeps running, and sound continues. High refresh rates and resolutions over a low-quality or overly long cable can do this. Try another DisplayPort or HDMI cable rated for your resolution and refresh rate, another port on the graphics card, and plug the display into the graphics card rather than the motherboard. Turning off adaptive sync features such as G-SYNC or FreeSync briefly is a quick test for flicker and black screens; our guide to screen flickering covers the display side.

For laptops connected to external monitors, also try the laptop's own screen alone; docking stations and adapters add another link that can drop the signal under load.

Overlays, recording and background apps

Overlays draw on top of games: Discord, Steam, the NVIDIA app, AMD Software, Xbox Game Bar, and performance monitors such as RivaTuner. They hook into the game's graphics and are a frequent cause of crashes, especially when several run at once. Turn them all off, then add back only the ones you need. Our guide to disabling the Xbox Game Bar shows how for that one.

RGB lighting software, fan control utilities, old tuning tools and some antivirus suites also interfere with games. A clean boot, starting Windows with non-Microsoft services and startup apps turned off through msconfig and Task Manager, quickly shows whether background software is responsible.

Peripheral software and drivers

Gaming mice, keyboards, headsets and controllers often come with their own software for lighting, macros and audio. These programs run in the background, hook into games for features such as per-game profiles, and load their own drivers. Outdated versions are a common cause of crashes, especially after game or Windows updates. Update them from the maker's site, or uninstall those you do not need; most peripherals work fine with Windows' built-in drivers, minus the extras. Virtual audio software for headsets and streaming is a frequent culprit when crashes coincide with sound glitches.

USB hubs and front-panel ports with many devices attached can also cause brief disconnects of controllers or headsets that some games handle badly; plugging key devices directly into rear motherboard ports is a simple test.

Anti-cheat software

Many online games use anti-cheat systems that run as kernel-level drivers, deep inside Windows. They can conflict with other low-level software, such as tuning utilities, RGB controllers, some antivirus products and virtualization features, causing crashes or refusing to let the game start. If crashes name an anti-cheat driver in Reliability Monitor or a dump, update the game, close tuning and monitoring tools before playing, and check the game's support pages for known conflicts. Reinstalling the anti-cheat component, which most games offer through their launcher's repair option, fixes broken installations.

Turning on Windows' Memory integrity occasionally blocks old drivers some games or tools rely on; the game's support pages say whether its anti-cheat requires or conflicts with particular security features.

When a game's anti-cheat refuses to start after a Windows update, waiting a day or two is often the fix; anti-cheat vendors push compatibility updates quickly after major Windows releases.

Windows updates and system files

If crashes started right after a Windows update, check Settings > Windows Update > Update history for what changed, including driver updates. Uninstalling the most recent quality update, as our guide to uninstalling a Windows update explains, is a valid test. Repair Windows' own files by opening Terminal as administrator and running DISM /Online /Cleanup-Image /RestoreHealth followed by sfc /scannow.

Also install chipset drivers from the motherboard or CPU maker, which matter for stability, and check storage: a failing SSD can cause crashes while games load data. The SSD maker's tool shows health and offers firmware updates, and storage-related stop codes are covered in our guide to storport.sys blue screens.

Keep at least 15 to 20 percent free space on the drive where games are installed too: large game updates need temporary room, and an almost full drive can make updates fail and leave games broken.

If repairs find and fix corrupted files repeatedly, suspect the storage drive or memory, which can corrupt files as they are written.

Hidden miners and malware

A PC whose graphics card runs hot even when idle may be running hidden cryptocurrency mining software, often bundled with pirated games, cheats or cracked tools. Miners load the GPU constantly, raising temperatures and making crashes during gaming much more likely. Check Task Manager's GPU usage at the desktop with no games running; it should be near zero. Run a full Microsoft Defender scan and a Defender Offline scan if anything looks wrong, and avoid game downloads from unofficial sources, which are the most common route for such software.

Cheat tools and "FPS boosters" from unknown sites also install kernel drivers of their own, a second reason they lead to crashes as well as account bans.

Defender's Protection history shows whether anything was found and removed, with dates you can match to when the crashes began.

Don't disable the page file

Some old optimization guides suggest disabling Windows' page file to speed up games. On a gaming PC, that is a reliable way to cause crashes: modern games can briefly need more memory than is physically installed, and without a page file they simply close or the system stops with a memory error. Make sure System Properties > Advanced > Performance Settings > Advanced > Virtual memory is set to Automatically manage paging file size for all drives, and that the system drive has some free space for it.

The same applies to aggressive memory-cleaning tools; Windows manages memory well on its own, and these tools mostly add another program that can crash.

When Windows will not start after a crash

Occasionally a crash leaves Windows unable to start normally, often after a bad driver install. Windows usually opens its recovery environment automatically after a few failed starts. From there, choose Troubleshoot > Advanced options > Startup Settings and restart into Safe Mode, where only basic drivers load. In Safe Mode, uninstall the most recent graphics driver or program, then restart normally. Our guide to booting into Safe Mode shows every route. System Restore, in the same advanced options, can also roll back to before the change if restore points exist.

Once Windows starts again, install the previous, known-good driver rather than the one that failed, and wait for the next release before trying again.

Game Mode and GPU scheduling

Windows has two settings worth testing. Game Mode, in Settings > Gaming > Game Mode, prioritizes games and pauses some background activity; it is normally best left on. Hardware-accelerated GPU scheduling, in Settings > System > Display > Graphics > Advanced graphics settings, changes how the GPU manages its work; it helps some systems and features, and is required for some features like frame generation on certain cards, but on others it has been linked to stutters or instability. If crashes persist, toggle it, restart and test.

Change one of these settings at a time and play a full session before judging; their effects are subtle and easy to confuse with normal variation.

Variable refresh rate and Auto HDR settings in the same Graphics page are also worth toggling once if crashes coincide with switching between the game and the desktop.

Reading crash dump files

For stubborn problems, Windows saves a small file for each stop error in C:\Windows\Minidump. Microsoft's free WinDbg app, from the Microsoft Store, opens these files; run the !analyze -v command and it reports the likely faulting driver or module. If several dumps name the same graphics, network or audio driver, that driver is your prime suspect. If they name different modules each time, suspect hardware, such as memory or CPU instability, instead.

Make sure dumps are being saved: in System Properties > Advanced > Startup and Recovery, set Write debugging information to Small memory dump or Automatic memory dump, and keep enough free space on the system drive.

If reading dumps feels daunting, attach them to a post on the game's or hardware maker's support forum; experienced volunteers read them regularly and can often name the culprit quickly.

When to use the warranty

If the PC is new and crashes persist after the software steps and default settings, do not spend weeks troubleshooting a faulty part. Note the stop codes, the results of memory and stress tests, and what you tried, and contact the maker or retailer. Prebuilt PCs and laptops are covered as a whole; for self-built PCs, each part has its own warranty, and the tests above help show which part to return. Graphics cards and memory are the most commonly replaced parts for gaming crashes, followed by power supplies.

Keep the evidence: screenshots of stop codes and exported Reliability Monitor reports make warranty claims much quicker.

Retailers' return windows are short, so on a brand-new PC that crashes from the first day, contact the seller early rather than troubleshooting past the return period.

The order Jake follows

1. Note the stop code and check Reliability Monitor and Event Viewer.
2. Verify the game files and turn off overlays if only one game crashes.
3. Clean-install the graphics driver.
4. Monitor temperatures during play and clean the PC if hot.
5. Reset overclocks and turn off XMP or EXPO to test.
6. Update the BIOS and chipset drivers.
7. Test the memory.
8. Check the power supply's rating and every power connector.
9. Repair Windows files and review recent updates.
10. Analyze crash dumps if the problem remains.

Most problems are solved by step five. Steps six to ten are for the persistent cases.

Keep a simple log as you go: the date, what you changed, and whether the game crashed in the next session. After a few evenings, the pattern is usually obvious, and the log is invaluable if you end up contacting support.

For Ethan's son, steps one, three and four found everything: Reliability Monitor showed hardware errors, the driver was replaced, and the heat check led straight to the dusty filter and the loose power connector.

Quick tests and what they rule out

The frame rate cap is an underrated test: limiting a game to, say, 60 frames per second lowers the load on the GPU and power supply. If crashes vanish with the cap, the hardware is struggling at full load, which points toward heat or power rather than software.

Run each test for at least one full session of the game that crashed most often, so a pass means something.

What this page said in 2019

The original version of this page, from April 2019, reported gamers' crashes and blue screens after a Windows 10 update that month. Specific update problems come and go, and that one was resolved long ago. The method for diagnosing gaming crashes has stayed the same, which is why this rewrite turns one month's news into a lasting guide.

If you arrived here because of a crash after a recent update, the method still applies: check update history first, then follow the order above.

Gaming crashes have only become more varied since then, as games grew more demanding, but the tools to diagnose them have improved just as much.

Gaming crashes and blue screens: frequently asked questions

Ethan's son has played for months since without a single crash. The fix that mattered most was the least technical: a power connector pushed fully home. The driver and the dust helped too. Jake's rule for gaming crashes is simple: let Windows tell you what happened, then test the likely causes one by one. A gaming PC that crashes is almost never a lost cause, just a problem waiting to be narrowed down.

Revision note. Written October 2, 2026, rewriting our 2019 news note on gaming crashes after a Windows 10 update into a complete guide to diagnosing crashes and blue screens while gaming. May every match end on your terms.