How to Fix UNEXPECTED_STORE_EXCEPTION Blue Screen

To fix UNEXPECTED_STORE_EXCEPTION, protect your files first, then check recent updates and hardware, repair Windows with DISM and SFC, check the drive, and test memory. The stop code usually points to storage or file-system trouble, but faulty drivers, failing memory, or damaged Windows files can cause the same crash. Do not reset Windows or format the drive until you have backed up your data and ruled out failing hardware.

What to do immediately after the UNEXPECTED_STORE_EXCEPTION crash

Windows displays this stop code when it encounters an unexpected failure while handling a system or storage operation. It can appear during startup, while opening files, or under heavier disk activity. The word “store” refers to a Windows system component, not necessarily the Microsoft Store app.

UNEXPECTED_STORE_EXCEPTION

If Windows is still running after the restart, save open work and copy irreplaceable files to an external drive or a trusted cloud location before repairing anything. Prioritize documents, photos, project folders, browser exports, and any data that is not already backed up.

Disconnect recently added USB storage, docks, adapters, printers, and other peripherals. Leave the keyboard, mouse, display, and network connection attached unless one of those was recently changed. Restart once normally. Do not repeatedly hold the power button to force shutdowns; repeated interrupted writes can worsen file-system damage.

Do not start with Reset this PC, a clean installation, or drive formatting. Those actions can remove applications and, depending on the option selected, personal data. First determine whether the computer can stay stable long enough to back up files and run diagnostics.

Does your PC boot normally or keep crashing in a loop?

This procedure applies to supported Windows 10 and Windows 11 desktop editions. Repair commands require an Administrator account. Several tests require a restart, so keep a current backup before changing drivers or repairing the disk.

• If the desktop stays usable, back up your files and follow the repair steps in order. Stop if the drive starts making unusual noises, disappears from firmware, or reports a serious health warning.
• If crashes are intermittent, record what happens immediately before each failure: waking from sleep, gaming, copying files, connecting a device, or installing a driver. That pattern helps distinguish storage, graphics, power, and driver causes.
• If Windows repeatedly restarts, use the recovery environment instead of allowing the loop to continue.

Before making changes, disconnect recently added peripherals and confirm that your important files exist in a second location. If the data is not backed up and the drive appears unreliable, copy files from another computer or have a repair technician image the drive before attempting extensive repairs.

To reach Windows Recovery, interrupt startup only when Windows is loading: turn the PC on and, when the Windows logo appears, hold the power button to turn it off. Repeat this startup interruption until Windows displays Automatic Repair. This is not a normal shutdown, so use it only to reach recovery when the system will not boot.

Choose Advanced options, then Troubleshoot. Select Startup Settings, restart, and choose Safe Mode or Safe Mode with Networking. Safe Mode loads a limited set of drivers. If the crash stops there, a recently installed driver, service, or startup program becomes more likely. From Advanced options, System Restore can undo a recent driver or software change without deleting personal files, if a restore point exists.

If you cannot reach recovery, start from Windows installation or recovery media and choose Repair your computer, not Install now.

Fix UNEXPECTED_STORE_EXCEPTION in the safest order

Work through these checks in order. After each major change, restart and use the computer normally for a while before moving on. That gives you a clear indication of which change affected the crashes.

1. Install Windows and optional hardware updates.

Open Settings with an Administrator account.

Settings > Windows Update > Check for updates
Settings > Windows Update > Advanced options > Optional updates

Install pending Windows updates and restart. In Device Manager, inspect recently changed devices and install drivers from the computer or component manufacturer rather than from random driver-download sites. Prioritize storage, chipset, graphics, and controller drivers.

If the crash began immediately after a driver update, open the device's Properties, choose the Driver tab, and select Roll Back Driver when available. The expected result is that Windows remains stable after the restart. If the same crash returns, continue to step 2.

2. Remove recent hardware, software, or driver changes.

Shut down, unplug a newly added device, and test again. Remove recently installed utilities, antivirus products, disk tools, or driver packages from Settings > Apps > Installed apps. For a driver, Device Manager can uninstall the device and offer to remove its driver package. Do not remove storage-controller drivers unless you know which device they control and have a recovery path.

If the blue screen stops after removing one change, reinstall only a current, compatible version from the manufacturer. If it continues with the new hardware disconnected, Windows corruption, the system drive, RAM, or an unrelated driver remains possible.

3. Repair the Windows component store and system files.

Open Windows Terminal (Admin) or Command Prompt (Admin). Run DISM first because SFC uses the component store as its repair source.

DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannow

DISM should complete without an error. SFC should report either that it found no integrity violations or that it found corrupt files and successfully repaired them. Restart and run SFC once more if it says that it could not fix some files.

