Fix Unexpected Store Exception Error in Windows 10

This guide walks you through resolving the Unexpected Store Exception error in Windows 10, a blue screen of death (BSOD) that often appears during startup, after an update, or while using heavy applications. The error points to a problem with your system’s storage driver or the way Windows communicates with your hard drive or SSD. Below you’ll find step-by-step fixes, from quick restarts to deeper driver and disk checks, plus common pitfalls and troubleshooting advice.

What You’ll Need

Administrator access to your Windows 10 PC
A stable internet connection (for driver updates)
Your Windows installation media or recovery drive (only for the last-resort repair option)
About 30–60 minutes of time, depending on which fix works

Step-by-Step

Restart your PC normally. Sometimes the error is a one-time glitch. Press and hold the power button to force a shutdown if needed, then turn it back on. If the error reappears, continue.
Boot into Safe Mode. Restart your PC and press F8 repeatedly before the Windows logo appears (or use Shift + Restart from the login screen). Choose Troubleshoot > Advanced options > Startup Settings > Restart, then press 4 or F4 for Safe Mode. Safe Mode loads only essential drivers, which can help isolate the cause.
Run the Windows Memory Diagnostic. In Safe Mode, type “Windows Memory Diagnostic” in the search box and open it. Select Restart now and check for problems. The PC will reboot and run a memory test. If errors are found, your RAM may be faulty—replace it if possible.
Check your disk for errors. Open Command Prompt as administrator (right-click Start > Command Prompt (Admin)). Type chkdsk C: /f /r and press Enter. You’ll be prompted to schedule the scan for the next restart—type Y and reboot. This scans for bad sectors and filesystem corruption.
Update or roll back storage drivers. In Safe Mode, right-click Start > Device Manager. Expand Disk drives and Storage controllers. Right-click each device and select Update driver > Search automatically. If you recently updated a driver and the error started, right-click the device, select Properties > Driver > Roll Back Driver.
Run the System File Checker (SFC). In Command Prompt (Admin), type sfc /scannow and press Enter. This repairs corrupted system files. After it completes, also run DISM /Online /Cleanup-Image /RestoreHealth to fix the system image.
Check for Windows updates. Go to Settings > Update & Security > Windows Update and click Check for updates. Install any pending updates, then restart. If the error appeared after a recent update, you can uninstall it from View update history.
Disable Fast Startup. Open Control Panel > Power Options > Choose what the power buttons do > Change settings that are currently unavailable. Uncheck Turn on fast startup and save changes. Fast Startup can sometimes cause storage driver conflicts.
Run a clean boot. Type msconfig in the search box and open System Configuration. On the Services tab, check Hide all Microsoft services, then click Disable all. On the Startup tab, click Open Task Manager and disable all startup items. Restart. If the error stops, re-enable services one by one to find the culprit.
Reset your PC (last resort). If nothing works, go to Settings > Update & Security > Recovery and choose Reset this PC. Select Keep my files to reinstall Windows without losing personal data, or Remove everything for a full wipe.

Common Mistakes

Skipping Safe Mode. Running fixes in normal mode may fail if the system crashes repeatedly. Always try Safe Mode first.
Ignoring the chkdsk scan. Many users skip the disk check because it takes time, but bad sectors are a leading cause of this error.
Updating drivers blindly. Installing the latest driver without checking the manufacturer’s site can introduce a new problem. Use the rollback option if the error started after a driver update.
Forgetting to disable Fast Startup. This feature is enabled by default and often interferes with storage drivers.
Not backing up data. Before running chkdsk or resetting, ensure important files are backed up to an external drive or cloud.

Tips

If you have a desktop PC, reseat the SATA or NVMe cable connecting your drive—loose connections can trigger this error.
Use the manufacturer’s diagnostic tool for your SSD or HDD (e.g., Samsung Magician, Crucial Storage Executive) to check drive health.
Keep your BIOS/UEFI firmware updated, but only from the motherboard manufacturer’s official site.
After fixing the error, create a system restore point so you can revert if it happens again.
If the error occurs only after waking from sleep, adjust power settings to disable hybrid sleep or change the hard disk turn-off time.

Troubleshooting

If the error persists after trying the steps above, consider these additional checks:

Test your RAM with MemTest86. Create a bootable USB and run a full memory test—Windows Memory Diagnostic is quick but may miss intermittent issues.
Check the event log. Open Event Viewer, go to Windows Logs > System, and look for errors with source disk or ntfs around the time of the BSOD. The error code may point to a specific driver.
Try a different SATA port. On desktops, switching the drive to another port can help if the current port is faulty.
Boot from a Windows installation USB. If you have one, boot from it and choose Repair your computer. Then run Startup Repair or open Command Prompt to run chkdsk on the system drive.
Check for overheating. High temperatures can cause storage controllers to fail. Clean dust from fans and ensure proper airflow.
If you recently installed new hardware (RAM, GPU, or a new drive), remove it temporarily to see if the error disappears.

Frequently Asked Questions

What exactly causes the Unexpected Store Exception error?

It’s typically caused by a faulty storage driver, corrupted system files, a failing hard drive or SSD, or issues with the storage controller (like AHCI or NVMe). It can also be triggered by incompatible updates or faulty RAM.

Will I lose my files if I reset my PC?

If you choose Keep my files, Windows will reinstall but preserve your personal files in the Windows.old folder. However, it’s safer to back up important data before resetting, as no reset is 100% risk-free.

How long does chkdsk take?

It depends on the size and speed of your drive. A typical 1TB HDD can take 1–2 hours, while an SSD may take 15–30 minutes. Let it run uninterrupted.

Can this error be caused by a virus?

While rare, malware can corrupt storage drivers or system files. Run a full scan with Windows Defender or a trusted third-party antivirus if you suspect infection.

Is there a way to prevent this error in the future?

Keep Windows and drivers updated, avoid force-shutting down your PC, regularly run chkdsk (monthly), and ensure your drive has enough free space (at least 15% of its capacity).

Should I replace my hard drive if the error keeps coming back?

If you’ve tried all software fixes and the error persists, especially after running chkdsk and finding bad sectors, the drive may be failing. Back up your data immediately and consider replacing it.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →