Fixes / Windows · Checked

Windows UNEXPECTED_STORE_EXCEPTION: what it means and how to fix it

Short answer

UNEXPECTED_STORE_EXCEPTION (bug check 0x154) means the Windows kernel memory store, which moves memory pages to and from your drive, hit an error it could not handle. The most common cause is a failing or badly connected SSD or hard drive. Check the drive's health, run chkdsk C: /f /r, update the SSD firmware and storage driver, then test your RAM.

What this message means

Windows compresses some memory and moves it between RAM and the page file on your system drive. The part of the kernel that manages this is the "store". Microsoft documents stop code 0x154 as this store component catching an exception it did not expect, so Windows halts to protect your data. In practice the exception almost always happens because a read from the drive failed or returned bad data. That points to a dying SSD or hard drive, a loose cable, outdated SSD firmware or storage driver, faulty RAM, or a third-party antivirus driver interfering with disk access. One crash after an update can be a one-off. Repeated crashes mean hardware should be checked first.

Common causes

CauseHow to tell
Failing or worn-out SSD or hard driveCrashes come with freezes, slow boots or file copy errors. The drive shows "Warning" or a low "Estimated remaining life" in Settings > System > Storage > Advanced storage settings > Disks & volumes > Properties (Windows 11), or chkdsk reports bad sectors. Event Viewer's System log shows disk, Ntfs or storahci/stornvme errors (Event ID 7, 51, 129 or 153) just before the crash.
Loose or faulty drive connection (SATA cable, M.2 seating, external enclosure)Crashes started after the PC was moved, opened or knocked, or the drive sometimes disappears from File Explorer or the BIOS. Common on desktops and on laptops after a repair or upgrade.
Outdated SSD firmware or storage controller driver (Intel RST, AMD SATA/NVMe, vendor NVMe drivers)The drive tests healthy, but crashes happen under heavy disk load or when waking from sleep. The SSD maker's tool (Samsung Magician, Crucial Storage Executive, WD Dashboard and so on) shows a firmware update available.
Faulty or unstable RAM, including XMP/EXPO overclockYou also see other stop codes such as MEMORY_MANAGEMENT or PAGE_FAULT_IN_NONPAGED_AREA, and Windows Memory Diagnostic or MemTest86 reports errors. Crashes stop when XMP/EXPO is turned off in the BIOS.
Third-party antivirus or disk utility driverCrashes began after installing or updating antivirus, encryption, backup or disk caching software. The crash dump or a tool like WhoCrashed or BlueScreenView names a driver from that product.
Corrupted system files or a problem left by Fast StartupThe crash tends to happen right after turning the PC on (not after a restart), or sfc /scannow reports corrupted files it repaired.

How to fix it

1. Check the drive's health

  1. Windows 11: open Settings > System > Storage > Advanced storage settings > Disks & volumes, select your system drive and click Properties. Look at Drive health (shown for NVMe SSDs).
  2. On any version, right-click Start, choose Terminal (Admin) or Windows PowerShell (Admin), and run: Get-PhysicalDisk | Select FriendlyName, MediaType, HealthStatus, OperationalStatus
  3. Anything other than Healthy / OK means the drive is failing. Back up your files immediately.
  4. For more detail, install the drive maker's tool or the free CrystalDiskInfo and check for Caution or Bad status, reallocated sectors or low remaining life.
  5. If the drive is failing, replace it. None of the software fixes below will stop the crashes.

2. Run chkdsk to find and fix disk errors

  1. Right-click Start and choose Terminal (Admin) (Windows 11) or Windows PowerShell (Admin) (Windows 10).
  2. Type chkdsk C: /f /r and press Enter.
  3. When asked to schedule the check for the next restart, type Y and press Enter.
  4. Restart the PC and let the scan finish. It can take an hour or more on large hard drives.
  5. To see the result afterwards, open Event Viewer (Win+R, eventvwr.msc), go to Windows Logs > Application and filter for source Wininit.

