“Your device ran into a problem and needs to restart” is Windows’ stop code error, better known as the blue screen of death (BSOD). Microsoft says a one-off crash usually needs nothing more than the restart Windows does on its own. If it keeps coming back, write down the stop code at the bottom of the screen, remove any hardware you added recently, update or roll back the driver it points to, and run Windows Update. If the PC crashes before you reach the desktop, use Troubleshoot > Advanced options in the Windows Recovery Environment to get into Safe Mode, uninstall the latest update or use System Restore.
On Windows 11 version 24H2 and later the same crash shows up as a black screen instead of a blue one, according to Microsoft’s blue screen page. The fixes below apply to both, and to Windows 10.
What people stuck on this screen tried
Forum threads about this error rarely end with a neat “solved”. Reading through them is still useful, because they show which steps people try first and where they get stuck.
“Every time the PC reboots it goes to the same page”
That’s close to the original post in a long Microsoft Community Hub thread that started in 2021 and was still getting replies in 2026. The stop code was PAGE_FAULT_IN_NONPAGED_AREA, the failing file was Wdf01000.sys, and the PC could reach its firmware menu but not Windows. The first suggested fix was to force Automatic Repair, boot into Safe Mode with Command Prompt and run sfc /scannow. Several later posters said that alone didn’t help them. The recoveries people did report were different: one PC came back after an automatic System Restore, and another owner traced a repeating crash to a damaged laptop battery. Read that as a hint, not a rule: when software fixes do nothing, hardware deserves a look.
An HP laptop looping on the error, no second PC to hand
In a Microsoft Q&A question from May 2025, the owner of an HP 15 running Windows 11 had already drained the battery and checked connections. The advisor first asked whether they had tried System Restore or repair from the recovery menu, reached by interrupting startup with the power button three times. The fallback was a clean install from a USB stick made with Microsoft’s Media Creation Tool. The thread stalls there because the owner had no other working computer to make that USB stick. The lesson is simple: try the recovery menu first, and if you end up needing install media, borrow a PC for twenty minutes.
“I reset the laptop and it still loops”
An Acer Aspire 3 owner on Microsoft Q&A had already reset Windows 11 from the recovery menu and was still stuck. The advice there was a full clean install from USB media. That matches Microsoft’s own order of things: restore and repair options come first, and reinstalling is the last step because it wipes the drive.
Step one: read the stop code before it disappears
The stop code is the most useful thing on the screen. Microsoft’s troubleshooting page says it appears at the bottom, for example PAGE_FAULT_IN_NONPAGED_AREA or MEMORY_MANAGEMENT, and sometimes with the name of the module (often a driver file ending in .sys) that was running when Windows stopped. Take a phone photo of the screen. The next restart comes fast.
Microsoft’s advanced guide for stop errors gives a good sense of where to look. It estimates that about 70% of these crashes come from third-party driver code, about 10% from hardware, about 5% from Microsoft’s own code, and about 15% can’t be traced because memory is too damaged. So a driver is the first suspect almost every time. The same guide links common codes to a first move:
| Stop code | What Microsoft suggests first |
|---|---|
| DRIVER_IRQL_NOT_LESS_OR_EQUAL | Update the network driver |
| PAGE_FAULT_IN_NONPAGED_AREA | Update or disable the driver named on screen, then check the disk |
| KMODE_EXCEPTION_NOT_HANDLED | Disable or remove the named or recently added driver |
| NTFS_FILE_SYSTEM | Run a disk check |
| DPC_WATCHDOG_VIOLATION | Update or disable the faulty driver |
| SYSTEM_SERVICE_EXCEPTION | Run System File Checker |
Missed the code? Open Event Viewer and check the System log for errors around the time of the crash, which the guide recommends for spotting the device or driver involved.
How to fix the error when Windows still starts
If the crash happens now and then but you can still reach the desktop, work through these in order. They come from Microsoft’s basic checklist, with the repair commands from its other support pages.
- Remove new hardware. Shut down, unplug anything you added just before the crashes started (a drive, RAM, a dock, a USB device), and restart.
- Check Device Manager. Right-click Start and choose Device Manager. Look for any device with an exclamation mark, right-click it and choose Update driver. If that doesn’t help, disable or uninstall the device.
- Get the driver from the source. If the stop code named a driver file, get the current version from your PC, graphics card or motherboard maker. Microsoft’s guide also says to update the BIOS and firmware.
- Free up disk space. Microsoft recommends keeping roughly 10% to 15% of the drive free, because Windows needs room for its swap files.
- Install updates. Go to Start > Settings > Windows Update and select Check for updates.
- Repair system files. Search for cmd, right-click Command Prompt and choose Run as administrator. Run DISM.exe /Online /Cleanup-image /Restorehealth first, then sfc /scannow, as Microsoft’s System File Checker page says. Leave the window open until it reaches 100%.
- Check the drive. Run chkdsk /f /r from the same admin Command Prompt. On the system drive it asks to run at the next restart, so say yes and restart.
Software can trigger the crash too. Microsoft’s guide says an app usually only exposes an underlying driver or hardware problem, so uninstalling the app you installed last is fine as a quick test, but don’t stop there if the crashes continue.
What if it restarts before you reach the desktop?
When the error loops at startup, your way in is the Windows Recovery Environment (WinRE). Windows usually opens it after several failed starts. If it doesn’t, Microsoft’s WinRE page says to force it:
- Turn the PC on. When the Windows or manufacturer logo appears, hold the power button until it switches off.
- Do that a second time.
- On the third start you should see Automatic Repair. Select Advanced options.
Then go to Troubleshoot > Advanced options. Here’s what to try, roughly in this order:
- Uninstall Updates if the crashes started right after Windows updated. It removes the most recent updates.
- System Restore to roll Windows back to an earlier restore point. Your personal files stay where they are.
- Startup Repair to let Windows fix common problems that stop it from loading.
- Startup Settings > Restart, then press 4 or F4 for Safe Mode, or 5 or F5 for Safe Mode with Networking. Microsoft’s Safe Mode page lists the keys. Safe Mode loads only basic drivers, so it’s the place to roll back or uninstall the driver from the stop code and run the repair steps from the previous section.
One catch: if your drive is encrypted with BitLocker, some of these tools ask for the BitLocker recovery key. Have it ready before you start.
WinRE also offers Reset this PC. Keep it for last. It reinstalls Windows, and as the Acer thread above shows, it doesn’t always break a loop that hardware or firmware is causing.
Signs the problem is hardware, not Windows
If you get different stop codes each time, crashes under load, or crashes that survive a reset, look at the hardware. Microsoft’s guide lists hardware and memory tests as a standard step, and many PC makers build a diagnostic tool into the startup menu. Reseat RAM and drives on a desktop if you’re comfortable doing it. On a laptop, a failing battery or charger is worth ruling out, as one poster in the Community Hub thread found.
Driver Verifier, a tool some forum posts recommend, deliberately stresses drivers to catch the bad one. Microsoft warns that it can slow the PC a lot and cause more crashes, and that you shouldn’t verify every driver at once. If it leaves the PC unable to start, boot into Safe Mode to turn it off. It’s fine for advanced users, but most people should skip it.
Frequently asked questions
Is “your device ran into a problem and needs to restart” a virus?
Usually not. Microsoft says the cause is normally a hardware device, its driver or software. Its advanced guide does include a malware scan with Microsoft Safety Scanner or another antivirus as one of the standard checks.
Will I lose my files when the PC restarts?
Files you had saved are normally fine, but anything unsaved in open apps is lost. System Restore and Uninstall Updates keep personal files; Reset this PC and a clean install can remove them.
Why is my Windows 11 crash screen black instead of blue?
From Windows 11 version 24H2, Microsoft shows stop errors on a black screen. It’s the same error with the same stop codes, so the same fixes apply.
Where does Windows save crash dump files?
Small memory dumps go to %SystemRoot%Minidump (normally C:WindowsMinidump), and larger dumps to %SystemRoot%MEMORY.DMP. You can change the dump type under Advanced system settings > Startup and Recovery > Settings.
How many crashes are too many?
Microsoft treats one crash as something the restart usually fixes. If the same stop code repeats, start troubleshooting.
Sources
- Microsoft Support: Troubleshooting unexpected restarts and stop code errors
- Microsoft Support: Windows blue screen errors
- Microsoft Learn: Advanced troubleshooting for stop errors
- Microsoft Support: Windows Recovery Environment
- Microsoft Support: Start your PC in Safe Mode
- Microsoft Support: System File Checker
- Microsoft Community Hub thread on the restart loop
- Microsoft Q&A: HP 15 restart loop
- Microsoft Q&A: Acer Aspire 3 loop after reset
Featured image: Szymon Shields / Pexels
