Windows 11 Laptop Stuck Restarting After 24H2 Update? BSOD Fix 2026

🔁

Windows 11 24H2 & later

Restart-Loop BSOD

Laptop & Desktop

Typical fix time (editor's estimate)

10 – 45 min

Difficulty: Beginner to Intermediate | Data risk: none for steps 1–6

✅ Files stay safe (steps 1–6) 🔧 Works from Recovery ⚠️ Check BitLocker key 🛑 Reset = last resort

Match my stop code Can't reach Windows?

3 min

Start here: the 3-minute triage

1) Write down the stop code (phone photo works). 2) Unplug docks, USB drives and external screens. 3) Note whether the loop started right after an update or a driver install. These three facts decide which section below you need.

What's In This Guide

1. Quick Overview & At-a-Glance 2. Stop Code Cheat Sheet 3. Reach the Recovery Environment 4. Uninstall the Latest Update 5. Safe Mode: DISM, SFC & chkdsk 6. Driver Culprits & Rollback 7. Boot Repair & BitLocker Trap 8. Read the Crash Dump 9. Is It Hardware? RAM & SSD 10. Fix Methods Compared 11. Effort vs. Risk Meter 12. Do's and Don'ts 13. Which Fix For Your Situation 14. Prevent the Next Loop 15. Final Summary 16. Frequently Asked Questions

01. Quick Overview: The Restart-Loop BSOD at a Glance

📌 Windows 11 Restart-Loop BSOD: Complete Summary

Item	Details
What you see	"Your device ran into a problem and needs to restart", then an automatic reboot, repeated
Screen color	Black on Windows 11 24H2 and later, blue on 23H2 and older. The stop code is what matters.
Common triggers	Failed or partial update, new or updated driver, corrupted system files, failing SSD or RAM, third-party security software
Most dangerous mistake	Hitting Reset this PC before reading the stop code or backing up
Safest first fix	Uninstall the latest quality update from Recovery
Skills needed	Pressing the power button, reading menus, copying a few commands

📸

Capture

Photograph the stop code

🔌

Unplug

Remove USB, dock, extra displays

↩️

Roll Back

Remove latest update

🛠️

Repair

SFC, DISM, boot fix

02. Stop Code Cheat Sheet: Match Yours

🚨 10 Stop Codes Behind Most Restart Loops

Stop Code	Hex	What It Usually Means	First Fix
CRITICAL_PROCESS_DIED	0xEF	A vital system process stopped or was damaged	Safe Mode, then DISM and SFC
0xc000021a	0xC000021A	Winlogon or CSRSS terminated, often after a broken update	Uninstall latest update, offline SFC
INACCESSIBLE_BOOT_DEVICE	0x7B	Windows can't reach its drive: storage driver, BIOS mode or BCD issue	Check BIOS mode, rebuild BCD
DRIVER_PNP_WATCHDOG	0x1D9	A driver hung during a power or plug-and-play event	Unplug devices, roll back drivers
SYSTEM_SERVICE_EXCEPTION	0x3B	Kernel-level fault, often graphics driver or security software	Roll back GPU driver
UNEXPECTED_STORE_EXCEPTION	0x154	Storage component failed: SSD health or antivirus conflict	chkdsk, SSD health check
KERNEL_SECURITY_CHECK_FAILURE	0x139	Corrupted data structure, usually a driver or memory issue	Update or roll back drivers, test RAM
DRIVER_IRQL_NOT_LESS_OR_EQUAL	0xD1	A driver touched memory it shouldn't have	Identify driver via dump file
MEMORY_MANAGEMENT	0x1A	Memory fault: bad RAM, overclock or driver	Windows Memory Diagnostic
WHEA_UNCORRECTABLE_ERROR	0x124	Hardware error reported by CPU, RAM or storage	Reset BIOS defaults, test hardware

💡

The stop code appears on the crash screen for only a moment. If it vanishes before you can read it, use the Startup Settings trick in the next section to stop the automatic restart.

03. Reach the Recovery Environment When Windows Won't Boot

🧭 Force WinRE in 5 Steps

Interrupt startup three times. Power on, and as soon as the Windows logo or spinner appears, hold the power button until the laptop shuts off. Repeat twice more.
Let Automatic Repair load. On the third boot you should see "Preparing Automatic Repair". Choose Advanced options when it appears.
Open Troubleshoot > Advanced options. This menu holds Uninstall Updates, Startup Settings, System Restore and Command Prompt.
Stop the instant reboot. Go to Startup Settings > Restart, then press 9 or F9 to disable automatic restart after failure. Now the crash screen stays so you can read the code.
Prefer Safe Mode? In the same Startup Settings list, press 4 or F4 for Safe Mode, 5 for Safe Mode with Networking, or 6 for Safe Mode with Command Prompt.

⚠️

