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.
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.