The Problem

Despite the name, UNEXPECTED_STORE_EXCEPTION has nothing to do with the Microsoft Store. The "store" here is the Windows memory manager's store component — the part that moves pages between RAM and the page file on disk. The stop code means it hit an error it could not handle while reading or writing a page.

That points at the path between memory and storage. In order of how often it turns out to be the cause: a failing or disconnecting drive, a display driver crashing during paging, third-party antivirus filter drivers, and genuinely bad RAM.

Drive already behaving oddly? Check it properly first: check SSD and hard drive health. Different stop code each restart? Start at how to fix a BSOD.

Symptoms

Blue screen reading UNEXPECTED_STORE_EXCEPTION, often while the PC is idle or waking from sleep.
File Explorer freezes for several seconds before the crash.
Disk activity light stays solid just before the blue screen.
Occasional "A device which does not exist was specified" errors, or a drive vanishing from File Explorer and reappearing after a reboot.

Step 1: Check the Drive's Health and SMART Data

This stop code is a storage problem until proven otherwise.

Open Terminal (Admin) and run:
```
wmic diskdrive get model,status
```
Anything other than OK is conclusive.
Then check the file system on the Windows drive:
```
chkdsk C: /scan
```
If it reports problems, schedule a repair pass and reboot:
```
chkdsk C: /f /r
```
The /r pass on a large mechanical drive can take hours — start it when you do not need the PC.
Read the SMART attributes properly, especially Reallocated Sectors, Pending Sectors, and NVMe Percentage Used: check SSD and hard drive health.
If SMART shows any warning, stop troubleshooting and copy your data off now: set up automatic backups.

Step 2: Reseat the Drive Cable or NVMe Module

An intermittent connection produces exactly this symptom — the drive answers most of the time and drops out under load.

Shut down fully, unplug the power cable, and hold the power button for five seconds.
On a desktop, reseat the SATA data and power cables at both ends, or unscrew and reseat the M.2 drive.
Swap in a different SATA cable if you have one. Cheap SATA cables fail more often than drives do.
On a laptop, this usually needs the bottom panel off — if that voids a warranty you care about, skip to Step 3.

Step 3: Update or Roll Back the Display Driver

A GPU driver that crashes while the memory manager is paging surfaces as a store exception rather than a graphics fault.

Right-click Start → Device Manager → Display adapters.
Right-click your GPU → Properties → Driver. If Roll Back Driver is available and the crashes started recently, use it.
Otherwise do a clean reinstall of the current driver from NVIDIA, AMD, or Intel directly: clean install GPU drivers with DDU.
Related symptom on the same driver: fix "display driver stopped responding".

Step 4: Uninstall Third-Party Antivirus Temporarily

Security suites install file-system filter drivers that sit directly in the paging path.

Open Settings → Apps → Installed apps.
Uninstall the third-party suite using the vendor's own removal tool where one exists — a partial uninstall leaves the filter driver behind.
Reboot. Windows Security takes over automatically, so you are not unprotected.
Use the PC for a day. If the crashes stop, reinstall the suite fresh, or stay on Windows Security.
Confirm the built-in protection is active: fix Windows Defender not working.

Step 5: Repair System Files and the Component Store

In Terminal (Admin), run in this order:

sfc /scannow

DISM /Online /Cleanup-Image /RestoreHealth

Reboot, then run sfc /scannow again and confirm it finds no integrity violations.
Full walkthrough: how to run SFC and DISM.

Step 6: Rebuild the Page File

A corrupted page file on a bad sector triggers this stop code every time the memory manager touches it.

Press Windows + R, type sysdm.cpl, press Enter.
Advanced tab → Performance → Settings → Advanced → Virtual memory → Change.
Untick Automatically manage paging file size for all drives.
Select the C: drive, choose No paging file, click Set, and reboot.
Return to the same screen, set it back to System managed size, click Set, and reboot again. This deletes and recreates pagefile.sys on fresh sectors.

Step 7: Test the Memory

Windows + R → mdsched.exe → Restart now and check for problems.
Press F1 during the test and choose the Extended test mix.
For a thorough result, run MemTest86 from a USB stick for four or more passes.
Any errors mean bad RAM or an unstable XMP/EXPO profile — turn the profile off in firmware and retest: how to enter BIOS or UEFI.
Related: fix MEMORY_MANAGEMENT BSOD.

Step 8: Disable Fast Startup

Fast Startup hibernates the kernel to disk on shutdown. If that hibernation file lands on damaged storage, the next boot faults immediately.

Open Control Panel → Power Options → Choose what the power buttons do.
Click Change settings that are currently unavailable.
Untick Turn on fast startup (recommended) and Save changes.
Shutdowns take a few seconds longer; boots become far more reliable on ageing drives.
Related: fix sleep and hibernation not working.

What Not to Do

Don't ignore a SMART warning because the PC still boots. Drives that report pending sectors fail soon, and this stop code is often the first warning you get.
Don't run chkdsk /r on a drive you have not backed up. A repair pass on a dying drive can push it over the edge.
Don't reinstall Windows onto the same failing drive — you will meet the same blue screen a week later.

Still Not Working?

If SMART is clean, RAM passes, the GPU driver is fresh, and no third-party security software remains, try booting from a Windows installer USB and running the same chkdsk from Repair your computer → Troubleshoot → Command Prompt. If the drive misbehaves there too, replace it.

When you do replace it: how to clone a hard drive to an SSD, or start fresh with how to clean install Windows 11.

Fix UNEXPECTED_STORE_EXCEPTION in Windows 11