Status: Resolved

130624: Finally, some time to update this blog post! Sorry for the delay... this particular issue is resolved in the May Rollup:

130211: we have asked the customer to implement the GDICaptureStackTraceForObjectType registry value to obtain additional information in subsequent dumps... fingers crossed!


Hi All,


Finally, my first post of the New Year! This involves a problem I've recently seen on a few customer machines. There is no resolution yet so if you have this problem let me know!

The debugger shows:

3: kd> knL
 # Child-SP          RetAddr           Call Site
00 fffff880`30c7d9b8 fffff803`50e84f8a nt!KeBugCheckEx
01 fffff880`30c7d9c0 fffff803`50becbcd nt!MiCheckSessionPoolAllocations+0xdf09e
02 fffff880`30c7da10 fffff803`50ca385a nt!MiDereferenceSessionFinal+0xf1
03 (Inline Function) --------`-------- nt!MiDereferenceSession+0x78
04 fffff880`30c7da80 fffff803`50caae28 nt!MmCleanProcessAddressSpace+0x2be
05 fffff880`30c7daf0 fffff803`50cab52a nt!PspExitThread+0x668
06 fffff880`30c7dc10 fffff803`508e5dd6 nt!PspTerminateThreadByPointer+0x4e
07 fffff880`30c7dc60 00000000`00000000 nt!KxStartSystemThread+0x16
3: kd> !poolused 8
 Sorting by Session Tag

               NonPaged                  Paged
 Tag     Allocs         Used     Allocs         Used

 Gla4         0            0          1          240 GDITAG_HMGR_LOOKASIDE_RGN_TYPE , Binary: win32k.sys

TOTAL         0            0          1          240