Back up before repeated crashes become data loss
If Windows still starts, copy important files now. Keep the PC on reliable power and return overclocking or undervolting to defaults during diagnosis. A drive that disappears, clicks, reports health errors or freezes recovery tools needs a backup-first hardware approach—not aggressive repair commands.
1. Record the crash evidence
- Photograph the stop code and any named
.sysfile. - Note whether the crash occurred during startup, gaming, sleep, an update or while idle.
- Write down recent driver, hardware, antivirus, firmware and Windows changes.
- Check
C:\Windows\Minidumpfor recent dump files after Windows restarts.
Do not assume the last application visible caused the crash. User applications rarely have direct permission to stop the kernel; their workload may only expose a driver or hardware fault.
2. Use the timing to narrow the cause
| Crash pattern | Stronger suspects |
|---|---|
| Immediately after a driver or update | Changed driver, filter software, update regression. |
| Only during games or rendering | Graphics driver, GPU, RAM, power, thermals. |
| During file copies or boot | Storage driver, SSD, file system, RAM. |
| Random codes on different days | RAM instability, storage, power, overclocking. |
| Same driver named repeatedly | That driver or the device/software using it. |
3. Use Safe Mode when normal Windows is unstable
Open Windows Recovery Environment, then choose Troubleshoot → Advanced options → Startup Settings → Restart → Safe Mode. If Safe Mode stays stable, third-party drivers, services and startup software become more likely.
Safe Mode is evidence, not a cure. Remove or roll back only the change connected to the crashes, then retest normal startup.
4. Repair the driver path without guessing
Open Device Manager and review devices changed near the first crash. Use Roll Back Driver when a specific new version caused the problem. Otherwise obtain chipset, graphics, storage and network drivers from Windows Update or the PC manufacturer.
A driver filename in a dump is useful, but it may be the victim of memory corruption rather than the original cause. Avoid generic driver-updater utilities and never download individual .sys files from file-sharing sites.
5. Repair Windows files and updates
In an elevated Terminal run:
DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannow
Install pending quality updates or uninstall the latest quality update from recovery when crashes began immediately after it. System Restore is appropriate when a clear restore point predates the failure.
6. Test memory properly
Run Windows Memory Diagnostic for an initial check, then use the PC or memory manufacturer’s extended diagnostics when crashes continue. Test at default firmware settings. A pass does not absolutely rule out intermittent RAM, but any repeatable error is significant.
Reseat or test modules individually only if you are comfortable following the manufacturer’s service instructions. Mixed kits and unstable XMP/EXPO settings can cause apparently random stop codes.
7. Check storage and file-system health
Run chkdsk C: /scan from an elevated Terminal for an online file-system check. Review the SSD manufacturer’s diagnostic and health information. Back up before deeper tests if Windows freezes during reads, files become corrupt or the drive vanishes.
Do not treat a generic percentage health number as conclusive; controller errors, timeouts and disappearing storage matter even when a tool says “good.”
8. Check heat, power and hardware changes
- Return CPU, GPU and RAM tuning to defaults.
- Check temperatures, fans and blocked vents.
- Remove newly added non-essential hardware for a controlled test.
- Run manufacturer CPU, GPU, memory and storage diagnostics.
Crashes inside Windows installation media or recovery, especially with changing codes, strongly increase the likelihood of hardware instability.
9. Reinstall only after the evidence is exhausted
An in-place repair installation can repair Windows components while retaining more applications when Windows remains usable. Reset this PC removes applications even with Keep my files. A clean install erases the selected Windows partition.
If a clean environment also crashes, stop reinstalling and investigate memory, storage, motherboard, GPU, thermals and power.
Avoid these common mistakes
- Do not install every available driver at once.
- Do not use registry cleaners or random “BSOD fixer” programs.
- Do not run destructive disk repairs before backing up an unstable drive.
- Do not assume reinstalling Windows proves the hardware is healthy.
Frequently asked questions
Where can I find the Windows 11 blue screen stop code?
It appears near the bottom of the crash screen. Windows may also save minidump files under C:\Windows\Minidump and record the unexpected shutdown in Event Viewer.
Can one blue screen be ignored?
One isolated crash may never return, but record the code and recent changes. Repeated crashes, hardware warnings or data errors require diagnosis.
Should I reset Windows to fix a BSOD?
Reset is a late software step. First check the stop code, drivers, updates, memory, storage and crash pattern because reset cannot repair faulty hardware.
Technical steps align with Microsoft guidance for Windows stop errors, Startup Settings, Device Manager, Windows Memory Diagnostic, DISM, System File Checker and recovery options.
Official references
For platform-specific behavior and recovery options, compare this guide with the current documentation from the relevant official source.