Unexpected Store Exception (UNEXPECTED_STORE_EXCEPTION) in Windows 10 or 11: diagnose and fix it safely

If crashes repeat or storage symptoms are present, copy irreplaceable documents, photos, projects, and recovery codes to a different physical drive or a trusted cloud location. Open a few copied files to confirm the backup is readable.

• If Device Encryption or BitLocker is enabled, save the recovery key somewhere separate from this PC. Microsoft explains how to find a BitLocker recovery key.
• Note the exact stop code, date, time, what the PC was doing, and whether the progress counter moved beyond 0%.
• If %SystemRoot%\Minidump exists, preserve copies of the recent .dmp files before cleanup or recovery. Dumps can contain system and memory data, so do not post them publicly.

Press Win + R, enter eventvwr.msc, and open Windows Logs → System. Look at warnings and errors from the minutes around the recorded crash time. One isolated event is weaker evidence than the same storage, controller, device, or driver event repeating beside several crashes.

• Record the source, event ID, time, and full General message; do not delete a file merely because an event names it.
• A Kernel-Power event can confirm that Windows did not shut down cleanly, but it may not identify what caused the crash.
• Compare at least two crashes when possible. Microsoft specifically recommends examining multiple dumps for a repeated pattern.

Disconnect only nonessential hardware added just before the crashes, then restart. Keep the keyboard, mouse, display, and system drive connected. Do not open a laptop or reseat an internal NVMe drive unless the device documentation allows it and you are comfortable doing so.

• Keep roughly 10% to 15% free on the Windows drive; Microsoft includes this range in its consumer stop-code guidance.
• On Windows 11, install available Windows updates. Standard Windows 10 support ended October 14, 2025; an eligible ESU enrollment or an edition with a separate supported lifecycle may still receive applicable updates. Otherwise, plan migration to a supported Windows version rather than assuming a new Windows 10 fix will arrive.
• If the first crash followed a new external device, leave that device disconnected for the comparison test.

Right-click Start → Device Manager. Check for warning icons, then review Disk drives, Storage controllers, and any device that changed when the problem began. The Events and Driver tabs can help connect a device change to the crash timeline.

• Use Windows Update first for recommended drivers. For a model-specific storage or chipset package, use the exact PC, motherboard, or drive manufacturer's official support page.
• If a named driver was updated immediately before the crashes, use Roll Back Driver when that supported option is available.
• Do not use third-party driver-updater sites or uninstall a storage controller at random.

In Windows 11, open Settings → System → Storage → Advanced storage settings → Disks & volumes, select the system disk, and open Properties. Windows 10 uses a similar Manage disks and volumes path on supported builds.

• A critical reliability, spare-capacity, or read-only warning means: back up and seek support.
• Microsoft notes that this built-in health view monitors NVMe SSDs, not SATA SSDs or hard disks. A missing warning therefore is not a clean bill of health for every drive type.
• For a SATA SSD or HDD, identify the exact model in Device Manager and use the manufacturer's official short diagnostic. Firmware updates must match the exact model and should be done only after backup, with stable AC power and vendor instructions.
• If the drive is missing before Windows starts, do not change storage modes or keep rebooting to “test” it. Use hardware support.

Only continue after important files are safe and the drive remains visible and stable. Open Terminal (Admin) or Command Prompt (Admin), then start with the lighter online NTFS scan:

chkdsk C: /scan

• If Windows is installed on another volume, replace C: with its drive letter. Drive letters can differ inside Windows Recovery Environment.
• If no errors are reported, do not escalate to a full-surface scan just because the BSOD mentioned “Store.”
• If file-system errors are reported, confirm the backup, then use chkdsk C: /f. Windows will normally offer to schedule the system-volume repair at restart.
• Do not interrupt a scheduled repair.
• Do not use /r as a routine first fix. It includes repair work and reads every sector; Microsoft notes that repeated full-surface scans can add unnecessary SSD wear.

Microsoft lists System File Checker among the 0x154 checks. Use its documented sequence so SFC has a healthy Windows component source to work from:

1. In an administrator terminal, run DISM.exe /Online /Cleanup-Image /RestoreHealth.
2. Let it finish; DISM may use Windows Update to obtain repair files.
3. Then run sfc /scannow and wait for verification to reach 100%.
4. Restart and use the PC normally.

Search Start for Windows Memory Diagnostic, choose to restart and check, and let the standard test finish. For a recurring problem, press F1 during the test, choose Extended, and press F10 to apply it. The extended test takes longer.

• After Windows returns, check the System log for MemoryDiagnostics-Results.
• A reported hardware error is actionable: return XMP, EXPO, or other memory-overclock settings to the device maker's supported configuration and seek qualified memory service.
• A pass is useful but does not prove that every intermittent memory, motherboard, heat, or power condition is healthy.

Use this branch when the drive evidence is clean and the crash timeline points to an app, service, driver, or Windows change.

• Use Microsoft's Windows Startup Settings to test Safe Mode if normal startup is unstable.
• A clean boot can isolate a non-Microsoft service or startup app. Restore normal startup after the test.
• If the problem began directly after a driver update, prefer the relevant driver's supported rollback. If it began after a wider system change, review Microsoft's recovery options and choose the least destructive match.

For recurring 0x154 crashes, a technician or support team should compare several dumps rather than guess from one filename such as ntoskrnl.exe or MemCompression. Provide the stop-code times, System log events, drive model and health result, Windows version, recent changes, and completed tests.

• Microsoft documents small dumps under %SystemRoot%\Minidump. Keep originals private and share them only with a trusted support channel.
• Driver Verifier is an advanced diagnostic that deliberately stresses drivers and can trigger more crashes. It is not a routine home-user fix.
• Before System Restore, Reset this PC, or reinstalling Windows, confirm the backup and BitLocker key. “Keep my files” still removes apps and settings.
• If the drive health warning is critical or the drive disappears, replace or service the hardware path before reinstalling. Windows installation cannot repair failing hardware.