CRITICAL_PROCESS_DIED, WHEA_UNCORRECTABLE_ERROR, and stornvme.sys Event ID 11/129 crashes on DRAM-less Western Digital NVMe SSDs (including the WD Black SN770, WD Blue SN580, and WD Blue SN5000) running Windows 11 24H2/25H2 are caused by a Host Memory Buffer (HMB) allocation mismatch. Whereas Windows 11 23H2 respected the SSD's preferred 64 MB HMB size, Windows 11 24H2 allocates up to the drive's reported 200 MB maximum boundary, triggering controller firmware lockups. To fix it permanently, update your SSD firmware via SanDisk/Western Digital Dashboard, or apply the temporary HmbAllocationPolicy Windows Registry workaround below before upgrading.
1. Root Cause Analysis: What Is Host Memory Buffer (HMB) and Why Does Windows 11 24H2 Break It?
To keep prices competitive and power consumption low, popular midrange NVMe SSDsβsuch as the WD Black SN770 and WD Blue SN580βuse a DRAM-less architecture. Instead of soldering a dedicated DDR4 DRAM chip onto the M.2 PCB to cache the Flash Translation Layer (FTL) logical-to-physical address lookup table, DRAM-less drives rely on a PCIe NVMe 1.2+ specification feature called Host Memory Buffer (HMB).
With HMB, the NVMe controller asks the Windows kernel (`stornvme.sys`) to reserve a tiny slice of your PC's main system RAM over Direct Memory Access (DMA) to store active FTL metadata. During the PCIe initialization handshake, the SSD firmware reports two key descriptor registers to the operating system:
- HMPRE (Host Memory Buffer Preferred Size): The exact amount of RAM the controller firmware was tested and optimized to address ( typically 64 MB).
- HMMIN / Maximum Descriptor Boundary: The theoretical upper ceiling reported in the controller's firmware table (erroneously advertised as up to 200 MB on older SN770 and SN580 firmware revisions).
In Windows 10 and Windows 11 22H2/23H2, Microsoft's `stornvme.sys` driver conservatively capped HMB allocations at 64 MB, matching the drive's preferred `HMPRE` value. However, starting with Windows 11 Version 24H2, kernel memory management was modified to grant NVMe drives their full maximum advertised HMB buffer (up to 200 MB). When the WD controller attempts to index DMA memory descriptors beyond the 64 MB boundary, an internal pointer overflow locks up the NVMe ASIC, instantly severing access to the C: boot volume and triggering a `CRITICAL_PROCESS_DIED` or `KERNEL_DATA_INPAGE_ERROR` Blue Screen of Death (BSOD).
2. Affected Western Digital & SanDisk NVMe Models and Target Firmware Versions
Check your exact SSD model and currently active firmware revision inside Windows Device Manager or CrystalDiskInfo against our engineering compatibility matrix below:
| SSD Model Name | Capacities Affected | Buggy Firmware Versions | Fixed Firmware Version (2026 Safe) |
|---|---|---|---|
| WD_BLACK SN770 NVMe SSD | 500GB, 1TB, 2TB | 731120WD and earlier | 731130WD (or newer) |
| WD_BLACK SN770M (M.2 2230 Handheld) | 500GB, 1TB, 2TB | 731120WD and earlier | 731130WD (or newer) |
| WD Blue SN580 NVMe SSD | 500GB, 1TB, 2TB | 281040WD and earlier | 281050WD (or newer) |
| WD Blue SN5000 NVMe SSD | 500GB, 1TB, 2TB | 291000WD and earlier | 291020WD (or newer) |
| SanDisk Extreme M.2 NVMe SSD | 500GB, 1TB, 2TB | 731120WD and earlier | 731130WD (or newer) |
3. Method 1: The Immediate Windows Registry Workaround (No Reboot Loops)
If your PC is already running Windows 11 24H2 and crashing every 10 minutes before you can download a firmware updater, boot into Windows Safe Mode (or open an elevated terminal immediately upon login) and force `stornvme.sys` to restrict HMB allocation back to the safe 64 MB limit (HmbAllocationPolicy = 2).
Step-by-Step PowerShell & Command Prompt Fix
Right-click the Windows Start button, select Terminal (Admin) or Command Prompt (Admin), and execute these two registry commands:
# Force Windows 11 stornvme.sys to cap Host Memory Buffer at 64MB (Policy = 2)
reg add "HKLM\SYSTEM\CurrentControlSet\Control\StorPort" /v HmbAllocationPolicy /t REG_DWORD /d 2 /f
# Optional emergency fallback: Only use if Policy 2 still crashes (0 = Disable HMB completely)
# reg add "HKLM\SYSTEM\CurrentControlSet\Control\StorPort" /v HmbAllocationPolicy /t REG_DWORD /d 0 /f
Understanding the three valid HmbAllocationPolicy DWORD values in Windows 11:
0(Disabled): Completely turns off Host Memory Buffer. The SSD will be 100% stable, but random 4K read/write IOPS will drop by 35% to 50% because every FTL lookup must read directly from NAND flash.1(Minimum Size β HMMIN): Allocates the smallest buffer supported by the drive (typically 4 MB to 16 MB).2(Preferred Safe Cap β 64 MB Limit): Restores the exact Windows 11 23H2 behavior, granting the full 64 MB preferred buffer while preventing the buggy 200 MB allocation. Always use value2first.
Restart your computer immediately after running the command for the kernel storage port driver to reload the parameter.
4. Method 2: The Permanent Fix β Updating Western Digital SSD Firmware
Once your system is stabilized via the Registry tweak above, you should apply the permanent hardware fix by flashing the updated controller firmware. The patched firmware updates the NVMe Identify Controller descriptor structure so the drive accurately reports 64 MB as its hard ceiling across both Windows and Linux kernels.
- Backup Critical Files First: Although NVMe firmware updates are non-destructive and take less than 15 seconds, power loss during an EEPROM flash can brick a storage controller.
- Install Western Digital / SanDisk Dashboard: Download and launch the official Western Digital Dashboard utility with Administrator privileges.
- Check for Firmware Updates: Select your WD_BLACK SN770 or WD Blue SN580 from the top drop-down selector, navigate to the Tools tab on the left sidebar, and click Check for Updates under the Firmware Update section.
- Perform a Full Cold Shutdown (Crucial Step!): After the firmware flash reaches 100%, clicking "Restart" in Windows is often insufficient because Windows Fast Startup keeps the PCIe NVMe controller powered on in standby. Instead, select Shut Down, wait 15 seconds for all motherboard LEDs and capacitors to discharge, and press the physical power button to cold-boot the new firmware.
5. Verifying System Stability & Repairing Corrupted System Files
Because sudden `CRITICAL_PROCESS_DIED` crashes interrupt active NTFS metadata writes, repeated BSODs prior to applying the fix frequently leave corrupted system DLLs or orphaned MFT journal entries on your boot drive. After updating your firmware, run this three-stage integrity repair in an Administrator PowerShell window:
# 1. Verify and repair the Windows Component Store image
DISM.exe /Online /Cleanup-Image /RestoreHealth
# 2. Scan and replace any corrupted Windows system binaries
sfc /scannow
# 3. Verify zero stornvme Event ID 129 / 11 resets in the past 24 hours
Get-WinEvent -FilterHashtable @{LogName='System'; ProviderName='stornvme'} -MaxEvents 10
Finally, if you successfully flashed firmware 731130WD (SN770) or 281050WD (SN580), you can safely delete the temporary registry override by running reg delete "HKLM\SYSTEM\CurrentControlSet\Control\StorPort" /v HmbAllocationPolicy /f so Windows manages HMB natively through the patched firmware descriptors.
Frequently Asked Questions (Technical Deep-Dive)
Why did my BSOD stop code say CRITICAL_PROCESS_DIED without creating a minidump file in C:\Windows\Minidump?
When the WD SN770 or SN580 controller locks up due to the 200 MB HMB overflow bug, the entire C: boot drive disconnects from the PCIe bus instantaneously. Because the Windows kernel (svchost.exe / csrss.exe) loses access to the pagefile and boot volume, it crashes with CRITICAL_PROCESS_DIED and cannot write a .dmp file to the disconnected SSD.
Are the WD Black SN850X or Samsung 990 Pro affected by the Windows 11 24H2 HMB bug?
No. Flagship drives like the WD_BLACK SN850X, Samsung 990 Pro, Crucial T500, and Kingston KC3000 have dedicated onboard LPDDR4/DDR4 DRAM cache chips soldered directly onto the SSD PCB. Because they have physical onboard DRAM, they do not use Host Memory Buffer (HMB) and are completely immune to this bug.
How can I update my WD SN770 or SN580 firmware on Linux if I don't have Windows installed?
You can update Western Digital NVMe firmware directly from Ubuntu, Fedora, or Arch Linux using 'nvme-cli' by downloading the raw .fluf firmware binary from Western Digital's public repository and running 'sudo nvme fw-download /dev/nvme0n1 --fw=731130WD.fluf' followed by 'sudo nvme fw-commit /dev/nvme0n1 -s 2 -a 1' and a full cold power cycle.
- β‘ How to Configure ZRAM, Swappiness, and EarlyOOM on Linux to Run Heavy IDEs Smoothly on 4GB/8GB RAM PCs
- β‘ How to Fix Micro-Stuttering and DPC Latency in Windows 11 24H2: Complete DX12 & UE5 Optimization Guide (2026)
- β‘ How to Completely Disable Windows 11 Telemetry, Copilot Recall, and Background Ads (2026 Step-by-Step Guide)
- β‘ How to Speed Up Slow Wi-Fi: Best DNS Settings and Router Tweaks for Minimum Gaming Ping in 2026
For top-tier drive recommendations that avoid host memory buffer issues, explore our roundup of the best NVMe SSDs in 2026.
- β How to Fix Windows 11 24H2 Audio Freezes, Game Crashes & AC-3 Decoding Bug (KB5127648 Guide)
- β How to Fix Windows 11 Black Screen with Cursor: 6 Verified Fixes for Post-Login & Boot Freezes (2026)
- β How to Fix "WiFi Connected, No Internet" in Windows 11: Winsock, TCP/IP & DNS Flush Guide (2026)
- β How to Configure ZRAM, Swappiness, and EarlyOOM on Linux to Run Heavy IDEs Smoothly on 4GB/8GB RAM PCs
π¬ Reader Discussion & Feedback 0