locked
KERNEL_DATA_INPAGE_ERROR (7a) RRS feed

  • Question

  • Hi,

    Getting blue screen error......

    I am running Windows 7 and it is a Dell xps L401x Laptop. I already formatted my laptop. check with CHKDSK various tool of Hiren booCD but nothing found.

    finally i run the debug and get the report which is paste below due to lack of knowledge i am unable to know the exect

    problem and solution...Thanks

    link for mini dump file

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

    Debugging report...............

    Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\081114-21762-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available


    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       srv*http://msdl.microsoft.com/download/symbols
    Symbol search path is: srv*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Machine Name:
    Kernel base = 0xfffff800`02e5e000 PsLoadedModuleList = 0xfffff800`030a1890
    Debug session time: Mon Aug 11 20:05:01.977 2014 (UTC - 7:00)
    System Uptime: 0 days 8:57:27.329
    Loading Kernel Symbols
    .

    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.

    ..............................................................
    ................................................................
    .....................................
    Loading User Symbols
    Loading unloaded module list
    .............
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 7A, {fffff6fc40044088, ffffffffc000000e, 77fdf860, fffff88008811087}

    *** WARNING: Unable to verify timestamp for RTKVHD64.sys
    *** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys
    Probably caused by : hardware ( RTKVHD64+198087 )

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

    2: 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: fffff6fc40044088, lock type that was held (value 1,2,3, or PTE address)
    Arg2: ffffffffc000000e, error status (normally i/o status code)
    Arg3: 0000000077fdf860, current process (virtual address for lock type 3, or PTE)
    Arg4: fffff88008811087, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

    Debugging Details:
    ------------------


    ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

    DISK_HARDWARE_ERROR: There was error with disk hardware

    BUGCHECK_STR:  0x7a_c000000e

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

    TRAP_FRAME:  fffff88007dbe4a0 -- (.trap 0xfffff88007dbe4a0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=00000000c00000bb rbx=0000000000000000 rcx=000000000000001b
    rdx=fffffa80064db000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88008811087 rsp=fffff88007dbe630 rbp=fffffa800666fc0f
     r8=fffffa8006292000  r9=0000000000000000 r10=fffff88007dbe440
    r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    RTKVHD64+0x198087:
    fffff880`08811087 ffb45807ffb458  push    qword ptr [rax+rbx*2+58B4FF07h] ds:00000001`18b4ffc2=????????????????
    Resetting default scope

    MISALIGNED_IP: 
    RTKVHD64+198087
    fffff880`08811087 ffb45807ffb458  push    qword ptr [rax+rbx*2+58B4FF07h]

    LAST_CONTROL_TRANSFER:  from fffff80002f46752 to fffff80002ed3bc0

    STACK_TEXT:  
    fffff880`07dbe188 fffff800`02f46752 : 00000000`0000007a fffff6fc`40044088 ffffffff`c000000e 00000000`77fdf860 : nt!KeBugCheckEx
    fffff880`07dbe190 fffff800`02efa91f : fffffa80`054341c0 fffff880`07dbe300 fffff800`0310e540 fffffa80`054341c0 : nt! ?? ::FNODOBFM::`string'+0x36c1a
    fffff880`07dbe270 fffff800`02ee11b9 : 00000000`00000000 00000000`00000008 ffffffff`ffffffff fffff880`04465ae9 : nt!MiIssueHardFault+0x28b
    fffff880`07dbe340 fffff800`02ed1cee : 00000000`00000008 fffff880`08811087 00000000`ffffff00 00000000`00000005 : nt!MmAccessFault+0x1399
    fffff880`07dbe4a0 fffff880`08811087 : 00000000`00000000 00000000`00000005 ffff0000`0fa372cc fffffa80`0666f2d0 : nt!KiPageFault+0x16e
    fffff880`07dbe630 00000000`00000000 : 00000000`00000005 ffff0000`0fa372cc fffffa80`0666f2d0 fffff880`07dbe7b0 : RTKVHD64+0x198087


    STACK_COMMAND:  kb

    FOLLOWUP_IP: 
    RTKVHD64+198087
    fffff880`08811087 ffb45807ffb458  push    qword ptr [rax+rbx*2+58B4FF07h]

    SYMBOL_STACK_INDEX:  5

    SYMBOL_NAME:  RTKVHD64+198087

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: hardware

    IMAGE_NAME:  hardware

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_RTKVHD64.sys

    BUCKET_ID:  X64_IP_MISALIGNED_RTKVHD64.sys

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:x64_ip_misaligned_rtkvhd64.sys

    FAILURE_ID_HASH:  {a2776c08-6e06-71ea-9f78-79cfb284ff53}

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

    2: 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: fffff6fc40044088, lock type that was held (value 1,2,3, or PTE address)
    Arg2: ffffffffc000000e, error status (normally i/o status code)
    Arg3: 0000000077fdf860, current process (virtual address for lock type 3, or PTE)
    Arg4: fffff88008811087, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

    Debugging Details:
    ------------------


    ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

    DISK_HARDWARE_ERROR: There was error with disk hardware

    BUGCHECK_STR:  0x7a_c000000e

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

    TRAP_FRAME:  fffff88007dbe4a0 -- (.trap 0xfffff88007dbe4a0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=00000000c00000bb rbx=0000000000000000 rcx=000000000000001b
    rdx=fffffa80064db000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88008811087 rsp=fffff88007dbe630 rbp=fffffa800666fc0f
     r8=fffffa8006292000  r9=0000000000000000 r10=fffff88007dbe440
    r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    RTKVHD64+0x198087:
    fffff880`08811087 ffb45807ffb458  push    qword ptr [rax+rbx*2+58B4FF07h] ds:00000001`18b4ffc2=????????????????
    Resetting default scope

    MISALIGNED_IP: 
    RTKVHD64+198087
    fffff880`08811087 ffb45807ffb458  push    qword ptr [rax+rbx*2+58B4FF07h]

    LAST_CONTROL_TRANSFER:  from fffff80002f46752 to fffff80002ed3bc0

    STACK_TEXT:  
    fffff880`07dbe188 fffff800`02f46752 : 00000000`0000007a fffff6fc`40044088 ffffffff`c000000e 00000000`77fdf860 : nt!KeBugCheckEx
    fffff880`07dbe190 fffff800`02efa91f : fffffa80`054341c0 fffff880`07dbe300 fffff800`0310e540 fffffa80`054341c0 : nt! ?? ::FNODOBFM::`string'+0x36c1a
    fffff880`07dbe270 fffff800`02ee11b9 : 00000000`00000000 00000000`00000008 ffffffff`ffffffff fffff880`04465ae9 : nt!MiIssueHardFault+0x28b
    fffff880`07dbe340 fffff800`02ed1cee : 00000000`00000008 fffff880`08811087 00000000`ffffff00 00000000`00000005 : nt!MmAccessFault+0x1399
    fffff880`07dbe4a0 fffff880`08811087 : 00000000`00000000 00000000`00000005 ffff0000`0fa372cc fffffa80`0666f2d0 : nt!KiPageFault+0x16e
    fffff880`07dbe630 00000000`00000000 : 00000000`00000005 ffff0000`0fa372cc fffffa80`0666f2d0 fffff880`07dbe7b0 : RTKVHD64+0x198087


    STACK_COMMAND:  kb

    FOLLOWUP_IP: 
    RTKVHD64+198087
    fffff880`08811087 ffb45807ffb458  push    qword ptr [rax+rbx*2+58B4FF07h]

    SYMBOL_STACK_INDEX:  5

    SYMBOL_NAME:  RTKVHD64+198087

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: hardware

    IMAGE_NAME:  hardware

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_RTKVHD64.sys

    BUCKET_ID:  X64_IP_MISALIGNED_RTKVHD64.sys

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:x64_ip_misaligned_rtkvhd64.sys

    FAILURE_ID_HASH:  {a2776c08-6e06-71ea-9f78-79cfb284ff53}

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

    2: 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: fffff6fc40044088, lock type that was held (value 1,2,3, or PTE address)
    Arg2: ffffffffc000000e, error status (normally i/o status code)
    Arg3: 0000000077fdf860, current process (virtual address for lock type 3, or PTE)
    Arg4: fffff88008811087, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

    Debugging Details:
    ------------------


    ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

    DISK_HARDWARE_ERROR: There was error with disk hardware

    BUGCHECK_STR:  0x7a_c000000e

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

    TRAP_FRAME:  fffff88007dbe4a0 -- (.trap 0xfffff88007dbe4a0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=00000000c00000bb rbx=0000000000000000 rcx=000000000000001b
    rdx=fffffa80064db000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88008811087 rsp=fffff88007dbe630 rbp=fffffa800666fc0f
     r8=fffffa8006292000  r9=0000000000000000 r10=fffff88007dbe440
    r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    RTKVHD64+0x198087:
    fffff880`08811087 ffb45807ffb458  push    qword ptr [rax+rbx*2+58B4FF07h] ds:00000001`18b4ffc2=????????????????
    Resetting default scope

    MISALIGNED_IP: 
    RTKVHD64+198087
    fffff880`08811087 ffb45807ffb458  push    qword ptr [rax+rbx*2+58B4FF07h]

    LAST_CONTROL_TRANSFER:  from fffff80002f46752 to fffff80002ed3bc0

    STACK_TEXT:  
    fffff880`07dbe188 fffff800`02f46752 : 00000000`0000007a fffff6fc`40044088 ffffffff`c000000e 00000000`77fdf860 : nt!KeBugCheckEx
    fffff880`07dbe190 fffff800`02efa91f : fffffa80`054341c0 fffff880`07dbe300 fffff800`0310e540 fffffa80`054341c0 : nt! ?? ::FNODOBFM::`string'+0x36c1a
    fffff880`07dbe270 fffff800`02ee11b9 : 00000000`00000000 00000000`00000008 ffffffff`ffffffff fffff880`04465ae9 : nt!MiIssueHardFault+0x28b
    fffff880`07dbe340 fffff800`02ed1cee : 00000000`00000008 fffff880`08811087 00000000`ffffff00 00000000`00000005 : nt!MmAccessFault+0x1399
    fffff880`07dbe4a0 fffff880`08811087 : 00000000`00000000 00000000`00000005 ffff0000`0fa372cc fffffa80`0666f2d0 : nt!KiPageFault+0x16e
    fffff880`07dbe630 00000000`00000000 : 00000000`00000005 ffff0000`0fa372cc fffffa80`0666f2d0 fffff880`07dbe7b0 : RTKVHD64+0x198087


    STACK_COMMAND:  kb

    FOLLOWUP_IP: 
    RTKVHD64+198087
    fffff880`08811087 ffb45807ffb458  push    qword ptr [rax+rbx*2+58B4FF07h]

    SYMBOL_STACK_INDEX:  5

    SYMBOL_NAME:  RTKVHD64+198087

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: hardware

    IMAGE_NAME:  hardware

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_RTKVHD64.sys

    BUCKET_ID:  X64_IP_MISALIGNED_RTKVHD64.sys

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:x64_ip_misaligned_rtkvhd64.sys

    FAILURE_ID_HASH:  {a2776c08-6e06-71ea-9f78-79cfb284ff53}

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

    2: 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: fffff6fc40044088, lock type that was held (value 1,2,3, or PTE address)
    Arg2: ffffffffc000000e, error status (normally i/o status code)
    Arg3: 0000000077fdf860, current process (virtual address for lock type 3, or PTE)
    Arg4: fffff88008811087, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

    Debugging Details:
    ------------------


    ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

    DISK_HARDWARE_ERROR: There was error with disk hardware

    BUGCHECK_STR:  0x7a_c000000e

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

    TRAP_FRAME:  fffff88007dbe4a0 -- (.trap 0xfffff88007dbe4a0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=00000000c00000bb rbx=0000000000000000 rcx=000000000000001b
    rdx=fffffa80064db000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88008811087 rsp=fffff88007dbe630 rbp=fffffa800666fc0f
     r8=fffffa8006292000  r9=0000000000000000 r10=fffff88007dbe440
    r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    RTKVHD64+0x198087:
    fffff880`08811087 ffb45807ffb458  push    qword ptr [rax+rbx*2+58B4FF07h] ds:00000001`18b4ffc2=????????????????
    Resetting default scope

    MISALIGNED_IP: 
    RTKVHD64+198087
    fffff880`08811087 ffb45807ffb458  push    qword ptr [rax+rbx*2+58B4FF07h]

    LAST_CONTROL_TRANSFER:  from fffff80002f46752 to fffff80002ed3bc0

    STACK_TEXT:  
    fffff880`07dbe188 fffff800`02f46752 : 00000000`0000007a fffff6fc`40044088 ffffffff`c000000e 00000000`77fdf860 : nt!KeBugCheckEx
    fffff880`07dbe190 fffff800`02efa91f : fffffa80`054341c0 fffff880`07dbe300 fffff800`0310e540 fffffa80`054341c0 : nt! ?? ::FNODOBFM::`string'+0x36c1a
    fffff880`07dbe270 fffff800`02ee11b9 : 00000000`00000000 00000000`00000008 ffffffff`ffffffff fffff880`04465ae9 : nt!MiIssueHardFault+0x28b
    fffff880`07dbe340 fffff800`02ed1cee : 00000000`00000008 fffff880`08811087 00000000`ffffff00 00000000`00000005 : nt!MmAccessFault+0x1399
    fffff880`07dbe4a0 fffff880`08811087 : 00000000`00000000 00000000`00000005 ffff0000`0fa372cc fffffa80`0666f2d0 : nt!KiPageFault+0x16e
    fffff880`07dbe630 00000000`00000000 : 00000000`00000005 ffff0000`0fa372cc fffffa80`0666f2d0 fffff880`07dbe7b0 : RTKVHD64+0x198087


    STACK_COMMAND:  kb

    FOLLOWUP_IP: 
    RTKVHD64+198087
    fffff880`08811087 ffb45807ffb458  push    qword ptr [rax+rbx*2+58B4FF07h]

    SYMBOL_STACK_INDEX:  5

    SYMBOL_NAME:  RTKVHD64+198087

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: hardware

    IMAGE_NAME:  hardware

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_RTKVHD64.sys

    BUCKET_ID:  X64_IP_MISALIGNED_RTKVHD64.sys

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:x64_ip_misaligned_rtkvhd64.sys

    FAILURE_ID_HASH:  {a2776c08-6e06-71ea-9f78-79cfb284ff53}

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

    2: 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: fffff6fc40044088, lock type that was held (value 1,2,3, or PTE address)
    Arg2: ffffffffc000000e, error status (normally i/o status code)
    Arg3: 0000000077fdf860, current process (virtual address for lock type 3, or PTE)
    Arg4: fffff88008811087, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

    Debugging Details:
    ------------------


    ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

    DISK_HARDWARE_ERROR: There was error with disk hardware

    BUGCHECK_STR:  0x7a_c000000e

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

    TRAP_FRAME:  fffff88007dbe4a0 -- (.trap 0xfffff88007dbe4a0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=00000000c00000bb rbx=0000000000000000 rcx=000000000000001b
    rdx=fffffa80064db000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88008811087 rsp=fffff88007dbe630 rbp=fffffa800666fc0f
     r8=fffffa8006292000  r9=0000000000000000 r10=fffff88007dbe440
    r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    RTKVHD64+0x198087:
    fffff880`08811087 ffb45807ffb458  push    qword ptr [rax+rbx*2+58B4FF07h] ds:00000001`18b4ffc2=????????????????
    Resetting default scope

    MISALIGNED_IP: 
    RTKVHD64+198087
    fffff880`08811087 ffb45807ffb458  push    qword ptr [rax+rbx*2+58B4FF07h]

    LAST_CONTROL_TRANSFER:  from fffff80002f46752 to fffff80002ed3bc0

    STACK_TEXT:  
    fffff880`07dbe188 fffff800`02f46752 : 00000000`0000007a fffff6fc`40044088 ffffffff`c000000e 00000000`77fdf860 : nt!KeBugCheckEx
    fffff880`07dbe190 fffff800`02efa91f : fffffa80`054341c0 fffff880`07dbe300 fffff800`0310e540 fffffa80`054341c0 : nt! ?? ::FNODOBFM::`string'+0x36c1a
    fffff880`07dbe270 fffff800`02ee11b9 : 00000000`00000000 00000000`00000008 ffffffff`ffffffff fffff880`04465ae9 : nt!MiIssueHardFault+0x28b
    fffff880`07dbe340 fffff800`02ed1cee : 00000000`00000008 fffff880`08811087 00000000`ffffff00 00000000`00000005 : nt!MmAccessFault+0x1399
    fffff880`07dbe4a0 fffff880`08811087 : 00000000`00000000 00000000`00000005 ffff0000`0fa372cc fffffa80`0666f2d0 : nt!KiPageFault+0x16e
    fffff880`07dbe630 00000000`00000000 : 00000000`00000005 ffff0000`0fa372cc fffffa80`0666f2d0 fffff880`07dbe7b0 : RTKVHD64+0x198087


    STACK_COMMAND:  kb

    FOLLOWUP_IP: 
    RTKVHD64+198087
    fffff880`08811087 ffb45807ffb458  push    qword ptr [rax+rbx*2+58B4FF07h]

    SYMBOL_STACK_INDEX:  5

    SYMBOL_NAME:  RTKVHD64+198087

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: hardware

    IMAGE_NAME:  hardware

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_RTKVHD64.sys

    BUCKET_ID:  X64_IP_MISALIGNED_RTKVHD64.sys

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:x64_ip_misaligned_rtkvhd64.sys

    FAILURE_ID_HASH:  {a2776c08-6e06-71ea-9f78-79cfb284ff53}

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

    2: 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: fffff6fc40044088, lock type that was held (value 1,2,3, or PTE address)
    Arg2: ffffffffc000000e, error status (normally i/o status code)
    Arg3: 0000000077fdf860, current process (virtual address for lock type 3, or PTE)
    Arg4: fffff88008811087, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

    Debugging Details:
    ------------------


    ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

    DISK_HARDWARE_ERROR: There was error with disk hardware

    BUGCHECK_STR:  0x7a_c000000e

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

    TRAP_FRAME:  fffff88007dbe4a0 -- (.trap 0xfffff88007dbe4a0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=00000000c00000bb rbx=0000000000000000 rcx=000000000000001b
    rdx=fffffa80064db000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88008811087 rsp=fffff88007dbe630 rbp=fffffa800666fc0f
     r8=fffffa8006292000  r9=0000000000000000 r10=fffff88007dbe440
    r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    RTKVHD64+0x198087:
    fffff880`08811087 ffb45807ffb458  push    qword ptr [rax+rbx*2+58B4FF07h] ds:00000001`18b4ffc2=????????????????
    Resetting default scope

    MISALIGNED_IP: 
    RTKVHD64+198087
    fffff880`08811087 ffb45807ffb458  push    qword ptr [rax+rbx*2+58B4FF07h]

    LAST_CONTROL_TRANSFER:  from fffff80002f46752 to fffff80002ed3bc0

    STACK_TEXT:  
    fffff880`07dbe188 fffff800`02f46752 : 00000000`0000007a fffff6fc`40044088 ffffffff`c000000e 00000000`77fdf860 : nt!KeBugCheckEx
    fffff880`07dbe190 fffff800`02efa91f : fffffa80`054341c0 fffff880`07dbe300 fffff800`0310e540 fffffa80`054341c0 : nt! ?? ::FNODOBFM::`string'+0x36c1a
    fffff880`07dbe270 fffff800`02ee11b9 : 00000000`00000000 00000000`00000008 ffffffff`ffffffff fffff880`04465ae9 : nt!MiIssueHardFault+0x28b
    fffff880`07dbe340 fffff800`02ed1cee : 00000000`00000008 fffff880`08811087 00000000`ffffff00 00000000`00000005 : nt!MmAccessFault+0x1399
    fffff880`07dbe4a0 fffff880`08811087 : 00000000`00000000 00000000`00000005 ffff0000`0fa372cc fffffa80`0666f2d0 : nt!KiPageFault+0x16e
    fffff880`07dbe630 00000000`00000000 : 00000000`00000005 ffff0000`0fa372cc fffffa80`0666f2d0 fffff880`07dbe7b0 : RTKVHD64+0x198087


    STACK_COMMAND:  kb

    FOLLOWUP_IP: 
    RTKVHD64+198087
    fffff880`08811087 ffb45807ffb458  push    qword ptr [rax+rbx*2+58B4FF07h]

    SYMBOL_STACK_INDEX:  5

    SYMBOL_NAME:  RTKVHD64+198087

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: hardware

    IMAGE_NAME:  hardware

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_RTKVHD64.sys

    BUCKET_ID:  X64_IP_MISALIGNED_RTKVHD64.sys

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:x64_ip_misaligned_rtkvhd64.sys

    FAILURE_ID_HASH:  {a2776c08-6e06-71ea-9f78-79cfb284ff53}

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

    2: 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: fffff6fc40044088, lock type that was held (value 1,2,3, or PTE address)
    Arg2: ffffffffc000000e, error status (normally i/o status code)
    Arg3: 0000000077fdf860, current process (virtual address for lock type 3, or PTE)
    Arg4: fffff88008811087, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

    Debugging Details:
    ------------------


    ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

    DISK_HARDWARE_ERROR: There was error with disk hardware

    BUGCHECK_STR:  0x7a_c000000e

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

    TRAP_FRAME:  fffff88007dbe4a0 -- (.trap 0xfffff88007dbe4a0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=00000000c00000bb rbx=0000000000000000 rcx=000000000000001b
    rdx=fffffa80064db000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88008811087 rsp=fffff88007dbe630 rbp=fffffa800666fc0f
     r8=fffffa8006292000  r9=0000000000000000 r10=fffff88007dbe440
    r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    RTKVHD64+0x198087:
    fffff880`08811087 ffb45807ffb458  push    qword ptr [rax+rbx*2+58B4FF07h] ds:00000001`18b4ffc2=????????????????
    Resetting default scope

    MISALIGNED_IP: 
    RTKVHD64+198087
    fffff880`08811087 ffb45807ffb458  push    qword ptr [rax+rbx*2+58B4FF07h]

    LAST_CONTROL_TRANSFER:  from fffff80002f46752 to fffff80002ed3bc0

    STACK_TEXT:  
    fffff880`07dbe188 fffff800`02f46752 : 00000000`0000007a fffff6fc`40044088 ffffffff`c000000e 00000000`77fdf860 : nt!KeBugCheckEx
    fffff880`07dbe190 fffff800`02efa91f : fffffa80`054341c0 fffff880`07dbe300 fffff800`0310e540 fffffa80`054341c0 : nt! ?? ::FNODOBFM::`string'+0x36c1a
    fffff880`07dbe270 fffff800`02ee11b9 : 00000000`00000000 00000000`00000008 ffffffff`ffffffff fffff880`04465ae9 : nt!MiIssueHardFault+0x28b
    fffff880`07dbe340 fffff800`02ed1cee : 00000000`00000008 fffff880`08811087 00000000`ffffff00 00000000`00000005 : nt!MmAccessFault+0x1399
    fffff880`07dbe4a0 fffff880`08811087 : 00000000`00000000 00000000`00000005 ffff0000`0fa372cc fffffa80`0666f2d0 : nt!KiPageFault+0x16e
    fffff880`07dbe630 00000000`00000000 : 00000000`00000005 ffff0000`0fa372cc fffffa80`0666f2d0 fffff880`07dbe7b0 : RTKVHD64+0x198087


    STACK_COMMAND:  kb

    FOLLOWUP_IP: 
    RTKVHD64+198087
    fffff880`08811087 ffb45807ffb458  push    qword ptr [rax+rbx*2+58B4FF07h]

    SYMBOL_STACK_INDEX:  5

    SYMBOL_NAME:  RTKVHD64+198087

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: hardware

    IMAGE_NAME:  hardware

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_RTKVHD64.sys

    BUCKET_ID:  X64_IP_MISALIGNED_RTKVHD64.sys

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:x64_ip_misaligned_rtkvhd64.sys

    FAILURE_ID_HASH:  {a2776c08-6e06-71ea-9f78-79cfb284ff53}

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

    2: kd> lmvm hardware
    start             end                 module name
    2: kd> lmvm hardware
    start             end                 module name

    Tuesday, August 12, 2014 8:27 AM

All replies

  • Please share the original DMP files for the BSOD. 

    Arnav Sharma | http://arnavsharma.net/ 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.

    Tuesday, August 12, 2014 8:35 AM
  • Thanks for you Reply

    Please check the blow link.

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

    Tuesday, August 12, 2014 8:47 AM