Recovery asks for a BitLocker key? That is normal on many laptops. Get it at aka.ms/myrecoverykey from your phone using the Microsoft account tied to the PC. Work or school laptops keep it with your IT admin.

04. Uninstall the Latest Update: Fastest Fix After a Patch

↩️ Roll Back Without Touching Your Files

Troubleshoot > Advanced options > Uninstall Updates.
Pick "Uninstall latest quality update" first. This removes the most recent monthly patch.
Still looping? Repeat and choose "Uninstall latest feature update". This rolls back to your previous Windows version and usually works only within a limited window after upgrading (typically 10 days).
Restart and test. If Windows boots, pause updates for a couple of weeks from Settings > Windows Update so the same patch doesn't reinstall at once.

Quality updates are the usual suspect when the loop starts right after a Patch Tuesday install. Rolling back keeps your apps and personal files intact.

✅

Stuck on "Undoing changes made to your computer"? Wait a full 30 to 40 minutes before force-powering off. If it never finishes, open Command Prompt from Recovery and try the pending-actions revert shown in section 7.

05. Safe Mode Repair: DISM, SFC and chkdsk

🛠️ Repair Corrupted System Files

Once you reach Safe Mode, open Terminal (Admin) and run these in order. Each can take several minutes; don't interrupt.

DISM /Online /Cleanup-Image /RestoreHealth

sfc /scannow

chkdsk C: /f /r

Can't reach Safe Mode? Run SFC offline from Recovery

Open Command Prompt from Troubleshoot > Advanced options. The Windows drive often isn't C: in Recovery, so check first with dir C:\ or diskpart then list vol.

sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

06. Driver Culprits and How to Roll Them Back

🎛️ Drivers That Commonly Trigger Restart Loops

🎮

Graphics (GPU)

A fresh GPU driver is a frequent trigger of SYSTEM_SERVICE_EXCEPTION and black-screen crashes. Roll back or install the previous version.

🔊

Audio (Intel SST)

Microsoft has pointed to updating the affected Intel Smart Sound Technology driver for some update-related blue screens. Use your laptop maker's version.

💽

Storage (RST / VMD)

A storage driver mismatch can cause INACCESSIBLE_BOOT_DEVICE. Don't change BIOS storage mode as a "fix".

🧩

Chipset & Docks

DRIVER_PNP_WATCHDOG often points to power or plug-and-play drivers. Unplug docks and USB-C hubs first.

Boot Safe Mode and right-click Start > Device Manager.
Open the device you updated last, then Properties > Driver tab.
Click Roll Back Driver. If it's grayed out, choose Uninstall device and check "Attempt to remove the driver" if offered.
Install the laptop manufacturer's driver, not a generic one from a driver-updater tool.

driverquery /v

🚫

Skip "driver booster" style utilities. Mismatched drivers installed by these tools are a classic cause of repeat crashes.

07. Boot Repair and the BitLocker Trap

🧱 When the Boot Configuration Is Damaged

Use these from Command Prompt in Recovery, especially for INACCESSIBLE_BOOT_DEVICE or a loop that happens before the Windows logo.

bootrec /scanos

bootrec /rebuildbcd

bcdboot C:\Windows

Advanced: clear a stuck pending update

If the loop sits on update rollback screens, this revert command can clear pending servicing actions. Replace C:\ with your Windows drive.

DISM /Image:C:\ /Cleanup-Image /RevertPendingActions

🔐

Changes to boot data, firmware or the recovery partition can trigger a BitLocker recovery prompt. Have the key ready before you run boot commands.

08. Read the Crash Dump: Find the Real Culprit

🔍 Three Places That Name the Failing Component

📈

Reliability Monitor

Run perfmon /rel once Windows opens. Red X marks show the exact failure time and the update or driver nearby.

📋

Event Viewer

Windows Logs > System. Look for Kernel-Power 41 (unexpected restart) and BugCheck 1001 (crash details).

🗂️

Minidump Files

Saved in C:\Windows\Minidump. Open with WinDbg or BlueScreenView to see the driver named in the crash.

💡

If three crashes name three different drivers, stop chasing drivers. That pattern points to RAM, storage or power hardware (next section).

09. Is It Hardware? RAM and SSD Checks

⚙️ Signs the Problem Isn't Software

🧪 Suspect Hardware If…

⚡Stop codes change from crash to crash
⚡Crashes continue in Safe Mode
⚡chkdsk reports bad sectors
⚡MEMORY_MANAGEMENT or WHEA errors appear

🧰 Run These Tests

🔹Windows Memory Diagnostic: mdsched.exe
🔹Disk check: chkdsk C: /f /r
🔹SSD health using the maker's own tool
🔹Reset BIOS to defaults, disable any overclock

10. Fix Methods Compared

📊 Risk, Time and Data Impact

