Fixing Windows Crashes Step by Step So Your PC Stays Stable
Windows crashes after normal use are usually caused by a recent change, overheating, a bad driver, or corrupted system files. Start with the safest fixes first: restart, check recent updates, and roll back anything that changed just before the crashes began. If the problem keeps coming back after that, treat hardware or power delivery as a real possibility.
What the crash looks like matters
The pattern tells you a lot about where to look first.
Blue screen, instant restart, app closes, full freeze, or crash during gaming, startup, or other heavy useIf you see a blue screen, Windows is usually catching a serious driver or hardware fault. If the PC restarts with no message, that can still be a blue screen that reboots too fast to read, or it can be power-related. If only one app closes, the problem may be that app, a plug-in, or a driver it depends on. If the whole PC freezes, becomes unresponsive, or crashes during gaming, video playback, or other heavy use, overheating, unstable power, or a graphics driver is more likely.
Watch for timing too. Crashes right after a Windows update, driver update, new antivirus, new dock, or new hardware point toward a recent change. Crashes during startup can mean a bad startup app, a driver loaded early, or failing storage. Crashes only under load usually point away from random software and toward thermals, graphics, memory, or the power supply.
Which crashes this guide can fix
These steps are for Windows 10 and Windows 11 systems that started crashing after updates, driver changes, new software, or with no clear change at all. They work best when the problem is software-related or when software is exposing a weak hardware issue.
They are less likely to fix a machine that has obvious hardware trouble, such as repeated crashes before Windows fully loads, a strong burning smell, visible damage, or shutdowns that happen exactly when the machine gets hot or the power cord moves. If the PC crashes only during gaming or other heavy load and the fan area feels very hot, you should treat overheating or power delivery as a serious suspect.
Before you start:
- This applies to Windows 10 and Windows 11.
- Some steps need an Administrator account.
- A restart is involved early on.
- Back up important files before deeper troubleshooting if you have not done that recently.
- A safe first check is to note whether the crashes began after one specific change.
- Another safe check is to open Reliability Monitor so you can see whether Windows is reporting the same failure over and over.
Start with the safest fixes first
- Restart the PC cleanly.
A full restart clears stuck drivers, pending updates, and temporary glitches. If Windows still crashes right after boot, the problem is probably not just a one-time hiccup.
- Undo the most recent change you remember.
If the crashes started after a Windows update, new driver, new app, or new piece of hardware, remove or roll back that change first. For a recently installed app, uninstall it from Settings. For a driver, roll it back from Device Manager if the option is available.
- Check for Windows updates.
Open Settings and install pending updates, then restart if Windows asks you to.
Settings > Windows Update > Check for updatesIf crashes began right after an update, the fix can still be another update, since Microsoft often ships follow-up patches for bad behavior. If the system is worse after a specific update, note the update name before removing anything.
- Roll back a suspect driver.
This is especially worth trying for display, Wi-Fi, audio, storage, and chipset drivers.
Device Manager > device > Properties > Driver > Roll Back DriverIf the button is unavailable, Windows does not have an older driver to return to. In that case, you can uninstall the device driver and let Windows reinstall it on restart, or install a known-stable driver from the hardware maker later.
- Check for overheating signs.
If crashes happen in games, during video editing, or when the machine is under load, make sure vents are clear, fans are spinning, and the PC is not packed against a wall or soft surface. If the fan noise ramps up right before the crash, heat moves up the list. A dusty cooler or blocked airflow can make a system look like it has a software problem.
- Run the system file check tools.
Open an elevated Command Prompt or PowerShell window and run these commands one at a time.
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealthSFC repairs missing or damaged Windows files. DISM repairs the Windows image that SFC depends on. If SFC says it found and fixed files, restart and test again. If it says it could not fix some files, DISM often helps. If both tools finish cleanly and the crashes continue, software corruption is less likely to be the only cause.
- Boot into Safe Mode.
Safe Mode loads a minimal set of drivers and startup items. If the crashing stops there, the problem is usually a driver, startup app, or third-party service rather than core Windows itself.
Settings > System > Recovery > Advanced startup > Restart now > Troubleshoot > Advanced options > Startup Settings > RestartAfter restart, choose Safe Mode. If the PC is stable in Safe Mode but not in normal mode, focus on recent drivers, startup software, and anything that hooks into the system at boot.
Check whether Windows is stable now
Do not assume the fix worked just because the machine booted once. Recreate the action that used to trigger the crash and watch for repeat failures.
Open Reliability Monitor to see whether Windows is still logging app failures, driver failures, or blue screens.
Control Panel > Security and Maintenance > Maintenance > View reliability historyYou are looking for a steady line with no new red X entries after you made the change. If the same failure appears again, the latest fix was not the right one, or there is more than one problem.
You can also check Event Viewer for clues such as a specific driver name, kernel-power events, or repeated app errors.
Start > Event Viewer > Windows Logs > SystemIf crashes happen when you open one game, plug in one device, or launch one app, repeat that exact action. If the problem is gone there but returns later during heavy load, hardware stress is still on the table. If Windows stays stable for normal use, gaming, and startup over several sessions, the immediate crash issue is probably under control.
How to keep it from happening again
Once the system is stable, the best prevention is steady maintenance in the right order.
Keep Windows and your hardware drivers current, but only change one major thing at a time so you can tell what caused a problem. If a driver or update causes fresh crashes, make a note of it before trying something else. Create a restore point before installing a graphics driver, BIOS update, or other major change so you have an easy rollback path.
Watch temperatures if the PC tends to crash during gaming or heavy work. Dust buildup, blocked vents, and failed fans often show up as random instability long before a part fully fails. Avoid piling startup apps into the system tray, since they can create conflicts and make boot crashes harder to read.
If the crashes start coming back after you have already checked updates, drivers, system files, and Safe Mode, stop guessing. Back up your files and have the hardware tested, especially the RAM, storage, graphics card, and power supply. Repeating crashes that survive the software checks are often the sign that one piece of hardware is getting unreliable.
Conclusion
If the crashes are still happening after the safe fixes above, back up anything you care about before trying deeper changes. The next best move is to narrow it down by hardware testing or by removing the most likely recent change, not by reinstalling everything at random. If you want, I can help you turn your specific crash pattern into a short step-by-step plan.
Frequently Asked Questions
Should I reinstall Windows first if my PC keeps crashing?
No. Reinstalling is a later step. Start with updates, driver rollback, system file checks, Safe Mode, and Reliability Monitor so you have a better idea of what is actually failing.
If Safe Mode is stable, what does that mean?
It usually means the core Windows installation is usable and the problem is more likely a driver, startup app, or third-party service that normal mode loads.
Do blue screens always mean bad hardware?
No. Bad drivers and corrupted system files can also cause blue screens. Repeated crashes during heavy load, startup, or with heat buildup make hardware more suspicious, but they do not prove it by themselves.