Windows xp bluescreen probably caused by : ntkrnlpa.exe

**Posty:** 151 · przez **matix56** 30 Sty 2014, 19:13

Witam
Mojej cioci już parę razy wyskoczył blue screen i nie wiem czego może to by przyczyna na dole Minidump

Kod: Zaznacz wszystko: Microsoft (R) Windows Debugger Version 6.11.0001.402 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini011114-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 \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe Windows XP Kernel Version 2600 (Service Pack 3) MP (3 procs) Free x86 compatible Product: WinNt Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720 Debug session time: Sat Jan 11 12:26:37.859 2014 (GMT+1) System Uptime: 0 days 0:02:22.437 ********************************************************************* * 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 \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe Loading Kernel Symbols ............................................................... ...................................... Loading User Symbols Loading unloaded module list ... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C0000218, {e1988230, 0, 0, 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 *** *** *** ************************************************************************* ********************************************************************* * 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 : ntkrnlpa.exe ( nt+22fa3 ) Followup: MachineOwner ---------

Proszę o pomoc , System windows XP

**Posty:** 493 · przez **kliszka** 30 Sty 2014, 21:09

Prawdopodobnie uszkodzony plik ntkrnlpa.exe
Spróbuj: Start -> Uruchom -> cmd -> sfc /scannow - to jest komenda do sprawdzenia plików systemowych.
Możesz to naprawić na dwa sposoby :
1.) Naprawa uszkodzonego systemu Windows XP ,
2.) Druga metoda to kopiowanie plików w konsoli odzyskiwania systemu.
Restartujesz system i uruchamiasz instalator Windowsa XP z płyty. Na ekranie instalatora naciskasz R - napraw. Czekaj aż załaduje się konsola .
Teraz trzeba skopiować pliki. Wydajesz polecenia (zakładająć, że pliki znajdują się na c:\ i katalog Windows jest też na tym dysku):
copy c:\hal.dll c:\windows\system32 <ENTER>
copy c:\ntkrnlpa.exe c:\windows\system32 <ENTER>
Po skopiowaniu restart systemu. Po restarcie system sam powinien wykryć nowe jądro .