Method	Data Loss Risk	Typical Time	Best For
Uninstall latest quality update	None	5–15 min	Loop began after a patch
Startup Repair	None	10–30 min	Boot-time failures
Safe Mode + SFC / DISM	None	15–40 min	CRITICAL_PROCESS_DIED, 0xc000021a
Driver rollback	None	10–20 min	Driver-named crashes
bootrec / bcdboot	Low	10–20 min	INACCESSIBLE_BOOT_DEVICE
System Restore	Low (apps may change)	15–30 min	Restore point exists
Reset this PC (keep files)	Apps removed	45–90 min	Everything else failed
Clean install	Full wipe	60+ min	Last resort, backed-up data

✅

Times are rough estimates and vary with drive speed and how much is installed. For Reset this PC you can choose Cloud download or Local reinstall.

11. Effort vs. Risk Meter

🎚️ Editor's Estimate (out of 10)

Uninstall latest update: effort

2 / 10

Risk

1 / 10

SFC / DISM: effort

4 / 10

Risk

1 / 10

Boot repair: effort

6 / 10

Risk

3 / 10

Reset this PC: effort

5 / 10

Risk

8 / 10

12. Do's and Don'ts During a Restart Loop

✅ Protect Your Data and Your Time

✅ Do

✔️Photograph the stop code first
✔️Find your BitLocker key before repairs
✔️Try the safest fix first, then escalate
✔️Unplug USB devices, docks and extra displays
✔️Back up files from Recovery or a bootable USB if possible

🚫 Don't

✖️Run Reset this PC as step one
✖️Install "driver updater" tools
✖️Force-power-off during "Undoing changes" too early
✖️Change BIOS storage mode without noting the old value
✖️Format drives you haven't backed up

13. Which Fix For Your Situation

🎯 Your Situation to Your Best First Move

Your Situation	Start With	Then Try
Loop began right after an update	Uninstall latest quality update	Offline SFC, System Restore
Stop code 0xc000021a	Uninstall latest update	Offline SFC, revert pending actions
Began after a new graphics or audio driver	Safe Mode, driver rollback	Clean driver install from maker
INACCESSIBLE_BOOT_DEVICE	Verify BIOS storage mode	bootrec, bcdboot
Can reach Safe Mode	DISM then SFC	chkdsk, driver review
Random changing stop codes	mdsched.exe	SSD health, BIOS defaults
No restore point and nothing works	Back up files	Reset this PC (keep files)

14. Prevent the Next Restart Loop

🛡️ Habits That Save a Weekend

💾

Back up before big updates

Feature updates like a new Windows version deserve a full file backup first.

📍

Create a restore point

Turn on System Protection so Recovery has something to restore.

⏸️

Delay, don't skip

Pausing updates for a short period lets early bugs get patched or documented.

🔑

Save your BitLocker key

Keep it in your Microsoft account and one offline place.

15. Final Summary

The Order That Works Best

Read the stop code, then escalate gently: uninstall the latest update, repair system files in Safe Mode, roll back the suspect driver, repair the boot configuration, and only then reach for System Restore or a reset.

If the stop code keeps changing or crashes continue in Safe Mode, test your RAM and SSD before reinstalling anything. Always have your BitLocker key and a backup plan ready.

16. Frequently Asked Questions

Usually a faulty or freshly updated driver, corrupted system files after an update, a failing drive or RAM, or a conflicting security update. The stop code on the crash screen points to which one.

Interrupt startup three times to open Recovery. Go to Troubleshoot > Advanced options > Uninstall Updates and remove the latest quality update. If the loop continues, try Startup Repair or System Restore.

Power off during the Windows logo three times to reach Recovery. Choose Troubleshoot > Advanced options > Startup Settings > Restart, then press 4 or F4 for Safe Mode.

A process Windows can't run without stopped or was damaged. Common triggers are bad drivers, corrupted system files, or disk errors. Run DISM and SFC from Safe Mode first.

A core Windows process such as Winlogon or the client server runtime terminated unexpectedly. It often follows an interrupted or mismatched update. Uninstall the latest update, then run SFC offline from Recovery.

In Recovery, open Startup Settings and press 9 or F9. Inside Windows, run sysdm.cpl, open Advanced > Startup and Recovery > Settings, and clear the Automatically restart box.

Uninstalling updates, SFC, DISM, Startup Repair and System Restore leave personal files alone. Reset this PC can keep files but removes apps, so back up first when possible.

Changes to boot settings, firmware or recovery mode can trigger it. Find your key at aka.ms/myrecoverykey with your Microsoft account, or ask your IT admin on a work or school device.

Open the dump files in C:\Windows\Minidump with WinDbg or BlueScreenView. Also check Reliability Monitor and Event Viewer for Kernel-Power 41 and BugCheck 1001 entries.

Suspect hardware when stop codes keep changing, crashes happen in Safe Mode, or disk errors appear. Run Windows Memory Diagnostic and check your SSD health before reinstalling Windows.