When a Windows 11 update leaves you with blue screens, random troubleshooting wastes time. What works is a method: capture the evidence, reverse the change, fix the underlying driver, and verify. This walkthrough gives you that order of operations, with each step telling you what to look for and what to do next.

The core insight is simple — something changed, and now the system crashes. Your job is to identify the change, undo it, and then address whatever made the change dangerous in the first place. Let’s go step by step.

Why this happens

  • A driver bundled with the update is incompatible. Graphics, storage, and network drivers pushed through Windows Update are the top cause.
  • The update conflicts with kernel-level software. Antivirus, disk encryption, and VPN clients hook into the system at a level where updates can break them.
  • System files were corrupted during installation. Interrupted downloads, full disks, or power loss leave mismatched components.
  • Firmware is too old for the new build. Feature updates expect modern BIOS behavior; old firmware misreports hardware capabilities.
  • The update exposed marginal hardware. RAM or SSDs that were borderline can start crashing under new code paths.
  • Multiple pending updates stacked up. Installing months of updates at once multiplies the chances of a conflicting combination.

How to fix it

Work through these in order — each step either fixes the problem or gives you the evidence the next step needs.

Fix 1: Capture the stop code and suspect driver

Evidence first. A photo of the blue screen is genuinely useful here.

  1. When the blue screen appears, note the stop code (e.g. MEMORY_MANAGEMENT) and any driver file named (e.g. dxgkrnl.sys).
  2. Photograph the screen with your phone — you may not see it again, and the details matter.
  3. If the laptop reboots too fast to read it, disable automatic restart later: in recovery, this setting lives under Troubleshoot > Advanced options > Startup Settings, or in Windows via System Properties > Advanced > Startup and Recovery.
  4. Check Settings > Windows Update > Update history and write down which update installed right before the crashes started.

Fix 2: Boot into Safe Mode to stabilize

Safe Mode bypasses the crashing driver and gives you a working desktop for repairs.

  1. Interrupt the boot three times to reach Automatic Repair, then go to Troubleshoot > Advanced options > Startup Settings > Restart.
  2. Press 4 for Safe Mode (press 5 if you need networking to download drivers).
  3. Once in, open Device Manager and look for yellow warning icons — these flag devices whose drivers are in a bad state.
  4. From Safe Mode you can uninstall updates, remove drivers, and run repair tools without the crashing driver loading. If you need a refresher on the options, see the guide on booting Windows 11 in Safe Mode .

Fix 3: Uninstall the offending update

Reverse the change that started the trouble.

  1. In normal or Safe Mode, go to Settings > Windows Update > Update history > Uninstall updates.
  2. Select the update dated just before the crashes began and click Uninstall.
  3. Restart and test for a full day of normal use.
  4. If Windows won’t boot at all, do it from recovery: Troubleshoot > Advanced options > Uninstall Updates, choosing the latest quality or feature update as appropriate.

Fix 4: Fix the driver the stop code points to

The update may be gone, but the driver it broke often needs direct attention.

  1. Match the stop code or driver filename to its device: nvlddmkm.sys is NVIDIA graphics, rtwlanu.sys is Realtek Wi-Fi, stornvme.sys is the NVMe storage driver.
  2. In Device Manager, right-click the device, choose Uninstall device, and tick Attempt to remove the driver for this device.
  3. Restart, then install the correct driver from the laptop maker’s site (Dell , HP , Lenovo ) or the component vendor (NVIDIA , AMD ).
  4. Pause Windows Update for a few weeks (Settings > Windows Update > Pause updates) so the bad version isn’t immediately reinstalled.

Fix 5: Repair system files and the boot configuration

If crashes survive the update’s removal, the installation damaged something structural.

  1. From recovery, open Command Prompt under Advanced options.
  2. Run sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows to check protected files offline.
  3. Then run DISM /Image:C:\ /Cleanup-Image /RestoreHealth followed by the boot repairs: bootrec /fixmbr, bootrec /fixboot, and bootrec /rebuildbcd.
  4. Restart. These commands fix the large majority of update-damaged boot configurations without touching personal data.

Fix 6: Check firmware and hardware health

Rule out the physical layer before doing anything drastic.

  1. Check your BIOS version with msinfo32 and compare it to the latest on your manufacturer’s support page — install the update if you’re behind.
  2. Run Windows Memory Diagnostic to rule out RAM that the update merely exposed.
  3. Check drive health with CrystalDiskInfo; a failing SSD plus a major update is a classic crash combination, and storage faults also produce UNEXPECTED_STORE_EXCEPTION errors.
  4. Clean dust from vents and confirm the laptop isn’t overheating — thermal crashes get misattributed to updates all the time.

Fix 7: Reset Windows with files kept

When targeted fixes fail, a reset gives you a clean system while preserving your data.

  1. Boot to recovery and choose Troubleshoot > Reset this PC > Keep my files.
  2. Pick Cloud download for a fresh Windows image rather than reusing local files that may be damaged.
  3. After the reset, install chipset and graphics drivers from the manufacturer before running Windows Update.
  4. Reinstall applications one batch at a time over a few days — if crashes return after a particular install, you’ve found a software conflict.

Closing

Troubleshooting post-update blue screens is a process of elimination done in the right order: read the stop code, get into Safe Mode, remove the update, fix the named driver, repair system files, check hardware, and reset only as a last resort. Most cases resolve in the first four steps. Keep notes on which update caused it so you can pause or hide it next time — and if the crashes keep pointing at one driver file, that driver’s dedicated fix guide is your next read, starting with the walkthrough for general blue screen of death errors .

Frequently asked questions

What is the first thing to check when a blue screen appears after an update?
Read the stop code on the blue screen and note any driver file named, such as nvlddmkm.sys. That code and filename point straight at the failing component. Then check Settings > Windows Update > Update history to see exactly which update installed just before the crashes began.
How do I get into Safe Mode if Windows keeps blue-screening?
Force the recovery environment by interrupting the boot three times (hold the power button during the Windows logo), then go to Troubleshoot > Advanced options > Startup Settings > Restart and press 4 for Safe Mode. Safe Mode loads minimal drivers, which usually avoids the crashing driver.
Should I use System Restore or uninstall the update?
Uninstall the update first — it directly reverses the change that caused the problem. Use System Restore if the uninstall option is unavailable or if multiple changes happened at once. Both leave your personal files untouched.
When should I reset Windows instead of troubleshooting further?
Reset when you have spent over an hour on driver and update fixes without progress, when SFC and DISM report unfixable corruption, or when the system cannot stay booted long enough to apply fixes. Choose Keep my files so your documents survive the reset.