If you download and run the “NVME HMB info” from http://vlo.name:3000/ssdtool/ does it show the 64MB config applied?
Are you on an intel platform? Maybe you have Intel RST enabled? Which means a different NVME controller driver is in use and it’s ignoring the registry settings.
Maybe uninstall the Intel RST drivers or disable it in bios.
Yes on intel, but RST is disabled in BIOS. I will give it another try today, maybe I mistyped something.
I think it is very disappointing that WD did not yet reply here or in my support case. It has been 6 days now.
I have no problems with the sn580 1gb on the 24h2 pro, the nvme hbm program shows that the system allocates 200 MB for the buffer
Turn on RST and the problem will disappear
Great, thanks! I tried running the new script and no crashes so far.
We’re live, people! I’ve seen multiple YouTube reports about this issue in the last couple of days, which is extremely promising. As long as we keep making noise about all this, more outlets will bring all the needed attention to this issue. Hopefully we’ll soon receive an official statement from either MS, or Western Digital themselves.
That is to say we shouldn’t rest on our laurels and, rather, we should make our voices heard… loud and clear.
2 Likes
I began having random hangs and finally reported this to WD Support in January 2024, but was using Intel RST. I ran a number of diagnostics but they were not able to identify an issue. At the time the symptoms were seeing Warnings for iaStorVd (“Reset to device, \Device\RaidPort0, was issued.”) followed by many Warnings for disk (“The IO operation at logical block address [address] for Disk 0 (PDO name: \Device\00000045) was retried.”) that occurred in a small time period. Post BSOD, the system would fail to generate a dump. Restarting would result in BSOD about half of the time.
This past weekend I decided to try a clean re-install without RST, and began having issues that led me to several Reddit threads (two posts on Microsoft Answers, and 1 post on Toms Hardware Forums), some of which pointed me here. I have two SN770s and haven’t had any stornvme or volmgr events since making the two registry changes described here. I set the HMB policy to 2. I do not know if my prior issues are related, but am very disappointed in these drives.
My questions are:
- Can you implement these registry tweaks BEFORE upgrading to 24H2 (I have not upgraded yet, still on 23H2)? Will the tweaks survive the upgrade?
- Also, my computer actually has two 770’s installed (a 1TB and a 2TB). Will the two tweaks (HMBAllocationPolicy and HostMemoryBufferBytes) affect both drives? The multi-string value for HostMemoryBufferBytes is identical for both of my 770’s.
- Do you really need to do both the HMBAllocationPolicy tweak and the HostMemoryBufferBytes tweak?
For me the install of 24H2 went smoothly, I did a clean install via a USB created with the media creation tool. The setup process and initial couple of restarts were fine. It must have been after some chipset drivers installed either from windows update or manually that the problems started, it probably had HMB disabled before the drivers kicked in.
But I’m not sure if you can set them before doing an upgrade.
I just did the registry tweak now and updated to 24h2. Can confirm it saved and no longer crashing on SN580
I guess my concern is, if you can’t boot to the desktop, how can you implement the registry fix? Safe mode?
Let me confirm that you did the registry tweak(s) first before upgrading to 24H2, then upgraded to 24H2, and finally the tweak(s) is/are still in place in the registry after the upgrade.
Correct, I made the registry change while I was on 23H2, then ran windows update assistant to upgrade, and it saved and is not crashing
1 Like
Thank you. I was concerned I wouldn’t have an opportunity to implement the registry change if I had to do it after the upgrade.
Did you do both tweaks (HMBAllocationPolicy and HostMemoryBufferBytes) or just the HMBAllocationPolicy tweak?
You’ve just described the same issue I was having with my drive (SN770). I’m on an AMD platform, however, so the Intel RST driver is out of the question.
I did both the Policy and Bytes tweak and I am yet to have my NVMe stall on me.
So, I’d say it’s a win for us both.
Personally I need both registry entries to keep HMB enabled and at 64MB.
Today I finally got a response from WD
Hello,
Thanks for getting back to us and for the time you gave us to review the matter in depth.
In order to investigate further this matter, please kindly share with us the below details:
A photo of the blue screen with the error message
WD Dashboard report file
Event viewer logs
WD Dashboard report: Download, Install, Test Drive and Update Firmware Using Western Digital Dashboard
Event viewer logs: Steps to Collect Microsoft Event Viewer Logs
If you have any further questions, please reply to this email and we will be happy to assist.
Thank you for your time and for your cooperation.
Alternatively Jamin, you can start a live chat with one of our support specialists on this link- at the bottom right of the new page, just click the chat bubble! If you prefer to call us, click here.
Sincerely,
redacted
Western Digital Customer Service and Support
I responded that all the information she needs is in this thread.
2 Likes
Thank you.
See? All it took was some fuss and lots of shouting about. Now, we’re getting somewhere! Slowly, but surely…
Not sure. This could also be a halfway automated response.
What I haven’t seen yet is a public acknowledge from a WD or Windows spokesperson that even admits that there is a problem.
1 Like
