ERROR NAME: KERNEL_DATA_INPAGE_ERROR STOP Code: 0x0000007a

Question

Hey,

I bought this computer 1 year ago. I am using windows 8.1 and ubuntu 14.04 dual boot. 1 week ago while I was watching a movie, the system suddenly  got hanged and the "BLUE SCREEN OF DEATH " appeared and it showed the error message as I wrote in the title. I first ignored and it happened thrice till now. So, I read about it in microsoft forums and browsed a lot to know about this.

1. I ran the "chkdsk C: /f /r /x" and the result I am attaching with this post.
2. I also did the same disk check process in memory diagnostics tool and it says "no problems with memory"

I dont understand what to do now.... This also happened while I was writing code in ubuntu. It suddenly showed the error message and restarted. Please help me this is very serious problem.....

*********This is results of "chkdsk C: /f /r /x" :**************

ListChkdskResult by SleepyDude v0.1.7 Beta | 21-09-2013

------< Log generate on 06-07-2015 12:33:19 >------

Category: 0

Computer Name: Dheeraj

Event Code: 1001

Record Number: 146220

Source Name: Microsoft-Windows-Wininit

Time Written: 07-05-2015 @ 00:52:34

Event Type: Information

User: 

Message: 

Checking file system on C:

The type of the file system is NTFS.

Volume label is Windows8_OS.

A disk check has been scheduled.

Windows will now check the disk.                         

Stage 1: Examining basic file system structure ...

  584704 file records processed.                                                        

File verification completed.

  11658 large file records processed.                                   

  0 bad file records processed.                                     

Stage 2: Examining file name linkage ...

  709840 index entries processed.                                                       

Index verification completed.

  0 unindexed files scanned.                                        

  0 unindexed files recovered.                                      

Stage 3: Examining security descriptors ...

Cleaning up 11 unused index entries from index $SII of file 0x9.

Cleaning up 11 unused index entries from index $SDH of file 0x9.

Cleaning up 11 unused security descriptors.

Security descriptor verification completed.

  62569 data files processed.                                           

CHKDSK is verifying Usn Journal...

  17465816 USN bytes processed.                                                           

Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...

  584688 files processed.                                                               

File data verification completed.

Stage 5: Looking for bad, free clusters ...

  106772486 free clusters processed.                                                       

Free space verification is complete.

Windows has scanned the file system and found no problems.

No further action is required.

 887353343 KB total disk space.

 459380040 KB in 292682 files.

    181496 KB in 62570 indexes.

         0 KB in bad sectors.

    701863 KB in use by the system.

     65536 KB occupied by the log file.

 427089944 KB available on disk.

      4096 bytes in each allocation unit.

 221838335 total allocation units on disk.

 106772486 allocation units available on disk.

Internal Info:

00 ec 08 00 a2 6b 05 00 8b 4a 0a 00 00 00 00 00  .....k...J......

a3 02 00 00 35 00 00 00 00 00 00 00 00 00 00 00  ....5...........

Windows has finished checking your disk.

Please wait while your computer restarts.

---

Category: 0

Computer Name: Dheeraj

Event Code: 26226

Record Number: 145609

Source Name: Chkdsk

Time Written: 07-03-2015 @ 19:36:05

Event Type: Information

User: 

Message: Chkdsk was executed in scan mode on a volume snapshot.  

Checking file system on \Device\HarddiskVolume5

Volume label is Windows8_OS.

Stage 1: Examining basic file system structure ...

---

Stage 1: Examining basic file system structure ...

---

Category: 0

Computer Name: Dheeraj

Event Code: 26228

Record Number: 145312

Source Name: Chkdsk

Time Written: 07-03-2015 @ 10:14:28

Event Type: Information

User: 

Message: Chkdsk was executed in verify mode on a volume snapshot.  

Checking file system on \Device\HarddiskVolume5

Volume label is Windows8_OS.

Examining 1 corruption record ...

Record 1 of 1: Corrupt File "<0x39,0x2345a>" ... no corruption found.

1 corruption record processed in 0.1 seconds.

Windows has examined the list of previously identified potential issues and found no problems.

No further action is required.

---

Category: 0

Computer Name: Dheeraj

Event Code: 26228

Record Number: 145309

Source Name: Chkdsk

Time Written: 07-03-2015 @ 10:10:33

Event Type: Information

User: 

Message: Chkdsk was executed in verify mode on a volume snapshot.  

Checking file system on \Device\HarddiskVolume5

Volume label is Windows8_OS.

Examining 2 corruption records ...

Record 1 of 2: Corrupt File "<0x72,0x23459>" ... The USA check value, 0x0, at block 0x1 is incorrect.

The expected value is 0x24b.

no corruption found.

Record 2 of 2: Corrupt File "<0x9c,0x233ec>" ... The USA check value, 0x0, at block 0x1 is incorrect.

The expected value is 0x191.

no corruption found.

2 corruption records processed in 0.1 seconds.

Windows has examined the list of previously identified potential issues and found no problems.

