This error is a fairly new one, only recently surface on Windows 10; it is sometimes very similar to KERNEL_DATA_INPAGE_ERROR, have very similar symptoms. PCs on Windows 10 haven't been experiencing the KERNEL_DATA_INPAGE_ERROR but have been experiencing this, especially those that were formerly getting KERNEL_DATA_INPAGE_ERROR.
Possible Symptoms
NB: The list of symptoms listed here are not exhaustive and are from experience only
- Very random occurrence (hard to replicate)
- Happens mostly when the system has either been on for hours / just recently resumed from hibernation
- Frequency of occurrence is also random, sometimes frequent and sometimes not.
- Most times no dump file is created as the system abruptly restarts before even the message can be read.
- You experience "Critical Process has died" Exception once after a couple of this error
- If the system is left for long after BSOD, it restarts but doesn't show bios logo, until forcefully shut-down and boot back up.
This and many more are experiences from this error, the problem is sometimes caused by software (especially drivers and bugs) and sometimes hardware.
Possible Solutions
Possible Fix 1 (Windows Update):
Check for the latest update for windows; you can access this by searching for "updates" in "Start" menu and clicking "Check for updates" under the Settings group. You can also;
- click on Start or Windows Logo on your taskbar.
- click on Settings.
- click on Updates and security.
- click on Check for updates.
It is also possible your system was working perfectly before a recent update screwed it up, if that's the case, update can be uninstalled by searching in "Start" menu for "programs and features" and selecting "Programs and Features" from the result; when the screen shows up, click on "View installed updates" on the left side of the screen, scroll to the suspected culprit, right click and uninstall; use the "Installed on" column to help ease your search.
Possible Fix 2 (System File Checker):
Before resorting to a clean install of Widows (which should always be the last resort IMO), run the system file checker tool (SFC). This can help replace any corrupt windows file, and can be very helpful when the exception is caused by a bad system file. To run this,
- click on "Start" or Windows Logo on your taskbar
- search for CMD.
- right-click Command Prompt from the menu and "run as administrator".
- or Press Window + X.
- click on Command Prompt (Admin).
After command prompt shows up, enter:
sfc /scannow
press enter after entering this command, wait for windows to complete it's task.
Possible Fix 3 (Checkdisk)
Another possible fix is to check your hard drive for errors, by running the disk checker utility on all Partitions. This can help remap dead sectors, which by happenstance may be the reason for the ...STORE... exception is being caused by that.
Run Command Prompt as Administrator
- click on "Start" or Windows Logo on your taskbar
- search for CMD.
- right-click Command Prompt from the menu and "run as administrator".
- or Press Window + X.
- click on Command Prompt (Admin).
In the prompt, enter the drive letter for your partition, the enter
"chkdsk /f /r"
and press "enter". Sample for Drive C below;
c:
chkdsk /f /r /x
The /x tries to unmount the drive, if it can't and asks you for a boot time schedule, enter "y" and restart. Wait for the scan to complete, please don;t interrupt once started.
Possible Fix 4 (Turn off Fast Startup)
A possible fix for this error is also to turn off "Fast Start-up". Some users on the internet have reported this worked for them, Disable it by:
- Go to Power Options
- click on "Start" or Windows Logo on your taskbar
- search for "Power Options"
or
- right-click the battery icon
- select Power Options
- Click on "Choose what the power buttons do" (located on the left side of the window)
- Click on "Change Settings that are currently unavailable"
- Disable "Fast Startup" and save changes.
After disabling, restart and hope for the best.
Possible Fix 5 (Drive update):
An Outdated Driver may also be the cause of this dreadful error, visit your manufacturer site and download the latest Windows 10 drivers for your device or simply download "slimdriver" or "drive the life" and search your system for drivers that need updating.
Possible Fix 6 (Antivirus)
Case 1:
You may have harmful viruses on your system interfering with normal windows operations, it is recommended you update your Antivirus and perform "Boot-time Scan" of your system.
You may have harmful viruses on your system interfering with normal windows operations, it is recommended you update your Antivirus and perform "Boot-time Scan" of your system.
Case 2:
Your Antivirus may be the original culprit of this error, for now, try uninstalling your Antivirus and use Windows 10's default Anti-virus. Try that for a week and see if the BSOD will pop up again
Your Antivirus may be the original culprit of this error, for now, try uninstalling your Antivirus and use Windows 10's default Anti-virus. Try that for a week and see if the BSOD will pop up again
Possible Fix 7 (Clean install or Refresh)
If after all this, before attempting Step 8, perform a clean install of your O.S, or do a system refresh.
Possible Fix 8 (Hardware Maintenance)
At this point, I'll recommend you confirm if you are still under Warrantee,
if not!!!
If you believe in your repair skills, I'll recommend you do the following else take it to a repair-man to help do the following:
- simple RAM connector cleanup
- Clean or eliminate dust from your PC fan
- make sure all cables are plugged in tightly
Possible Fix 9 (Watch this Space)
Bless You "My Brother", the Lord is your strength....(I'll definitely update this post as soon as more solutions are discovered)
