Windows 11 24H2 Update: BSOD Issues with WD SSDs Explained

  • Thread Author
It's a familiar refrain echoing through the halls of Windows Forum: yet another day, another bug in the latest Windows 11 update. The recent 24H2 rollout has triggered a series of frustrating issues, including crashes culminating in the dreaded Blue Screen of Death (BSOD), particularly impacting users with certain Western Digital (WD) SSDs. Here’s what you need to know about this troubling situation, the underlying technology involved, and the possible pathways to solutions.

The Nitty-Gritty Details​

As users gobbled up the latest features of the Windows 11 24H2 update, many owners of Western Digital's SN770 and SN580 SSDs found themselves in a digital whirlpool of frustration. Just over a week ago, reports began to trickle in about sudden crashes that seemed to correlate directly with the installation of the updates. Those afflicted experienced BSODs, a chilling hallmark of critical errors inside the Windows ecosystem.
The crux of the issue lies in how these specific SSDs handle data. Being DRAM-less, these drives utilize a feature called Host Memory Buffer (HMB), relying on your PC’s main memory instead of their own dedicated RAM. This design is commonplace in budget drives aimed at reducing costs but can lead to inefficiencies in handling data. Under normal conditions, these SSDs request around 64 MB of HMB to store transient information. However, after the 24H2 update, they suddenly began asking for up to 200 MB, overwhelming the system. The unintended result? A hard crash – hence the BSOD.

User Woes and Community Responses​

Reports flooded in on various forums, illustrating the widespread impact. One user recounted in exasperation, "After installing Windows 11 24H2, I got this in the event viewer: The driver detected a controller error on \Device\RaidPort1." Others echoed these frustrations, highlighting the error repeating itself after multiple device restarts.
A bright glimmer, however, emerged from the chaos as a workaround surfaced within the community. Users have found success by making registry modifications, effectively taming the HMB requirement, at least temporarily while they wait for an official fix. This DIY approach is not uncommon in tech circles; when the large bureaucratic ships of companies like Microsoft and WD take too long to respond, users often become resourceful.

Why Does This Matter?​

Understanding the implications of using DRAM-less SSDs is crucial for users navigating this tumultuous landscape. While they're often more affordable and energy-efficient, the trade-offs can be significant, especially in high-demand environments or after system-level updates. The reliance on HMB, while a clever strategy to save costs, creates hidden latency issues and potential for critical failures when additional memory demands are placed on the SSD.

Crash Course in SSD Technology:​

  • DRAM-less vs. DRAM SSDs: DRAM SSDs store their metadata in dedicated memory, allowing for faster access and better performance. Comparatively, DRAM-less SSDs tap into the system's RAM which can lead to slower speeds and more complications, particularly when firmware or operating system behaviors change.
  • Host Memory Buffer (HMB): This NVMe feature allows SSDs to use the system’s RAM for metadata storage, but its improper handling may lead to performance inconsistencies and, in this situation, BSOD instances.

The Bigger Picture​

The anxiety stemming from the Windows 11 24H2 update resembles echoes of past updates, like the infamous Windows 10 April 2021 KB5001330, which caused myriad crashes and performance issues. Although the 24H2 troubles appear less catastrophic, they still contribute to a growing narrative of user dissatisfaction surrounding software updates.
With Microsoft and Western Digital both acknowledging the situation, hope remains that they will provide effective patches soon to remediate the glitches that have emerged.

Conclusion: Is It Time to Roll Back?​

For those experiencing relentless crashes, rolling back to a previous version can be a tempting option. But this isn't always the ideal fix, as every version comes with its own bugs and vulnerabilities. The discussion continues in user forums, with advice ranging from tentative registry adjustments to waiting for future patches.
So, what’s next for Windows 11 users? Are we perpetually at the mercy of updates that provoke more issues than they resolve? The dialogue is far from over, and it’s one that may yet see new resolutions—if only users can hang on a bit longer without crashing.
In the spirit of community and troubleshooting, share your experiences, potential fixes, and thoughts on how to navigate the unpredictable waters of Windows updates. After all, every new glitch is just another story waiting to unfold.
Source: TechRadar Another day, another huge Windows 11 24H2 update bug, this time triggering the dreaded Blue Screen of Death
 


Back
Top