3. Update SSD firmware, storage drivers and Windows

  1. Install your SSD maker's utility and apply any firmware update. Back up first.
  2. Right-click Start > Device Manager. Expand Storage controllers and Disk drives and look for any device with a yellow exclamation mark.
  3. Get the latest storage/chipset driver (Intel RST, AMD chipset) from your PC or motherboard maker's support page, not a driver-updater app.
  4. Windows 11: Settings > Windows Update > Check for updates. Windows 10: Settings > Update & Security > Windows Update > Check for updates. Install optional driver updates too.
  5. Restart and see if the crashes stop.

4. Repair system files with DISM and SFC

  1. Open Terminal (Admin) or Command Prompt as administrator.
  2. Run DISM.exe /Online /Cleanup-image /Restorehealth and wait for it to finish.
  3. Then run sfc /scannow and do not close the window until it reaches 100%.
  4. Restart the PC. If SFC could not fix some files, run it again in Safe Mode.

5. Turn off Fast Startup and remove conflicting software

  1. Open Control Panel > Hardware and Sound > Power Options > Choose what the power buttons do.
  2. Click Change settings that are currently unavailable, untick Turn on fast startup, and click Save changes.
  3. If you use third-party antivirus, disk encryption or disk caching software, uninstall it from Settings > Apps > Installed apps (Windows 11) or Settings > Apps > Apps & features (Windows 10). Microsoft Defender turns on automatically.
  4. If crashes began after a Windows update, uninstall it: Windows 11 Settings > Windows Update > Update history > Uninstall updates; Windows 10 Settings > Update & Security > Windows Update > View update history > Uninstall updates.

6. Test RAM and reseat hardware

  1. Press Start, type Windows Memory Diagnostic, open it and choose Restart now and check for problems.
  2. For a deeper test, press F1 during the test, set Test Mix to Extended and press F10. MemTest86 from a USB stick is more thorough.
  3. If you enabled XMP/EXPO in the BIOS, turn it off and see if the crashes stop.
  4. On a desktop, shut down, unplug the power, then reseat the RAM sticks and the drive's SATA data and power cables or M.2 module. Try a different SATA cable and port.
  5. If one RAM stick fails testing, remove it and run on the rest until it is replaced.

Next time, skip the search

Crade is an AI assistant for Mac and Windows that sees your screen. When a message like this pops up, ask “what does this mean?” and it explains the exact error in front of you, step by step.

Download Crade

Still not fixed?

If the crashes continue, open Event Viewer (Win+R, eventvwr.msc) > Windows Logs > System and look for critical or disk errors at the time of each crash. Upload the minidump files in C:\Windows\Minidump to a Microsoft Q&A or Ten Forums post and ask for an analysis, as the dump usually names the driver or device involved. If Windows won't boot far enough, hold Shift while clicking Restart (or let it fail to boot twice) to reach the recovery screen, then use Troubleshoot > Advanced options > System Restore or Startup Settings > Safe Mode. If the PC is under warranty, contact the manufacturer with your drive and memory test results, since this error is usually a hardware fault. As a last resort, back up your data and use Settings > System > Recovery > Reset this PC.

Questions people ask

Does UNEXPECTED_STORE_EXCEPTION mean my SSD is dying?

Often, but not always. A failing or badly connected drive is the most common cause, so check drive health first. If the drive is healthy, look at SSD firmware, storage drivers, RAM and antivirus software.

Is it related to the Microsoft Store?

No. The "store" here is the part of the Windows kernel that manages compressed memory and paging to disk. Resetting or reinstalling the Microsoft Store app will not fix it.

What is stop code 0x00000154?

It is the numeric code for UNEXPECTED_STORE_EXCEPTION. Microsoft describes it as the kernel memory store component catching an unexpected exception.

Why is my screen black instead of blue?

Starting with Windows 11 version 24H2, stop errors appear on a black screen instead of a blue one. The stop code and fixes are the same.

Can I fix it without reinstalling Windows?

Usually, yes. Most cases are fixed by replacing a failing drive, reseating cables, updating firmware or drivers, or removing conflicting software. A clean install won't help if the hardware is at fault.

Sources

Related errors