Windows 11 keeps blue-screening: isolate the stop code before broad repair
A safe-first route for repeated Windows 11 stop-code crashes that separates recent hardware, drivers and recovery options.
- Photograph or write down the exact stop code and any “What failed” module name.
- If the crash began after adding hardware, disconnect that new hardware and retest.
- If Windows can start, check Device Manager for devices showing an error.
- Install current Windows updates before moving into deeper recovery work.
What this problem usually means
A repeated stop-code crash is a symptom class, not one diagnosis. Microsoft notes that hardware, drivers or software can trigger stop-code errors. The useful first step is to preserve the exact stop code and what changed immediately before the crashes, then isolate the newest variable before using system-wide repair.
Work from the narrowest fix to the broader one.
Test whether a recent hardware change is the trigger
Low riskWhy this belongs here: Microsoft puts removal of newly added hardware near the start of repeated stop-code troubleshooting.
- Shut down the PC.
- Disconnect hardware that was added immediately before the crashes, when it is safe to do so.
- Restart and test whether the same stop code returns.
Use Safe Mode when normal startup is unstable
Low riskWhy this belongs here: Safe Mode loads a reduced driver/service set and can help separate a normal-startup driver or software problem from a deeper failure.
- Open Windows Recovery Environment if normal startup is unreliable.
- Choose Troubleshoot > Advanced options > Startup Settings > Restart.
- Choose a Safe Mode option and test whether the repeated crash still occurs.
Check Device Manager and recent drivers
Medium riskWhy this belongs here: A device marked with an error or a driver changed immediately before the crashes gives you a narrower branch than generic resets.
- Open Device Manager.
- Look for warning icons and note the affected device and Device status code.
- If a recent driver update directly preceded the crashes, use the device-specific rollback path when available.
Move to Windows recovery only after the narrower checks
Medium riskWhy this belongs here: System Restore and other recovery options change more system state and belong after the obvious recent hardware/driver branches.
- Open Settings > System > Recovery when Windows starts, or use Windows RE when it does not.
- Choose the recovery option that matches when the problem began.
- Back up important files before using recovery options that can remove data or apps.
When this guide stops being the right path
If the stop code identifies a specific hardware class, or crashes continue outside normal Windows startup, move to that stop code or hardware diagnostic path instead of repeating generic blue-screen steps.
If the problem is still not fixed
Use the exact stop code to branch into a scoped error record. Persistent hardware-oriented stop codes may require memory, storage, thermal or manufacturer diagnostics.
Sources reviewed for this page
Primary technical guidance is preferred. A source supports the scope stated here; it does not imply that every possible cause is covered.