locked
BLUESCREEN ISSUES "KERNEL_DATA_INPAGE_ERROR " RRS feed

  • Question

  •  I keep getting a blue screen and i have tried many things and the problem still persist. I am running Windows 7 and it is a Dell Inspiron all in one PC.  It is only about 1 year and a few months old.  I installed BlueScreen Viewer and here is the most current information that came up.  Any help would be greatly appreciated since Dell customer service in INDIA could not help at all.  

    Dump FIle: 080312-22089-01.dmp 

    Crash time:8/3/2012 7:38:01 AM 

    Bug Check String: KERNEL_DATA_INPAGE_ERROR 

    Bug Check Code: 0x0000007a 

    Parameter1: 00000000`00000020 

    Parameter 2: ffffffff`c000009d

    Parameter 3:  fffffa80`08712078

    Parameter 4:  00000000`00000000

    Caused by Driver:  fltmgr.sys

    Caused by Address:   fltmgr.sys+16df  

    Processor: x64

    Crash Address: ntoskrnl.exe+7f1c0

    Full Path: C:\Windows\Minidump\080312-22089-01.dmp 

    4 15 7601 275,016 

    Is there a way to fix this issue??

    Here is a link to Skydrive for my Dump files information

    https://skydrive.live.com/redir?resid=CF17537F14DAD1A2!147

    Thanks




    Friday, August 3, 2012 12:59 PM

