Comment #10 on issue 10011 by [email protected]: BSOD in win32k.sys on XP
SP3
http://code.google.com/p/chromium/issues/detail?id=10011
coryizzo: You are facing the same problem as vpa1176, so I would recommend
the same
procedure. It looks to me like you have SP3 installed already (install it
if you
don't) and then apply the hotfix listed in comment 9.
Here is the crashdump analysis (for posterity).
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.090206-1234
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80554040
Debug session time: Fri May 1 17:34:37.781 2009 (GMT-7)
System Uptime: 0 days 5:06:26.344
BugCheck 1000008E, {c0000005, bf952aaa, b5446c00, 0}
Probably caused by : win32k.sys ( win32k!GreGetGlyphIndicesW+af )
Followup: MachineOwner
---------
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: bf952aaa, The address that the exception occurred at
Arg3: b5446c00, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"
referenced
memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
win32k!GreGetGlyphIndicesW+af
bf952aaa 8b4004 mov eax,dword ptr [eax+4]
TRAP_FRAME: b5446c00 -- (.trap 0xffffffffb5446c00)
ErrCode = 00000000
eax=00000000 ebx=00000100 ecx=000000b9 edx=e1b7b404 esi=e1b84000
edi=e1b7b008
eip=bf952aaa esp=b5446c74 ebp=b5446c8c 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!GreGetGlyphIndicesW+0xaf:
bf952aaa 8b4004 mov eax,dword ptr [eax+4]
ds:0023:00000004=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: chrome.exe
LAST_CONTROL_TRANSFER: from bf94a137 to bf952aaa
STACK_TEXT:
b5446c8c bf94a137 e3305348 e1b84200 e1299888 win32k!GreGetGlyphIndicesW+0xaf
b5446d28 bf94a1b3 ec010a35 00f0ef30 00000100
win32k!NtGdiGetGlyphIndicesWInternal+0xf2
b5446d48 8053d648 ec010a35 00f0ef30 00000100
win32k!NtGdiGetGlyphIndicesW+0x1b
b5446d48 7c90e514 ec010a35 00f0ef30 00000100 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
00f0ecc4 00000000 00000000 00000000 00000000 0x7c90e514
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!GreGetGlyphIndicesW+af
bf952aaa 8b4004 mov eax,dword ptr [eax+4]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!GreGetGlyphIndicesW+af
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 49900fc9
FAILURE_BUCKET_ID: 0x8E_win32k!GreGetGlyphIndicesW+af
BUCKET_ID: 0x8E_win32k!GreGetGlyphIndicesW+af
Followup: MachineOwner
---------
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
