*** Fatal System Error: 0x00000019 (0x00000003,0x8D1E9380,0x8D1E937F,0x8D1E9380) Break instruction exception - code 80000003 (first chance) A fatal system error has occurred. Debugger entered on first try; Bugcheck callbacks have not been invoked. A fatal system error has occurred. Connected to Windows 7 7601 x86 compatible target at (Mon Mar 16 10:33:54.155 2015 (UTC + 1:00)), ptr64 FALSE Loading Kernel Symbols ............................................................... ................................................................ .................................. Loading User Symbols ................................................................ ................................................................ ........................................................... Loading unloaded module list ................................................. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 19, {3, 8d1e9380, 8d1e937f, 8d1e9380} Probably caused by : win32k.sys ( win32k!Win32AllocPool+13 ) Followup: MachineOwner --------- nt!RtlpBreakWithStatusInstruction: 82ac58a8 cc int 3 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BAD_POOL_HEADER (19) The pool is already corrupt at the time of the current request. This may or may not be due to the caller. The internal pool links must be walked to figure out a possible cause of the problem, and then special pool applied to the suspect tags or the driver verifier to a suspect driver. Arguments: Arg1: 00000003, the pool freelist is corrupt. Arg2: 8d1e9380, the pool entry being checked. Arg3: 8d1e937f, the read back flink freelist value (should be the same as 2). Arg4: 8d1e9380, the read back blink freelist value (should be the same as 2). Debugging Details: ------------------ BUGCHECK_STR: 0x19_3 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: explorer.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 82b29f3b to 82ac58a8 STACK_TEXT: a3fdb014 82b29f3b 00000003 ae6453a3 00000065 nt!RtlpBreakWithStatusInstruction a3fdb064 82b2aa39 00000003 8d1e8e04 8d1e9380 nt!KiBugCheckDebugBreak+0x1c a3fdb428 82b6c68c 00000019 00000003 8d1e9380 nt!KeBugCheck2+0x68b a3fdb490 9698c9ef 00000021 0000040c 6f746547 nt!ExAllocatePoolWithTag+0x682 a3fdb4a4 96993c79 0000040c 6f746547 00000000 win32k!Win32AllocPool+0x13 a3fdb4b8 9699aa9a 000003fc 6f746547 00000d0d win32k!AllocThreadBufferWithTag+0x1e a3fdb73c 9699cd8e fe113010 a3fdb798 fdf8a470 win32k!EngTextOut+0x1e1 a3fdba38 9692bf8a a3fdbbfc ffa75700 ffa7575c win32k!GreExtTextOutWLocked+0x1040 a3fdbab4 9697ea60 00000000 ffbbe068 00000010 win32k!GreBatchTextOut+0x1e6 a3fdbc24 82a8882c 0000023d 03e8e598 03e8e628 win32k!NtGdiFlushUserBatch+0x123 a3fdbc34 775d70f3 badb0d00 03e8e598 00000000 nt!KiSystemServiceAccessTeb+0x10 a3fdbc38 badb0d00 03e8e598 00000000 00000000 ntdll!KiFastSystemCall+0x3 WARNING: Frame IP not in any known module. Following frames may be wrong. a3fdbc3c 03e8e598 00000000 00000000 00000000 0xbadb0d00 a3fdbc40 00000000 00000000 00000000 00000000 0x3e8e598 STACK_COMMAND: kb FOLLOWUP_IP: win32k!Win32AllocPool+13 9698c9ef 5d pop ebp SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: win32k!Win32AllocPool+13 FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 54ee8ecd FAILURE_BUCKET_ID: 0x19_3_win32k!Win32AllocPool+13 BUCKET_ID: 0x19_3_win32k!Win32AllocPool+13 Followup: MachineOwner ---------