The UNEXPECTED_STORE_EXCEPTION error is a Windows stop-code or Blue Screen of Death (BSOD) error that can cause a computer to suddenly crash and restart. It may appear while Windows is starting, during normal use, after waking from sleep, while running demanding applications, or seemingly at random.

A typical message may display:

Stop code: UNEXPECTED_STORE_EXCEPTION

The corresponding Windows bug check is:

0x00000154

Despite the word "STORE", this error does not refer to the Microsoft Store application. Microsoft defines bug check 0x154 as a condition in which the kernel memory store component caught an unexpected exception.

The error can involve several underlying areas, including storage devices, storage-controller drivers, memory, corrupted system files, firmware, or other hardware/driver problems. For that reason, replacing the SSD immediately is not always the correct first step.

This guide explains how to systematically diagnose and fix UNEXPECTED_STORE_EXCEPTION in Windows 11 and Windows 10.

What Is UNEXPECTED_STORE_EXCEPTION?

UNEXPECTED_STORE_EXCEPTION is Windows bug check 0x00000154.

According to Microsoft's documentation, the bug check indicates that the kernel memory store component encountered an unexpected exception. The first bug-check parameter points to the store context or data manager, while the second contains exception information.

For an end user or IT engineer, the important point is that the BSOD itself does not automatically identify the defective component.

You need to investigate what Windows was doing when the exception occurred.

Common Symptoms

A computer experiencing this problem may show one or more of the following symptoms:

• Sudden BSOD followed by an automatic restart
• Stop code UNEXPECTED_STORE_EXCEPTION
• Random freezing before the BSOD
• Crashes shortly after Windows starts
• Crashes when the computer is under heavy load
• BSOD after waking from sleep or hibernation
• Slow or unresponsive storage before the crash
• Applications freezing before Windows crashes
• Repeated disk-related errors in Event Viewer
• Windows becoming temporarily unresponsive
• BSOD occurring during large file operations
• System instability after installing a driver or Windows update

A single occurrence does not necessarily mean the SSD or HDD is failing. Repeated occurrences, however, should be investigated.

What Causes UNEXPECTED_STORE_EXCEPTION?

There is no single universal cause.

Microsoft notes that Windows stop-code errors can originate from hardware devices, drivers, or software.

For UNEXPECTED_STORE_EXCEPTION specifically, important areas to investigate include the following.

1. SSD, HDD or NVMe Problems

Storage problems deserve particular attention when troubleshooting this stop code.

Possible issues include:

• Failing SSD
• Failing HDD
• NVMe instability
• Storage-controller problems
• File-system corruption
• Disk I/O errors
• Firmware problems
• Loose SATA cable
• SATA power connection problems
• Motherboard storage-controller problems

Do not assume that an SSD is healthy simply because Windows still boots.

2. Storage Controller or Device Driver Problems

Windows depends on drivers to communicate correctly with storage hardware.

Potentially relevant components can include:

• SATA/AHCI controllers
• NVMe controllers
• Intel storage drivers
• AMD chipset/storage components
• Microsoft storage drivers
• RAID controllers
• Manufacturer-specific NVMe drivers

A corrupted, incompatible or unstable driver can contribute to storage I/O problems and system crashes.

3. RAM Problems

UNEXPECTED_STORE_EXCEPTION can also appear in situations involving memory corruption or instability.

Possible causes include:

• Defective RAM
• Incorrect memory timings
• Unstable XMP/EXPO settings
• Overclocking
• Poor RAM contact
• Motherboard memory-slot problems
• Mixed or incompatible RAM modules

Microsoft specifically recommends Windows Memory Diagnostic as one troubleshooting option for bug check 0x154.

4. Corrupted Windows System Files

Damage to protected Windows files or the Windows component store can cause unpredictable operating-system behavior.

Possible reasons include:

• Interrupted Windows updates
• Improper shutdown
• Disk corruption
• Malware
• Storage errors
• Failed upgrades
• Third-party system utilities

Windows includes DISM and System File Checker tools that can help repair Windows components and protected system files.

5. BIOS, UEFI or Firmware Problems

Older firmware can sometimes create compatibility or stability problems with:

• NVMe SSDs
• SATA controllers
• CPU power management
• RAM
• PCIe devices

Firmware should therefore be considered when repeated BSODs remain unexplained.

However, BIOS updates should be performed carefully. Use firmware intended specifically for the exact computer or motherboard model and avoid interrupting the update.

6. Recently Installed Hardware

If the problem began immediately after installing new hardware, consider the new component a major troubleshooting clue.

Examples include:

