Blue screen win vista hp sp1


(Spiderman3) #1

w viście home premium z zintegrowanym dodatkiem sp1 co jakiś czas sam z siebie wyskakuje mi blue screen a po ponownym uruchomieniu wyskakuje okienko "system Windows odzyskał poprawność po nieoczekiwanym zamknięciu" Pliki, które pomogą odczytać błąd C:\Windows\Minidump\Mini020209-02.dmp

Według wcześniejszych wskazówek, które dostałem na forum odczytałem ten błąd i nie wiem co dalej robić.

Raport błędu wygląda tak:

Loading Dump File [C]

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 argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Unable to load image \SystemRoot\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 Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Machine Name:

Kernel base = 0x81a4e000 PsLoadedModuleList = 0x81b65c70

Debug session time: Mon Feb 2 17:07:41.789 2009 (GMT+1)

System Uptime: 0 days 3:11:34.571

*********************************************************************

* 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 argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Unable to load image \SystemRoot\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 1A, {3451, c049d158, 859cfa88, 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 ***

*** ***

*************************************************************************

*********************************************************************

* 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 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 argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Probably caused by : ntkrnlpa.exe ( nt+cd0e3 )

Followup: MachineOwner


kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

MEMORY_MANAGEMENT (1a)

Any other values for parameter 1 must be individually examined.

Arguments:

Arg1: 00003451, The PTEs of an outswapped kernel thread stack are corrupt.

Arg2: c049d158

Arg3: 859cfa88

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 ***

*** ***

*************************************************************************

*********************************************************************

* 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 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 argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

MODULE_NAME: nt

FAULTING_MODULE: 81a4e000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b7fa

BUGCHECK_STR: 0x1a_3451

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 81ad1a08 to 81b1b0e3

STACK_TEXT:

WARNING: Stack unwind information not available. Following frames may be wrong.

86b1fcb4 81ad1a08 0000001a 00003451 c049d158 nt+0xcd0e3

86b1fd38 81a9f563 859cfa88 86b1fd58 00000000 nt+0x83a08

86b1fd6c 81a8971a 859cfaf8 00000000 86b1fdc0 nt+0x51563

86b1fd7c 81c23b18 00000000 12d6de84 00000000 nt+0x3b71a

86b1fdc0 81a7ca2e 81a89697 00000000 00000000 nt+0x1d5b18

00000000 00000000 00000000 00000000 00000000 nt+0x2ea2e

STACK_COMMAND: kb

FOLLOWUP_IP:

nt+cd0e3

81b1b0e3 8be5 mov esp,ebp

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+cd0e3

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntkrnlpa.exe

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner


Kiedy próbuję uruchomić " ntkrnlpa.exe" to wyskakuje mi:

Nie można uruchomić apkilacji C:\Windows\System32\ntkrnlpa.exe w trybie win 32

A jak chcę usunąć ten plik to wyskakuje:

Musisz mieć uprawnienia do wykonania tej operacji

ntkrnlpa

opis pliku: NT kernel & system

firma: Microsoft Corporation

wersja pliku: 6.0.600.18145

data utworzenia: 2008-12-31 18:27

rozmiar: 3,43 MB

Moje pytanie brzmi jak usunąć ten błąd??

z góry dzięki pozdro


(Mandrasik17) #2

kiedy CI się pokazuje BSOD jak co robisz?


(Cosik Ktosik) #3

Opis błędu 0x0000001A powinien być tutaj http://www.hotfix.pl/articles.php?article_id=11 Tam jest link do MSDN, ale ogólnie najpierw sprawdź pamięć programem Memtest86+.