If your PC is crashing with blue screen errors after installing Windows 11 24H2, and you have a WD Black SN770, WD Blue SN580, WD Blue SN5000, or SanDisk Extreme M.2 NVMe SSD at the 2TB capacity, the cause is a known firmware incompatibility — not a failed drive. Windows 11 24H2 changed the way it allocates system RAM for a storage feature called Host Memory Buffer (HMB), and the original firmware on these specific 2TB models could not handle the new allocation size. The result is random BSODs, boot loops, or a blocked upgrade. Western Digital and SanDisk released a firmware fix in October 2024. Before you replace your SSD, update the firmware using the SanDisk Dashboard. This guide walks through how to confirm your drive is affected, how to apply the update safely, and what to check if instability continues afterward.
Quick Fix Checklist
- Check whether your SSD model and capacity are on the confirmed affected list (2TB models only).
- Back up all important data before proceeding — the firmware update carries a small risk of data loss.
- Make sure the SSD is installed internally — USB adapters are not compatible with the firmware update process.
- Download and install SanDisk Dashboard from the official SanDisk support page.
- Launch SanDisk Dashboard, click UPDATE AVAILABLE or navigate to Tools, then click UPDATE FIRMWARE → PROCEED → SHUTDOWN NOW.
- Power the PC back on to let the firmware apply.
- Retry the Windows 11 24H2 upgrade via Windows Update.
Why the WD SN770 Can Trigger Problems With Windows 11 24H2
The drive itself is not failing. Windows 11 24H2 changed how it allocates Host Memory Buffer (HMB) system RAM, and the original firmware on affected 2TB models could not handle the larger request — causing BSODs, boot loops, or a blocked upgrade. The October 2024 firmware caps HMB allocation at 64MB to restore stable operation.
The WD SN770, SN580, SN5000, and SanDisk Extreme M.2 are DRAM-less NVMe SSDs. Instead of having their own dedicated cache memory, they use a feature called Host Memory Buffer (HMB), which borrows a portion of your PC’s system RAM to handle drive operations. This approach is common in modern budget-to-mid-range NVMe drives and works reliably under normal conditions.
Windows 11 24H2 introduced changes to how it allocates RAM for HMB. According to multiple community reports and technical repair analyses, the updated OS began requesting significantly more HMB than previous Windows versions — far beyond what the affected drives’ firmware was designed to handle. The drive’s internal controller would stall trying to process the oversized allocation, triggering blue screen errors, disappearing from the BIOS in severe cases, or blocking the upgrade entirely when Microsoft’s safeguard systems detected the incompatibility before installation completed.
This is a firmware-level issue specific to affected 2TB models. The problem does not indicate a defective or worn-out drive. Drives that have not yet been updated remain at risk; drives that receive the firmware update have the HMB allocation capped at 64MB, which restores stable operation under 24H2.
First Check: Is Your SSD One of the Affected WD or SanDisk Models?
Only the 2TB versions of the WD_BLACK SN770, SN770M, WD Blue SN580, WD Blue SN5000, and SanDisk Extreme M.2 are reported affected. The same product lines at 1TB or 4TB, and SATA-based WD drives, are not part of this issue. Check your model in System Information or Device Manager before assuming the firmware is the cause.
The confirmed affected models are all 2TB NVMe SSDs from Western Digital and SanDisk. Drives from the same product lines at other capacities — such as 1TB or 4TB — are not reported to be affected by this specific HMB firmware issue. SATA-based WD drives are also a separate category and not part of this problem.
Check your SSD model in one of the following ways:
- Windows: Open Start → System Information → Components → Storage → Disks. Look for the drive model string.
- Device Manager: Expand Disk drives to see the model name.
- Physical label: If accessible, the model number is printed on the SSD itself.
The confirmed affected 2TB models and their corresponding firmware updates are:
| SSD Model | Capacity | Updated Firmware |
|---|---|---|
| WD_BLACK SN770 NVMe SSD | 2TB only | 731130WD |
| WD_BLACK SN770M NVMe SSD | 2TB only | 731130WD |
| WD Blue SN580 NVMe SSD | 2TB only | 281050WD |
| WD Blue SN5000 NVMe SSD | 2TB only | 291020WD |
| SanDisk Extreme M.2 NVMe SSD | 2TB only | 731130WD |
If your drive is not on this list, this particular firmware issue is unlikely to be the cause of your BSOD. See the later section for other checks to try.
For the official confirmed model list and the most current firmware availability, refer to the SanDisk support page covering this issue.
Update the SSD Firmware Before Replacing the Drive
Back up your data first — there is a small risk of loss if the update is interrupted — and confirm the SSD is connected internally, since USB enclosures are not supported. Then run the firmware update through SanDisk Dashboard, which now manages both WD and SanDisk consumer NVMe drives from a single interface.
The firmware update is delivered through SanDisk Dashboard, the official management tool for both SanDisk and WD consumer SSDs. Western Digital’s standalone WD Dashboard has been consolidated into SanDisk Dashboard, which supports WD_BLACK, WD Blue, and SanDisk NVMe drives from a single interface.
Before you begin: Back up all important data. While the firmware update process is designed to be non-destructive, there is a small but real risk of data loss if a power failure or interruption occurs during flashing. Do not skip this step, especially if the SSD is your primary OS drive.
Also confirm the SSD is connected internally. The SanDisk Dashboard firmware update process requires a direct internal M.2 or PCIe connection. If you are trying to update an SSD installed in a USB enclosure or adapter, the update tool will not be able to complete the process.
How to Update the Firmware Using SanDisk Dashboard
- Download SanDisk Dashboard from the official SanDisk support page (online or offline installer available).
- Install and launch SanDisk Dashboard. Your WD or SanDisk NVMe SSD should appear automatically.
- If a firmware update is available, the dashboard will show an UPDATE AVAILABLE notification on the main screen. You can also navigate to Tools to check the firmware update view manually.
- Click UPDATE FIRMWARE.
- Click PROCEED to confirm.
- Click SHUTDOWN NOW. The PC will power off.
- Power the PC back on. The firmware applies during this boot cycle.
- Once Windows loads, reopen SanDisk Dashboard to confirm the firmware version has updated to the target build listed in the table above.
After the update completes, open Settings → Windows Update and check for the 24H2 upgrade again. In most cases, the safeguard hold placed by Microsoft lifts once the updated firmware is detected, and the upgrade will proceed normally.
According to multiple community reports from users who went through this process, the upgrade completed without further issues after the firmware was updated. Community reports confirm that SanDisk Dashboard shows HMB allocation reduced to 64MB after the update, indicating the firmware workaround is in effect. Related Overclockers UK discussion / Related Windows Forum discussion
What to Do If Windows 11 24H2 Still Fails or BSODs After the Firmware Update
If you have applied the firmware update and are still seeing crashes or upgrade failures, the SSD firmware alone may not be the only factor. Work through the following checks before assuming the drive is defective or that hardware replacement is needed.
Verify the Firmware Version in SanDisk Dashboard
Reopen SanDisk Dashboard and confirm that the firmware version shown under Drive Details matches the updated version for your model (for example, 731130WD for the SN770). If the version did not change, the update may not have applied correctly. Try launching Dashboard with administrator privileges and repeating the update.
Check Windows Update for Pending Cumulative Updates
Open Settings → Windows Update and install any pending cumulative updates before retrying the 24H2 feature update. Some post-24H2 cumulative updates include additional stability improvements that can address edge-case instability not covered by the firmware update alone.
Review Event Viewer for Specific Error Codes
Open Event Viewer → Windows Logs → System and filter for critical errors around the time of the BSOD. Look for entries from stornvme or errors referencing DeviceRaidPort. If these errors are present, they point to the NVMe storage stack and suggest the storage firmware or driver interaction is still a factor. If errors point elsewhere — graphics, audio, or kernel memory — the cause may be unrelated to the SSD.
Update Chipset and NVMe Drivers
Outdated chipset drivers or NVMe controller drivers can independently cause storage instability. Check your motherboard or laptop manufacturer’s support page for the latest chipset package. For Intel systems, the Intel Driver & Support Assistant can help identify outdated packages. For AMD systems, check AMD’s Chipset Software page directly.
Run Windows Memory Diagnostic
Because HMB borrows system RAM, a RAM issue can interact with HMB-related instability. Open Start → Windows Memory Diagnostic and run a standard memory test to rule out a RAM fault as a contributing factor.
When You Should Pause the 24H2 Upgrade or Consider a Different SSD
For most users with an affected 2TB WD or SanDisk NVMe SSD, applying the firmware update resolves the problem. However, there are specific situations where it makes sense to wait or evaluate alternatives before proceeding.
If You Cannot Back Up Data Before Updating
The firmware update carries a small risk of data loss in the event of interruption. If you are unable to create a verified backup of your data before updating, do not proceed with the firmware update. Pause the 24H2 upgrade until you have a backup in place. This is not an unusual precaution — it applies to any firmware update process across any manufacturer.
If Windows 11 24H2 Is Not Yet Being Offered to Your Device
Microsoft uses safeguard holds to delay the 24H2 upgrade on systems where compatibility issues are detected. If your system has not been offered 24H2 via Windows Update and you have an affected SSD, the hold is likely still active for your device. Update the firmware first, then wait for Windows Update to offer the upgrade. Do not use the Installation Assistant or Media Creation Tool to manually force the upgrade while a safeguard hold is in effect — Microsoft’s own guidance on active holds recommends against this.
If Your System Is Mission-Critical and Timing Is a Concern
If you rely on the PC for work or cannot risk any downtime, it is reasonable to defer the 24H2 upgrade until you have a confirmed backup, a scheduled maintenance window, and a tested recovery path. Windows 11 23H2 remains supported; there is no immediate security risk in staying on a prior version while resolving this compatibility issue.
If Instability Continues After All Checks
If you have updated the firmware, verified the version, applied all pending updates, and the system continues to BSOD or show storage errors, contact Western Digital or SanDisk support directly. In rare cases, a drive that has already experienced firmware-related corruption may require a replacement or professional data recovery assessment. Do not attempt to use unofficial firmware files, third-party flashing tools, or registry-based HMB workarounds that circulated before the official firmware patch was released.
How We Researched
This article is based on official SanDisk and Western Digital support documentation, including the published firmware update notice covering the HMB-related BSOD issue on Windows 11 24H2. Additional sourcing includes reporting from Tom’s Hardware and The Register, both of which covered WD’s acknowledgment of the issue and the firmware release. Community reports from Overclockers UK forums and Windows Forum were reviewed and cross-referenced to confirm the affected model list, symptom patterns, and post-update behavior. We have not conducted hands-on lab testing. Firmware version numbers and affected model details are attributed to official sources and clearly identified community reports. All claims about Microsoft’s safeguard hold behavior are based on reporting from Neowin and Windows Forum, which covered the block in detail as of mid-2025.
Frequently Asked Questions
Does the WD SN770 need a firmware update for Windows 11 24H2?
For the affected 2TB models, yes. The original firmware cannot handle 24H2’s larger HMB allocation, so updating through SanDisk Dashboard before upgrading is the recommended fix. The same product lines at other capacities are not reported to be affected by this specific issue.
Can the WD SN770 cause a BSOD on Windows 11 24H2?
Yes, on affected 2TB drives. The HMB allocation conflict introduced by 24H2 can trigger random blue screens, boot loops, or a blocked upgrade. This points to a firmware issue rather than a failed drive, and the October 2024 firmware update is designed to resolve it.
Should I update my SSD firmware before upgrading to 24H2?
For affected 2TB WD or SanDisk drives, update the firmware first. In most reported cases, Microsoft’s safeguard hold lifts once the updated firmware is detected, and the 24H2 upgrade then proceeds normally through Windows Update.
What should I do before updating SSD firmware?
Back up all important data first — there is a small risk of loss if power is interrupted during flashing — and make sure the SSD is connected internally. USB enclosures and adapters are not supported for the firmware update process.
Conclusion
A BSOD or upgrade block on Windows 11 24H2 with a WD or SanDisk NVMe SSD is almost certainly a firmware issue, not a sign that your drive needs to be replaced. The root cause is an HMB allocation conflict introduced by 24H2 that specifically affects five 2TB NVMe models from Western Digital and SanDisk. The official resolution — a firmware update delivered through SanDisk Dashboard — has been confirmed to restore stability in the majority of reported cases. Back up your data, verify your model is on the affected list, and apply the update before drawing any conclusions about the drive’s health.
