“Your device ran into a problem and needs to restart”: Fix error on Windows 10/11

1. Introduction

This guide resolves the Windows “blue screen” that forces a reboot and sometimes shows a Stop code (e.g., CRITICAL_PROCESS_DIED, IRQL_NOT_LESS_OR_EQUAL). You’ll learn fast triage steps to get back in, how to collect evidence (minidumps, Event Viewer logs), and the exact fixes for drivers, updates, system files, disk and memory errors, and firmware/BIOS problems.

2. Quick Triage (do these first)

1. Capture the stop code: Snap a photo or note the exact Stop code shown on the BSOD.
2. Power cycle & cool-down: Shut down fully (hold power 10s). Let the device cool if it was hot. Remove overclock/undervolt tools.
3. Unplug peripherals: Disconnect USB hubs, printers, external drives, docks, new GPUs/RAM.
4. Boot to Safe Mode: Hold Shift and click Restart → Troubleshoot → Advanced options → Startup Settings → Restart → press 4 (Safe Mode) or 5 (Safe Mode with Networking).
5. Run Startup Repair: Troubleshoot → Advanced options → Startup Repair.
6. System Restore (if available): Troubleshoot → Advanced options → System Restore and pick a point from before the crashes.

If you can now reach the desktop, continue with the steps below. If you cannot, use Advanced options → Command Prompt to run the command-line fixes where noted.

3. Prerequisites

• Local admin account.
• Stable power supply (avoid running on a dying battery).
• Free disk space: aim for 15–20 GB on the system drive.
• A recent backup if you plan to uninstall major updates or reset Windows.

4. Step-by-Step Guide

4.1 Turn off auto-restart and enable crash dumps

1. Disable auto-restart (so you can read the stop code):
   Control Panel → System → Advanced system settings → Startup and Recovery → uncheck Automatically restart.
2. Ensure minidumps are saved: In Startup and Recovery, set Write debugging information to Small memory dump (256 KB); verify path is %SystemRoot%\Minidump. After the next crash, check C:\Windows\Minidump\ for .dmp files.

4.2 Inspect Reliability History and Event Viewer

1. Press Win+R → perfmon /rel. Look for red X around the crash time; note failing module or update.
2. Open Event Viewer → Windows Logs → System. Filter for Error and Critical, and check:
   • Event ID 1001 (BugCheck) for code parameters.
   • disk/ntfs/storahci/volmgr errors around the same time (storage issues).

4.3 Undo problematic updates (quality or feature)

1. Settings → Windows Update → Update history → Uninstall updates. Remove the most recent quality update first.
2. If crashes started after a feature update, use Recovery → Go back (within Microsoft’s rollback window).
3. From WinRE: Advanced options → Uninstall Updates (choose Latest Quality Update or Feature Update).

4.4 Repair system files and component store

Run an elevated Command Prompt (or WinRE Command Prompt):

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

If SFC reports repairs, reboot and run SFC again until it’s clean.

4.5 Check and repair disk errors

Quick online scan (no reboot):

chkdsk /scan

Schedule full fix on next boot (long, intrusive – use if errors are found):

chkdsk C: /f

Surface scan (even longer; use only if you suspect bad sectors):

chkdsk C: /r

4.6 Update, roll back, or remove drivers

1. Device Manager → focus on Display adapters, Storage controllers, Network adapters, Audio, and any device with a warning icon.
2. If the crash began after a driver update: Properties → Driver → Roll Back Driver.
3. Prefer OEM drivers (GPU: NVIDIA/AMD/Intel; Chipset/Storage: motherboard or laptop vendor).
4. DDU (Display Driver Uninstaller) is effective for stubborn GPU driver issues (advanced users).
5. For USB Wi-Fi/Bluetooth dongles, temporarily uninstall the device and unplug it to test stability.

4.7 Memory diagnostics

1. Built-in test: Win+R → mdsched.exe → Restart now and check for problems.
2. If errors appear, reseat RAM, test one stick at a time, and replace faulty modules.
3. If the built-in test is inconclusive, run an extended overnight memory test (e.g., MemTest86 from a bootable USB).

4.8 Clean boot to isolate third-party conflicts

1. Win+R → msconfig → Services tab → check Hide all Microsoft services → Disable all.
2. Task Manager → Startup tab → Disable all non-essential entries.
3. Reboot. If stable, re-enable items in batches to find the culprit.

4.9 GPU, CPU, and power sanity checks

