BSOD 0x00007a KERNEL_DATA_INPAGE_ERROR

[ErvinBoyes]

I've been having loads of blue screens recently with the error: 0x00007a KERNEL_DATA_INPAGE_ERROR. I've searched the error up and apparently I needed to run a CHKDSK /f /r on the C: drive. I did it not only for the C: drive, but for every other hard drive I have and it did not fix anything. I also tried downloading a windows hotfix but when I use it an error message comes up and I can't use it. One other thing is that 90% of the time that it happens, Im not actually at my computer, only when it first started happening would it be when I'm actually doing something on my PC. It might just be a coincidence but what the hell.

Here are my specs:

-MSI GTX 970
-750w Corsair Psu
-MSI Z87-G45
-i7 4790K w/ stock cooler
-8gb of RAM
-2TB HDD which I bought about a month or 2 ago and only contains games (823gb is in use)
-1TB HDD which I bought about a year ago which also has a few games on but its mostly videos and music related stuff like plugins and samples (572gb is in use)
-a 275gb SSD which I bought at the same time as the 2TB HDD and has windows on it, aswell as my everyday software such as Chrome, Discord, Spotify (141gb is in use)
-a 160gb HDD which I've had for about 2 to 3 years and just contains a load of random files. Only 2gbs are being used up there so theres loads of space left.
- a 120gb SSD which I've had for about 1 and a half years and currently doesnt have anything on it because I formatted it when I bought my other SSD
- I am running Windows 7

I hope that's not too much information. Any help is appreciated. Thanks.

 

[ErvinBoyes]

I've just had another BSOD right after writing this. I've had 3 today that have happened whilst downloading things to my 2tb hdd, so that could be a hint as to which hard drive is causing the problems.

 

[johnbl]

a in page error means the system can not copy data from storage to RAM for some reason.
the reason is stored as a code in the bugcheck data
https://msdn.microsoft.com/en-us/library/windows/hardware/ff559211(v=vs.85).aspx

depending on what the bugcheck data looks like you can figure out the cause.
if the error code indicates a CRC error then it could be drive defects, bad sectors, loose cable.
if the memory address is wrong, it can be data corruption in memory, malware attacking the storage driver,
bugs in the storage driver or in its support in the BIOS.

even bugs in the BIOS sleep functions or bugs in the firmware/hardware of each drive can cause this bugcheck.

generally, you would run bluescreenview.exe or who crashed and post the bugcheck data so someone could see all of the parameters. You could also copy the memory dump files to a server, share them as public and post a link. Someone with a windows debugger can read the reason windows shut down.

you can just apply fixes for the most common causes and hope.
IE run Malwarebytes to scan for malware attacks on the storage drivers,
update the storage drivers from the motherboard vendor to get the current ones.
check your hard drive cables, Maybe move your data cable to another sata controller.
(the slow one supported by the CPU will have the least number of bugs)
update any secondary SATA driver from your motherboard vendor.
you can run crystaldiskinfo.exe to read firmware versions and SMART error info from your various drives to get an idea if one is failing.

turn off any bios and software overclocking. incorrect overclocks can cause memory contents to be incorrect when read. a bad memory read will cause a inpage error.
booting memtest on its own images can often detect this problem.

 

[ErvinBoyes]

a in page error means the system can not copy data from storage to RAM for some reason.
the reason is stored as a code in the bugcheck data
https://msdn.microsoft.com/en-us/library/windows/hardware/ff559211(v=vs.85).aspx

depending on what the bugcheck data looks like you can figure out the cause.
if the error code indicates a CRC error then it could be drive defects, bad sectors, loose cable.
if the memory address is wrong, it can be data corruption in memory, malware attacking the storage driver,
bugs in the storage driver or in its support in the BIOS.

even bugs in the BIOS sleep functions or bugs in the firmware/hardware of each drive can cause this bugcheck.

generally, you would run bluescreenview.exe or who crashed and post the bugcheck data so someone could see all of the parameters. You could also copy the memory dump files to a server, share them as public and post a link. Someone with a windows debugger can read the reason windows shut down.

you can just apply fixes for the most common causes and hope.
IE run Malwarebytes to scan for malware attacks on the storage drivers,
update the storage drivers from the motherboard vendor to get the current ones.
check your hard drive cables, Maybe move your data cable to another sata controller.
(the slow one supported by the CPU will have the least number of bugs)
update any secondary SATA driver from your motherboard vendor.
you can run crystaldiskinfo.exe to read firmware versions and SMART error info from your various drives to get an idea if one is failing.

turn off any bios and software overclocking. incorrect overclocks can cause memory contents to be incorrect when read. a bad memory read will cause a inpage error.
booting memtest on its own images can often detect this problem.

Thank you, I will try that tomorrow and see how it goes

 

[ErvinBoyes]

a in page error means the system can not copy data from storage to RAM for some reason.
the reason is stored as a code in the bugcheck data
https://msdn.microsoft.com/en-us/library/windows/hardware/ff559211(v=vs.85).aspx

depending on what the bugcheck data looks like you can figure out the cause.
if the error code indicates a CRC error then it could be drive defects, bad sectors, loose cable.
if the memory address is wrong, it can be data corruption in memory, malware attacking the storage driver,
bugs in the storage driver or in its support in the BIOS.

even bugs in the BIOS sleep functions or bugs in the firmware/hardware of each drive can cause this bugcheck.

generally, you would run bluescreenview.exe or who crashed and post the bugcheck data so someone could see all of the parameters. You could also copy the memory dump files to a server, share them as public and post a link. Someone with a windows debugger can read the reason windows shut down.

you can just apply fixes for the most common causes and hope.
IE run Malwarebytes to scan for malware attacks on the storage drivers,
update the storage drivers from the motherboard vendor to get the current ones.
check your hard drive cables, Maybe move your data cable to another sata controller.
(the slow one supported by the CPU will have the least number of bugs)
update any secondary SATA driver from your motherboard vendor.
you can run crystaldiskinfo.exe to read firmware versions and SMART error info from your various drives to get an idea if one is failing.

turn off any bios and software overclocking. incorrect overclocks can cause memory contents to be incorrect when read. a bad memory read will cause a inpage error.
booting memtest on its own images can often detect this problem.

I think the problem could have actually been loose cables. I'll wait a few days and see if it works. Thank you for the help