Western Digital NVMe SSD users beware: Windows 11 24H2 is causing BSODs unless you tweak your registry

[-]

DRIVER_93@reddit

Does this only affect os drives?

I'm using a SN770 as a secondary drive.

[-]

No it affects the drive regardless of it being OS boot drive or not. My SN770 was installed as a secondary game storage drive and when fortnite updated it corrupted the drive and windows reported read write failures.

[-]

DRIVER_93@reddit

Yeah your spot on, anything installed on sn770 is throwing out errors now, oddly other than one error two night ago it was running fine last night.

I just fresh installed 24h2 from windows 10 last week, thinking I'd get a head start on EOL. Does Microsoft have it out for it's users.

[-]

pcfarrar@reddit

Firmware update is out now to fix the problem.

[-]

DRIVER_93@reddit

Yeah I already updated thanks anyway.

[-]

kwirky88@reddit

So the cost savings of hmb (particularly ramless ssds) is biting consumers in the ass?

[-]

faverodefavero@reddit

Nope. Windows 11 is just shit.

[-]

BoringCabinet@reddit

Yet it's only occurring to WD drives.

[-]

zsaleeba@reddit

I have a Samsung ssd and I'm getting the bsod too. And I'm hearing of other Samsung ssd users with the same problem.

[-]

ryanvsrobots@reddit

Which one?

[-]

zsaleeba@reddit

It's a 980. But now I'm wondering if it's more related to the performance changes they made for Ryzen in 24H2.

[-]

gingeydrapey@reddit

I have a random sata SSD and 24h2 runs flawlessly. Feels quicker than 23h2

[-]

zsaleeba@reddit

With an Intel processor or an AMD? Mine's an AMD and I'm wondering if it relates to the changes they've made for AMD Spectre performance,

[-]

gingeydrapey@reddit

Intel. Seems AMD does boot slower for whatever reason.

[-]

dustarma@reddit

I don't think SATA drives can make use of HMB

[-]

gingeydrapey@reddit

I didn't say they can. They're still really fast tho

[-]

faverodefavero@reddit

Not the first time Windows 11 has problems with different NVMEs from different manufacturers, not to mention their problems with AMD recently, among other things.

[-]

GladiatorUA@reddit

Could be playing fast and loose with implementation.

[-]

dc_IV@reddit

Seriously, fuck Tom's Hardware for using a stock photo of an SN850X and it is not even the affected SSD. Do better.

[-]

Arbiter02@reddit

Lazy ass “journalism” as usual from tech

[-]

QuintoBlanco@reddit

The problem is that most people are unwilling to pay for journalism.

[-]

Default_Defect@reddit

I bought an SN850X to throw linux on to play around with so I could have my windows stuff untouched in case of an issue. Kind of a funny dodged bullet.

[-]

-CerN-@reddit

SN850X is not affected

[-]

Default_Defect@reddit

Dyslexia strikes again, I saw the 580 mentioned and got mixed up.

[-]

Forsaken_Ad242@reddit

Is everybody with a WD NVME and Windows 11 supposed to be hit by this? Because I have a WD SN850X and I haven’t yet. Or is this something I should look out for and adjust my registry anyway?

[-]

1soooo@reddit

Was gonna say WD Blacks wont be affected as they are high end drives with dram as this is an HMB issue.

But then i remembered WD ruined it by releasing a WD Blue dressed in black in the form of SN770.

[-]

Traditional_Yak7654@reddit

That drive shouldn't be using HMB so technically it shouldn't have any issues if the problem is truly the HMB thing only.

[-]

nuclearbananana@reddit

Same, also 850x and no issue yet

[-]

imaginary_num6er@reddit (OP)

How To Fix NVMe SSD Crashing in Windows 11 24H2

Open Start Menu, type Regedit to enter the Registry Editor.

Find “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\StorPort key”

Create “HmbAllocationPolicy” subkey unless it’s already there.

Set DWORD to 0 or 2— 0 disables HMB entirely, while 2 sets it to the default 64MB value.

[-]

Using this ASCII.jp：HMBはNVMe SSD低価格化の切り札!?東芝メモリ「BG4」で実力検証 (3/6) 31 and google translate.
Set HMBAllocationPolicy back to 2 (max / default)
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’
Back in regedit go to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device
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’
Reboot

Source: https://community.wd.com/t/windows-24h2-wd-blue-screens/297867/41

[-]

Penecho987@reddit

Is there a list which drives are affected?

[-]

Gnerma@reddit

I've just built a SN770 rig for a friend and it isn't showing any signs of this issue which seems strange to me. 24H2 clean install.