• Remove overclocks/undervolt profiles (BIOS, MSI Afterburner, Intel XTU, Ryzen Master).
• Ensure the PSU is adequate and cables are firmly seated (desktop).
• Watch temps: Task Manager → Performance (Windows 11 shows GPU temp). Clean dust from fans/heatsinks.

4.10 Firmware/BIOS and chipset updates

• Update BIOS/UEFI and chipset/storage drivers from the vendor support page (match exact model).
• Enable Secure Boot and Memory Integrity (Core Isolation) after driver compatibility is confirmed.

4.11 Malware and rootkit scan

• Run Windows Security → Virus & threat protection → Scan options → Microsoft Defender Offline scan.
• If malware is found, remediate and re-run SFC/DISM, then reassess stability.

4.12 Analyze minidumps (advanced)

1. Install WinDbg (Preview) from Microsoft Store.
2. Open a .dmp from C:\Windows\Minidump\.
3. In the command window:

!analyze -v
lmvm <driver_name>

Focus on the Probably caused by module and STACK_TEXT context to identify the failing driver.

4.13 Targeted fixes by common Stop codes

• SYSTEM_THREAD_EXCEPTION_NOT_HANDLED / KMODE_EXCEPTION_NOT_HANDLED: Usually a bad driver. Update/rollback GPU, storage, or network drivers; run Driver Verifier only as a last resort.
• IRQL_NOT_LESS_OR_EQUAL: Often RAM/driver. Run memory test; check NIC/GPU drivers; remove endpoint security temporarily to test.
• PAGE_FAULT_IN_NONPAGED_AREA: RAM or disk/AV filter driver. Test memory; check storage drivers; ensure pagefile isn’t disabled.
• CRITICAL_PROCESS_DIED: Corrupted system files/disk. Run SFC/DISM, CHKDSK, and undo recent updates.
• INACCESSIBLE_BOOT_DEVICE: Storage driver/boot chain. From WinRE: Startup Repair; update storage/RAID drivers; don’t change SATA mode ad-hoc; if needed run:

  bootrec /scanos
  bootrec /rebuildbcd
  

• UNEXPECTED_STORE_EXCEPTION: Disk, firmware, or storage filter drivers. Update BIOS/SSD firmware; check SMART/CHKDSK; remove third-party “tune-up” tools.

4.14 Driver Verifier (experts only)

Caution: this will intentionally stress drivers and may cause rapid BSOD loops.

1. Win+R → verifier → Create standard settings → Select driver names from a list → check non-Microsoft drivers → Finish → reboot.
2. If it loops, boot to Safe Mode and disable:

   verifier /reset
   

3. Analyze the new dumps to find the offending driver and remove/update it.

4.15 In-place repair or reset (last resort)

• In-place repair (keeps apps/files): Run the Windows 10/11 ISO setup from the desktop → Upgrade this PC now → choose Keep personal files and apps.
• Reset this PC: Settings → System → Recovery → Reset this PC. Prefer Keep my files first.

5. Validation and Testing

1. No new BugCheck events: Event Viewer → Windows Logs → System; confirm Event ID 1001 stops appearing across several reboots.
2. Reliability Monitor score rising and no red X for a few days.
3. Stress tests:
   • Graphics: run a game/benchmark for 15–30 minutes.
   • Storage: copy a large file to/from the system drive.
   • Network: speed test + sustained download.
4. Sleep/Resume cycles: Put the PC to sleep and resume 3–5 times; BSODs often reveal here if drivers remain faulty.

6. Security Hardening (prevent recurrences)

1. Enable System Restore on the system drive and create a restore point after major changes.
2. Patch cadence: Install quality updates promptly; defer feature updates for 2–4 weeks on production systems.
3. Driver strategy: Prefer OEM drivers; avoid automatic driver “updaters”.
4. Core isolation & Secure Boot: Turn on Memory Integrity (Windows Security → Device security) once drivers are compatible; keep Secure Boot enabled.
5. Disk health monitoring: Periodically check SMART/Health and keep 15–20% free space on the system drive.
6. Backup: Maintain an offline or cloud image backup so you can roll back quickly.

7. Conclusion

Most “Your device ran into a problem” loops boil down to three root causes: driver faults, file/disk corruption, or unstable hardware/firmware. If you methodically gather evidence (stop code, minidumps), apply SFC/DISM/CHKDSK, stabilize drivers and firmware, and validate with Reliability Monitor, you can restore stability without a full reset in the majority of cases.

8. FAQ