|
|||||||
|
|
|
![]() |
|
|
Strumenti |
|
|
#1 |
|
Junior Member
Iscritto dal: Aug 2008
Messaggi: 27
|
schermata blu con errore win32k.sys
Ciao, mi hanno da poco cambiato scheda madre e ora mi esce un nuovo BSOD mai visto prima.... le ram sembrano ok, il sistema operativo e' windows xp sp3, l'errore e' stop0x00000050 PAGE_FAULT_IN_NONPAGED_AREA , ho cercato su google ma nn ho ben capito cosa fare...
mi e' successo mentre aprivo chrome appena avviato il pc allego il minidump analizzato: Microsoft (R) Windows Debugger Version 6.11.0001.402 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini041009-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: C:\WINDOWS\Symbols Executable search path is: Unable to load image ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720 Debug session time: Fri Apr 10 13:48:39.328 2009 (GMT+2) System Uptime: 0 days 0:27:17.051 Unable to load image ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe Loading Kernel Symbols ............................................................... ................................................................ ... Loading User Symbols Loading unloaded module list ........... Unable to load image win32k.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for win32k.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 10000050, {e147a01c, 0, bf837426, 1} Could not read faulting driver name Probably caused by : win32k.sys ( win32k!RFONTOBJ::vXlatGlyphArray+35e ) 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: e147a01c, memory referenced. Arg2: 00000000, value 0 = read operation, 1 = write operation. Arg3: bf837426, 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: e147a01c FAULTING_IP: win32k!RFONTOBJ::vXlatGlyphArray+35e bf837426 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 bf85b720 to bf837426 STACK_TEXT: b465caf0 bf85b720 b465cb18 00000001 b465cb0c win32k!RFONTOBJ::vXlatGlyphArray+0x35e b465cb10 bf86a95e 00000020 00000001 00000000 win32k!EngFreeMem+0x24 b465cb6c bf86bcb8 00000002 00000000 b465cce0 win32k!RFONTOBJ::bGetDEVICEMETRICS+0x91 b465cc14 bf808043 b465cce0 b465cc9c 00000003 win32k!RFONTOBJ::bRealizeFont+0x3d4 b465cca4 bf8080ab e5186008 00000000 00000002 win32k!RFONTOBJ::bInit+0x2d0 b465ccbc bf837965 b465cce0 00000000 00000002 win32k!RFONTOBJ::bInit+0x2b1 b465ccd8 bf8379d5 e19289c8 b465ccf4 b465cd64 win32k!RFONTOBJ::lOverhang+0xa9 b465cd50 8054162c 01010070 01a2f5e8 00000044 win32k!GreGetTextMetricsW+0x3c b465cd64 7c91e4f4 badb0d00 01a2f5d0 b46e4d98 nt!RtlIpv4StringToAddressExW+0xad WARNING: Frame IP not in any known module. Following frames may be wrong. b465cd78 00000000 00000000 00000000 00000000 0x7c91e4f4 STACK_COMMAND: kb FOLLOWUP_IP: win32k!RFONTOBJ::vXlatGlyphArray+35e bf837426 8b470c mov eax,dword ptr [edi+0Ch] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: win32k!RFONTOBJ::vXlatGlyphArray+35e FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 49900fc9 FAILURE_BUCKET_ID: 0x50_win32k!RFONTOBJ::vXlatGlyphArray+35e BUCKET_ID: 0x50_win32k!RFONTOBJ::vXlatGlyphArray+35e Followup: MachineOwner --------- |
|
|
|
|
| Strumenti | |
|
|
Tutti gli orari sono GMT +1. Ora sono le: 14:03.



















