UNEXPECTED_STORE_EXCEPTION (0x154): Disk and Driver Checks

What bug check 0x154 says, and what it leaves out

Microsoft documents the value as 0x00000154 and describes it as the kernel memory store component catching an unexpected exception. It has 4 parameters: a pointer to the store context or data manager, exception information, and two reserved values.

The word Store here has nothing to do with the Microsoft Store app. Microsoft's page is written for programmers and does not name a disk or SSD as the cause. Advice that blames the drive is common, but the official page reads only as a pointer to the System log, memory, drivers and system files, so this page treats the drive as one check among five.

Act only if the same stop code returns

Microsoft's blue screen guide says a restart usually clears the error and that you should act only when the same stop code recurs. Write down the code at the bottom of the screen the second time it appears. UNEXPECTED_STORE_EXCEPTION is a different code from STORE_DATA_STRUCTURE_CORRUPTION (0x1C7) and STORAGE_DEVICE_ABNORMALITY_DETECTED (0x140), which are separate lines in Microsoft's bug check list.

Read the System log first

Press Win+R, type eventvwr.msc and press Enter. Open Windows Logs > System and look for critical errors in the same time frame as the blue screen. Microsoft lists this as the way to find the device or driver behind the crash.

Note the source name next to each error. The chkdsk results also land in the Application log, under sources Chkdsk and Wininit.

Look at the drive health in Settings

On Windows 11 open Start > Settings > System > Storage > Advanced storage settings > Disks & volumes, then Properties for the disk. Microsoft reports 3 health attributes: Estimated remaining life, Available spare (0% to 100%) and Temperature in degrees Celsius. The first is an approximate percentage used, and Microsoft notes that consumption alone does not mean the device will fail.

Critical warnings come in 3 types: spare capacity is low, reliability is degraded, or the drive is set to read-only. Windows monitors only NVMe SSDs, not SATA SSDs or hard disks, so a missing panel does not prove the drive is fine. If a critical warning appears, Microsoft strongly recommends backing up your data first.

A worked example: three crashes in one week

Say a laptop shows the same stop code on Monday, Wednesday and Friday. Step 1: open the System log and note the critical events near each crash time. Step 2: check Disks & volumes for a warning. Step 3: open an administrator Command Prompt and run DISM.exe /Online /Cleanup-image /Restorehealth, which can take several minutes. Step 4: run sfc /scannow and leave the window open until it reaches 100%. Step 5: run chkdsk C: /f /r and restart when asked.

Step 6: run Windows Memory Diagnostics. Step 7: keep a note of whether the crash returns within 7 days. If the System log named a driver in step 1, step 8 is to update that driver instead of repeating the scans.

Run DISM before SFC, in that order

Microsoft's file-repair article puts DISM first. In an elevated Command Prompt run DISM.exe /Online /Cleanup-image /Restorehealth, then sfc /scannow. SFC ends with 1 of 4 messages: no integrity violations, could not perform the operation, found and repaired corrupt files, or found corrupt files but could not fix some.

For the last message, the details are in %windir%\Logs\CBS\CBS.log. If Windows Update is broken, DISM accepts a local source with /Source:C:\RepairSource\Windows /LimitAccess, using the path of your own repair source.

What chkdsk C: /f /r does and how long it takes

Without parameters chkdsk only reports. The /f switch fixes errors and needs the disk locked, so on your system drive Windows offers to check at the next restart. The /r switch locates bad sectors, recovers readable data and includes /f. You need the local Administrators group.

Microsoft says that on large hard drives /r can run for hours, and that on an SSD repeated full-surface scans slightly reduce lifespan, though occasional checks are not a concern. A boot partition check ends with an automatic restart. Chkdsk exit code 0 means no errors, 1 means errors were found and fixed, 2 means cleanup ran or /f was missing, and 3 means the check failed or errors were not fixed.

Test the memory with the extended mix

Search for Windows Memory Diagnostics and choose to restart now or at the next restart. A standard test runs by itself. For the extended test, press F1 during the test, use the arrow keys to set Test Mix to Extended and press F10 to apply. Microsoft lists this tool directly on its 0x154 page.

Drivers are the largest cause of stop errors overall

Microsoft's analysis of crashes across all stop codes says 70% come from third-party driver code, 10% from hardware, 5% from Microsoft code, and 15% are unknown because memory is too corrupted to analyze. It is not specific to 0x154, but it explains why Device Manager is on Microsoft's list.

Right-click Start, open Device Manager and look for a device marked with an exclamation point (!). Open its properties, read the events log, and update the driver. Also update the BIOS and firmware, and keep 10% to 15% of the drive free.

Safe mode when the PC crashes at startup

From Settings > Update & security > Recovery choose Restart now under Advanced startup, then Troubleshoot > Advanced options > Startup Settings > Restart. Press 4 or F4 for safe mode, or 5 or F5 for Safe Mode with Networking. Microsoft's blue screen guide also says to remove any hardware you added before the first crash.

Mistakes that waste a weekend

Running chkdsk /r every day is the main one: Microsoft warns it adds write cycles to an SSD. Another is skipping the log, since the System log is the only place that may name the driver. Interrupting chkdsk is not recommended either, although Microsoft says it should not leave the volume more corrupt.

If a blue screen shows a code you do not recognize, Crade can read the screen and explain what the text means, which is useful when you only have a photo of the error.

When to ask for help instead

A PC that crashes with 0x154 after a repeat of every step above, with a critical drive warning or a drive missing from File Explorer, needs a backup first and a technician second. A managed work PC should go to IT, who can read the memory dump (%SystemRoot%\MEMORY.DMP, or the 256 KB files in %SystemRoot%\Minidump) with a debugger.