Comment #13 on issue 10011 by [email protected]: BSOD in win32k.sys on XP
SP3
http://code.google.com/p/chromium/issues/detail?id=10011
kevarh: Three of your minidumps are identical to the ones vap1176 sent. One
of them is slightly
different (Mini061009-01.dmp seen below). All of them, however, have the
same root cause, which
is the bug in win32k.sys. Please see comment 9 for a resolution (install
MS' hotfix on top of
SP3).
For posterity, here is the analysis for the issue that isn't like the other
three:
Loading Dump File [Mini061009-01.dmp]
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 = 0x8055b1c0
Debug session time: Wed Jun 10 20:50:37.803 2009 (GMT-7)
System Uptime: 3 days 22:41:15.145
BugCheck 1000008E, {c0000005, bf812491, b5ed31bc, 0}
Probably caused by : win32k.sys ( win32k!ESTROBJ::vInit+43 )
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: bf812491, The address that the exception occurred at
Arg3: b5ed31bc, 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!ESTROBJ::vInit+43
bf812491 f6410410 test byte ptr [ecx+4],10h
TRAP_FRAME: b5ed31bc -- (.trap 0xffffffffb5ed31bc)
ErrCode = 00000000
eax=00000400 ebx=b5ed3500 ecx=00000000 edx=e3d6e9c8 esi=b5ed32bc
edi=00000000
eip=bf812491 esp=b5ed3230 ebp=b5ed3244 iopl=0 nv up ei pl nz ac pe
nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
efl=00010216
win32k!ESTROBJ::vInit+0x43:
bf812491 f6410410 test byte ptr [ecx+4],10h
ds:0023:00000004=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: firefox.exe
LAST_CONTROL_TRANSFER: from bf81185a to bf812491
STACK_TEXT:
b5ed3244 bf81185a 7ffde22c 00000008 b5ed3788 win32k!ESTROBJ::vInit+0x43
b5ed34e8 bf812fb1 b5ed3788 00000251 000000ef
win32k!GreExtTextOutWLocked+0x666
b5ed3650 bf80c3b4 b5ed3788 7ffde1dc 000000a4 win32k!GreBatchTextOut+0x344
b5ed37a4 804de7be 000000fc 00129c58 00129c70
win32k!NtGdiFlushUserBatch+0x11b
b5ed37b4 7c90e514 badb0d00 00129c58 035d0000 nt!KiFastCallEntry+0xca
WARNING: Frame IP not in any known module. Following frames may be wrong.
b5ed37b8 badb0d00 00129c58 035d0000 10102adf 0x7c90e514
b5ed37bc 00129c58 035d0000 10102adf 000d0ad0 0xbadb0d00
b5ed37c0 035d0000 10102adf 000d0ad0 0012f488 0x129c58
b5ed37c4 10102adf 000d0ad0 0012f488 0012f4e0 0x35d0000
b5ed37c8 000d0ad0 0012f488 0012f4e0 00001fa1 0x10102adf
b5ed37cc 0012f488 0012f4e0 00001fa1 badb0d00 0xd0ad0
b5ed37d0 0012f4e0 00001fa1 badb0d00 00000000 0x12f488
b5ed37d4 00000000 badb0d00 00000000 00000000 0x12f4e0
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!ESTROBJ::vInit+43
bf812491 f6410410 test byte ptr [ecx+4],10h
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!ESTROBJ::vInit+43
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 49900fc9
FAILURE_BUCKET_ID: 0x8E_win32k!ESTROBJ::vInit+43
BUCKET_ID: 0x8E_win32k!ESTROBJ::vInit+43
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
-~----------~----~----~----~------~----~------~--~---
