locked
KERNEL_DATA_INPAGE_ERROR Bluescreen RRS feed

  • Question

  • Hey i don't know if i have set the right category but im kind of desperate.

    My Lenovo laptop with Windows 8 keeps crashing to a bluescreen with the error  KERNEL_DATA_INPAGE_ERROR. I already tried to fix it with a CHKDSK and it seemed to work because i didn't get a single error friday and saturday unlike thursday where i got like five. but i dont know if i was just lucky those days or if it actually helped. I'm also sure what CHKDSK does and if i was supposed to do anything or read anything when it was done, because the CHKDSK was running while i was sleeping. It might have crased while running the check.

    here's the latest dump file from this morning when i was booting up my pc.

    https://drive.google.com/file/d/0Bzz54J9yiO98WWpqQ2hNY2lmTWc/view?usp=sharing

    ohh and i should also mention that my pc is in a very bad shape mostly beacause its the cheapest piece of chinese C*** i have ever had the displeasure of owning... basically my laptop's case and hinges is cracked and i'm not sure if the internal hadware is in one piece. could that be the cause error?


    Sunday, December 7, 2014 11:04 AM

All replies

  • Please upload a copy of your system information file. Click "start", type 'msinfo32", Click "file" at the top of the page, select "export" and give the file a name and click "save".

    Navigate to where the file was saved to, and upload the generated text file to a public folder on your OneDrive account and post the link here.

    Sunday, December 7, 2014 8:40 PM
  • Here you go 

    https://onedrive.live.com/redir?resid=ABBFD1BC98CFE1EB!8636&authkey=!AFcAKVPh_xTurFY&ithint=file%2ctxt


    Sunday, December 7, 2014 9:30 PM
  • I have looked at both the crash dump and MSinfo files and there is really nothing that jumps out or definitive on them.

    Run driver verifier (DV) per the instructions in the link below and if we get lucky, we can identify the culprit
    Note: Make sure to read and remember the steps to reset DV in the event of a crash, and post a link to the newly generated crash dump here.

    Driver Verifier-- tracking down a mis-behaving driver. Created by ZigZag3143, Co.authored by by JMH3143
    http://answers.microsoft.com/en-us/windows/wiki/windows_other-system/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

    • Proposed as answer by ZigZag3143x Wednesday, December 17, 2014 11:14 PM
    Monday, December 8, 2014 12:31 AM
  • Hi Frederik,

    The following is the dump file analyze result:

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 7A, {4, 0, ffffe00119f343e0, ffffc0012ca61828}
    
    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+27e )
    
    Followup: Pool_corruption
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KERNEL_DATA_INPAGE_ERROR (7a)
    The requested page of kernel data could not be read in.  Typically caused by
    a bad block in the paging file or disk controller error. Also see
    KERNEL_STACK_INPAGE_ERROR.
    If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
    it means the disk subsystem has experienced a failure.
    If the error status is 0xC000009A, then it means the request failed because
    a filesystem failed to make forward progress.
    Arguments:
    Arg1: 0000000000000004, lock type that was held (value 1,2,3, or PTE address)
    Arg2: 0000000000000000, error status (normally i/o status code)
    Arg3: ffffe00119f343e0, current process (virtual address for lock type 3, or PTE)
    Arg4: ffffc0012ca61828, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
    
    Debugging Details:
    ------------------
    
    
    ERROR_CODE: (NTSTATUS) 0 - STATUS_SUCCESS
    
    BUGCHECK_STR:  0x7a_0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  1
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    TRAP_FRAME:  ffffd0003c07d710 -- (.trap 0xffffd0003c07d710)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffc001345aa820 rbx=0000000000000000 rcx=ffffc001345aa810
    rdx=ffffc001345a5010 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff803b8eb0aee rsp=ffffd0003c07d8a0 rbp=000000000000000d
     r8=ffffc001345aa000  r9=ffffc00134173820 r10=ffffc0012ca61820
    r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na po nc
    nt!ExDeferredFreePool+0x27e:
    fffff803`b8eb0aee 49394208        cmp     qword ptr [r10+8],rax ds:ffffc001`2ca61828=ffffc001345aa820
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff803b8d999e5 to fffff803b8d5c9a0
    
    STACK_TEXT:  
    ffffd000`3c07d398 fffff803`b8d999e5 : 00000000`0000007a 00000000`00000004 00000000`00000000 ffffe001`19f343e0 : nt!KeBugCheckEx
    ffffd000`3c07d3a0 fffff803`b8cae6c8 : 00000000`00000002 ffffd000`3c07d508 fffff803`b8f67dc0 ffffd000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2cb35
    ffffd000`3c07d490 fffff803`b8c6410a : fffff803`b8f67dc0 ffffe001`15f4e040 00000000`00000000 00000000`00000000 : nt!MiIssueHardFault+0x184
    ffffd000`3c07d550 fffff803`b8d66c2f : 00000000`00000000 00000000`00000000 00000000`0013ee00 00000000`74536d4d : nt!MmAccessFault+0x5ba
    ffffd000`3c07d710 fffff803`b8eb0aee : 00000000`00000000 ffffe001`15e00000 00000000`00000000 ffffc001`3b7769d0 : nt!KiPageFault+0x12f
    ffffd000`3c07d8a0 fffff803`b8eaf84e : ffffc001`3bb6b010 ffffc001`3b7769d0 00000000`00000000 00000000`00000003 : nt!ExDeferredFreePool+0x27e
    ffffd000`3c07d920 fffff803`b8c9a608 : 00000000`00000000 00000000`00088011 ffffe001`1a005170 00000000`00000021 : nt!ExFreePoolWithTag+0x84e
    ffffd000`3c07da10 fffff803`b902753f : ffffe001`1a005170 00000000`00000011 ffffe001`00088081 00000000`00000000 : nt!MiDeleteSegmentPages+0x32c
    ffffd000`3c07daa0 fffff803`b8d25bb4 : fffff803`b8f67000 ffffd000`3c07db50 ffffe001`1a005178 00000000`00000000 : nt!MiSegmentDelete+0x57
    ffffd000`3c07dae0 fffff803`b8d4402d : 00000000`00000000 fffff803`b8ee57a0 ffffe001`15e49900 00000000`00000012 : nt!MiProcessDereferenceList+0x100
    ffffd000`3c07db70 fffff803`b8d0dc70 : ffffe001`15f4e040 00000000`00000080 ffffe001`15f4e040 00000000`00000000 : nt!MiDereferenceSegmentThread+0xd9
    ffffd000`3c07dc00 fffff803`b8d62fc6 : fffff803`b8f0f180 ffffe001`15f4e040 fffff803`b8f68a00 00000000`00000000 : nt!PspSystemThreadStartup+0x58
    ffffd000`3c07dc60 00000000`00000000 : ffffd000`3c07e000 ffffd000`3c078000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!ExDeferredFreePool+27e
    fffff803`b8eb0aee 49394208        cmp     qword ptr [r10+8],rax
    
    SYMBOL_STACK_INDEX:  5
    
    SYMBOL_NAME:  nt!ExDeferredFreePool+27e
    
    FOLLOWUP_NAME:  Pool_corruption
    
    IMAGE_NAME:  Pool_Corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    IMAGE_VERSION:  6.3.9600.17415
    
    MODULE_NAME: Pool_Corruption
    
    BUCKET_ID_FUNC_OFFSET:  27e
    
    FAILURE_BUCKET_ID:  0x7a_0_nt!ExDeferredFreePool
    
    BUCKET_ID:  0x7a_0_nt!ExDeferredFreePool
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x7a_0_nt!exdeferredfreepool
    
    FAILURE_ID_HASH:  {9eb467a0-7278-53f6-1f41-484375c2c0b0}
    

    ;

    ;

    The following is the information about Bugcheck 7A: Bug Check 0x7A: KERNEL_DATA_INPAGE_ERROR.

    Please follow the resolutions mentioned in the above article:

    Run the chkdsk again;

    then Run the hardware diagnostics that the system manufacturer supplies, especially the memory scanner. For more information about these procedures, see the owner's manual for your computer. Read more on the Resolving a failing RAM problem: part.

    Best regards


    Michael Shao
    TechNet Community Support


    • Edited by Michael_LS Tuesday, December 9, 2014 7:06 AM
    Tuesday, December 9, 2014 7:05 AM
  • Hey im just running the chkdsk again but it has stopped at 20% the last time i did the chkdsk it stopped at 17% for several hous untill i went to bed so i don't know if it ever completed the check.

    is this normal or is it a problem?

    Tuesday, December 9, 2014 5:40 PM
  • Hi Frederik,

    We could take a look at the Event Viewer for the chkdsk log files:

    Open Event Viewer, navigate to the Windows Logs to expand it, then right click on Application and
    click on Find, Copy and paste Chkdsk, then click on Find Next; then use the same way to find Wininit.

    If the above steps seems to be a little hard to find the result, we could copy and paste the following powershell commands with PowerShell.exe:

    In PowerShell, copy and paste the command below, and press Enter. (see screenshot below)

    get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt

    Note:  To paste the copied command into PowerShell, you will just need to right click in PowerShell. The CHKDSKResults.txt file will be created on your desktop.

    After that, run the following commands under CMD with admin rights:

    Dism /Online /Cleanup-Image / RestoreHealth

    If have errors that logged, upload the DISM.log(under %windir%\Logs\DISM ) and the CHKDSKResults.txt into OneDrive and paste the shared link here.

    Best regards


    Michael Shao
    TechNet Community Support


    • Edited by Michael_LS Wednesday, December 10, 2014 6:36 AM
    Wednesday, December 10, 2014 6:35 AM