none
BSOD - ntoskrnl.exe KERNEL_DATA_INPAGE_ERROR WIN 7 x64

    Question

  • My PC seems to shut down due to an unexpected error, always after i leave for the day. 

    Via event viewer i get a critical error referencing Kernel-Power event id 41 and a Bugcheck error
    stating  the following:

    The bugcheck was: 0x0000007a (0x0000000000000020, 0xffffffffc000009d, 0xfffffa800655f7c8, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 090910-34023-01.

    More info in the reboot:


    ==================================================
    Dump File         : 090910-34023-01.dmp
    Crash Time        : 9/9/2010 7:59:33 AM
    Bug Check String  : KERNEL_DATA_INPAGE_ERROR
    Bug Check Code    : 0x0000007a
    Parameter 1       : 00000000`00000020
    Parameter 2       : ffffffff`c000009d
    Parameter 3       : fffffa80`0655f7c8
    Parameter 4       : 00000000`00000000
    Caused By Driver  : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+70740
    File Description  : NT Kernel & System
    Product Name      : Microsoft® Windows® Operating System
    Company           : Microsoft Corporation
    File Version      : 6.1.7600.16617 (win7_gdr.100618-1621)
    Processor         : x64
    Computer Name     :
    Full Path         : C:\Windows\Minidump\090910-34023-01.dmp
    Processors Count  : 2
    Major Version     : 15
    Minor Version     : 7600
    ==================================================

    Dump Info:

    0: 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: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
    Arg2: ffffffffc000009d, error status (normally i/o status code)
    Arg3: fffffa800655f7c8, 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:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  1

    LAST_CONTROL_TRANSFER:  from fffff800029073fc to fffff800028cf740

    STACK_TEXT: 
    fffff880`0312b7e8 fffff800`029073fc : 00000000`0000007a 00000000`00000020 ffffffff`c000009d fffffa80`0655f7c8 : nt!KeBugCheckEx
    fffff880`0312b7f0 fffff800`028b9637 : fffffa80`0655f760 00000000`c000009d 00000000`00000000 fffffa80`0655f7f8 : nt! ?? ::FNODOBFM::`string'+0x4c5e0
    fffff880`0312b8b0 fffff800`028ac0c7 : fffffa80`04e49b60 fffffa80`04e49bb0 fffffa80`06717e10 ffff0000`0234689e : nt!IopCompletePageWrite+0x57
    fffff880`0312b8e0 fffff800`028d6b9d : fffffa80`04e49b60 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
    fffff880`0312b960 fffff800`028d2d4b : fffffa80`055b5d90 ffffffff`ffffffff 00000000`00000000 fffffa80`00000204 : nt!KiCommitThreadWait+0x3dd
    fffff880`0312b9f0 fffff800`02869abf : fffffa80`00000002 fffff880`0312bce0 00000000`00000001 fffffa80`00000013 : nt!KeWaitForMultipleObjects+0x271
    fffff880`0312bca0 fffff800`02b73c06 : fffffa80`04e49b60 00000000`00000000 00000000`00000080 00000000`00000001 : nt!MiModifiedPageWriter+0xcf
    fffff880`0312bd00 fffff800`028adc26 : fffff800`02a49e80 fffffa80`04e49b60 fffff800`02a57c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`0312bd40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt! ?? ::FNODOBFM::`string'+4c5e0
    fffff800`029073fc cc              int     3

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4c5e0

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

    FAILURE_BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c5e0

    BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c5e0

    Followup: MachineOwner
    ---------

     

    Any input/troubleshooting tips would be greatly appreciated!

    Slade1040

     

     

    Thursday, September 09, 2010 2:03 PM

Answers

All replies