Windows xp - blue screen

**Posty:** 23 · przez **L a s e K** 01 Mar 2010, 21:06

Witam.
Miałem Win XP nastąpiły bluescreen'y po włączeniu kompa, zalogowaniu, czasami po włączeniu mozilli, a czasami po włączeniu xfire. Ok, zrobiłem formata, było ok przez 2 dni, teraz to powraca. Mam blue screeny z Win, wykluczam wirusy, jest to wina czegoś innego, ale nie wiem dokładnie jak to naprawić, bo nie znam powodu.

Kod: Zaznacz wszystko: Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [E:\WINDOWS\Minidump\Mini030110-05.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol 遳earch path is: *** Invalid *** **************************************************************************** * Symbol loading may be unreliable without a symbol search path. * * Use .symfix to have the debugger choose a symbol path. * * After setting your symbol path, use .reload to refresh symbol locations. * **************************************************************************** Executable search path is: ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700 Debug session time: Mon Mar 1 19:53:09.312 2010 (GMT+1) System Uptime: 0 days 0:00:51.875 ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded 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 *** ERROR: Module load completed but symbols could not be loaded for win32k.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, 8054afd2, a9a86ae8, 0} *** WARNING: Unable to verify timestamp for mssmbios.sys *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys ***** Kernel symbols are WRONG. Please fix symbols to do analysis. 逍************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Probably caused by : win32k.sys ( win32k+2b6d ) Followup: MachineOwner --------- 0: 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: 8054afd2, The address that the exception occurred at Arg3: a9a86ae8, Trap Frame Arg4: 00000000 Debugging Details: ------------------ ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. MODULE_NAME: win32k FAULTING_MODULE: 804d7000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 4a85564f EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod "0x%08lx" odwo FAULTING_IP: nt+73fd2 8054afd2 894804 mov dword ptr [eax+4],ecx TRAP_FRAME: a9a86ae8 -- (.trap 0xffffffffa9a86ae8) ErrCode = 00000002 eax=00000000 ebx=863eb028 ecx=863ebbc0 edx=00000091 esi=e3435490 edi=000001ff eip=8054afd2 esp=a9a86b5c ebp=a9a86bb0 iopl=0 nv up ei pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202 nt+0x73fd2: 8054afd2 894804 mov dword ptr [eax+4],ecx ds:0023:00000004=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 5 DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT BUGCHECK_STR: 0x8E LAST_CONTROL_TRANSFER: from bf802b6d to 8054afd2 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. a9a86bb0 bf802b6d 00000001 00000001 35306847 nt+0x73fd2 a9a86bd0 bf80fc15 0000047c 35306847 00000000 win32k+0x2b6d a9a86be4 bf8059dd 0000047c 35306847 a9a86c7c win32k+0xfc15 a9a86c00 bf808fcd 0000047c 00000005 00000001 win32k+0x59dd a9a86c48 bf829caf 00000040 00000000 00000000 win32k+0x8fcd a9a86cc4 bf834578 060104e6 00000002 00000000 win32k+0x29caf a9a86d30 8054088c 060104e6 00000010 00000010 win32k+0x34578 a9a86d64 7c90e514 badb0d00 0013fa3c 00000028 nt+0x6988c a9a86d68 badb0d00 0013fa3c 00000028 00000001 0x7c90e514 a9a86d6c 0013fa3c 00000028 00000001 00000000 0xbadb0d00 a9a86d70 00000000 00000001 00000000 00000000 0x13fa3c STACK_COMMAND: kb FOLLOWUP_IP: win32k+2b6d bf802b6d ?? ??? SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: win32k+2b6d FOLLOWUP_NAME: MachineOwner IMAGE_NAME: win32k.sys BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner --------- 0: 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: 8054afd2, The address that the exception occurred at Arg3: a9a86ae8, Trap Frame Arg4: 00000000 Debugging Details: ------------------ ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. MODULE_NAME: win32k FAULTING_MODULE: 804d7000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 4a85564f EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod "0x%08lx" odwo FAULTING_IP: nt+73fd2 8054afd2 894804 mov dword ptr [eax+4],ecx TRAP_FRAME: a9a86ae8 -- (.trap 0xffffffffa9a86ae8) ErrCode = 00000002 eax=00000000 ebx=863eb028 ecx=863ebbc0 edx=00000091 esi=e3435490 edi=000001ff eip=8054afd2 esp=a9a86b5c ebp=a9a86bb0 iopl=0 nv up ei pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202 nt+0x73fd2: 8054afd2 894804 mov dword ptr [eax+4],ecx ds:0023:00000004=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 5 DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT BUGCHECK_STR: 0x8E LAST_CONTROL_TRANSFER: from bf802b6d to 8054afd2 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. a9a86bb0 bf802b6d 00000001 00000001 35306847 nt+0x73fd2 a9a86bd0 bf80fc15 0000047c 35306847 00000000 win32k+0x2b6d a9a86be4 bf8059dd 0000047c 35306847 a9a86c7c win32k+0xfc15 a9a86c00 bf808fcd 0000047c 00000005 00000001 win32k+0x59dd a9a86c48 bf829caf 00000040 00000000 00000000 win32k+0x8fcd a9a86cc4 bf834578 060104e6 00000002 00000000 win32k+0x29caf a9a86d30 8054088c 060104e6 00000010 00000010 win32k+0x34578 a9a86d64 7c90e514 badb0d00 0013fa3c 00000028 nt+0x6988c a9a86d68 badb0d00 0013fa3c 00000028 00000001 0x7c90e514 a9a86d6c 0013fa3c 00000028 00000001 00000000 0xbadb0d00 a9a86d70 00000000 00000001 00000000 00000000 0x13fa3c STACK_COMMAND: kb FOLLOWUP_IP: win32k+2b6d bf802b6d ?? ??? SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: win32k+2b6d FOLLOWUP_NAME: MachineOwner IMAGE_NAME: win32k.sys BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner ---------

