UNEXPECTED_STORE_EXCEPTION (stop code 0x154) is Windows 11’s memory manager catching corrupted data coming out of its storage layer — the component that handles compressed memory and paging to disk. The name is obscure; the meaning is not: your SSD or your RAM is feeding Windows bad data. UNEXPECTED_STORE_EXCEPTION (stop code 0x154) is Windows 11’s memory manager catching corrupted data coming out of its storage layer — the component that handles compressed memory and paging to disk. The name is obscure; the meaning is not: your SSD or your RAM is feeding Windows bad data.

The whole troubleshooting challenge is figuring out which one. This guide runs that diagnostic in the right order, with the backup-first discipline a potential drive failure demands. The whole troubleshooting challenge is figuring out which one. This guide runs that diagnostic in the right order, with the backup-first discipline a potential drive failure demands.

Why this happens

  • Failing SSD. The most common cause — bad flash returns corrupted pages to the store.
  • Faulty RAM. Corrupts stored pages in memory before they are even written.
  • Corrupted page file or storage drivers. Damage in the paging path itself.
  • Antivirus filter drivers. Bugs in the filter layer corrupt data between disk and store.
  • Failing storage controller or cable. On laptops, usually the controller or a loose M.2 seating.
  • Windows 11 storage driver bugs. Occasional bad storport/storahci updates cause store exceptions.

How to fix it

Work through these in order, from the quickest and most likely fixes to the deeper ones. Stop as soon as the crashes stop.

Fix 1: Back up immediately

A potential drive failure means the backup comes before the diagnosis. A potential drive failure means the backup comes before the diagnosis — every hour of use on a dying drive risks more data.

  1. Copy important files to external storage or cloud right now.
  2. If crashes interrupt the copy, boot into Safe Mode — less disk activity, fewer crashes — using our Safe Mode guide .
  3. Do not run intensive diagnostics before the backup is safe.

Fix 2: Check SSD health thoroughly

The highest-probability cause gets the first real test. The highest-probability cause gets the first real test — and the maker’s SMART toolbox tells you far more than the basic status command.

  1. Run wmic diskdrive get status in an elevated Terminal — anything but OK is decisive.
  2. Install your SSD maker’s toolbox (Samsung Magician, WD Dashboard, Crucial Storage Executive, Intel MAS) and read the full SMART data: media wear, reallocated sectors, CRC errors.
  3. Health below 80%, growing reallocated sectors, or interface CRC errors mean replace the drive — back up and clone immediately.

Fix 3: Run CHKDSK on the system drive

Catches file-system-level corruption feeding the store bad data. Catches file-system-level corruption feeding the store bad data — but growing bad-sector counts still mean the drive is dying regardless.

  1. In an elevated Terminal, run chkdsk C: /f /r.
  2. Press Y to schedule at restart, then reboot and let the full scan complete — it can take over an hour.
  3. If chkdsk finds and repairs bad sectors, retest for several days; growing bad-sector counts still mean the drive is dying.

Fix 4: Test the RAM

The other half of the storage-vs-memory question. The other half of the storage-vs-memory question — store exceptions from RAM are often intermittent, which is why the overnight test matters.

  1. Press Win + R, type mdsched.exe, and press Enter.
  2. Choose Restart now and check for problems.
  3. If clean, run MemTest86 overnight for certainty — store exceptions from RAM are often intermittent. Our memory troubleshooting walkthrough covers RAM isolation in depth.

Fix 5: Update storage drivers and firmware

The software layer between Windows and the disk. The software layer between Windows and the disk — SSD firmware updates have fixed store-exception bugs more than once.

  1. Update chipset and storage controller drivers from your laptop maker’s support site.
  2. Check the SSD maker’s toolbox for firmware updates — several vendors fixed store-exception-causing firmware bugs.
  3. Install pending Windows 11 cumulative updates, which include storport fixes. If crashes began right after a storage driver update, roll it back in Device Manager.

Fix 6: Clean-boot to isolate filter drivers

Catches the antivirus and encryption filter drivers that corrupt the data path. Catches the antivirus and encryption filter drivers that corrupt the data path — the clean boot isolates them by elimination.

  1. Run msconfig, hide all Microsoft services, Disable all; disable startup items in Task Manager; restart.
  2. If stable, re-enable in halves. Antivirus products are the prime suspects here — clean-reinstall or temporarily replace with Windows Security to test.
  3. Also temporarily disable third-party disk encryption if you use any.

Fix 7: Reseat the drive and consider replacement

The hardware endgame. The hardware endgame — reseat the drive if you are comfortable opening the machine, replace it if SMART says it is dying.

  1. If comfortable opening the laptop: power off, disconnect battery if possible, reseat the M.2 SSD firmly, and reboot — loose seating causes intermittent store errors.
  2. If the drive is failing SMART, replace it: clone with Macrium Reflect or do a clean Windows install from the Windows 11 download page .
  3. Persistent 0x154 with a healthy drive and clean RAM points at the motherboard’s storage controller — professional repair territory.

Fix 8: Test with a different SATA/NVMe driver mode

On some laptops the storage controller driver itself corrupts the data path — switching between RAID/IRST and AHCI/NVMe modes in the BIOS is a legitimate diagnostic.

  1. Enter BIOS/UEFI and find the storage controller mode (often under Advanced > SATA/NVMe configuration).
  2. Note the current setting, then switch it (RAID to AHCI or vice versa) — warning: Windows may not boot after the switch without preparation, so only do this if you have installation media handy.
  3. If you cannot risk the boot issue, instead update or roll back the storage controller driver in Device Manager under Storage controllers.
  4. A mode or driver change that stops the exceptions proves the controller path was the problem, not the drive media.

Closing

UNEXPECTED_STORE_EXCEPTION is a ‘your data path is corrupt’ warning, and on Windows 11 laptops the SSD is guilty more often than not. Back up first, check the drive’s SMART health honestly, test the RAM, and you will have your answer — usually within an evening. When the drive is dying, speed matters more than thoroughness — back up, confirm with SMART, and replace. Everything else is for the cases where the drive is innocent.

Frequently asked questions

What is the 'store' in UNEXPECTED_STORE_EXCEPTION?
The memory manager’s store — the component that manages compressed memory pages and the page file backing them. Stop code 0x154 fires when the store hits an unexpected condition, which in practice means the data it read from disk or RAM was corrupted. It is a storage-or-memory error wearing a cryptic name.
Is this error caused by the SSD or the RAM?
Either — that is the central diagnostic question. SSDs are the more common cause on Windows 11 laptops (the store reads from disk constantly), but RAM faults produce identical crashes. The troubleshooting below separates them: drive health checks first, then memory tests.
Can antivirus cause UNEXPECTED_STORE_EXCEPTION?
Yes — antivirus filter drivers sit between the store and the disk, and their bugs corrupt the data path. It is less common than hardware causes, but if your drive and RAM test clean, the AV filter driver is the next suspect. A clean boot isolates it.
Will I lose data if my SSD is causing this?
Possibly, which is why backing up is step one. A failing SSD can corrupt files silently before the crashes even start. Back up now, diagnose second — if the drive is dying, every hour of use risks more data.