מסך כחול

פורסם 2011 במרץ 1214 שנים

קיבלתי מסך כחול באמצע הורדה של משהו קטן 4MB בערך:

ניתוח הMinidump:


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini031311-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*[url]http://msdl.microsoft.com/download/symbols[/url]
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.101209-1647
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sun Mar 13 00:20:49.593 2011 (GMT+2)
System Uptime: 0 days 4:50:14.284
Loading Kernel Symbols
...............................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
............................
*******************************************************************************
*                                       *
*            Bugcheck Analysis                  *
*                                       *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {e301901c, 0, bf846742, 1}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!RFONTOBJ::vXlatGlyphArray+5a )

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

1: kd> !analyze -v
*******************************************************************************
*                                       *
*            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: e301901c, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bf846742, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 00000001, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: e301901c 

FAULTING_IP: 
win32k!RFONTOBJ::vXlatGlyphArray+5a
bf846742 8b470c     mov   eax,dword ptr [edi+0Ch]

MM_INTERNAL_CODE: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: chrome.exe

LAST_CONTROL_TRANSFER: from bf89c267 to bf846742

STACK_TEXT: 
a59e6c08 bf89c267 a59e6c30 00000001 a59e6c24 win32k!RFONTOBJ::vXlatGlyphArray+0x5a
a59e6c28 bf953a1a 00000078 00000000 a59e6d1c win32k!RFONTOBJ::hgXlat+0x19
a59e6cc4 bf94a82b e76536f8 00000078 00000000 win32k!GreGetGlyphOutlineInternal+0xa9
a59e6d3c 8054167c f9010d4d 00000078 00000000 win32k!NtGdiGetGlyphOutline+0x85
a59e6d3c 7c90e514 f9010d4d 00000078 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0013dbfc 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND: kb

FOLLOWUP_IP: 
win32k!RFONTOBJ::vXlatGlyphArray+5a
bf846742 8b470c     mov   eax,dword ptr [edi+0Ch]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!RFONTOBJ::vXlatGlyphArray+5a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4d1dd63f

FAILURE_BUCKET_ID: 0x50_win32k!RFONTOBJ::vXlatGlyphArray+5a

BUCKET_ID: 0x50_win32k!RFONTOBJ::vXlatGlyphArray+5a

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