Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\121209-28314-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*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
[B]Built by: 7600.16385.amd64fre.win7_rtm.090713-1255[/B]
Machine Name:
Kernel base = 0xfffff800`02c12000 PsLoadedModuleList = 0xfffff800`02e4fe50
Debug session time: Fri Dec 11 12:54:28.872 2009 (GMT-5)
System Uptime: 0 days 13:26:05.464
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff80002ccf5ad, 0, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt!KiDpcInterrupt+1d )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
[B]KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002ccf5ad, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception[/B]
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!KiDpcInterrupt+1d
fffff800`02ccf5ad 48cf iretq
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eba0e0
ffffffffffffffff
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002cc3a17 to fffff80002c83f00
STACK_TEXT:
fffff800`00b9c248 fffff800`02cc3a17 : 00000000`0000001e ffffffff`c0000005 fffff800`02ccf5ad 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c250 fffff800`02c83542 : fffff800`00b9ca28 00000000`00000000 fffff800`00b9cad0 fffff800`02dfce80 : nt! ?? ::FNODOBFM::`string'+0x460da
fffff800`00b9c8f0 fffff800`02c81e4a : fffff800`0321e301 fffff800`00b9cb80 00000000`00000000 fffff800`02c889fa : nt!KiExceptionDispatch+0xc2
fffff800`00b9cad0 fffff800`02ccf5ad : fffffa80`039a9970 fffff880`03fc09c2 00000000`00000010 00000000`00000246 : nt!KiGeneralProtectionFault+0x10a
fffff800`00b9cc60 fffffa80`039a9970 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x1d
00000000`00000246 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`039a9970
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiDpcInterrupt+1d
fffff800`02ccf5ad 48cf iretq
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: nt!KiDpcInterrupt+1d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
FAILURE_BUCKET_ID: X64_0x1E_nt!KiDpcInterrupt+1d
BUCKET_ID: X64_0x1E_nt!KiDpcInterrupt+1d
Followup: MachineOwner
---------
