The latest Windows 11 24H2 update was intended to bring performance enhancements and new features. However, for users with specific hardware configurations, it has turned into a nightmare. A critical and widespread issue has emerged where systems—particularly those utilizing 2TB WD SN770 SSDs and other Western Digital NVMe drives—are experiencing frequent Blue Screen of Death (BSOD) crashes immediately after updating.
If your system is stuck in a boot loop or crashing randomly after the 24H2 update, you are not alone. Here is a breakdown of why this happens and, more importantly, how to fix it.
Quick Guide: Which Fix Should You Choose?
| Fix Method | Difficulty | Permanent? | Recommended For |
| Firmware Update | Medium | Yes | All affected users (Best Solution) |
| Roll Back Update | Easy | No | Users stuck in a boot loop |
| Disable HMB | Advanced | Workaround | If firmware updates are unavailable |
The Problem: Why Is This Happening?
The Windows 11 24H2 update introduced changes to the storage driver stack and memory management that conflict with the Host Memory Buffer (HMB) feature used by certain NVMe drives. The WD SN770, being a DRAM-less drive, relies heavily on HMB to allocate a portion of your system RAM as cache.
Due to a driver compatibility bug tied to the stornvme.sys driver, the system fails to manage this allocation properly, leading to memory corruption and the infamous “CRITICAL PROCESS DIED” or “SYSTEM SERVICE EXCEPTION” BSOD errors.
Step-by-Step Solutions
If you have already updated and cannot boot, or if you are preparing to update, follow these troubleshooting steps.
1. Roll Back the Update (If You Can Access Recovery)
If you are experiencing crashes but can still access the Advanced Startup Options:
- Force shut down your PC three times to trigger the Windows Recovery Environment (WinRE).
- Go to Troubleshoot > Advanced Options > Uninstall Updates.
- Select Uninstall latest quality update.
2. Update Your SSD Firmware (The Permanent Fix)
Western Digital has acknowledged this issue. The permanent fix involves updating the firmware of your SN770 or other affected NVMe drives via the Western Digital Dashboard.
- Note: If you cannot boot into Windows to run the Dashboard, you will need to perform this fix from a safe mode environment or by using a secondary PC to update the drive.
3. Disable HMB (The Technical Workaround)
If you cannot update the firmware immediately, you can disable the Host Memory Buffer feature. This can be done via the Registry.
⚠️ Warning: Editing the registry can be risky. Back up your registry before proceeding.
- Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device - Create a new DWORD (32-bit) named
DisableHMBand set the value to1. - Restart your computer.
4. Ensure Your Hardware Meets Baseline Requirements
While the 24H2 update triggers this specific BSOD, system instability is often exacerbated by older hardware or insufficient resources. Before attempting a re-installation of the update, it is crucial to ensure your system meets the baseline requirements for a stable Windows 11 experience.
If you are running an older system, check out our guide on the Windows 11 System Minimum Requirements: CPU, TPM, and RAM Guide to ensure your hardware isn’t the root cause of the instability.
5. Verify Storage Health and Compatibility
This issue highlights the importance of understanding your storage configuration. Not all SSDs behave the same way under heavy OS updates. If you are using a mix of older SATA SSDs and modern NVMe drives, conflicts can arise.
For a deeper understanding of the hardware differences, refer to our detailed breakdown: HDD vs SSD vs NVMe: A Comprehensive Comparison. This will help you understand why DRAM-less drives like the SN770 behave differently than high-end NVMe drives with onboard cache.
6. Rule Out Memory (RAM) Issues
BSOD errors often mimic RAM failure. Before blaming the update entirely, it is wise to ensure your system’s memory is stable. The Windows 11 24H2 update places a heavy load on system resources.
Read our guide on How Much RAM Do You Really Need? to verify that your current memory capacity isn’t being maxed out by the new OS features, which could be triggering the crashes alongside the NVMe bug.
Final Wrap
Microsoft and Western Digital are actively working on a permanent patch. Currently, if you are experiencing the BSOD loop, the safest course of action is to roll back the update and wait for the official driver fix to be pushed through Windows Update. If you must stay on 24H2, updating your WD SSD firmware via the Western Digital Dashboard is the most reliable solution.
