Kernel_data_inpage_error

[FordGT90Concept]

I've gotten several of these over the last month or so and I can't figure out the source. I'm going to itemize what I know...

-Here's a picture of the most recent BSOD
-The last time it BSOD'd, I was browsing the web and not much else. I noticed IE9 wasn't responding, then tried to focus on another program and it wasn't responding. Then I tried ctrl+alt+del and that didn't work either. 15-30 seconds after noticing IE9 locked up, it finally switched to the BSOD pictured.
-Also after that BSOD, the link to TPU in the IE9 Favorites Bar got borked. It literally wouldn't work. Don't know if that is of any significance.
-No hardware has changed.
-Most times after restarting the computer, BIOS gives an INSERT DISK message. I have to restart again for it to refind Windows.
-Twice after what is presumably the BSOD, when the computer is supposed to restart, it doesn't and the power button becomes completely unresponsive. I have to flip the rocker switch on the PSU to restore functionality to the power button.
-I have had problems with my HD 5870 but after flashing the card BIOS, it seems to be working without problems. I am 80% confident my computer has thrown this BSOD before and after the flashing the BIOS on the card.
-

Spoiler: chkdsk

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
426496 file records processed.
File verification completed.
564 large file records processed.
0 bad file records processed.
2 EA records processed.
60 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 5)...
509640 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 5)...
426496 file SDs/SIDs processed.
Cleaning up 752 unused index entries from index $SII of file 0x9.
Cleaning up 752 unused index entries from index $SDH of file 0x9.
Cleaning up 752 unused security descriptors.
Security descriptor verification completed.
41573 data files processed.
CHKDSK is verifying Usn Journal...
34165488 USN bytes processed.
Usn Journal verification completed.

CHKDSK is verifying file data (stage 4 of 5)...
426480 files processed.
File data verification completed.

CHKDSK is verifying free space (stage 5 of 5)...
27886271 free clusters processed.
Free space verification is complete.

CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

488287231 KB total disk space.
376026380 KB in 354025 files.
173020 KB in 41574 indexes.
0 KB in bad sectors.
542743 KB in use by the system.
65536 KB occupied by the log file.
111545088 KB available on disk.

4096 bytes in each allocation unit.
122071807 total allocation units on disk.
27886272 allocation units available on disk.

The power button not working leads me to believe the issue, in at least some major way, involves the motherboard. Anyone concur of have an alternative?

 

[razor2890]

The error code KERNEL_DATA_INPAGE_ERROR STOP: 0x0000007A states that the requested page of kernel data from the paging file could not be read into memory. It appears that there are some issues with the hard disk.
Use check disk command for any errors on hard disk -
Warning: Microsoft does not recommend interrupting the CHKDSK process. Microsoft does not guarantee the integrity of the disk if the CHKDSK program is interrupted. For safety you can back up your data before using the check disk command.
Use the check disk commands as follows:
1. Click Start.
2. In search window type 'cmd' and ENTER. Right click and select 'Run as administrator'.
3. Type at the command prompt CHKDSK /P and press ENTER to scan the disk.
4. Then type CHKDSK C: /F /R and press ENTER to repair corrupt sectors, if there are any.
NOTE: The root drive has to be C: and the command may schedule a task at the system startup, if it does, then press Y to schedule a task and restart the computer to perform chkdsk.
Once chkdsk completes, boot to the desktop and then check.
You may refer to the below mentioned link for more details -
http://msdn.microsoft.com/en-us/library/ms793989.aspx
Hope this helps.

 

[FordGT90Concept]

I did chkdsk. No major errors were found.

 

[razor2890]

http://answers.microsoft.com/en-us/...ing-ie-8/c675b7b8-795f-474d-a1c4-6b77b3fcd990

http://support.microsoft.com/kb/977178

http://mikemstech.blogspot.in/2011/12/troubleshooting-0x0000007a.html

http://www.sevenforums.com/crashes-debugging/170593-bsod-kernel_data_inpage_error.html

Try out these links..it may help.

 

[FordGT90Concept]

BlueScreenView doesn't find any dump files. C:\Windows\Minidump doesn't exist despite minidumps being enable and that being the selected directory to put them in. This BSOD simply doesn't create them apparently.

Intel RST says both drives are "Normal" and the RAID0 strip is "Normal" too. Despite that, I started the verification process (4% complete).

If verify finishes before I go to bed, I'll try to start memtestx86 but I'm very confident it isn't a memory issue (I'd have a lot more problems than just this BSOD).

Edit: RAID0 verified with no errors found.

 

[FordGT90Concept]

I think I'm going to pass on memtestx86 and instead, if it happens again, going to install Windows on a spare 500 GB drive I have and see if it produces the same error on a different OS install on a different hard drive.

 

[Peter1986C]

Good idea.

 

[FordGT90Concept]

I'm thinking chkdsk fixed it. It hasn't BSOD'd since.