Bluescreen win xp

**Posty:** 39 · przez **kleofas** 21 Lip 2009, 12:53

Od jakiegoś czasu raz na kilka dni występuje bluescrren. Podaję komunikat błędu:
0x10000050 (0xc22decf4, 0x00000000, 0x805b4026, 0x00000000)
oraz kopię pliku minidump:

Kod: Zaznacz wszystko: Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini072009-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search 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 3) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x80554040 Debug session time: Mon Jul 20 19:51:15.140 2009 (GMT+2) System Uptime: 0 days 0:50:40.703 ********************************************************************* * 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 ............ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 10000050, {c22decf4, 0, 805b4026, 0} ***** 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 *** *** *** ************************************************************************* *** WARNING: Unable to verify timestamp for intelppm.sys *** ERROR: Module load completed but symbols could not be loaded for intelppm.sys ************************************************************************* *** *** *** *** *** 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 : intelppm.sys ( intelppm+1255 ) Followup: MachineOwner ---------

Komputer to laptop HP Compaq nx6110, Win XP oryginalne oprogramowanie i sterowniki ze strony producenta.
Dodaje, że wcześniej kilka lat działał baz problemów.
Proszę o pomoc w ustaleniu przyczyny.

**Posty:** 336 · przez **piotrplenzler** 21 Lip 2009, 14:06

podaj jaki plik jest przyczyną błedu, np. win32k.dll

**Posty:** 9184 · przez **MUTOPOMPKA** 21 Lip 2009, 17:33

piotrplenzler napisał(a):podaj jaki plik jest przyczyną błedu, np. win32k.dll

nie zawsze w BSOD-zie będziesz miał plik, który wywołuje błąd.

Ale z przytoczonego loga wsio jak na dłoni widać:
1) BugCheck 10000050, {c22decf4, 0, 805b4026, 0}
2) Probably caused by : intelppm.sys ( intelppm+1255 ) <- prawdopodobny plik wywołujący błąd

Spróbuj rozwiązań zastosowanych w tym artykule: http://support.microsoft.com/kb/953356/

Autor postu otrzymał pochwałę

**Posty:** 39 · przez **kleofas** 21 Lip 2009, 19:11

To bardzo prawdopodobne że kłopoty zaczęły się po instalacji Sp3.
Zobaczę czy te zmiany w rejestrze pomogą ale wielkie dzięki za pomoc.

Dodano 22.07.2009 07:21:25:
Przeczytałem to rozwiązanie zaproponowane przez MUTOPOMPKA ale w tym laptopie jest procesor Intela co prawda Celeron ale zastanawiam się czy jak dokonam tych zmian w rejestrze to komp nie zwariuje jeszcze bardziej.
Czy jest jakaś możliwość naprawy lub zamiany tego pliku intelppm.sys?
Oczywiście mogę zrobić format ale.....

No i problem rozwiązany. Dziś dysk padł całkowicie. Myślę, że to była przyczyna.