Windows 11 updates are designed to improve security, fix problems, and optimize PC performance. However, sometimes they can do the opposite: Windows restarts unexpectedly with a Blue Screen of Death (BSOD) and crashes repeatedly before you can even get to the desktop. A BSOD error usually occurs when Windows encounters a serious problem that it could not safely recover from, so it stops the system to prevent further damage.
If the problem started after a Windows 11 update, the update may have triggered a compatibility issue with an existing driver, software, or hardware. An outdated or incompatible driver, corrupted Windows system files, or even a hardware problem can cause a BSOD error on Windows 11. Here are 10 practical solutions to fix the BSOD and get back your PC to normal working condition.
Why Does Windows 11 Show a BSOD After an Update?
A Windows update can change system files, drivers, security components, and other parts of the operating system. Most updates install without problems, but occasionally a new change can conflict with something already installed on your PC. That conflict may cause Windows to crash and display a Blue Screen of Death (BSOD).
Some common reasons include:
- Incompatible or faulty drivers: An update may expose a problem with an older graphics, network, storage, or chipset driver.
- Corrupted system files: Files involved in the update may become damaged or fail to install correctly.
- A problematic Windows update: Occasionally, an update itself may contain a bug that causes crashes on certain hardware or configurations.
- Software conflicts: Third-party antivirus programs, system utilities, or other software may not work correctly after Windows changes.
- Hardware-related problems: An update may not necessarily be the root cause. Existing RAM, storage, overheating, or other hardware problems can sometimes become noticeable around the same time.
Fix 1: Restart Your PC and Check the BSOD Error
If the BSOD occurred only once after installing an update, start with a simple restart. Windows may have encountered a temporary driver or system error that doesn’t happen again after rebooting.
If the PC keeps crashing, pay attention to the stop code shown on the blue screen. Take a photo of the BSOD or write down the stop code before restarting. Search for that specific stop code later to identify the likely cause.
For example:
DRIVER_POWER_STATE_FAILUREoften points to a driver or power management issue.SYSTEM_SERVICE_EXCEPTIONcan be related to drivers or Windows system components.MEMORY_MANAGEMENTmay indicate a memory problem or corrupted system data.PAGE_FAULT_IN_NONPAGED_AREACan be caused by drivers, system files, or faulty hardware.
If Windows keeps crashing during startup or you can’t reach the desktop, you’ll need to troubleshoot from Windows Recovery Environment (Windows RE). It provides tools such as Startup Repair, Safe Mode, System Restore, and Uninstall Updates that can help when Windows won’t start normally.

Fix 2: Update Device Drivers
An outdated or incompatible driver can cause BSOD errors after a Windows 11 update, especially with graphics, chipset, network, and storage devices. Updating these drivers can resolve compatibility problems introduced by the update.
- Press Win + X and select Device Manager.
- Expand Display adapters, Network adapters, Storage controllers, or System devices.
- Right-click the relevant device and select Update driver.
- Choose Search automatically for drivers and install any available update.
- Restart your PC and check whether the BSOD returns.

If Windows says the best driver is already installed, visit your PC manufacturer’s support website and download the latest Windows 11-compatible driver for your exact model.
- For graphics, check NVIDIA, AMD, or Intel.
- For laptops, go to your brand’s support page (e.g., Dell, HP, Lenovo) for driver bundles.
Tip: If the BSOD started after a driver update, open the device’s Properties > Driver tab and select Roll Back Driver, if the option is available.
Fix 3: Run System File Checker and DISM
Corrupted or damaged Windows system files can sometimes cause BSOD errors after an update. Windows includes two built-in tools DISM and System File Checker (SFC) that can check and repair damaged system components.
First, open Windows Terminal (Admin) or Command Prompt (Admin) and run:
DISM /Online /Cleanup-Image /RestoreHealthWait for the scan to finish. It can take several minutes.

Then run:
sfc /scannowWhen the scan reaches 100%, restart your PC and check whether the BSOD occurs again.
Tip: Run DISM first, then SFC. DISM can repair the Windows component store that SFC relies on when replacing corrupted system files.
Fix 4: Check for Third-Party Software Conflicts
Third-party antivirus programs, VPNs, system-tuning tools, and hardware-monitoring software can sometimes conflict with Windows after an update and trigger BSOD errors.
If the crashes started after an update:
- Temporarily disable or uninstall any third-party software you recently updated.
- Pay particular attention to antivirus, VPN, driver management, and system optimization tools.
- Restart your PC and check whether the BSOD returns.
- If the crashes stop, update the affected software or contact its developer for a compatible version.
If you’re unsure which program is causing the problem, you can perform a clean boot to start Windows with only essential services and drivers. If the BSOD stops during a clean boot, you can gradually re-enable services and startup apps to identify the conflicting software.
Fix 5: Disable Fast Startup
Fast Startup can sometimes cause driver and power management issues after a Windows 11 update, particularly when crashes occur during shutdown, startup, or wake-from-sleep.
To disable it:
- Press Win + R, type
control, and press Enter. - Go to Hardware and Sound > Power Options.
- Select Choose what the power buttons do.
- Click Change settings that are currently unavailable.
- Uncheck Turn on fast startup (recommended).
- Click Save changes and restart your PC.

