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\012311-35459-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e65000 PsLoadedModuleList = 0xfffff800`030a2e50
Debug session time: Sun Jan 23 23:26:10.854 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:54.884
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 A, {0, 2, 0, fffff80002ef52b3}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
Followup: MachineOwner
---------
6: 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: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80002ef52b3, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310d0e0
0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!IopCompleteRequest+ae3
fffff800`02ef52b3 488b09 mov rcx,qword ptr [rcx]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: Soluto.exe
IRP_ADDRESS: ffffffffffffff89
TRAP_FRAME: fffff88009d9a410 -- (.trap 0xfffff88009d9a410)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88009d9a428 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ef52b3 rsp=fffff88009d9a5a0 rbp=0000000000000000
r8=fffffa800891b2f0 r9=fffff88009d9a6a0 r10=0000000000000002
r11=fffffa8008657010 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po cy
nt!IopCompleteRequest+0xae3:
fffff800`02ef52b3 488b09 mov rcx,qword ptr [rcx] ds:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002ed4ca9 to fffff80002ed5740
STACK_TEXT:
fffff880`09d9a2c8 fffff800`02ed4ca9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`09d9a2d0 fffff800`02ed3920 : 00000000`00000000 fffffa80`08f2e4b0 00000001`00000080 fffff880`09d9a428 : nt!KiBugCheckDispatch+0x69
fffff880`09d9a410 fffff800`02ef52b3 : fffffa80`08f0a6f0 fffff800`02edb5da 00000001`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`09d9a5a0 fffff800`02eb20c7 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopCompleteRequest+0xae3
fffff880`09d9a670 fffff800`02edcb9d : fffffa80`08f0a6f0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`09d9a6f0 fffff800`02edecff : 00000000`00000000 00000000`00000000 0000007f`00000000 fffffa80`06b08e40 : nt!KiCommitThreadWait+0x3dd
fffff880`09d9a780 fffff800`02e971a2 : fffff8a0`00006200 00000000`00000022 00000000`00000100 fffff800`00000000 : nt!KeWaitForSingleObject+0x19f
fffff880`09d9a820 fffff800`02eeb2f1 : fffffa80`08dcd1c8 fffff800`031cfb54 00000000`00000000 fffff880`09d9a9c4 : nt!KiAcquireFastMutex+0x4e
fffff880`09d9a860 fffffa80`06cb167e : 00000000`00000000 fffff800`030094d3 fffffa80`06cb34b8 00000000`00000010 : nt!ExAcquireFastMutexUnsafe+0x31
fffff880`09d9a890 00000000`00000000 : fffff800`030094d3 fffffa80`06cb34b8 00000000`00000010 fffff8a0`02470722 : 0xfffffa80`06cb167e
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiPageFault+260
fffff800`02ed3920 440f20c0 mov rax,cr8
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiPageFault+260
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0xA_nt!KiPageFault+260
BUCKET_ID: X64_0xA_nt!KiPageFault+260
Followup: MachineOwner
---------