Fix blue screen (stop code) errors in Windows 11 and Windows 10
Your device ran into a problem and needs to restart.
In short
- The stop code, such as PAGE_FAULT_IN_NONPAGED_AREA or MEMORY_MANAGEMENT, appears at the bottom of the blue screen1.
- Microsoft's analysis found that 70% of stop errors are caused by third-party driver code and 10% by hardware issues5.
- Microsoft suggests keeping 10% to 15% of the drive free, because Windows needs space for swap files1.
- System Restore reverts system files, registry settings and installed programs to a restore point without affecting personal files4.
- Small memory dump files are saved in %SystemRoot%\Minidump5.
A blue screen that says "Your device ran into a problem and needs to restart" is a stop code error, also called a bug check1. A hardware device, its driver or software can cause it1. One restart usually solves it. If it keeps happening, remove new hardware, check Device Manager, free up space and install updates1. Then undo recent changes with System Restore4.
What the error means
When a serious problem occurs, Windows can shut down or restart on its own. You briefly see "Your device ran into a problem and needs to restart."1 Microsoft also calls this a stop code error, a bug check, a kernel error or a blue screen error1. Windows stops on purpose when something could compromise security or corrupt the system or your data5.
A hardware device, its driver or software can cause it1. The screen shows a stop code, such as PAGE_FAULT_IN_NONPAGED_AREA or MEMORY_MANAGEMENT1. If available, it also shows the name of the module that was running1. Note both before the PC restarts.
Before you start
- If the blue screen appeared only once, you may not need to do anything. In most cases the restart resolves the problem1.
- If Windows won't start normally, you can do the remaining steps from safe mode1.
- If your device is encrypted with BitLocker, have your recovery key ready. You need it for Startup Settings and for System Restore in Windows RE2,4.
- Startup Settings and System Restore both restart the PC, so save your work2,4.
Fixes
Remove any new hardware. If you added hardware before the error, shut down your PC, remove the hardware and restart1.
Start in safe mode if Windows won't start. Safe mode starts Windows with a limited set of files and drivers2. First open the Windows Recovery Environment (Windows RE). In Settings, select System > Recovery, then select Restart now next to Advanced startup3. If Windows can't start, hold the power button as soon as the logo appears, two times; on the third start, select Advanced options on the Automatic Repair screen3. In Windows RE, select Troubleshoot > Advanced options > Startup Settings > Restart2. After the restart, press 4 or F4 for safe mode, or 5 or F5 for Safe Mode with Networking5.
Check Device Manager. Right-click the Start button and select Device Manager1. Look for devices marked with an exclamation point (!). Right-click the device and select Update driver1. If updating the driver doesn't help, try disabling or uninstalling the device1.
Check free space on the hard drive. Windows and some apps need free space for swap files and other work1. The exact need varies, but Microsoft suggests keeping 10% to 15% free1.
Install the latest updates. In Windows 11, select Start > Settings > Windows Update, then select Check for updates1. In Windows 10, select Start > Settings > Update & Security > Windows Update, then select Check for Windows updates1.
Undo recent changes with System Restore. System Restore can undo software installs, driver updates and settings changes without affecting your personal files4. In Control Panel, select Recovery and choose Open System Restore. Or press Windows key + R, type rstrui.exe and press Enter4. Select Next, pick a restore point, then select Next and Finish4. Windows restarts when the restore point is applied4. If Windows won't start, open Windows RE and select Troubleshoot > Advanced options > System Restore4.
If nothing works
If Windows keeps restarting with the same stop code, Microsoft has advanced steps for IT professionals and advanced users1. They start with the stop code in the event logs5. Next, update the BIOS and firmware and run hardware and memory tests5. If the stop error names a driver, ask that hardware or software vendor for an update5.
Some stop codes have their own advice. For PAGE_FAULT_IN_NONPAGED_AREA, Microsoft suggests this command to detect and repair disk errors5. Run it in a Command Prompt opened with Run as administrator7:
chkdsk /f /rOn the system drive, you need to restart before the disk scan begins5. For SYSTEM_SERVICE_EXCEPTION, Microsoft points to the System File Checker, which repairs missing or corrupted system files5.
For deeper analysis, Windows can save a memory dump. A small memory dump goes to %SystemRoot%\Minidump, and the other dump types go to %SystemRoot%\MEMORY.DMP5. Microsoft's Bug Check Code Reference describes each stop code6. If none of this helps, Microsoft's Recovery options in Windows page lists other ways to restore the PC1.
Questions
- Do I need to do anything after a single blue screen?
- Usually not. In most cases the restart resolves the problem1. Troubleshoot when Windows restarts often with the same stop code1.
- Where can I look up a stop code?
- Microsoft's Bug Check Code Reference lists stop codes by number and name, such as 0x00000050 for PAGE_FAULT_IN_NONPAGED_AREA6. It is written for programmers; Microsoft points other readers to its blue screen troubleshooting page6.
20 Sept 2026: Published.