UNEXPECTED_STORE_EXCEPTION (stop code 0x154) means Windows’ kernel memory store component caught an unexpected exception—most often when reading compressed memory pages or pagefile data back from an NVMe or SATA drive, or when unstable RAM corrupts compressed store pages. Back up critical files first, check SMART media errors and event IDs 129/153/51 in Event Viewer, turn off PCIe Link State Power Management and Fast Startup, reseat the M.2 drive and update its firmware, and test XMP/EXPO off before replacing storage.
At a glance
- Applies to
- Windows 11 and Windows 10, stop code 0x00000154
- Before anything
- Back up irreplaceable files before chkdsk or heavy stress tests
- No minidump?
- Classic clue that the boot NVMe drive dropped offline at crash time
- Top non-failing causes
- PCIe ASPM link sleep, loose/hot M.2 drive, outdated SSD firmware, unstable XMP/EXPO
Provenance
- Nov 21, 2026Published
First, clear up the misleading name: UNEXPECTED_STORE_EXCEPTION (0x00000154) has nothing to do with the Microsoft Store app.
According to Microsoft’s 0x154 reference, the “store” is Windows’ kernel memory store manager—the subsystem that compresses background RAM pages and shuttles pagefile data to and from your boot SSD. When an NVMe drive momentarily drops off the PCIe bus, returns garbled bytes, or an unstable memory profile corrupts a compressed page so decompression throws an exception (Parameter 2), Windows halts immediately with 0x154.
Before touching anything: copy irreplaceable files off the PC
Because 0x154 is one of the primary early-warning signs of a failing NVMe or SATA boot drive, copy your documents, photos, SSH/crypto keys, and project folders to an external drive or cloud folder before running chkdsk or stress tests. If the drive is healthy and the culprit turns out to be a Windows power setting, the backup cost you ten minutes; if the SSD controller dies mid-test, it saved your data.
Step 1. Check Event Viewer & SMART to separate storage dropouts from RAM
1. Look for the volmgr / stornvme smoking gun in Event Viewer
Press Win + R, run eventvwr.msc, open Windows Logs > System, and inspect the 60 seconds leading up to the crash:
| Event Source & ID | What it means |
|---|---|
stornvme Event 129 (Reset to device, \Device\RaidPort0, was issued) or disk Event 153 / 51 | Your NVMe or SATA drive timed out on an I/O request right before the blue screen. Storage path (Steps 2–3) is confirmed |
volmgr Event 161 or 46 (Dump file creation failed due to error during dump creation) + empty C:\Windows\Minidump | Your boot drive vanished completely during the crash, so Windows couldn’t even write the .dmp file (or booted straight into BIOS once before reappearing after a full power-off) |
Clean storage logs + C:\Windows\Minidump wrote a dump cleanly | The drive stayed online; compressed-memory corruption in RAM (Step 4) or damaged OS files (Step 5) moves up the list |
2. Read the drive’s actual SMART counters (2 minutes)
Check every internal drive using CrystalDiskInfo or the built-in steps in our SSD health check guide (and hard drive health check if your page file sits on a spinning disk). Focus on Microsoft’s NVME_HEALTH_INFO_LOG failure counters, not just the overall percentage:
Critical Warningnon-zero orAvailable Sparebelow threshold: the drive itself is flagging imminent failure—skip straight to replacing it.0E — Media and Data Integrity Errorsabove0(especially climbing between reboots): unrecoverable NAND read errors directly trigger0x154when they hitpagefile.sysor system binaries.- High drive temperature (
70°C+) during gaming: an M.2 SSD cooked underneath a 250–360W graphics card without a heatsink can controller-throttle or drop off the PCIe bus mid-game—see our M.2 SSD heatsink guide.
Step 2. Stop healthy NVMe drives from dropping offline (ASPM, Fast Startup & Firmware)
If SMART shows 0 Media Errors and healthy spare blocks, your SSD may be fine—modern PCIe 4.0 and 5.0 drives frequently throw 0x154 (stornvme 129) when Windows puts the PCIe link into a deep low-power state and the controller wakes a few milliseconds too late:
- Disable PCIe Link State Power Management: press
Win + R->powercfg.cpl-> Change plan settings -> Change advanced power settings -> PCI Express > Link State Power Management -> set to Off and click Apply. - Disable Windows Fast Startup: in
powercfg.cpl-> Choose what the power buttons do -> Change settings that are currently unavailable -> uncheck Turn on fast startup so stale storage-controller states aren’t reloaded fromhiberfil.sys. - Update SSD firmware in the maker’s official utility: open Samsung Magician, SanDisk/WD Dashboard, Crucial Storage Executive, Kingston SSD Manager, or Solidigm Storage Tool. Controller hangs under Windows 11
stornvmeare routinely patched via two-minute non-destructive firmware updates (still back up first!).
Step 3. Reseat the M.2 SSD (or swap SATA cables)
Thermal expansion across dozens of gaming heat cycles can creep an M.2 card slightly in its edge connector—especially on tool-less plastic motherboard latches or bent standoffs:
- Shut down, flip the PSU switch off, and unplug AC power.
- Remove the M.2 heatsink, release the M.2 latch/screw, pull the SSD out at a 30-degree angle, inspect the gold fingers for dust or thermal-pad silicone oil, and re-insert it firmly until the gold contacts disappear evenly before fastening it flat (never angled down without a standoff!).
- Check the thermal pad contact while the cover is off: peel any forgotten protective film and confirm the pad actually touches the controller chip near the M.2 notch.
Step 4. Test for compressed-RAM corruption (turn XMP/EXPO off)
Windows 10 and 11 compress cold memory pages in RAM (Memory Compression under the System process) instead of writing every page straight to disk. If an aggressive DDR5 XMP or EXPO overclock flips a single bit inside a compressed store page, the decompression checksum fails and throws 0x154—even on a brand-new SSD!
- Enter BIOS and set XMP / EXPO to Disabled (
Auto/ JEDEC) for 48 hours of normal use (XMP/EXPO guide). - Or run Windows Memory Diagnostic (
mdsched.exefrom Start search -> pressF1on reboot to select the Extended test mix, as Microsoft’s0x154guide recommends) or PassMark MemTest86—and follow ourMEMORY_MANAGEMENT(0x1A) isolation matrix if errors appear.
Step 5. Repair Windows system files (DISM & SFC)
Once storage dropouts or memory errors are resolved, repair any damaged OS binaries from an elevated Terminal (Admin):
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
Only run chkdsk C: /f if NTFS file-system errors (Ntfs Event ID 55) appear in Event Viewer and SMART shows zero rising media errors. If 0x154 alternates with 0xEF, check Fix CRITICAL_PROCESS_DIED as well.
If SMART confirms your boot SSD is failing
When Media and Data Integrity Errors (0E) are climbing, Critical Warning is tripped, or the drive keeps vanishing into BIOS across two different M.2 slots with ASPM off, retire the drive before it locks into read-only mode or stops detecting altogether.
Check current daily 2TB NVMe observations on our SSD Price Index and datasheet grades on the SSD Tier List. In our November 20, 2026 Newegg affiliate catalogue capture, the WD_BLACK SN7100 2TB (WDS200T4X0E, PCIe 4.0 TLC NAND) was $329.99 under Newegg item N82E16820250275 ($50 above the QLC WD Blue SN5100 2TB at $279.99, and well suited as a primary OS boot drive).
I may earn a commission if you buy through these affiliate links. As an Amazon Associate I earn from qualifying purchases.
Search AmazonLink checked 2026-11-20 Check NeweggLink checked 2026-11-20Frequently asked questions
Does UNEXPECTED_STORE_EXCEPTION mean Windows Store (Microsoft Store) is broken?
Why didn’t Windows save a minidump file in C:\Windows\Minidump after 0x154?
Does 0x154 prove my SSD is dying?
Should I run chkdsk /r right away for UNEXPECTED_STORE_EXCEPTION?
Why do UNEXPECTED_STORE_EXCEPTION and CRITICAL_PROCESS_DIED appear together?
Sources and corrections
- Last updated
- Methodology
- See our methodology for research and review standards. It draws on 5 cited sources, listed below, each checked against the original page on the date above. Bug-check parameters (Parameter 1 store context pointer, Parameter 2 exception record) and built-in Windows troubleshooting steps come from Microsoft Learn’s Bug Check 0x154 reference opened November 21, 2026 (UTC), paired with Microsoft’s NVMe health log documentation, Event ID 41 guide and System File Checker page. The optional replacement SSD price at the bottom comes from TechFuelHQ’s cached November 20, 2026 Newegg affiliate catalogue (N82E16820250275).
- Sources
- Microsoft Learn: Bug Check 0x154 UNEXPECTED_STORE_EXCEPTION accessed 2026-11-21
- Microsoft Learn: NVME_HEALTH_INFO_LOG structure (MediaErrors, AvailableSpare, CriticalWarning) accessed 2026-11-21
- Microsoft Learn: Event ID 41 when the system restarts unexpectedly accessed 2026-11-21
- Microsoft Support: Using System File Checker in Windows accessed 2026-11-21
- SanDisk / Western Digital: WD_BLACK SN7100 NVMe SSD Datasheet accessed 2026-11-21
- Corrections
- Spotted an error? Email a correction with the affected line and what you found. The draft includes this page’s address. Verified changes are recorded here. Contact details.