Answers

  • Hi,

    *******************************************************************************
    *                                                                             *
    *                        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: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
    Arg2: ffffffffc000009d, error status (normally i/o status code)
    Arg3: fffffa8008712078, current process (virtual address for lock type 3, or PTE)
    Arg4: 0000000000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
    Debugging Details:
    ------------------
    ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED
    DISK_HARDWARE_ERROR: There was error with disk hardware
    BUGCHECK_STR:  0x7a_c000009d
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  1
    LAST_CONTROL_TRANSFER:  from fffff80002e8726c to fffff80002e931c0
    STACK_TEXT:  
    fffff880`03508a88 fffff800`02e8726c : 00000000`0000007a 00000000`00000020 ffffffff`c000009d fffffa80`08712078 : nt!KeBugCheckEx
    fffff880`03508a90 fffff800`02e7c167 : fffffa80`08712010 00000000`c000009d 00000000`00000000 fffffa80`087120a8 : nt! ?? ::FNODOBFM::`string'+0x505d0
    fffff880`03508b50 fffff800`02e85bd7 : fffffa80`0550fa00 fffffa80`0550fa50 00000000`00000000 fffffa80`00000008 : nt!IopCompletePageWrite+0x57
    fffff880`03508b80 fffff800`02e88ddd : fffffa80`0550fa00 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1c7
    fffff880`03508c00 fffff800`02e558eb : fffffa80`0550fa00 fffff880`03168f40 00000000`00000000 fffff800`02e20990 : nt!KiCommitThreadWait+0x3dd
    fffff880`03508c90 fffff800`02e209ea : fffffa80`0550fa00 00000000`00000001 fffffa80`054ea990 00000000`00000000 : nt!KeWaitForGate+0xfb
    fffff880`03508ce0 fffff800`03129e6a : fffffa80`0550fa00 00000000`00000000 00000000`00000080 00000000`00000001 : nt!MiModifiedPageWriter+0x5a
    fffff880`03508d40 fffff800`02e83ec6 : fffff880`03164180 fffffa80`0550fa00 fffff880`0316efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`03508d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+505d0
    fffff800`02e8726c cc              int     3
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+505d0
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  4fa390f3
    FAILURE_BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+505d0
    BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+505d0
    Followup: MachineOwner
    --------------------------------------------------------------------------------------------------------------------------------------------------------------------

    Bug Check 0x7a : http://msdn.microsoft.com/en-us/library/windows/hardware/ff559211(v=vs.85).aspx

    ** try to Run The system checker   SFC /SCANNOW   ,  also Run This Command in CMD.

    Start ---> Run... ---> CMD --->  Chkdsk /f /r

    will restart your computer and checking your HDD for errors.

    Regards,


    MCT / MCITP / MCTS / MCSA / MCSE / C|EH

    • Proposed as answer by tracycai Wednesday, August 22, 2012 8:03 AM
    • Marked as answer by Cloud_TS Thursday, August 23, 2012 2:06 AM
    Sunday, August 5, 2012 12:10 PM
  • Adding on other advise, you could also download the HD utility from it's manufacturer website to run a test on the drive itself. Alternatively you might also want to run memtest or windows memory diagnostic to ensure the problem does not lies with the ram

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

    • Proposed as answer by tracycai Wednesday, August 22, 2012 8:04 AM
    • Marked as answer by Cloud_TS Thursday, August 23, 2012 2:06 AM
    Monday, August 6, 2012 10:17 AM
    Answerer

All replies

  • Hi,

    *******************************************************************************
    *                                                                             *
    *                        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: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
    Arg2: ffffffffc000009d, error status (normally i/o status code)
    Arg3: fffffa8008712078, current process (virtual address for lock type 3, or PTE)
    Arg4: 0000000000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
    Debugging Details:
    ------------------
    ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED
    DISK_HARDWARE_ERROR: There was error with disk hardware
    BUGCHECK_STR:  0x7a_c000009d
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  1
    LAST_CONTROL_TRANSFER:  from fffff80002e8726c to fffff80002e931c0
    STACK_TEXT:  
    fffff880`03508a88 fffff800`02e8726c : 00000000`0000007a 00000000`00000020 ffffffff`c000009d fffffa80`08712078 : nt!KeBugCheckEx
    fffff880`03508a90 fffff800`02e7c167 : fffffa80`08712010 00000000`c000009d 00000000`00000000 fffffa80`087120a8 : nt! ?? ::FNODOBFM::`string'+0x505d0
    fffff880`03508b50 fffff800`02e85bd7 : fffffa80`0550fa00 fffffa80`0550fa50 00000000`00000000 fffffa80`00000008 : nt!IopCompletePageWrite+0x57
    fffff880`03508b80 fffff800`02e88ddd : fffffa80`0550fa00 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1c7
    fffff880`03508c00 fffff800`02e558eb : fffffa80`0550fa00 fffff880`03168f40 00000000`00000000 fffff800`02e20990 : nt!KiCommitThreadWait+0x3dd
    fffff880`03508c90 fffff800`02e209ea : fffffa80`0550fa00 00000000`00000001 fffffa80`054ea990 00000000`00000000 : nt!KeWaitForGate+0xfb
    fffff880`03508ce0 fffff800`03129e6a : fffffa80`0550fa00 00000000`00000000 00000000`00000080 00000000`00000001 : nt!MiModifiedPageWriter+0x5a
    fffff880`03508d40 fffff800`02e83ec6 : fffff880`03164180 fffffa80`0550fa00 fffff880`0316efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`03508d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+505d0
    fffff800`02e8726c cc              int     3
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+505d0
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  4fa390f3
    FAILURE_BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+505d0
    BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+505d0
    Followup: MachineOwner
    --------------------------------------------------------------------------------------------------------------------------------------------------------------------

    Bug Check 0x7a : http://msdn.microsoft.com/en-us/library/windows/hardware/ff559211(v=vs.85).aspx

    ** try to Run The system checker   SFC /SCANNOW   ,  also Run This Command in CMD.

    Start ---> Run... ---> CMD --->  Chkdsk /f /r

    will restart your computer and checking your HDD for errors.

    Regards,


    MCT / MCITP / MCTS / MCSA / MCSE / C|EH

    • Proposed as answer by tracycai Wednesday, August 22, 2012 8:03 AM
    • Marked as answer by Cloud_TS Thursday, August 23, 2012 2:06 AM
    Sunday, August 5, 2012 12:10 PM
  • Adding on other advise, you could also download the HD utility from it's manufacturer website to run a test on the drive itself. Alternatively you might also want to run memtest or windows memory diagnostic to ensure the problem does not lies with the ram

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

    • Proposed as answer by tracycai Wednesday, August 22, 2012 8:04 AM
    • Marked as answer by Cloud_TS Thursday, August 23, 2012 2:06 AM
    Monday, August 6, 2012 10:17 AM
    Answerer
  • Please check the below link

    https://onedrive.live.com/redir?resid=6CB3B43C2BD0BF32!107&authkey=!AFzXv8urMjarb-Q&ithint=file%2cdmp

    Tuesday, August 12, 2014 8:42 AM