- Software and digital services
- Operating system
UNEXPECTED_STORE_EXCEPTION
Windows UNEXPECTED_STORE_EXCEPTION: kernel memory store fault
Risk level
Medium
Proceed carefully and stop if the check is unclear.
Urgency
High
Quick answer
UNEXPECTED_STORE_EXCEPTION (0x154) means the kernel component that manages the memory store hit an exception it did not expect. Start by checking Event Viewer for critical errors logged at the same time as the blue screen.
Safety first
Stop and check this first
- Before restoring Windows to an earlier point or resetting it, copy your personal files to another drive or to the cloud.
- If your PC uses BitLocker, have the recovery key located before resetting Windows or changing startup settings.
Safe checks you can perform
- Critical errors at the time of the crash
- Memory diagnostics with the extended test
- Flagged devices and Windows files
- Free space and Windows Update current
Leave these tasks to a qualified professional
- Do not attempt this professional task: Memory dump analysis for 0x154
- Do not attempt this professional task: Hardware test if memory fails
What a technician must be able to justify
Technician visit
These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.
These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.
Memory dump analysis for 0x154
What they doA technician opens MEMORY.DMP or the minidumps in WinDbg and compares several to see whether the same code is always running when the crash arrives.
They must show youthe !analyze -v output and the module or driver reported as the cause.
In writingthe driver identified, the version that fixes it and whether a hardware test is advisable.
Hardware test if memory fails
What they doIf the memory diagnostic shows errors, the technician confirms with the maker's tools which component fails before replacing anything.
They must show youthe memory test report naming the failing module.
In writingwhich part is replaced, why, and the repair warranty.
Before accepting a part or repair
Nothing has been shown yet. Do not accept a part swap based on the code alone.
Follow these steps
Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.
Critical errors at the time of the crash
- Who:
- you.
- How:
- press Win+R, type eventvwr.msc and press Enter; open Windows Logs, System, and look for critical errors with the same time as the blue screen.
- Result that matters:
- finding the name of a device or driver that failed just before the stop.
- If a specific device or driver appears:
- note its name and look for its update from the maker or in Windows Update.
- If nothing clear shows in that window:
- move on to the memory test.
- Evidence to keep:
- screenshot of the critical event with date, time and source.
Evidence: Bug Check 0x154 UNEXPECTED_STORE_EXCEPTION
Memory diagnostics with the extended test
- Who:
- you.
- How:
- type Windows Memory Diagnostic in Start, choose to restart now or at next startup; during the test press F1, set Test Mix to Extended with the arrow keys and press F10 to continue.
- Result that matters:
- knowing whether the extended RAM test finishes without errors.
- If the tool reports errors:
- keep the result and take it to the technician, who will confirm which module fails.
- If it finishes clean:
- memory becomes less suspect; review the drivers.
- Evidence to keep:
- photo or screenshot of the diagnostic result.
Evidence: Bug Check 0x154 UNEXPECTED_STORE_EXCEPTION
Flagged devices and Windows files
- Who:
- you.
- How:
- right-click Start, open Device Manager and look for any device with an exclamation point; check the events in its properties. Then open Command Prompt as administrator and run sfc /scannow.
- Result that matters:
- updating the flagged driver and repairing damaged system files.
- If a device was flagged or sfc repaired files:
- restart and watch whether 0x154 returns.
- If everything looks fine and the crash continues:
- install Windows updates and leave dump analysis to a technician.
- Evidence to keep:
- name of the flagged device and the final sfc message.
Evidence: Troubleshooting Windows unexpected restarts and stop code errors · Bug Check 0x154 UNEXPECTED_STORE_EXCEPTION
Free space and Windows Update current
- Who:
- you.
- How:
- check that the system drive has 10 to 15 percent free and go to Start, Settings, Windows Update, Check for updates.
- Result that matters:
- the system having disk headroom and the latest fixes installed.
- If space was short or updates were pending:
- free up space, install them and watch whether the code repeats.
- If everything was already current:
- record the date of each new crash for the technician.
- Evidence to keep:
- free space percentage and the installed version after updating.
Evidence: Stop code error or bug check troubleshooting (IT professionals) · Troubleshooting Windows unexpected restarts and stop code errors
Still not solved
If the error persists, stop here. See what the technician must do and show you.
Where this code applies
A code is meaningful only inside the right product and version context.
Primary scope
- System
- Software and digital services
- Brand
- Microsoft Windows
- Product type
- Operating system
Known code variants
- 0x00000154
- 0x154
- blue screen UNEXPECTED_STORE_EXCEPTION
- código de detención UNEXPECTED_STORE_EXCEPTION
- pantalla azul UNEXPECTED_STORE_EXCEPTION
- STOP 0x00000154
- stop code UNEXPECTED_STORE_EXCEPTION
- UNEXPECTED STORE EXCEPTION
What it means
Microsoft defines code 0x00000154 as an unexpected exception caught by the Windows kernel memory store component. Its parameters point to the store context and the exception details, which only help someone analysing the dump. For people who cannot work with the code, Microsoft suggests reviewing the System log, testing memory, checking Device Manager and running System File Checker. Seeing this code is not enough to say that the memory or the drive is broken.
Warnings and stop conditions
- Mediumsource verified
Before restoring Windows to an earlier point or resetting it, copy your personal files to another drive or to the cloud.
Evidence: Troubleshooting Windows unexpected restarts and stop code errors
- Mediumsource verified
If your PC uses BitLocker, have the recovery key located before resetting Windows or changing startup settings.
Evidence: Find your BitLocker recovery key
Symptoms and causes
Probable causes · in order
- A device driver misbehavingCommon
The official page asks you to look in Device Manager for devices flagged with an exclamation point and update the related driver, a sign a driver may be behind it.
Evidence: Troubleshooting Windows unexpected restarts and stop code errors · Bug Check 0x154 UNEXPECTED_STORE_EXCEPTION
- RAM returning errorsPossible
Microsoft's tips for this code include running Windows Memory Diagnostics, with the extended test, to rule out faults in system memory.
Evidence: Bug Check 0x154 UNEXPECTED_STORE_EXCEPTION
- Corrupted Windows files after a crashPossible
Microsoft suggests System File Checker (sfc /scannow) because it finds and restores corrupted Windows files that can lead to the stop.
Evidence: Bug Check 0x154 UNEXPECTED_STORE_EXCEPTION
Virtual technician
Does UNEXPECTED_STORE_EXCEPTION still appear after these checks?
Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.
Sources and technical references
- 1
Stop code error or bug check troubleshooting (IT professionals)
Microsoft · 2026 · official_doc
- 2
Troubleshooting Windows unexpected restarts and stop code errors
Microsoft · 2026 · official_doc
- 3
Solución de problemas de reinicios inesperados y errores de código de detención de Windows
Microsoft · 2026 · official_doc
- 4
Find your BitLocker recovery key
Microsoft · 2026 · official_doc
- 5
Bug Check 0x154 UNEXPECTED_STORE_EXCEPTION
Microsoft · 2026 · official_doc
Was this entry useful?