Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\033011-29156-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02e61000 PsLoadedModuleList = 0xfffff800`030a6e90
Debug session time: Thu Mar 31 01:09:19.641 2011 (UTC - 4:00)
System Uptime: 0 days 3:03:56.233
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff960000ffbc8, fffff88006275160, 0}
Probably caused by : win32k.sys ( win32k!xxxDestroyWindow+160 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff960000ffbc8, Address of the instruction which caused the bugcheck
Arg3: fffff88006275160, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
win32k!xxxDestroyWindow+160
fffff960`000ffbc8 488b02 mov rax,qword ptr [rdx]
CONTEXT: fffff88006275160 -- (.cxr 0xfffff88006275160)
rax=fffff900c2153a60 rbx=fffff900c0877f10 rcx=000007ffffff0000
rdx=0080000000000000 rsi=0000000000000000 rdi=fffff900c2153a60
rip=fffff960000ffbc8 rsp=fffff88006275b40 rbp=0000000000000000
r8=fffff80002e61000 r9=0000000000000000 r10=fffff900c2153a60
r11=fffff88006275b10 r12=000000007efd8000 r13=000000000254fd20
r14=000000000254e990 r15=0000000075072450
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
win32k!xxxDestroyWindow+0x160:
fffff960`000ffbc8 488b02 mov rax,qword ptr [rdx] ds:002b:00800000`00000000=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: WerFault.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff9600010098b to fffff960000ffbc8
STACK_TEXT:
fffff880`06275b40 fffff960`0010098b : 00000000`00000000 00000000`00000000 fffff880`06275ca0 00000000`00000000 : win32k!xxxDestroyWindow+0x160
fffff880`06275bf0 fffff800`02ee08d3 : fffffa80`080a8490 fffff880`06275ca0 00000000`00e97f10 00000000`00000000 : win32k!NtUserDestroyWindow+0x3b
fffff880`06275c20 00000000`75072e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0254e918 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75072e09
FOLLOWUP_IP:
win32k!xxxDestroyWindow+160
fffff960`000ffbc8 488b02 mov rax,qword ptr [rdx]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!xxxDestroyWindow+160
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d2415ea
STACK_COMMAND: .cxr 0xfffff88006275160 ; kb
FAILURE_BUCKET_ID: X64_0x3B_win32k!xxxDestroyWindow+160
BUCKET_ID: X64_0x3B_win32k!xxxDestroyWindow+160
Followup: MachineOwner
---------