Na innych forach wyczytałem, że to problem ze sterownikami do karty graficznej. Wątpię, bo tak nagle się to stało, wcześniej było ok.
Czasami mam info przed załadowaniem Win "naprawianie uszkodzonych sektorów", lub też po załadowaniu Win "Odzyskano uszkodzony plik z rejestru". Mam problem ponieważ Xfire od razu error po włączeniu, a AV się wyłącza po jakimś czasie, często też FF siada jak i inne programy sieciowe.

**Posty:** 4459 · przez **jarski185** 01 Mar 2010, 21:17

Sprawdź pamięć memtestem

**Posty:** 23 · przez **L a s e K** 01 Mar 2010, 22:31

Memtest wykazał błędy, no ale co dalej?

Błędy nie opiszę, bo tylko wykazał ich istnienie, po 57 błędach i przetestowaniu 4% pamięci - przerwałem. Nie testowałem przez dos, ale przez gui, ale to chyba nie ma znaczenia, większego.

**Posty:** 4459 · przez **jarski185** 02 Mar 2010, 09:19

L a s e K napisał(a):no ale co dalej?

Wymiana pamięci.

**Posty:** 12734 · przez **Mikou@j** 02 Mar 2010, 10:38

jarski185 napisał(a):Wymiana pamięci.

dokładnie.
Już po pierwszym błędzie mogłeś sobie darować dalsze sprawdzanie.
Nie napisałeś ile masz kości pamięci, bo każdą osobno powinieneś testować (o ile masz więcej niż jedną).

**Posty:** 23 · przez **L a s e K** 02 Mar 2010, 14:47

@UP: Mam jedną - 1GB. Problem w tym, że jest to laptop

Teraz np. działa dobrze i mam włączone programy, ale pewnie znowu coś potem odwali i zacznie szaleć.

**Posty:** 12734 · przez **Mikou@j** 02 Mar 2010, 15:16

L a s e K napisał(a):Problem w tym, że jest to laptop

nie widzę problemu. Wymienić pamięć można.

**Posty:** 23 · przez **L a s e K** 03 Mar 2010, 00:02

Problem widzę, bo nie znam się na budowie laptopa, wolę nie ruszać jak się nie orientuję. W przypadku komputerów stacjonarnych nie widziałbym żadnego problemu. Na razie jest dobrze, nie wiem czym to było spowodowane.