You can check for both Windows and driver updates from the Windows Settings menu. Windows software and driver updates often come with important fixes and improvements for your PC that can stop BSOD errors like these from occurring.
If you’re seeing unexpected store code exception errors on your PC, you might want to check for Windows updates, as well search for any available driver updates for your hardware.
System conflicts causing BSODs can also be the result of outdated drivers or software. If any issues are detected, chkdsk should fix them, then boot into Windows automatically as soon as the process is complete. The chkdsk tool runs as a boot scan, meaning you’ll need to reboot your PC and let it scan your drive before Windows boots to ensure no conflicts. Once PowerShell is open, type sfc /scannow and press enter to begin the scan. Open a PowerShell window by right-clicking the start menu and clicking PowerShell (Admin).
The instructions below refer to using PowerShell for this, but they will also work for cmd, too. You can quickly test this using Window’s built-in system file checker ( sfc) command from an elevated PowerShell terminal or command line.
If you’ve checked your hardware and you’re confident that there are no faults or issues, an unexpected store exception error could point to another likely option: corrupted system files. Graphics cards and system memory can also cause this BSOD error to pop up, so test for bad memory using tools like memtest, or use software like FurMark to test your graphics card. If it is, get your files backed up quickly, because if your system drive fails, you’ll be left trying to extract files from a dead drive, which isn’t an easy process and will probably fail.ĭon’t forget to test your other system components, too. You should check your hard drive for errors to see if this is the cause.