Windows 2008 R2 - fully patched terminal server will bluescreen (sometimes) when shadowing other users. Here is what my minidump says:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Desktop\debug\072312-16140-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: Server, suite: TerminalServer
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`01652000 PsLoadedModuleList = 0xfffff800`01896670
Debug session time: Mon Jul 23 10:52:49.935 2012 (UTC - 5:00)
System Uptime: 3 days 7:41:26.004
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
...................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff960001bd3f6, fffff88007a66ee0, 0}
Probably caused by : win32k.sys ( win32k!EngFileIoControl+22 )
Followup: MachineOwner
---------
3: 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: fffff960001bd3f6, Address of the instruction which caused the bugcheck
Arg3: fffff88007a66ee0, 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!EngFileIoControl+22
fffff960`001bd3f6 f6415002 test byte ptr [rcx+50h],2
CONTEXT: fffff88007a66ee0 -- (.cxr 0xfffff88007a66ee0)
rax=0000000000000000 rbx=fffff88007a679f0 rcx=0000000000000000
rdx=0000000000381483 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960001bd3f6 rsp=fffff88007a678c0 rbp=fffffa800491d830
r8=fffff88007a679a0 r9=0000000000000014 r10=fffffa8003d099e0
r11=fffff88007a678e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
win32k!EngFileIoControl+0x22:
fffff960`001bd3f6 f6415002 test byte ptr [rcx+50h],2 ds:002b:00000000`00000050=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
BUGCHECK_STR: 0x3B
PROCESS_NAME: NotificationMa
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff960001bd3f6
STACK_TEXT:
fffff880`07a678c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!EngFileIoControl+0x22
FOLLOWUP_IP:
win32k!EngFileIoControl+22
fffff960`001bd3f6 f6415002 test byte ptr [rcx+50h],2
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!EngFileIoControl+22
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4fd6b298
STACK_COMMAND: .cxr 0xfffff88007a66ee0 ; kb
FAILURE_BUCKET_ID: X64_0x3B_win32k!EngFileIoControl+22
BUCKET_ID: X64_0x3B_win32k!EngFileIoControl+22
Followup: MachineOwner
---------