*******************************************************************************
* *
* 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: fffff6fc40018d88, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 00002001068c2be0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff880031b1000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
------------------
fffff800030370e8: Unable to get Flags value from nt!KdVersionBlock
GetUlongPtrFromAddress: unable to read from fffff800030f2300
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 5
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on AHMET
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 9
Key : Analysis.Memory.CommitPeak.Mb
Value: 59
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: 7a
BUGCHECK_P1: fffff6fc40018d88
BUGCHECK_P2: ffffffffc000000e
BUGCHECK_P3: 2001068c2be0
BUGCHECK_P4: fffff880031b1000
ERROR_CODE: (NTSTATUS) 0xc000000e - Varolmayan bir ayg t belirtildi.
DISK_HARDWARE_ERROR: There was error with disk hardware
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff880`0332b898 fffff800`02fb1ece : 00000000`0000007a fffff6fc`40018d88 ffffffff`c000000e 00002001`068c2be0 : nt!KeBugCheckEx
fffff880`0332b8a0 fffff800`02fbdff8 : fffffa80`06a25e90 fffff880`0332b9c0 fffff800`030f5540 ffffffff`ffffffff : nt!MiWaitForInPageComplete+0x63e
fffff880`0332b970 fffff800`02fc4eb0 : ffffffff`ffffffff 00000000`00000001 00000000`c0033333 ffffffff`ffffffff : nt!MiIssueHardFault+0x4b8
fffff880`0332ba10 fffff800`02fed40e : 00000000`00000001 fffff880`031b1000 fffffa80`06a3d000 fffff6fc`40018d60 : nt!MmAccessFault+0x4820
fffff880`0332bb60 fffff800`02eb6e80 : 00000000`00000001 fffff880`0332bc90 00000000`00000000 00000000`00000000 : nt!MiInPageSingleKernelStack+0x23e
fffff880`0332bc70 fffff800`02eb5ac3 : fffffa80`0520fb50 fffffa80`05189710 00000000`00000001 00000000`00000080 : nt!MmInPageKernelStack+0x40
fffff880`0332bcd0 fffff800`02eb5a9c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInSwapKernelStacks+0x1f
fffff880`0332bd00 fffff800`031942e8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSwapProcessOrStack+0x84
fffff880`0332bd40 fffff800`02eeeec6 : fffff880`02f63180 fffffa80`0520fb50 fffff880`02f72140 00000000`00000000 : nt!PspSystemThreadStartup+0x194
fffff880`0332bd80 00000000`00000000 : fffff880`0332c000 fffff880`03326000 fffff880`0332ba50 00000000`00000000 : nt!KiStartSystemThread+0x16
SYMBOL_NAME: nt!MiWaitForInPageComplete+63e
MODULE_NAME: nt
IMAGE_VERSION: 6.1.7601.24545
STACK_COMMAND: .thread ; .cxr ; kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x7a_c000000e_nt!MiWaitForInPageComplete+63e
OS_VERSION: 7.1.7601.24545
BUILDLAB_STR: win7sp1_ldr_escrow
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
FAILURE_ID_HASH: {e9aa3497-7e64-9715-9a20-fae8e75e1401}
Followup: MachineOwner
---------