No further action is required.

---

Category: 0

Computer Name: Dheeraj

Event Code: 26228

Record Number: 145308

Source Name: Chkdsk

Time Written: 07-03-2015 @ 10:09:59

Event Type: Information

User: 

Message: Chkdsk was executed in verify mode on a volume snapshot.  

Checking file system on \Device\HarddiskVolume5

Volume label is Windows8_OS.

Examining 3 corruption records ...

Record 1 of 3: Corrupt File "<0x56,0x23252>" ... The USA check value, 0x0, at block 0x1 is incorrect.

The expected value is 0x17a.

no corruption found.

Record 2 of 3: Corrupt File "<0x15,0x23432>" ... The USA check value, 0x0, at block 0x1 is incorrect.

The expected value is 0x138.

no corruption found.

Record 3 of 3: Corrupt File "<0x1e,0x23250>" ... The USA check value, 0x0, at block 0x1 is incorrect.

The expected value is 0x17a.

no corruption found.

3 corruption records processed in 0.2 seconds.

Windows has examined the list of previously identified potential issues and found no problems.

No further action is required.

---

Category: 0

Computer Name: Dheeraj

Event Code: 26228

Record Number: 145255

Source Name: Chkdsk

Time Written: 07-03-2015 @ 10:05:05

Event Type: Information

User: 

Message: Chkdsk was executed in verify mode on a volume snapshot.  

Checking file system on \Device\HarddiskVolume5

Volume label is Windows8_OS.

Examining 1 corruption record ...

Record 1 of 1: Corrupt File "<0x1b,0x23430>" ... The USA check value, 0x0, at block 0x1 is incorrect.

The expected value is 0x13b.

no corruption found.

1 corruption record processed in 0.1 seconds.

Windows has examined the list of previously identified potential issues and found no problems.

No further action is required.

---

Category: 0

Computer Name: Dheeraj

Event Code: 26228

Record Number: 145250

Source Name: Chkdsk

Time Written: 07-03-2015 @ 10:02:05

Event Type: Information

User: 

Message: Chkdsk was executed in verify mode on a volume snapshot.  

Checking file system on \Device\HarddiskVolume5

Volume label is Windows8_OS.

Examining 1 corruption record ...

Record 1 of 1: Corrupt File "<0x69,0x233ee>" ... no corruption found.

1 corruption record processed in 0.1 seconds.

Windows has examined the list of previously identified potential issues and found no problems.

No further action is required.

---

Category: 0

Computer Name: Dheeraj

Event Code: 26228

Record Number: 144270

Source Name: Chkdsk

Time Written: 07-02-2015 @ 12:12:28

Event Type: Information

User: 

Message: Chkdsk was executed in verify mode on a volume snapshot.  

Checking file system on \Device\HarddiskVolume5

Volume label is Windows8_OS.

Examining 1 corruption record ...

Record 1 of 1: Corrupt File "<0x5,0x2334c>" ... no corruption found.

1 corruption record processed in 0.1 seconds.

Windows has examined the list of previously identified potential issues and found no problems.

No further action is required.

---

Category: 0

Computer Name: Dheeraj

Event Code: 26228

Record Number: 144153

Source Name: Chkdsk

Time Written: 07-01-2015 @ 18:58:16

Event Type: Information

User: 

Message: Chkdsk was executed in verify mode on a volume snapshot.  

Checking file system on \Device\HarddiskVolume5

Volume label is Windows8_OS.

Examining 1 corruption record ...

Record 1 of 1: Corrupt File "<0x8f,0x2343d>" ... The USA check value, 0x30, at block 0x1 is incorrect.

The expected value is 0x3.

no corruption found.

1 corruption record processed in 0.1 seconds.

Windows has examined the list of previously identified potential issues and found no problems.

No further action is required.

---

Category: 0

Computer Name: Dheeraj

Event Code: 26228

Record Number: 144152

Source Name: Chkdsk

Time Written: 07-01-2015 @ 18:57:55

Event Type: Information

User: 

Message: Chkdsk was executed in verify mode on a volume snapshot.  

Checking file system on \Device\HarddiskVolume5

Volume label is Windows8_OS.

Examining 1 corruption record ...

Record 1 of 1: Corrupt File "<0xb,0x23319>" ... The USA check value, 0x0, at block 0x1 is incorrect.

The expected value is 0x7.

no corruption found.

1 corruption record processed in 0.1 seconds.

Windows has examined the list of previously identified potential issues and found no problems.

No further action is required.

---

Category: 0

Computer Name: Dheeraj

Event Code: 26228

Record Number: 144151

Source Name: Chkdsk

Time Written: 07-01-2015 @ 18:57:42

Event Type: Information

User: 

Message: Chkdsk was executed in verify mode on a volume snapshot.  

Checking file system on \Device\HarddiskVolume5

Volume label is Windows8_OS.

Examining 3 corruption records ...

Record 1 of 3: Corrupt File "<0xd1,0x23253>" ... no corruption found.