If DISM cannot find source files, connect to the internet and install pending updates; persistent errors may require matching Windows installation media. If the commands complete successfully but the blue screen returns, continue to step 4. These commands repair Windows files, not a physically failing SSD.

4. Check the file system and drive.

Save your work first. Open an elevated Command Prompt and run:

chkdsk C: /scan

The scan can report that no problems were found, that errors need an offline repair, or that it found and fixed file-system errors. If Windows schedules a repair, accept the restart and allow it to finish. To request an offline repair directly, use:

chkdsk C: /f

Do not interrupt the repair. A clean scan or a completed repair means the logical file-system check finished; it does not prove that the physical drive is healthy. CHKDSK can correct logical file-system errors, but it cannot restore data from a failing flash cell or controller.

Check the SSD or hard drive with the manufacturer’s own diagnostic tool and review its health status, firmware, and self-test result. A warning, failed self-test, rapidly worsening health, frequent disappearing drive, or repeated blue screens after repair points to hardware rather than a Windows setting.

5. Test memory.

Search for Windows Memory Diagnostic, select Restart now and check for problems, and let the test complete. You can also use mdsched.exe from Run.

Any reported memory error is significant. Power off, reseat removable memory if you are comfortable doing so, and test modules individually according to the computer or motherboard manual. If the built-in test passes but crashes continue, a longer bootable memory test or professional diagnosis may still be needed. A memory error can corrupt files, so avoid trusting the system with important work until the RAM issue is resolved.

How to verify the blue screen is actually gone

A single successful restart does not prove the problem is fixed. Restart the computer several times, sign in, open the applications you normally use, copy a group of files, and repeat the activity that previously triggered the crash. If the failure happened during gaming or another demanding task, test that workload only after your files are backed up.

Check Windows Reliability Monitor for a pattern of failures:

Control Panel > Security and Maintenance > Maintenance > View reliability history

Look for repeated Windows failures, hardware errors, driver crashes, or the same stop code on the dates of the blue screens. Event Viewer may contain additional storage or file-system entries, but a single event is not proof of a failing component. Minidump files, when created, are usually stored in C:\Windows\Minidump; they can help a technician or a suitable debugger.

The expected result is several normal restarts and no repeat of UNEXPECTED_STORE_EXCEPTION during the workload that caused it. If CHKDSK repairs errors and the crash returns, or the manufacturer’s diagnostic reports a warning or failed test, treat that as evidence of possible SSD or hard-drive failure. Copy your files immediately, avoid writing unnecessary data to the drive, and replace it or have the computer serviced. Software repairs cannot make unreliable storage safe.

How to prevent another UNEXPECTED_STORE_EXCEPTION crash

Keep Windows, chipset, storage-controller, graphics, and SSD firmware updates current, but avoid generic driver packages from untrusted sites. Check the drive’s health periodically with its manufacturer’s utility and keep reasonable free space so Windows and the SSD have room for normal operations.

Maintain backups that you can actually restore. A second copy on an external drive helps with drive failure; a separate copy protects against theft, malware, and accidental deletion. Disconnect a backup drive after copying when practical so a damaged system cannot affect every copy.

Stop applying software fixes and arrange replacement or repair when:

• The drive disappears from BIOS or UEFI, then returns intermittently.
• The manufacturer’s tool reports a warning, critical health state, or failed self-test.
• CHKDSK repeatedly finds new errors after a repair.
• Blue screens continue after Windows repairs, driver rollback, and a known-good memory test.
• Files become corrupted, folders take unusually long to open, or the system freezes during disk activity.

If the computer is under warranty, preserve the diagnostic results and contact the manufacturer. If personal files are not backed up, prioritize a file copy or professional drive recovery before replacing or reinstalling Windows.

Conclusion

Back up your files, choose the path that matches the computer’s boot behavior, and run the checks in order. If the crash returns after repeated file-system repairs or a failed storage diagnostic, stop troubleshooting in Windows and replace the drive or arrange professional repair.

Frequently Asked Questions

Will UNEXPECTED_STORE_EXCEPTION delete my files?

The blue screen itself does not normally delete personal files, but a failing drive or repeated forced shutdowns can cause corruption. Back up important files before running repairs.

Can I fix this error without reinstalling Windows?

Often, yes. Driver rollback, Windows updates, DISM, SFC, disk checks, and memory testing can resolve software and file-system causes. Reinstalling Windows will not fix a physically failing SSD or defective RAM.

What if the blue screen only happens once?

One isolated crash can result from a temporary driver or hardware event. Install pending updates, back up important files, and monitor Reliability Monitor. Repeated crashes or storage warnings require deeper diagnosis.