• RAM
• SSD
• NVMe drive
• Graphics card
• PCIe expansion card
• USB hardware

Microsoft recommends removing recently added hardware when investigating recurring Windows stop-code errors.

7. Insufficient Free Disk Space

Extremely low free space can interfere with normal Windows operation, paging, updates and temporary-file operations.

Microsoft's general stop-code troubleshooting guidance recommends checking that sufficient disk space is available.

Avoid running the Windows system drive continuously at or near 100% capacity.

Step-by-Step Troubleshooting

Step 1: Back Up Important Data

If UNEXPECTED_STORE_EXCEPTION happens repeatedly, particularly when accompanied by disk warnings, freezing or slow storage access, back up important files before performing extensive troubleshooting.

Copy critical data to:

• External HDD/SSD
• NAS
• File server
• Cloud storage
• Another computer

If a drive is physically failing, continuing intensive testing can sometimes make data recovery more difficult.

Step 2: Disconnect Recently Installed Hardware

If the BSOD started after installing hardware, temporarily remove it where practical.

Test the computer again.

If the crashes stop, investigate:

• Hardware compatibility
• Drivers
• Firmware
• Power requirements
• BIOS settings

Microsoft includes removing newly added hardware among its basic stop-code troubleshooting steps.

Step 3: Check Device Manager

Press:

Windows + X → Device Manager

Look for:

• Yellow warning symbols
• Unknown devices
• Storage-controller errors
• Driver failures

Pay particular attention to:

Disk drives

Storage controllers

IDE ATA/ATAPI controllers

System devices

Also check the Events section of suspicious device properties.

Microsoft specifically recommends checking Device Manager for devices showing an exclamation mark when troubleshooting stop errors.

Step 4: Check Event Viewer

Event Viewer can provide important clues about what happened immediately before the crash.

Press:

Windows + R

Enter:

eventvwr.msc

Press Enter.

Navigate to:

Windows Logs → System

Look for Critical and Error events around the exact time of the BSOD.

Pay particular attention to events involving:

• Disk
• Storage
• NTFS
• StorAHCI
• NVMe
• Controller errors
• Unexpected shutdowns
• Hardware errors

Microsoft specifically recommends examining the System log for errors occurring around the time of bug check 0x154.

Do not assume that every red error in Event Viewer caused the BSOD. Correlate the event's timestamp with the actual crash.

Step 5: Check the Health of the SSD or HDD

Check the system drive and any other drive involved in the crash.

For an SSD or NVMe drive, preferably use the manufacturer's diagnostic utility when available.

Check for:

• SMART warnings
• Critical warnings
• Media/data-integrity errors
• Excessive errors
• Firmware updates
• Abnormal temperature
• Drive health warnings

If the manufacturer's diagnostic software reports a critical health warning, prioritize backing up the data and replacing the drive.

Step 6: Run CHKDSK

Windows includes CHKDSK for checking file-system and volume errors.

Open Command Prompt as Administrator.

First run:

chkdsk C: /scan

For repair scenarios, you may use:

chkdsk C: /f

If Windows says the drive is currently in use, it may offer to schedule the check for the next restart.

Microsoft documents that CHKDSK checks file-system and file-system metadata for logical and physical errors, with repair behavior depending on the parameters used.

Important

Do not treat CHKDSK as an SSD-health test.

CHKDSK primarily evaluates the Windows volume/file system. A drive can pass CHKDSK and still have hardware or firmware problems.

Step 7: Repair the Windows Component Store with DISM

Open Command Prompt or Windows Terminal as Administrator.

Run:

DISM /Online /Cleanup-Image /ScanHealth

Then run:

DISM /Online /Cleanup-Image /RestoreHealth

Allow the operation to finish.

DISM can repair an online Windows image and restore damaged Windows components.

Restart Windows afterward if required.

Step 8: Run System File Checker

After repairing the Windows image, run:

sfc /scannow

System File Checker scans protected Windows system files and can replace incorrect or corrupted versions.

Possible results include:

Windows Resource Protection did not find any integrity violations

No protected system-file corruption was detected.

Windows Resource Protection found corrupt files and successfully repaired them

Restart the computer and monitor it.

If SFC repeatedly finds corruption after every repair, investigate the storage device, RAM and underlying system stability instead of repeatedly running SFC.

Step 9: Test the RAM

Press:

Windows + R

Enter:

mdsched.exe

Choose:

Restart now and check for problems

Windows will reboot and run Windows Memory Diagnostic.

Microsoft specifically lists Windows Memory Diagnostic as a troubleshooting method for UNEXPECTED_STORE_EXCEPTION.

For more thorough troubleshooting, an IT technician may perform extended memory testing.

If multiple RAM modules are installed and errors are detected, testing modules individually can help identify the defective module or slot.

Step 10: Update Storage and Chipset Drivers

Obtain appropriate drivers from the computer or motherboard manufacturer's support source.

Important categories include:

• Chipset driver
• SATA/AHCI driver
• NVMe/storage driver
• Intel Rapid Storage Technology driver where applicable
• AMD chipset driver where applicable

Avoid downloading random "driver updater" utilities from unknown websites.

For branded systems such as Dell, HP, Lenovo, ASUS or Acer, the manufacturer's validated driver packages are generally preferable for model-specific hardware.

Step 11: Update SSD/NVMe Firmware

Check whether the SSD manufacturer provides a firmware-management utility.

Firmware updates may address:

• Compatibility
• Stability
• Power management
• Error handling
• Controller behavior

Before updating storage firmware:

1. Back up important data.
2. Confirm the exact SSD model.
3. Use the manufacturer's official utility.
4. Ensure stable power.
5. Do not interrupt the firmware update.

Step 12: Install Windows Updates

Open:

Settings → Windows Update

Install applicable security, quality and driver updates.

Microsoft includes keeping Windows updated among its general recommendations for resolving repeated stop-code errors.

Restart the system and monitor it.

Step 13: Check SATA Cables on Desktop PCs

If the system uses a SATA SSD or HDD, shut down the computer and disconnect power before working inside it.

Check:

• SATA data cable
• SATA power cable
• Motherboard SATA port
• Drive-side connector

Where appropriate, test using:

• Another SATA cable
• Another motherboard SATA port

Intermittent connections can produce storage communication errors that are difficult to reproduce consistently.

Step 14: Check BIOS/UEFI Settings

Review the system firmware configuration.

Check for:

• Incorrect storage-controller settings
• Unsupported overclocking
• Aggressive RAM settings
• XMP/EXPO instability
• CPU undervolting
• PCIe instability

If the machine has been manually overclocked or undervolted, temporarily return it to manufacturer/default settings while troubleshooting.

Do not randomly change AHCI/RAID/storage mode on an existing Windows installation. Changing the controller mode incorrectly can make Windows unbootable.

Step 15: Update BIOS/UEFI

Check the computer or motherboard manufacturer's support page for BIOS/UEFI updates.

Before updating:

• Verify the exact model.
• Read the release notes.
• Connect laptops to AC power.
• Ensure desktops have stable power.
• Suspend BitLocker protection if the manufacturer's instructions require it.
• Keep the BitLocker recovery key available.
• Never interrupt firmware flashing.

BIOS updates should not be performed casually merely because a BSOD occurred once.

Step 16: Boot Windows in Safe Mode

If the computer crashes frequently during normal startup, test it in Safe Mode.

Safe Mode starts Windows with a reduced set of drivers and services.

If UNEXPECTED_STORE_EXCEPTION does not occur in Safe Mode, investigate:

• Recently installed drivers
• Third-party security software
• Storage utilities
• Hardware-monitoring utilities
• System optimization software
• Recently installed applications

Microsoft recommends Safe Mode as one of the basic troubleshooting approaches for recurring stop-code errors.

Step 17: Examine Crash Dump Files

For advanced troubleshooting, inspect Windows crash dumps.

Common locations include:

C:\Windows\Minidump

and:

C:\Windows\MEMORY.DMP

Microsoft recommends examining multiple dump files to determine whether repeated 0x154 crashes have common characteristics.

This is important because a single dump can sometimes point at a component that was involved in the crash without proving that component was the root cause.

Advanced Analysis with WinDbg

IT professionals can use Microsoft's WinDbg debugger to examine dump files.

A common debugger command is:

!analyze -v

Review information such as:

• BUGCHECK_CODE
• EXCEPTION_CODE
• MODULE_NAME
• IMAGE_NAME
• PROCESS_NAME
• FAILURE_BUCKET_ID
• stack trace

For this particular stop code, storage-related I/O information can be especially important.

Microsoft's documentation recommends using a debugger and comparing multiple dump files when determining the underlying cause of bug check 0x154.

What Does storahci.sys Mean?

Some UNEXPECTED_STORE_EXCEPTION dumps may reference:

storahci.sys

StorAHCI is part of the Windows storage stack for AHCI storage controllers.

If it appears in a dump, investigate the complete storage path:

• SSD/HDD
• SATA cable
• Storage controller
• Chipset
• Controller driver
• Firmware
• Motherboard
• Power

