Windows 24H2 + WD = blue screens

WD Internal Drives Internal Drives
22

yes, that’s true, but I quoted this:
‘‘24H2 grants the whole 200MB for SN770. If SSD firmware cannot handle the >64MB part, it will result write failure, and system file corrupt.’’

if this is true, then SN580 should handle 200mb part (24h2), because:

SN580 HMB size is 200 MB, which is more than the 64 MB that we’re typically seeing on DRAM-less SSDs.

edit: I’m using 23h2 since April. Tried 24h2 (25 days ago) just for few hours and removed it.

23

Disabled HMB and so far no more BSODs with an SN770 and 24H2. Thanks for tracking that down, now I guess we’ll just be waiting on a firmware update. Until then what does leaving it disabled do, just give a performance reduction? I did see that setting HMBAllocationPolicy to 2 gives a 64MB buffer, should that result in the same performance as having it enabled without crashing?

2 Likes
24

WD SN580 2TB

It doesn’t matter about the rest of my hardware because I have been fighting 24h2 for days. I just purchased a second WD SN580 2TB since windows 24h2 pooched my computer on sunday and I tried everything to get my computer back in running order. I have previously installed 24h2 on a Kingston 2TB and a Intel 256GB NVMe SSDs. They both installed fine. The other WD SN580 was purchased a month ago direct from the factory, it also gave me issues with the upgrade of my 23h2 to 24h2.

So I don’t think it is anything else. Anyone experiencing a blue screen boot loop with 24h2 and you are trying to install it on a western digital drive, be aware, you will probably get a blue screen.

1 Like
25

I think it worth a try to set HMBAllocationPolicy to 2.

And I need to mention that probably it is not WD’s problem. The problem maybe at Microsoft side. It may be because Windows cannot handle 200MB HMB. Maybe, Windows treats it as 256MB, and it causes memory exploit. That is also possible.

200MB is a weird number in binary world. I don’t know why WD picks that number.

2 Likes
26

Setting HMBAllocationPolicy to 0 solved the BSOD but the performance in games is crazy bad now. I will wait a couple of days for a fix or else i throw the ssd in the garbage can and buy another brand :slight_smile:

2 Likes
27

Has someone tried to set policy to 2?

1 Like
28

Yes, same problem with BSOD

29

Someone already tried the Phison driver?

30

Creating a DWORD32 “HMBAllocationPolicy” and setting it to the value of “2” fixed all issues related to EID 11 and NVMe (SN770) straight up stalling and crashing soon after.

So, yeah… it did alleviate my issues at no performance cost. R/W speeds remain as advertised. Cheers, Snailum! :slight_smile:

Also, to comment on the guy that went out here to give their ultimatum for all their problems in the world. Nobody comes here to listen to your whining and calling out ■■■■■■■■.

1 Like
31

Thanks for your answer! I’m looking forward to test it this afternoon.

32

So far my PC seems to be running fine with HMBAllocationPolicy set to 2 on an SN770.

1 Like
33

Nothing surprising… you’re allocating correct amounts of memory as cache.

I doubt WD will ever fix it, so we have to either rely on Microsoft and their bandaid Windows Update, or the HMB tweak for the foreseeable future.

34

24H2 is not widely available yet. It will be fun when everyone upgrades to 24h2, especially those that have SN580 and SN770.

35

I had one more today with my first boot with value 0:

imagen
imagen1308×631 39.2 KB

I changed the HMBAllocationPolicy to 2 to check if it’s better, I don’t know if I should come back to the generic windows driver or if with Micron NVMe driver v2.1.18.0 WHQL the edit registry path it’s the same.

Note that I didn’t have the stornvme error in events since I installed the new driver, but some BSOD still happening

Thanks everyone for the help, you are amazing, hope with this change to value 2 the BSOD stops, I will let you know

1 Like
36

I experienced the same issues after moving from Windows 10 to Windows 11 24H2 with this hardware:

  • SN770 2TB, latest firmware
  • B550I GAMING EDGE WIFI on BIOS version 7C92v1G

The OS can boot, but after a very short time (often on the login screen, before it even finishes loading) the OS becomes unresponsive and restarts.
The ONLY thing that has been able to alleviate the crashing is setting HMBAllocationPolicy to 0 while using the default NVMe controller driver. Any other combination of the value on this registry key or other NVMe controller drivers (have tried Micron and Phison) will cause the aforemented crashing. The error that is shown in Event Viewer upon each boot (Event 11, stornvme) persists though.

1 Like
37

I experienced another crash again, it might be the combination of Micron driver and HMBAllocationPolicy to 2.

Did you have the event 11 stornvme when you had Micron and Phison? It’s not there for me

I think I will try a fresh windows install with HMBAllocationPolicy to 0 and the default NVMe controller driver

Anyways I think in my case with a new computer, talk with the supplier and show them this post to get maybe a replacement for SSD or full refund

1 Like
38

Event 11 disappears with the other drivers, but the crashes persist. Either revert back to the default driver and set the DWORD back to 0, see if that helps (so far it’s worked for me), otherwise I guess Windows 11 24H2 has to be avoided until WD pushes out a firmware update for the drive.

2 Likes
39

Just updated to 24H2, and experienced crashes on start up and the same controller errors in the event log.

  • SN770 on firmware 731120WD
  • Asrock B650M Pro RS

HMBAllocationPolicy to 0 fixes the crashing, but is presumably having an impact on performance without HMB cache.

I tried HMBAllocationPolicy to 2, but that also allocated 200MB for me according to the NVME HMB info tool. I’ve set it to 1 this only allocates 3MB but better than nothing. Can’t find definitive info on the different values but a bit of Googling says “Valid values are 0 for disabled, 1 for minimum, 2 for maximum, and 3 for device usage-based”

I also tried the 64bit Micron NVMe driver v2.1.19.0 WHQL from the level1techs forum, but that just disables HMB according to the NVME HMB info tool.

So we need WD to fix the firmware to ask for 64MB, or MS to patch Windows.

1 Like
40

The fact that we are yet to receive an official repsonse or even basic acknowledgement of this issue, makes me doubt we will ever see a firmware update that would patch this stuff outright.

If you can, report this issue directly to Microsoft via the Feedback Hub. Given the severity of this issue and inability for an end-user to use their operating system, I’d wager this would be one of those “high priority” bugs for MS.

1 Like
41

Ah i’ve worked out how to set the HMB size to any value you want, i.e. back to 64MB for my SN770

Using this ASCII.jp：HMBはNVMe SSD低価格化の切り札!?東芝メモリ「BG4」で実力検証 (3/6) and google translate.

  1. Set HMBAllocationPolicy back to 2 (max / default)
  2. In device manager, under Disk drives find your affected drive. Right click Properties → Details tab and look at the parent property it’ll be like ‘PCI\VEN_15B7&DEV_5017&SUBSYS_501715B7&REV_01\4&333c8b5&0&0012’ you need to copy the VEN, DEV and REV parts. For my example it is ‘VEN_15B7&DEV_5017&REV_01’
  3. Back in regedit go to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device
  4. Create a new multi string value called ‘HostMemoryBufferBytes’ with the value from 2. followed by a space then the size in bytes you want i.e. ‘VEN_15B7&DEV_5017&REV_01 67108864’
  5. Reboot

Easy :sweat_smile:

4 Likes