Niebieski ekran


(Padoda) #1

Co powoduje wyświetlenie niebieskiego ekranu?

Oto wynik DMP

Microsoft ® Windows Debugger Version 6.9.0003.113 X86

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [F]

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 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) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620

Debug session time: Sun Sep 21 13:57:47.671 2008 (GMT+2)

System Uptime: 0 days 0:00:59.234

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

* 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 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 19, {20, e23d0791, e23d07b1, c041704}

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

*** ***

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

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

*** ***

*** ***

*** 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 Ntfs.sys

*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys

unable to get nt!MmSpecialPoolStart

unable to get nt!MmSpecialPoolEnd

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

*** ***

*** ***

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

*** ***

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

unable to get nt!MmPoolCodeStart

unable to get nt!MmPoolCodeEnd

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

*** ***

*** ***

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

*** ***

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

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

*** ***

*** ***

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

*** ***

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

Cannot get _POOL_TRACKER_BIG_PAGES type size

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

*** ***

*** ***

*** 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 : ntoskrnl.exe ( nt+5c54e )

Followup: MachineOwner



(Lukaszk 89) #2

Poczytaj i spróbuj przywrócić ten plik

:arrow: http://www.searchengines.pl/index.php?s ... entry76658


(Cosik Ktosik) #3

padoda , nie ruszaj tego pliku (przynajmniej nie teraz).

0x19: BAD_POOL_HEADER - ntoskrnl.exe - Błąd alokacji pamięci, dotyczy zarówno RAM oraz bad sektorów na dysku.

Sprawdź pamięć programem Memtest86.

Daj odczyt danych SMART dysku z programu HD Tune, zakładka Health.

Przeskanuj także dysk na bad sektory (zakładka Error Scan).


(Padoda) #4

Zapomniałem ważnej informacji , mam 2 dyski fizyczne i 2 systemy. Niebieski ekran pojawił się na obu systemach. Jest mało prawdopodobne aby jednocześnie uległy uszkodzeniu dwa dyski, ale daję wyniki

1 Samsung

HD Tune: SAMSUNG SP1213N Health

ID Current Worst ThresholdData Status

(01) Raw Read Error Rate 100 100 51 1 Ok

(03) Spin Up Time 100 100 25 5696 Ok

(04) Start/Stop Count 100 100 0 478 Ok

(05) Reallocated Sector Count 100 100 11 0 Ok

(07) Seek Error Rate 100 100 51 0 Ok

(08) Seek Time Performance 100 100 15 0 Ok

(09) Power On Hours Count 100 100 0 428136 Ok

(0A) Spin Retry Count 100 100 51 0 Ok

(0B) Calibration Retry Count 100 100 0 0 Ok

(0C) Power Cycle Count 100 100 0 243 Ok

(C2) Temperature 151 127 0 29 Ok

(C3) Hardware ECC Recovered 100 100 0 3884027 Ok

(C4) Reallocated Event Count 100 100 0 0 Ok

(C5) Current Pending Sector 100 100 0 0 Ok

(C6) Offline Uncorrectable 100 100 0 0 Ok

(C7) Ultra DMA CRC Error Count 200 200 0 0 Ok

(C8) Write Error Rate 100 100 51 0 Ok

(C9) TA Counter Detected 100 100 51 0 Ok

Power On Time : 428136

Health Status : Ok

  1. Seageate

HD Tune: ST340810A Health

ID Current Worst ThresholdData Status

(01) Raw Read Error Rate 73 64 25 225658358 Ok

(03) Spin Up Time 98 98 0 0 Ok

(04) Start/Stop Count 100 100 20 961 Ok

(05) Reallocated Sector Count 93 93 36 74 Ok

(07) Seek Error Rate 76 60 30 199601252 Ok

(09) Power On Hours Count 93 93 0 6556 Ok

(0A) Spin Retry Count 100 100 97 0 Ok

(0C) Power Cycle Count 96 96 20 4178 Ok

(C2) Temperature 36 50 0 36 Ok

(C3) Hardware ECC Recovered 100 253 0 0 Ok

(C5) Current Pending Sector 100 98 0 1 Ok

(C6) Offline Uncorrectable 100 100 0 0 Ok

(C7) Ultra DMA CRC Error Count 200 194 0 7 Ok

(C8) Write Error Rate 100 253 0 0 Ok

(CA) TA Counter Increased 100 253 0 0 Ok

Power On Time : 6556

Health Status : Ok

Wyjołem kości pamięci i przeczyściłem, na razie spokój.

Może sloty i styki kości pamięci nie działały prawidłowo? I to jest cały problem?


(system) #5

Albo była jakaś nieczystość na stykach i to powodowało problemy.


(Cosik Ktosik) #6

SAMSUNG SP1213N Health - zdrowy

Seageate - niezdrowy

74 bad sektory

1 sektor oczekuje na remap

Występuje problem z komunikacją dysk-kontroler. Należy wymienić taśmę/kabel sygnałowy. Następnie wykonaj zerowanie tego dysku połączone z remapem :arrow: instrukcja


(Padoda) #7

Czyli to nie RAM?


(Cosik Ktosik) #8

Tego nie zagwarantuję. Dysk jest na pewno uszkodzony, a RAM jeszcze sprawdź.