Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini032313-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: http://msdl.microsoft.com/download/symbols


Executable search path is: 
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Sat Mar 23 23:04:51.937 2013 (GMT+1)
System Uptime: 0 days 1:18:00.531
Loading Kernel Symbols
...............................................................
..............................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf804570, b1b4b768, 0}

Probably caused by : win32k.sys ( win32k!DEVLOCKOBJ::vDestructor+1b )

Followup: MachineOwner
---------

kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bf804570, The address that the exception occurred at
Arg3: b1b4b768, Trap Frame
Arg4: 00000000

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukce na adrese 0x%08lx odkazovala na adresu pam

FAULTING_IP: 
win32k!DEVLOCKOBJ::vDestructor+1b
bf804570 8b8094050000    mov     eax,dword ptr [eax+594h]

TRAP_FRAME:  b1b4b768 -- (.trap 0xffffffffb1b4b768)
ErrCode = 00000000
eax=00720063 ebx=7ffdf320 ecx=b1b47c00 edx=00000000 esi=b1b47c00 edi=00000000
eip=bf804570 esp=b1b4b7dc ebp=b1b4b924 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
win32k!DEVLOCKOBJ::vDestructor+0x1b:
bf804570 8b8094050000    mov     eax,dword ptr [eax+594h] ds:0023:007205f7=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  wuauclt.exe

LAST_CONTROL_TRANSFER:  from bf80c164 to bf804570

STACK_TEXT:  
b1b4b7dc bf80c164 8055a1f0 8988a790 00000002 win32k!DEVLOCKOBJ::vDestructor+0x1b
b1b4b924 804de7be 00000104 0007eda8 0007edc0 win32k!NtGdiFlushUserBatch+0x89a
b1b4b960 804db856 b1b4b9b8 8988a790 ffdff120 nt!KiFastCallEntry+0xca
b1b4b974 804dc10d 00000001 b1b4bc38 0000003b nt!KiSwapContext+0x2e
b1b4b9fc 804e3963 89ba26c8 89ba10e8 ffdff9c0 nt!KiSwapThread+0x68
b1b4ba10 bf8055b0 00000000 b1b4ba50 bf93fee7 nt!KeInsertQueueDpc+0xd9
b1b4ba24 00000000 00000000 00000000 00000000 win32k!HANDLELOCK::vLockHandle+0x75


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!DEVLOCKOBJ::vDestructor+1b
bf804570 8b8094050000    mov     eax,dword ptr [eax+594h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!DEVLOCKOBJ::vDestructor+1b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  48025f2a

FAILURE_BUCKET_ID:  0x8E_win32k!DEVLOCKOBJ::vDestructor+1b

BUCKET_ID:  0x8E_win32k!DEVLOCKOBJ::vDestructor+1b

Followup: MachineOwner
---------