Symbol search path is: srv*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18741.x86fre.win7sp1_gdr.150202-1526
Machine Name:
Kernel base = 0x8261c000 PsLoadedModuleList = 0x827665b0
Debug session time: Tue May  5 16:52:29.049 2015 (UTC + 2:00)
System Uptime: 0 days 0:00:31.134
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {ff6c6000, 0, 946fa40c, 0}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!itrp_IUP+213 )

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

kd> !analyze -v; .logclose; q
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ff6c6000, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 946fa40c, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from 8278684c
Unable to read MiSystemVaType memory at 82765f00
 ff6c6000 

FAULTING_IP: 
win32k!itrp_IUP+213
946fa40c 8b03            mov     eax,dword ptr [ebx]

MM_INTERNAL_CODE:  0

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 946fbc79 to 946fa40c

STACK_TEXT:  
89ef93b8 946fbc79 00000001 947017d3 00000000 win32k!itrp_IUP+0x213
89ef93c0 947017d3 00000000 ff6b24e0 00a404d9 win32k!itrp_InnerExecute+0x38
89ef93f8 946fbc79 ff6b24e0 946ff088 ff6b2574 win32k!itrp_CALL+0x23b
89ef9400 946ff088 ff6b2574 ff6b253c ff6b3314 win32k!itrp_InnerExecute+0x38
89ef9480 94703234 00a404b6 00a404d9 ff6b24e0 win32k!itrp_Execute+0x2b2
89ef94a8 947029dc 00a404b6 00a404d9 ff6b24e0 win32k!itrp_ExecuteGlyphPgm+0x4a
89ef94dc 94701e5e ff6af570 00000001 00000000 win32k!fsg_SimpleInnerGridFit+0x102
89ef9574 9470238c ff6af250 ff6b06ac ff6b24e0 win32k!fsg_ExecuteGlyph+0x1ce
89ef95d0 94702202 ff6af250 ff6b24e0 ff6b0624 win32k!fsg_CreateGlyphData+0xea
89ef9610 946ff419 ff6af250 ff6b24e0 ff6af2c4 win32k!fsg_GridFit+0x4d
89ef9688 9470906c 00000001 89ef96a4 94708fc3 win32k!fs__Contour+0x287
89ef9694 94708fc3 ff6af010 ff6af07c 89ef96c0 win32k!fs_ContourGridFit+0x12
89ef96a4 9470991f ff6af010 ff6af07c 00000003 win32k!fs_NewContourGridFit+0x10
89ef96c0 94709960 fc5c8e78 00000003 89ef96fc win32k!bGetGlyphOutline+0xd7
89ef96e8 94709b59 fc5c8e78 00000003 00000001 win32k!bGetGlyphMetrics+0x20
89ef982c 946fec63 fc5c8e78 00000003 89ef9918 win32k!lGetGlyphBitmap+0x2b
89ef9850 946feab6 00000000 00000001 00000003 win32k!ttfdQueryFontData+0x158
89ef98a0 946fdce2 ff7af010 fc43ccf0 00000001 win32k!ttfdSemQueryFontData+0x45
89ef98e8 94703717 ff7af010 fc43ccf0 00000001 win32k!PDEVOBJ::QueryFontData+0x3e
89ef9960 9477bc8d 89ef9c3c fbe6cd78 000020ac win32k!xInsertMetricsPlusRFONTOBJ+0xc3
89ef9990 946f594d 00000001 ff7bf000 89ef9cd0 win32k!RFONTOBJ::bGetGlyphMetricsPlus+0x179
89ef99c8 9477b78b 89ef9c1c 89ef9c3c 00000008 win32k!ESTROBJ::vCharPos_H3+0xf0
89ef9a0c 946f55d0 89ef9cd0 00000001 89ef9c1c win32k!ESTROBJ::vInit+0x268
89ef9c2c 946f5793 00000000 89ef9cd0 fc43ccf0 win32k!GreGetTextExtentExW+0x12a
89ef9d0c 82659896 0401024b 01290af4 00000001 win32k!NtGdiGetTextExtentExW+0x141
89ef9d0c 77bd70f4 0401024b 01290af4 00000001 nt!KiSystemServicePostCall
WARNING: Frame IP not in any known module. Following frames may be wrong.
0019f5c4 00000000 00000000 00000000 00000000 0x77bd70f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!itrp_IUP+213
946fa40c 8b03            mov     eax,dword ptr [ebx]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!itrp_IUP+213

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  54ee8ecd

FAILURE_BUCKET_ID:  0x50_win32k!itrp_IUP+213

BUCKET_ID:  0x50_win32k!itrp_IUP+213

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