Use your PC normally for a while and check whether the BSOD returns. If disabling Fast Startup makes no difference, you can turn it back on later.
Fix 6: Uninstall the Recent Windows Update
If the BSOD started immediately after a recent Windows 11 update, uninstalling that update can help confirm whether it is responsible. This is especially useful when the crashes started right after an update and your PC was working normally beforehand.
- Press Win + I to open Settings.
- Go to Windows Update > Update history.
- Scroll down and select Uninstall updates.
- Find the most recently installed update.
- Click Uninstall and follow the instructions.
- Restart your PC and check whether the BSOD continues.

If the problem started after a specific cumulative update, note its KB number before removing it.
Important: Don’t automatically uninstall an update simply because the BSOD appeared after updating. First try the driver and system-file fixes above, as the update may have exposed an existing compatibility problem rather than caused the crash itself.
Fix 7: Use System Restore
If the BSOD persists after removing the recent update, System Restore can revert Windows to an earlier restore point from when your PC was working normally. Your personal files won’t be removed, but apps, drivers, and system changes made after that restore point may be reverted.
- Press Win + R, type
rstrui.exe, and press Enter. - Select Next to see the available restore points.
- Choose a restore point created before the BSOD started.
- Click Scan for affected programs to see what may be changed.
- Select Next > Finish and allow Windows to complete the restore.
Your PC will restart during the process. Once Windows loads, use the computer normally and check whether the BSOD returns.
Note: System Restore only works if Windows has a suitable restore point available.
Fix 8: Run Windows Memory Diagnostic
A faulty or unstable RAM module can cause Windows 11 to crash with different BSOD errors, including MEMORY_MANAGEMENT and PAGE_FAULT_IN_NONPAGED_AREA. If the crashes continue after an update, it’s worth checking your system memory.
Windows has a built-in Windows Memory Diagnostic tool:
- Press Win + R, type
mdsched.exe, and press Enter. - Select Restart now and check for problems.
- Windows will restart and run a memory test automatically.
- Wait for the test to finish and allow Windows to start again.
- Check the results after signing back in.

If Windows reports memory problems, faulty RAM may be responsible for the BSODs. On a desktop, you can test RAM modules individually if you have more than one installed. For a laptop, consider contacting the manufacturer or a technician if the memory is not easily accessible.
Fix 9: Check for Hardware and Firmware Problems
If Windows 11 still crashes after updating drivers and repairing system files, the problem may be related to hardware or firmware rather than Windows itself. Faulty RAM, storage problems, overheating, or an outdated BIOS/UEFI can all cause system instability.
Start by checking whether your PC manufacturer provides a BIOS/UEFI or firmware update for your model. Also run any built-in hardware diagnostic tools provided by the manufacturer.
If the BSOD occurs mainly when using a particular device such as a USB drive, external display, printer, or docking station, temporarily disconnect it and check whether the crashes stop.
If hardware diagnostics report an error, or the BSOD continues even after a clean Windows installation, the underlying hardware may need to be repaired or replaced.
Fix 10: Repair Windows 11 Using an In-Place Upgrade
If you’ve tried the previous fixes and Windows 11 still shows BSOD errors, an in-place repair upgrade can replace damaged Windows components without removing your personal files, apps, or settings.
You can use a Windows 11 installation ISO or installation media that matches your current Windows version.
- Download the Windows 11 ISO from Microsoft’s official website.
- Mount the ISO and open
setup.exe. - Follow the setup instructions.
- When asked what to keep, select Keep personal files and apps.
- Continue with the installation and let Windows restart as needed.
This reinstalls the Windows system components while preserving your existing setup. It can help when repeated BSODs are caused by damaged Windows files or components that SFC and DISM couldn’t fully repair.
Important: Back up important files before performing a repair installation. If BSODs continue even after the repair, the problem is more likely to involve a driver, hardware, firmware, or other software conflict.
If Windows 11 Still Shows BSODs After an Update
If the BSOD continues after trying all 10 fixes, or Windows crashes repeatedly before you can reach the desktop, the problem may require more advanced troubleshooting.
If you can’t start Windows normally, enter Windows Recovery Environment (Windows RE). From there, you can access tools such as Startup Repair, Safe Mode, System Restore, and Uninstall Updates. Safe Mode is particularly useful because it starts Windows with only essential drivers and services, making it easier to identify whether a driver or third-party program is causing the crashes.
If Windows works normally in Safe Mode but crashes during a regular startup, a recently installed driver, service, or application is likely worth investigating.
If BSODs continue even in Safe Mode, consider checking your hardware, BIOS/UEFI firmware, and storage drive more closely. Persistent crashes after a Windows repair may indicate a hardware problem rather than an issue with the Windows update itself.
How to Prevent Windows 11 BSODs After Future Updates
Once the BSOD is resolved, a few simple habits can reduce the chance of the problem returning:
- Keep Windows 11 and device drivers updated.
- Install BIOS/firmware updates recommended by your PC manufacturer.
- Avoid installing multiple driver-update or system-optimization tools.
- Keep important files backed up before major Windows updates.
- If a particular update causes problems, check Microsoft’s release health information for known issues before making major changes.
If the BSOD returns after a future update, note the stop code and when the crash occurs. This can make it much easier to identify whether the problem is related to a driver, software conflict, Windows component, or hardware.