Do not automatically conclude that storahci.sys itself is defective merely because its name appears in the crash dump.

Microsoft Q&A examples of bug check 0x154 have shown cases involving storahci.sys and I/O-related exception information, demonstrating why the complete dump context matters.

What Does MemCompression Mean in a Crash Dump?

A dump may show:

PROCESS_NAME: MemCompression

This does not automatically mean Windows Memory Compression is the actual problem.

The crash may have occurred while Windows was processing compressed memory but the underlying failure could originate elsewhere, including an inability to retrieve required data successfully.

Therefore, avoid disabling Windows features simply because MemCompression appears in the dump.

Instead, inspect the exception code, I/O information, storage health, RAM and complete stack trace.

Recommended Diagnostic Order

For repeated UNEXPECTED_STORE_EXCEPTION crashes, a practical troubleshooting sequence is:

1. Back up important data.
2. Note when the BSOD occurs.
3. Check Event Viewer.
4. Check SSD/HDD/NVMe health.
5. Check Device Manager.
6. Check free disk space.
7. Run CHKDSK where appropriate.
8. Run DISM.
9. Run SFC.
10. Test RAM.
11. Update chipset/storage drivers.
12. Check SSD/NVMe firmware.
13. Install appropriate Windows updates.
14. Remove recent hardware/software changes.
15. Test in Safe Mode.
16. Check SATA connections where applicable.
17. Return overclocking/undervolting to defaults.
18. Consider BIOS/UEFI updates.
19. Analyze crash dumps.
20. Replace suspected hardware only when evidence supports the diagnosis.

This approach helps avoid replacing expensive components without sufficient evidence.

When Should You Suspect the SSD?

SSD/NVMe failure becomes more suspicious when the BSOD occurs together with symptoms such as:

• SMART or manufacturer health warnings
• Disk I/O errors
• Frequent file corruption
• Files disappearing or becoming unreadable
• Windows frequently freezing during disk activity
• Applications hanging when loading files
• Boot failures
• SSD occasionally disappearing from BIOS/UEFI
• Repeated storage-related errors in Event Viewer
• Manufacturer diagnostic failure
• Multiple crash dumps consistently pointing toward storage I/O problems

If several of these symptoms occur together, immediately back up important data.

When Should You Suspect RAM?

RAM becomes more suspicious when:

• Windows Memory Diagnostic reports errors.
• Multiple unrelated BSOD codes appear.
• Crashes occur under heavy memory load.
• Problems started after a RAM upgrade.
• XMP/EXPO or memory overclocking is enabled.
• Crashes disappear after removing a particular module.
• Errors follow one RAM module when modules are swapped.

A BSOD code alone should not be used to declare RAM defective.

When Should You Replace the SSD?

Consider SSD replacement when there is supporting evidence such as:

• Manufacturer diagnostics report failure.
• SMART/health data shows serious warnings.
• The drive repeatedly disconnects.
• BIOS intermittently fails to detect it.
• Storage-related I/O errors repeatedly appear.
• File corruption continues after Windows repairs.
• Problems follow the SSD when tested in another compatible system.
• Another known-good drive eliminates the crashes.

Always prioritize data backup before replacing or extensively testing a suspected failing drive.

Important Commands Summary

Run Command Prompt or Terminal as Administrator.

Check the file system

chkdsk C: /scan

Schedule file-system repairs

chkdsk C: /f

Check Windows image health

DISM /Online /Cleanup-Image /ScanHealth

Repair Windows image

DISM /Online /Cleanup-Image /RestoreHealth

Check protected Windows system files

sfc /scannow

Launch Windows Memory Diagnostic

mdsched.exe

Open Event Viewer

eventvwr.msc

Open Device Manager

devmgmt.msc

Mistakes to Avoid

Do Not Immediately Format Windows

Reinstalling Windows before checking hardware can temporarily hide symptoms without correcting a failing SSD, RAM module or storage controller.

Do Not Immediately Replace the SSD

UNEXPECTED_STORE_EXCEPTION does not automatically mean "SSD failure."

Perform diagnostics first.

Do Not Use Random Driver-Updater Software

Use Windows Update and official computer, motherboard or hardware-manufacturer sources.

Do Not Ignore Repeated Disk Errors

Repeated disk or I/O errors combined with BSODs deserve immediate investigation and data backup.

Do Not Disable Random Windows Services

Disabling services such as memory-related components without identifying the actual cause can introduce additional problems.

Do Not Depend on One Crash Dump

When possible, compare several dumps. Microsoft specifically recommends examining multiple dump files for recurring 0x154 crashes.

