Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\DMP\010511-17082-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c51000 PsLoadedModuleList = 0xfffff800`02e8ee50
Debug session time: Wed Jan 5 10:00:49.620 2011 (UTC - 5:00)
System Uptime: 0 days 6:11:44.181
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffffa7fffffdaf0, 2, 1, fffff80002d08349}
Probably caused by : memory_corruption ( nt!MmZeroPageThread+3d4 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffa7fffffdaf0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002d08349, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef90e0
fffffa7fffffdaf0
CURRENT_IRQL: 2
FAULTING_IP:
nt!MmZeroPageThread+3d4
fffff800`02d08349 f0410fba6d1000 lock bts dword ptr [r13+10h],0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff880009a9a80 -- (.trap 0xfffff880009a9a80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000003a rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d08349 rsp=fffff880009a9c10 rbp=000000000000003f
r8=0000000000000000 r9=0000058000000000 r10=0000000000000002
r11=fffff880009a9c08 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!MmZeroPageThread+0x3d4:
fffff800`02d08349 f0410fba6d1000 lock bts dword ptr [r13+10h],0 ds:a040:00000000`00000010=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002cc0ca9 to fffff80002cc1740
STACK_TEXT:
fffff880`009a9938 fffff800`02cc0ca9 : 00000000`0000000a fffffa7f`ffffdaf0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`009a9940 fffff800`02cbf920 : 00000000`00000000 ffffffff`ffffff3a 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009a9a80 fffff800`02d08349 : 00000000`0000003f 00000000`00000032 00000000`00000004 00000000`00000000 : nt!KiPageFault+0x260
fffff880`009a9c10 fffff800`02f65c06 : fffffa80`036ca040 00000000`00000080 fffffa80`0366b9e0 fffff800`02c9fc19 : nt!MmZeroPageThread+0x3d4
fffff880`009a9d40 fffff800`02c9fc26 : fffff800`02e3be80 fffffa80`036ca040 fffff800`02e49c40 4127733c`5d3b0000 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a99b0 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MmZeroPageThread+3d4
fffff800`02d08349 f0410fba6d1000 lock bts dword ptr [r13+10h],0
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MmZeroPageThread+3d4
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0xA_nt!MmZeroPageThread+3d4
BUCKET_ID: X64_0xA_nt!MmZeroPageThread+3d4
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\DMP\010611-19484-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c01000 PsLoadedModuleList = 0xfffff800`02e3ee50
Debug session time: Thu Jan 6 08:54:26.440 2011 (UTC - 5:00)
System Uptime: 0 days 4:52:49.126
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffffa7fffffd7f0, 2, 1, fffff80002cb8349}
Probably caused by : memory_corruption ( nt!MmZeroPageThread+3d4 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffa7fffffd7f0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002cb8349, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ea90e0
fffffa7fffffd7f0
CURRENT_IRQL: 2
FAULTING_IP:
nt!MmZeroPageThread+3d4
fffff800`02cb8349 f0410fba6d1000 lock bts dword ptr [r13+10h],0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff880009a9a80 -- (.trap 0xfffff880009a9a80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000002a rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cb8349 rsp=fffff880009a9c10 rbp=000000000000003f
r8=0000000000000000 r9=0000058000000000 r10=0000000000000002
r11=fffff880009a9c08 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!MmZeroPageThread+0x3d4:
fffff800`02cb8349 f0410fba6d1000 lock bts dword ptr [r13+10h],0 ds:a040:00000000`00000010=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c70ca9 to fffff80002c71740
STACK_TEXT:
fffff880`009a9938 fffff800`02c70ca9 : 00000000`0000000a fffffa7f`ffffd7f0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`009a9940 fffff800`02c6f920 : 00000000`00000000 ffffffff`ffffff2a 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009a9a80 fffff800`02cb8349 : 00000000`0000003f 00000000`00000016 00000000`00000008 00000000`00000000 : nt!KiPageFault+0x260
fffff880`009a9c10 fffff800`02f15c06 : fffffa80`036ca040 00000000`00000080 fffffa80`0366b9e0 fffff800`02c4fc19 : nt!MmZeroPageThread+0x3d4
fffff880`009a9d40 fffff800`02c4fc26 : fffff800`02debe80 fffffa80`036ca040 fffff800`02df9c40 dedae6ff`ff6ecfb9 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a99b0 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MmZeroPageThread+3d4
fffff800`02cb8349 f0410fba6d1000 lock bts dword ptr [r13+10h],0
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MmZeroPageThread+3d4
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0xA_nt!MmZeroPageThread+3d4
BUCKET_ID: X64_0xA_nt!MmZeroPageThread+3d4
Followup: MachineOwner
---------