Windows 11 occasionally freezes up for several seconds then crashes on the login screen after starting up, usually with “Critical Process Has Died” though I’ve also noticed “Kernel Data Inpage Error” sometimes. If it doesn’t crash right away then it’s usually fine afterwards, though I’ll still occasionally get crashes after a while. No dump file is created, but event viewer almost always shows a “The driver detected a controller error on” error right at the time it freezes.
The issue started after doing a fresh install from 23H2 to 24H2, and I had also updated from BIOS 1802 right before doing so. It happened both before and after updating the SSD to the latest firmware. Leaving all the other drivers on whatever Windows Update chooses to install or manually updating them from the manufacturer’s website seems to have no effect.
Motherboard: Asus Prime B760M-A AX (BIOS 1666)
CPU: Intel i5-13500
GPU: Asus Dual 4060ti 16GB
RAM: Corsair Vengeance DDR5 32GB
Storage: WD_Black SN770 2TB (Firmware 731120WD)
I got first blue screens starting around 2024-10-04.
Windows updates
2024-10-02 / 24H2
2024-10-04 / KB5043178
even more updates after blue screens started
Always same event when crashing:
ID 11 stornvme \Device\RaidPort1
Installed WD Dashboard and latest SSD firmware but did not help. MemTest86 passed without errors. Blue screen happens randomly. Sometimes even right after a reboot. Opening device-manager reliably causes BSOD. The only hint I have is the error event.
WD Blue SN580 NVMe SSD 2TB
AMD Ryzen 7 7800X3D
MSI PRO B650-S WIFI (MS-7E26)
Palit RTX 4080 SUPER
2x16 GB PC6000 Kingston Fury Beast
(Rollback to 23H2 looks good - at least no BSOD when opening device-manager - but needs more testing)
Same issue here after trying to update to 24H2 using Windows update assistant.
Gigabyte X670 GAMING X AX V2 (F30 BIOS)
WD Blue SN580 2TB (Firmware: 281040WD)
Only 24H2 has this issue. Rolling back to 23H2 resolves it. I have also found similar driver errors in my event viewer:
“The driver detected a controller error on \Device\RaidPort2.”
I have the same issues as described above with my WD SN770 2TB. Got a new PC with windows 11 24H2. The quotes below describe exactly what happens to me.
Windows 11 occasionally freezes up for several seconds then crashes on the login screen after starting up
The crash is preceded by stornvme 11 error with the description “The driver detected a controller error on \Device\RaidPort1.” The crash and restart also happens after I start the pc, so that every time I start twice.
Anyone with BSOD issue, can you please try to disable HMB?
Steps below
Open Registry Editor
Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\StorPort
Set HMBAllocationPolicy to 0. (If there is no HMBAllocationPolicy, create one as DWORD)
Reboot
If system runs stable, I believe you need a repair installation afterwards.
Start Menu → Settings
System → Recovery
Click the repair button to “Use Windows Update to Repair Computer”
If disabling HMB solves the problem, it means WD needs to release a new firmware with correct HMB table. Current HMB table indicates the SSD prefers 200MB system memory as cache. But from the other source, it seems SN770 originally only advertise 64MB HMB.
And, too bad, SN770 datasheet is no longer on WD website. So, we need WD to clarify what is the correct HMB size for SN770.
Can try Phison NVMe Driver 1.5.0.0
or Micron NVMe driver v2.1.19.0 WHQL. Found some old threads and some users reported that this solved the problems with stornvme error.
I can’t test it because I reverted to 23h2.
I installed the Micron NVMe driver v2.1.18.0 WHQL, and things got much better, but I’m still getting a BSOD issue (about 1 in every 30 restarts). The error The driver detected a controller error on \Device\RaidPort1 no longer appears in the event logs, but the system still crashes sometimes.
My PC is new, and I’ve already scheduled an online support session with the supplier. Hopefully, that helps. They will probably replace my SSD with a new one from WD. If that doesn’t fix it, I’m considering refunding the whole computer.
It’s really frustrating to have to revert to Windows 23H2. I haven’t tried it yet, but I just got a new PC, and I can’t even install the latest version of Windows. I’m also seeing other errors and crashes without events, and I’m starting to think everything is just broken.