Frequently Asked Questions (FAQ)

1. What does UNEXPECTED_STORE_EXCEPTION mean?

It is Windows bug check 0x154 (0x00000154). Microsoft describes it as the kernel memory store component encountering an unexpected exception.

2. Is UNEXPECTED_STORE_EXCEPTION caused by an SSD?

It can be associated with storage problems, but the stop code alone does not prove the SSD is defective. Drivers, RAM, system corruption, firmware and other hardware can also be involved.

3. Does "STORE" mean Microsoft Store?

No. It refers to an internal Windows kernel memory-store component, not the Microsoft Store application.

4. Can bad RAM cause UNEXPECTED_STORE_EXCEPTION?

Memory instability can contribute to BSODs, so RAM should be tested when diagnosing repeated crashes. Microsoft specifically recommends Windows Memory Diagnostic as one troubleshooting method for bug check 0x154.

5. Can an HDD cause this error?

Yes. Storage-related problems are not limited to SSDs. HDD, SATA communication, controllers and file-system problems should also be investigated.

6. Can an NVMe SSD cause this BSOD?

Potentially. Check NVMe health, firmware, motherboard BIOS/UEFI, chipset drivers and related Event Viewer errors before concluding the drive itself has failed.

7. Will CHKDSK fix UNEXPECTED_STORE_EXCEPTION?

CHKDSK can detect and repair certain file-system problems, but it cannot fix every hardware, driver, RAM or firmware problem.

8. What does SFC /scannow do?

System File Checker verifies protected Windows system files and replaces incorrect versions when possible.

9. What does DISM /RestoreHealth do?

DISM can repair the Windows image/component store used by Windows servicing and system-file repair operations.

10. Should I run SFC and DISM?

They are appropriate when Windows system-file or component corruption is suspected. They do not replace hardware diagnostics.

11. Should I update my BIOS?

Consider a BIOS/UEFI update when the manufacturer provides an applicable stability or compatibility update, especially when troubleshooting unresolved hardware compatibility problems. Follow the manufacturer's instructions carefully.

12. Can outdated drivers cause this error?

Yes, drivers are one possible source of Windows stop-code errors. Storage and chipset drivers deserve particular attention with storage-related symptoms.

13. Why does my PC restart automatically after the error?

Windows normally restarts after a serious stop-code error. This behavior is part of Windows crash handling.

14. Where are BSOD dump files stored?

Minidumps are commonly stored in:

C:\Windows\Minidump

A larger system memory dump may be stored at:

C:\Windows\MEMORY.DMP

The exact dump configuration can vary.

15. Can WinDbg identify the problem?

WinDbg can provide valuable information about the exception, stack and modules involved. However, dump analysis requires interpretation; the module named in a dump is not necessarily the defective component.

16. What should I do if the BSOD happens only occasionally?

Record the date/time and stop code, check Event Viewer, keep Windows and appropriate drivers updated, and monitor whether the problem repeats. One isolated crash does not automatically indicate hardware failure.

17. What if the BSOD happens every day?

Treat repeated crashes as a serious stability issue. Back up important data, check storage health and logs, test RAM, repair Windows files, update appropriate drivers/firmware and analyze crash dumps.

18. Can overheating cause this problem?

Thermal instability can contribute to general system crashes. Check CPU, GPU, motherboard and storage temperatures if crashes occur primarily under sustained load.

19. Can antivirus software cause UNEXPECTED_STORE_EXCEPTION?

Low-level security software can sometimes contribute to system instability, but do not uninstall security software merely because this stop code appeared. Use dump analysis and logs to establish evidence.

20. Can a clean Windows installation solve it?

A clean installation can resolve severe software corruption or driver problems, but it will not repair defective RAM, a failing SSD, bad cables or other hardware faults. Hardware diagnostics should therefore be performed before assuming Windows itself is the root cause.

Final Conclusion

UNEXPECTED_STORE_EXCEPTION (0x00000154) is a serious Windows stop error indicating that the kernel memory store component encountered an unexpected exception.

The most effective troubleshooting strategy is not to assume that one component is responsible. Instead, systematically investigate the complete chain:

Windows → system files → memory → drivers → storage controller → SSD/HDD/NVMe → firmware → motherboard/hardware

For repeated occurrences, start by backing up important data and checking storage health and Event Viewer. Then proceed with Windows repair commands, memory testing, driver and firmware checks, and crash-dump analysis.

If the same error continues after software repair, and diagnostics repeatedly show storage or hardware-related failures, hardware replacement becomes much more strongly justified.