Record 2 of 3: Corrupt File "<0x6f,0x232ea>" ... The USA check value, 0x66, at block 0x1 is incorrect.

The expected value is 0x1c4.

no corruption found.

Record 3 of 3: Corrupt File "<0x99,0x2334e>" ... The USA check value, 0x61, at block 0x1 is incorrect.

The expected value is 0x1bf.

no corruption found.

3 corruption records processed in 0.1 seconds.

Windows has examined the list of previously identified potential issues and found no problems.

No further action is required.

---

Category: 0

Computer Name: Dheeraj

Event Code: 26228

Record Number: 144148

Source Name: Chkdsk

Time Written: 07-01-2015 @ 18:57:25

Event Type: Information

User: 

Message: Chkdsk was executed in verify mode on a volume snapshot.  

Checking file system on \Device\HarddiskVolume5

Volume label is Windows8_OS.

Examining 1 corruption record ...

Record 1 of 1: Corrupt File "<0x98,0x233ef>" ... no corruption found.

1 corruption record processed in 0.1 seconds.

Windows has examined the list of previously identified potential issues and found no problems.

No further action is required.

---

Category: 0

Computer Name: Dheeraj

Event Code: 26228

Record Number: 144147

Source Name: Chkdsk

Time Written: 07-01-2015 @ 18:57:08

Event Type: Information

User: 

Message: Chkdsk was executed in verify mode on a volume snapshot.  

Checking file system on \Device\HarddiskVolume5

Volume label is Windows8_OS.

Examining 1 corruption record ...

Record 1 of 1: Corrupt File "<0x189,0x23431>" ... no corruption found.

1 corruption record processed in 0.1 seconds.

Windows has examined the list of previously identified potential issues and found no problems.

No further action is required.

---

Category: 0

Computer Name: Dheeraj

Event Code: 26228

Record Number: 144144

Source Name: Chkdsk

Time Written: 07-01-2015 @ 18:57:00

Event Type: Information

User: 

Message: Chkdsk was executed in verify mode on a volume snapshot.  

Checking file system on \Device\HarddiskVolume5

Volume label is Windows8_OS.

Examining 1 corruption record ...

Record 1 of 1: Corrupt File "<0x61,0x23458>" ... The USA check value, 0x33, at block 0x1 is incorrect.

The expected value is 0xf2.

no corruption found.

1 corruption record processed in 0.1 seconds.

Windows has examined the list of previously identified potential issues and found no problems.

No further action is required.

---

Category: 0

Computer Name: Dheeraj

Event Code: 26228

Record Number: 144138

Source Name: Chkdsk

Time Written: 07-01-2015 @ 18:56:30

Event Type: Information

User: 

Message: Chkdsk was executed in verify mode on a volume snapshot.  

Checking file system on \Device\HarddiskVolume5

Volume label is Windows8_OS.

Examining 2 corruption records ...

Record 1 of 2: Corrupt File "<0xef,0x2343e>" ... no corruption found.

Record 2 of 2: Corrupt File "<0x12,0x23318>" ... no corruption found.

2 corruption records processed in 0.3 seconds.

Windows has examined the list of previously identified potential issues and found no problems.

No further action is required.

---

Category: 0

Computer Name: Dheeraj

Event Code: 26228

Record Number: 135159

Source Name: Chkdsk

Time Written: 06-12-2015 @ 18:42:19

Event Type: Information

User: 

Message: Chkdsk was executed in verify mode on a volume snapshot.  

Checking file system on \Device\HarddiskVolume5

Volume label is Windows8_OS.

Examining 1 corruption record ...

Record 1 of 1: Corrupt File "<0x3,0x17010>" ... no corruption found.

1 corruption record processed in 0.1 seconds.

Windows has examined the list of previously identified potential issues and found no problems.

No further action is required.

---

Answer 1

Hello Sir,

Since BSOD hasn't showed up for 3 weeks I was unable to store the error messages. So, if BSOD occurs again I will definitely post the .dmp files.(actual log files).

Answer 2

We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

---

---

Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here

If you have any questions about the procedure please ask

Answer 3

Hello sir,

Thank you Sir, It is corrected and sorry for delay. Thank  you for your reply....

I hope this would help many people...

Answer 4

Thank you for your reply..

I will try all the steps you have suggested and I will reply the results in 2 days...

But I have 1 doubt... i.e.

If I keep my laptop into sleep mode with many apps running.. can this be a possible reason for this kernel inpage error?

Is it suggestible or not to keep my laptop in sleep mode with many apps running...

Answer 5

Hi,

Thank you for posting the query on Microsoft Community Forums. You have reached the right place. Let us work together to find the root cause of this issue and try resolving it.

The error code KERNEL_DATA_INPAGE_ERROR STOP: 0x0000007Astates 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.

I would suggest you to try all the steps from the following link and see if that helps.

Resolving Blue Screen errors in Windows

http://windows.microsoft.com/en-us/windows-8/resolve-windows-blue-screen-errors

Hope this helps. Let us know if you have any other issues with Windows in future.