Getting BSOD with KERNEL_DATA_INPAGE_ERROR when making a system image backup in Windows 10

Laurence1989

Reputable
Jan 13, 2016
6
0
4,510
I am trying to make a system image backup in windows 10 but when it gets about 75% of the way through my computer crashes to a blue screen with a 'KERNEL_DATA_INPAGE_ERROR'. it doesn't show any error code for this...

Things I have tried to remedy this after looking around extensively online:

Did a massive cleanup of my files - from about 1TB down to about 200GB

Performed a massive virus/malware hunt. Used AVG - nothing found, used MalwareBytes nothing found, used MRT - nothing found. Computer seems clean.

Ran chkdsk on the drive (2TB Seagate barracuda) and found no problems with the drive.

Checked the disk for errors (via properties>tools>error checking) - found no problems

Then ran chkdsk C: /f /r. It found around 20 'corrupted' files and fixed. From my rudimentary understanding of the report I found in the event viewer it found some system files with special characters in them and fixed.

Used Disk Cleanup and got rid of a bunch of junk files.

Used Windows Memory Diagnostic and found no issues with my RAM.

Opened the case and made sure the SATA cable was plugged in properly at the motherboard and the hard disk. At this point it seems doubtful that this is a hardware issue.

A potential fix for the system image backup itself I tried: went into services and put Shadow Copy and Windows Backup on 'Automatic'. Didn't help.

Note that I have no other issues with blue screen crashes and my system seems pretty much stable. However, Windows has been running a bit sluggishly and it's always the hard disk that is causing a bottleneck (100% disk in the task manager was happening a lot). But since cutting down my files from around 1TB to 200GB OS performance has improved greatly.

Also: I was able to make a system image backup when my computer was running Windows 8.1 a couple of months ago with no issues. At that point I had a lot of crap on my computer and hadn't even been very careful about malware etc.

I'm running an OEM version of Windows so I'm reluctant to do a clean install as I'll have to fork out for Windows again.

Seeking any further advice on why this would happen when creating a system image backup only and what else I can try to fix this.
 
Solution
if the drive is producing errors, and I wanted to keep it. I would do a full format of the drive (not a quick format) and reinstall windows 10 from a known good install image.

Windows 10 will try to remove data from bad clusters but it can take days, it does this by a background process that starts 5 minutes after the machine goes idle. You might turn off sleep functions and leave the system overnight while windows attempts to move data off of bad sectors.

a full format of the drive will mark these sectors as bad. A full format can take 4 to 8 hours.
a kernel inpage error means a driver could not read something from storage and transfer it to memory. I can mean the data was corrupted, or the drive is generating errors.

the bugcheck has a subcode that helps figure out the cause of the error.
you can put the memory dump from c:\windows\minidump directory on a server like microsoft onedriver, share the file and post a link.

you can also, try to fix any corrupted windows files on your local machine.
start cmd.exe as an admin then run
Dism.exe /online /cleanup-Image /restoreHealth

this will attempt to fix windows files from a trusted copy on a microsoft update server.

you can also google for crystaldiskinfo.exe and run it to read the smart data from your drives to see if it is generating errors.
 

Laurence1989

Reputable
Jan 13, 2016
6
0
4,510


Thanks for the response I will try these shortly. Here's a link to the last 3 DMP files and msinfo32: https://onedrive.live.com/redir?resid=A263A63852D89211!113&authkey=!AGZTEX3DhG3cpwQ&ithint=file%2czip

Update: Tried DISM and it failed with the following message:

Error: 0x800f081f

The source files could not be found.
Use the "source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.micorsoft.com/fwlink/?LinkId=243077.

The Dism log file can be found at C:\WINDOWS\Logs\DISM.log


Tried to go to the link in the error message but it's dead. Had a look online about that particular error message and situation but it seems like another rabbit hole with no clear solutions... still looking into it.

A link the the DISM log that was created for anyone who can understand it:
https://onedrive.live.com/redir?resid=A263A63852D89211!114&authkey=!ACr5bPi4iH1rHfI&ithint=file%2clog
 
other bugchecks were the same as the first. Update the BIOS and install current versions of the intel storage driver and see if you can still get a bugcheck.

----
update the BIOS to get sata fixes. bios version f13 2013/11/04
http://www.gigabyte.com/products/product-page.aspx?pid=4151#bios

also install the 3 motherboard drivers provided for windows 10.
storage driver was pretty old also
Intel RST (Rapid Storage Technology) driver
\SystemRoot\System32\drivers\iaStorA.sys Sat Sep 01 18:01:24 2012
-----

first bugcheck, the error code was success (no error)
maybe the other bugchecks will be more useful.
machine info:
BIOS Release Date 10/23/2012
BIOS Version F10
Manufacturer Gigabyte Technology Co., Ltd.
Product B75M-D3V
memory:part Number PSD34G133381
Processor Version Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz
Processor Voltage 8ah - 1.0V
External Clock 100MHz
Max Speed 7000MHz
Current Speed 3700MHz







 

Laurence1989

Reputable
Jan 13, 2016
6
0
4,510


Thanks again for your response. downloaded Crystaldiskinfo and it looks like the issues are pretty much my hard drive.

screenshot of Crystal Disk: https://imgur.com/AgqOFkS

Is there any way (other than things I've tried) to salvage it? If not I'm still hoping I can at least make a system image backup so I can replace it.

Also, I tried to update the BIOS to the exact version you are recommending earlier today. My computer completely screwed up and was stuck in a cycle of turning on and off every few seconds. I feel lucky to have managed to get it back on and running on the old BIOS backup again. I was almost about to give up thinking I had killed my motherboard. As such I'm pretty reluctant to try and flash it again! will download drivers tho.
 
if the drive is producing errors, and I wanted to keep it. I would do a full format of the drive (not a quick format) and reinstall windows 10 from a known good install image.

Windows 10 will try to remove data from bad clusters but it can take days, it does this by a background process that starts 5 minutes after the machine goes idle. You might turn off sleep functions and leave the system overnight while windows attempts to move data off of bad sectors.

a full format of the drive will mark these sectors as bad. A full format can take 4 to 8 hours.
 
Solution

Laurence1989

Reputable
Jan 13, 2016
6
0
4,510


Thank you again for you help. I am going to attempt to salvage the drive's bad sectors using SeaTools ATM and can then hopefully make a system image so I can format or replace the drive.