What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
A Windows crash screen—often called a blue screen, BSOD, bug check, kernel error, or STOP-code error—means Windows detected a serious problem and shut down or restarted to protect against data loss. The cause can be hardware, a device driver, or software.
Write down the STOP code and any “What failed” module name, then work from the least disruptive fix: remove newly added hardware, use Safe Mode, check Device Manager, install Windows and driver updates, verify free disk space, and review crash evidence. If Windows will not start, use Windows Recovery Environment (WinRE), beginning with Startup Repair and only moving to System Restore, Reset this PC, or a reinstall when the reversible options fail.
As an Amazon Associate I earn from qualifying purchases.
What the Windows crash screen means
A crash screen appears when Windows encounters a condition it cannot safely continue through. Microsoft calls these events bug checks or STOP-code errors. Windows stops or restarts instead of continuing with potentially corrupted operations or data.
The screen normally includes a STOP code, such as PAGE_FAULT_IN_NONPAGED_AREA. Some crashes also identify a “What failed” module name. These clues do not always identify the entire root cause, but they are valuable when you compare the crash with a recently installed driver, device, application, or update.
#1 Best Overall
A crash is not automatically proof that Windows itself is damaged. Hardware, a device driver, or software can all trigger the same protective shutdown. The right repair therefore depends on four questions:
- Does Windows still start normally, start only intermittently, or fail to boot?
- Did the problem begin after adding hardware, installing a driver or app, or applying an update?
- Can you preserve your personal files before attempting recovery?
- Is the next action reversible, or could it remove files and settings?
Record evidence before changing anything
On the next crash, pause long enough to capture the exact information on screen. If the computer restarts too quickly, use Safe Mode or WinRE later and look for the same event in Windows logs.
- Write down the complete STOP code, including underscores.
- Record the “What failed” module name if Windows shows one.
- Note what changed immediately beforehand: a new graphics card, USB device, memory module, printer, driver, application, or Windows update.
- Record whether the failure happens during startup, sign-in, gaming, sleep/wake, printing, networking, or another repeatable activity.
Keep this information with the date and time of each crash. A repeated code tied to one change is more actionable than a single unexplained restart.
First-response fixes when Windows still starts
Use these steps in order. They begin with actions that are easy to undo and avoid removing personal files.
1. Remove hardware added just before the crash
Shut down the PC, disconnect the newly added device, and restart. For an internal component, power the computer off completely before removing or reseating it and follow the hardware maker’s safety instructions. If the crashes stop, the device, its connection, or its driver is a leading suspect. Do not repeatedly reconnect a device that immediately reproduces the crash; continue troubleshooting with it disconnected.
2. Start Windows in Safe Mode
Safe Mode starts Windows with only essential services and drivers. That reduced environment helps isolate a third-party driver or application from the operating system’s basic components.
If Windows can reach the desktop, open the recovery options through Windows Settings and choose the restart option that opens Advanced startup. From the recovery menus, select Troubleshoot, then Advanced options, then Startup Settings, and restart. Choose the Safe Mode option shown on screen. If Windows cannot reach the desktop, the same Startup Settings tool is available through WinRE, described below.
Recommended Free Tools
Use Safe Mode to test the behavior:
- If the crash disappears, focus on recently installed drivers, startup software, and applications that do not load in Safe Mode.
- If the crash continues in Safe Mode, a low-level driver, hardware fault, or damaged Windows component remains possible.
- Restart normally after each test so you do not mistake Safe Mode’s limited features for a permanent repair.
3. Check Device Manager
Open Device Manager and expand the categories related to the suspected hardware. A warning exclamation mark identifies a device that Windows has flagged.
- Right-click the flagged device and choose Update driver.
- Restart and test the computer.
- If updating does not help, return to the device’s context menu and choose Disable device to test whether the crash stops.
- If the device is not needed for the test, choose Uninstall device, restart, and allow Windows to detect it again. Have the correct driver available before removing a device that is required for networking, storage, display, or input.
A driver change is most persuasive when the crash began immediately after that driver was installed. If the update itself introduced the failure, use the device’s available rollback option when Windows offers one, or uninstall the recently installed driver and test again.
4. Install Windows updates and current drivers
Use Windows Update to install available Windows updates and drivers whenever possible. Restart after installation, then test the activity that normally triggers the crash.
Do not ignore storage capacity. Microsoft’s blue-screen guidance says keeping about 10%–15% of the system drive free is a good idea because Windows and applications need room for swap files and other operations. Check the drive’s free-space indicator in File Explorer before attempting a major update or recovery. If free space is below that range, remove or move files you no longer need, then retry the update. This recommendation is about providing working room; it is not a promise that deleting files alone will cure a crash.
5. Review Event Viewer and run the memory test
If the crash repeats, open Event Viewer and inspect the System log at the same time as the restart. Look for critical errors and warnings that identify a driver, device, service, or power event occurring immediately before the bug check.
Run Windows Memory Diagnostic as an additional check for memory-related problems. After the test and restart, find the result in Event Viewer under the source MemoryDiagnostics-Results. Treat a reported memory error as a reason to investigate the installed memory and its configuration before continuing to use the machine for critical work.
When Windows will not boot
Windows Recovery Environment (WinRE) is the recovery workspace for startup failures. Windows can enter it automatically after repeated failed starts, or you can open it through Advanced startup. Its tools include Startup Repair, Startup Settings, System Restore, Reset this PC, uninstall updates, Command Prompt, and UEFI firmware settings.
Open WinRE from a working installation
If you can reach the sign-in screen or desktop, use the Windows recovery option for Advanced startup and choose Restart now. Save open work first. The computer restarts into WinRE, where you can select Troubleshoot and then Advanced options.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Open WinRE when the installed system cannot start
If the machine cannot reach WinRE on its own, create Windows installation media on a USB flash drive using another working PC. Boot the affected computer from that USB drive and choose Repair my PC, not the option that begins a new installation. That path opens WinRE without requiring the installed Windows desktop.
Manufacturer recovery media can contain hardware-specific drivers and factory applications. It may therefore offer a different recovery experience from generic Windows installation media. Before using either type of media, back up important files if you can access them.
Use WinRE tools from least to most disruptive
Startup Repair
In WinRE, choose Troubleshoot > Advanced options > Startup Repair. Startup Repair is a built-in Windows recovery tool that helps fix issues preventing the operating system from starting.
Microsoft says Startup Repair attempts repairs for missing or damaged system files, corrupted boot configuration data, a damaged master boot record (MBR), incompatible drivers, and registry errors. Let it complete, restart, and test a normal boot. If it reports that it could not repair the PC, return to Advanced options rather than repeatedly running the same operation.
Uninstall a recent update
If the crash or boot failure began immediately after a Windows update, choose Advanced options > Uninstall Updates. Select the available update-removal option, restart, and check whether Windows starts normally. This is a targeted rollback for a known timing relationship; it is preferable to resetting the entire installation when an update is the clear trigger.
System Restore
If the failure began after a known system change and restore points exist, choose Advanced options > System Restore. System Restore rolls back system files and settings to an earlier point without rolling back personal files.
Choose a restore point dated before the suspected change. Read the affected-program information when it is offered, confirm the restore, and allow the computer to restart. A restore does not remove the need to correct a faulty device or driver if that hardware remains connected.
Reset this PC
Use Reset this PC only after the less disruptive choices fail or when Windows is too damaged to repair another way. Reset can reinstall Windows while giving you a choice to keep personal files or remove them.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →The “keep personal files” path is less destructive than removing everything, but it still removes applications and resets many settings. The option that removes personal files is appropriate only after you have a verified backup and accept the consequences. Follow the on-screen explanation of what will be removed before confirming.
Best Value
Command Prompt and UEFI settings
WinRE also includes Command Prompt and UEFI Firmware Settings. Use Command Prompt only when you have a specific recovery procedure and understand which volume contains Windows; an incorrect command can make a startup problem worse. UEFI settings are useful when the computer is not selecting the correct boot device or when firmware configuration itself is part of the diagnosis. Do not change firmware settings at random.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Protect files before recovery
Back up important documents, game saves, photos, and configuration files before using Reset this PC or reinstalling Windows. Microsoft warns that some recovery options can cause data loss. If Windows will not start, copy files from the drive using another bootable environment or connect the drive to another working computer when practical.
Keep at least one backup separate from the affected PC. An external USB backup drive is useful for this purpose, but verify that the files actually open from the backup before beginning a destructive recovery. Cloud-synchronized folders are not a substitute for checking that unsynchronized local files have also been copied.
Choose the next fix by risk and reversibility
| Situation | Preferred action | Effect on personal files | Reversibility |
|---|---|---|---|
| New hardware preceded the first crash | Shut down, remove the hardware, and restart | No file change | High; reconnect only after testing |
| Windows starts but crashes during normal use | Safe Mode, Device Manager checks, Windows Update, and driver testing | No planned file removal | High; drivers can be updated, disabled, or uninstalled |
| Failure began after an update | Uninstall Updates in WinRE | Personal files remain | High; targeted rollback |
| Failure began after a system change | System Restore | Personal files are not rolled back | Moderate; system settings return to an earlier point |
| Windows cannot start and automated repair fails | Reset this PC after a backup | Choose to keep or remove personal files | Low; applications and settings may be removed |
| Installation is unusable or the disk must be replaced | Windows installation media and a clean installation | Reinstallation can erase the installation and files | Lowest; use only with a verified backup |
Common crash-loop pitfalls
Repeating the same restart
A restart can temporarily clear a driver or power-state problem, but repeated crashes need evidence. Record the code, enter Safe Mode, and inspect Device Manager and Event Viewer instead of continuing to restart without changing anything.
Removing a driver without a replacement plan
Uninstalling a network, storage, display, or input driver can leave you without a required function. Download or otherwise obtain the correct replacement first when possible, and keep the installation media available if the affected PC will be offline.
Resetting before backing up
Reset this PC is not the first response to a single blue screen. It can remove applications, settings, or personal files depending on the option selected. Use the reversible recovery choices and make a backup before confirming a reset.
Assuming a STOP code names the faulty part
A code such as PAGE_FAULT_IN_NONPAGED_AREA describes the class of failure, not necessarily one defective component. Compare it with the “What failed” module, Event Viewer entries, recent changes, Safe Mode behavior, and memory-test results.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsWindows 10 support status
The Microsoft troubleshooting and recovery guidance used for this procedure covers Windows 10 and Windows 11. Microsoft states that free Windows 10 updates, technical assistance, and security fixes ended on October 14, 2025. If the affected PC still runs Windows 10, plan a move to a supported Windows 11 installation when the hardware permits. A migration does not replace diagnosing the immediate crash, but remaining on an unsupported operating system leaves future faults without ongoing security and maintenance fixes.
Bottom line
Capture the STOP code, remove recently added hardware, test in Safe Mode, inspect Device Manager, install current Windows updates and drivers, keep 10%–15% of the system drive free, and review Event Viewer plus Windows Memory Diagnostic when crashes repeat. For a PC that will not boot, enter WinRE and try Startup Repair, then an update rollback or System Restore tied to the timing of the failure. Back up first, and reserve Reset this PC or a reinstall for cases where the safer, reversible paths do not restore startup.
Quick Recap
As an optional shortcut after trying the built-in steps, Outbyte PC Repair can check and repair more than 100 common Windows issues where possible, including broken system elements and shared DLL problems, while also offering crash logging and system-maintenance features. It runs on Windows 11, 10, 8, and 7, with a category-based free trial of at least two days followed by a paid subscription. It complements antivirus software rather than replacing it; results vary, and no tool repairs every crash.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Free tools Windows power users keep installed
One-click scans. No signup required.
