Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini061709-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.090206-1234
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Wed Jun 17 18:04:12.027 2009 (GMT+2)
System Uptime: 0 days 10:42:21.728
Loading Kernel Symbols
...............................................................
................................................................
....
Loading User Symbols
Loading unloaded module list
......................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, bf90714c, b51e29f8, 0}
Probably caused by : win32k.sys ( win32k!RFONTOBJ::vFixUpGlyphIndices+10 )
Followup: MachineOwner
---------
1: 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: bf90714c, The address that the exception occurred at
Arg3: b51e29f8, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod "0x%08lx" odwo
FAULTING_IP:
win32k!RFONTOBJ::vFixUpGlyphIndices+10
bf90714c f6400402 test byte ptr [eax+4],2
TRAP_FRAME: b51e29f8 -- (.trap 0xffffffffb51e29f8)
ErrCode = 00000000
eax=00000000 ebx=00000000 ecx=e1909e58 edx=00000000 esi=e1d64000 edi=00000000
eip=bf90714c esp=b51e2a6c ebp=b51e2a6c iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
win32k!RFONTOBJ::vFixUpGlyphIndices+0x10:
bf90714c f6400402 test byte ptr [eax+4],2 ds:0023:00000004=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: open-fm.exe
LAST_CONTROL_TRANSFER: from bf8e37b5 to bf90714c
STACK_TEXT:
b51e2a6c bf8e37b5 b51e2d00 00000001 00000000 win32k!RFONTOBJ::vFixUpGlyphIndices+0x10
b51e2cf4 bf8e34b2 f7011dff 00000053 00000001 win32k!GreGetCharWidthW+0xa9
b51e2d44 804dd99f f7011dff 00000053 00000001 win32k!NtGdiGetCharWidthW+0xe9
b51e2d44 7c90e514 f7011dff 00000053 00000001 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012b464 00000000 00000000 00000000 00000000 0x7c90e514
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!RFONTOBJ::vFixUpGlyphIndices+10
bf90714c f6400402 test byte ptr [eax+4],2
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!RFONTOBJ::vFixUpGlyphIndices+10
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 49e87572
FAILURE_BUCKET_ID: 0x8E_win32k!RFONTOBJ::vFixUpGlyphIndices+10
BUCKET_ID: 0x8E_win32k!RFONTOBJ::vFixUpGlyphIndices+10
Followup: MachineOwner
---------
--------------------------------------------------------------------------------------------------------------------------------------------
w tym przypadku w process name jest open.fm w drugim raporcie jest chrome
proszę pomóżcie
