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


Loading Dump File [C:\WINDOWS\Minidump\Mini032413-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 XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.101209-1647
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b240
Debug session time: Sat Mar 23 23:16:35.406 2013 (GMT+1)
System Uptime: 0 days 0:11:25.000
Loading Kernel Symbols
...............................................................
...............................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c000001d, bf8017bd, b1913a6c, 0}

Probably caused by : hardware ( win32k!HmgLock+f )

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: c000001d, The exception code that was not handled
Arg2: bf8017bd, The address that the exception occurred at
Arg3: b1913a6c, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {V JIMKA}  Neplatn  instrukce.  Prob

FAULTING_IP: 
win32k!HmgLock+f
bf8017bd ff              ???

TRAP_FRAME:  b1913a6c -- (.trap 0xffffffffb1913a6c)
ErrCode = 00000000
eax=0601023c ebx=0601023c ecx=0601023c edx=00000001 esi=b1913c28 edi=00000000
eip=bf8017bd esp=b1913ae0 ebp=b1913aec iopl=0         nv up ei pl nz ac pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010216
win32k!HmgLock+0xf:
bf8017bd ff              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  mmc.exe

MISALIGNED_IP: 
win32k!HmgLock+f
bf8017bd ff              ???

LAST_CONTROL_TRANSFER:  from bf8045a4 to bf8017bd

FAILED_INSTRUCTION_ADDRESS: 
win32k!HmgLock+f
bf8017bd ff              ???

STACK_TEXT:  
b1913aec bf8045a4 7ffdf000 b1913c44 bf80c135 win32k!HmgLock+0xf
b1913af8 bf80c135 0601023c 8055a270 898937b0 win32k!XDCOBJ::XDCOBJ+0x12
b1913c44 804de7be 00000172 0007e868 0007e914 win32k!NtGdiFlushUserBatch+0x9e
b1913c74 bf80ce54 e15dc048 00000000 bf8bb802 nt!KiFastCallEntry+0xca
b1913c80 bf8bb802 00000002 0000011d 000000ce win32k!SPRITELOCK::~SPRITELOCK+0xf
b1913d80 bf8ba7da e16c6018 e16c6018 00000000 win32k!bSpBltScreenToScreen+0x350
b1913e30 bf8bab4a e16c6018 e16c6018 00000000 win32k!SpBitBlt+0x56
b1913e64 b1913e90 b1913e80 bf8055b0 00000000 win32k!SpCopyBits+0x27
WARNING: Frame IP not in any known module. Following frames may be wrong.
b1913e88 bf908e76 b1913ed4 01040046 b1913eac 0xb1913e90
b1913ea8 bf80560e b1913f0c b1913f18 00000002 win32k!HmgLock+0x86
b1913f70 bf813d9b 00000002 b1913fb4 00000018 win32k!HANDLELOCK::vUnlock+0x20
b1913ff4 bf813f31 bc658768 0000000f 00000000 win32k!SfnDWORD+0xa8
b191403c bf814123 40658768 0000000f 00000000 win32k!xxxSendMessageToClient+0x176
b1914088 bf80ecc6 bc658768 0000000f 00000000 win32k!xxxSendMessageTimeout+0x1a6
b19140ac bf823e63 bc658768 0000000f 00000000 win32k!xxxSendMessage+0x1b
b19140d8 bf823d33 bc658768 00000001 0007eedc win32k!xxxUpdateWindow2+0x79
b19140f8 bf83654d bc658768 00000001 b1914124 win32k!xxxInternalUpdateWindow+0x6f
b1914108 bf8365a4 bc658768 0007eedc b1914478 win32k!xxxUpdateWindow+0xf
b1914124 804de7ec 00070152 0000005e 0007eedc win32k!NtUserCallHwndLock+0x4b
b1914124 7c90e514 00070152 0000005e 0007eedc nt!KiFastCallEntry+0xf8
0007eedc 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!HmgLock+f
bf8017bd ff              ???

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!HmgLock+f

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  IP_MISALIGNED

BUCKET_ID:  IP_MISALIGNED

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