Windows 11 24H2 BSOD Issues: Critical Process Dies on WD SSDs

If you’ve recently upgraded to Windows 11 24H2 and have been experiencing the dreaded Blue Screen of Death (BSOD) with the ominous “critical process has died” error, take a deep breath and know you’re not alone. A growing number of users are facing this frustrating issue, particularly those on certain configurations involving Western Digital SSDs. And yes, Microsoft is reportedly aware and is considering halting the problematic update for a wider range of affected devices.

What’s Going Wrong?​

Sources close to the situation inform us that the BSOD occurrences are primarily linked to issues with specific storage drivers and RAID controllers. Users have noted that devices with Western Digital’s SSDs, particularly the WD Blue SN580 and SN770 models, have been prone to crashing since the update.
The crux of the problem seems to lie in how Windows 11 24H2 allocates host memory buffers (HMB). In Windows 11 23H2, these drives were allocated 64MB for HMB, which worked without issues. However, in the latest upgrade, that allocation is set to a full 200MB, which has been identified as the trigger for the BSOD errors related to critical processes failing.
One user recounted their experience with a brand-new pre-built machine that came equipped with a 2TB WD Blue SN580. Despite reinstalling Windows and reseating the SSD, the errors persisted, leading them to return the machine before deciding to build their own PC.

Microsoft's Response​

Although Microsoft has not officially acknowledged the issue, reliable sources indicate that the company is taking steps to address the bug. There are plans to pause the Windows 11 24H2 update for devices that are facing these issues, preventing affected users from downloading the upgrade via Windows Update or the Media Creation Tool.

Steps to Mitigate BSODs​

For those who are interested in a possible temporary workaround, you can tweak your registry settings to disable the host memory buffer allocation. Here’s how to do it:

1. Open Registry Editor: Press Win + R, type regedit, and hit Enter.
2. Navigate to the Following Path:
   

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device

3. Create HMBAllocationPolicy Entry:
   • If the entry doesn’t exist, right-click in the right pane, select New > DWORD (32-bit) Value, and name it HMBAllocationPolicy.
4. Set the Value:
   • Double-click the newly created entry and set its value data to 0.
5. Restart Your Computer.

Caution: While this might resolve the BSOD issues, be aware that it could affect the performance of your SSD.

Real-World Implications​

The fallout from such a systemic issue could have substantial real-world implications for potential buyers and current users of the affected SSDs. For tech enthusiasts and everyday users alike, the reliability of updates is critical to maintaining productivity and trust in the broader Windows ecosystem.
As users weigh their options, many may reconsider purchasing hardware that has been linked to these issues until Microsoft has provided a definitive fix and reassurance regarding stability.

Conclusion​

As the situation evolves, it’s a stark reminder for Windows users to remain vigilant after major updates, especially those that involve changes to core system components like storage drivers. If you’re affected by these issues, check back regularly for updates from Microsoft and keep your eyes on community forums where users often share solutions and workarounds.
In the meantime, if you’ve experienced issues with Windows 11 24H2, share your experiences in the comments below—your input could be invaluable to others facing similar challenges.
Source: Windows Latest Windows 11 24H2 causing BSODs, Microsoft will reportedly halt update for more PCs