Another day, another huge Windows 11 24H2 update bug, this time triggering the dreaded Blue Screen of Death

Users are currently voicing concerns regarding a specific issue linked to the Windows 11 24H2 update, particularly affecting owners of Western Digital SSDs, namely the SN770 and SN580 models. This bug has been responsible for system crashes and the dreaded Blue Screens of Death (BSOD), with the full extent of the impact still unclear as the rollout of the update continues.

Reports began surfacing over a week ago from users of the SN770 and SN580 SSDs, who noticed an uptick in crashes following the installation of the 24H2 update. Initially, the cause of these disruptions was elusive, but a common thread emerged: the timing of the update. Users have explored various avenues to rectify the situation, and a temporary workaround has recently been identified.

The nitty-gritty details

One user detailed their experience, stating:

“After installing Windows 11 24H2, I received this in the event viewer: The driver detected a controller error on DeviceRaidPort1. Blue Screen and restart. WD SN580 2TB. Firmware is updated to 281040. WD Dashboard shows Drive Health 100%.”

Another user echoed similar frustrations:

“Since I bought my PC six months ago, I didn’t have any problems with Windows 23H2. After installing 24H2, I experienced 4-5 blue screens after 10-15 restarts, all with the same error: ‘The driver detected a controller error on DeviceRaidPort1.’”

A fellow forum member, who had just acquired a new pre-built PC with the 24H2 update, shared:

“I have a WD Blue SN580 2TB NVME and keep getting blue screens when restarting the PC or opening certain files in File Explorer. The event logs leading up to the blue screen show the same event ID 11 stornvme and volmgr error. Is the new Windows update the main reason? Should I roll back?”

On October 8, a member of the WD community forum proposed a potential workaround, expressing frustration over the lack of communication from both Western Digital and Microsoft:

“While we still have no official answer from WD or MS, there is a workaround! Thank you @nissel! This will create two registry entries. If you want to remove them again, delete them by hand or use this: Registry file to remove the HMB policy entries · GitHub 22. Apparently, for some devices, it is enough to just disable HBM: Windows Registry disable HMB · GitHub 19.”

Does Microsoft deserve the hate?

It’s important to note that no major operating system update is without its challenges. Windows 10’s infamous April 2021 KB5001330 update, for instance, led to a myriad of crashes, performance issues, and BSODs, including installation failures and missing files. Fortunately, the bugs associated with the Windows 11 24H2 update do not appear to be as severe.

Both Microsoft and Western Digital are aware of the ongoing issue, and it is anticipated that patches and firmware updates will be forthcoming. As the situation unfolds, it remains to be seen whether additional users with similar SSDs will experience these problems. Whatever intriguing bugs may arise with the latest version of Windows 11, the tech community will be closely monitoring and reporting on developments.

<h3 class="article-bodysection” id=”section-you-might-also-like”>You might also like…

Winsage
Another day, another huge Windows 11 24H2 update bug, this time triggering the dreaded Blue Screen of Death