Nagły restart systemu


(arak) #1

Witam Was.

Otóż przed momentem zdarzyło mi się coś dziwnego.

Nie wiem na ile to miało wpływ(o ile w ogóle miało,ale nagrywałem sobie płytę z filmem.Nagrywanie doszło do 100%,był komunikat:Wysuwanie i ....nagle system się zrestartował.Po ponownym uruchomieniu pojawił się komunikat następującej treści

BCCode:100000d0 BCP100000008 BCP2:00000002 BCP3:00000000 BCP4:8054805E

OSVer.5_1_2600 SP.3_0 Product:768_1

Oraz niżej Informacje techniczne na temat raportu o błędach:

C:\DOCUME~1\arcio\USTAWI~1\Temp\WER95bc.dir00\Mini122410-01.dmp

C:\DOCUME~1\arcio\USTAWI~1\Temp\WER95bc.dir00\sysdata.xml

Natomiast w dzienniku błędów z dzisejszego dnia mam dwa komunikaty:

System Error(źródło) Kod błędu 100000d0, parametr 1 00000008, parametr 2 00000002, parametr 3 00000000, parametr 4 8054805e.

oraz

JRAID(źródło) Urządzenie \Device\Scsi\JRAID1 nie odpowiedziało w ramach ustalonego limitu czasu.

Kolega doradził mi także aby przeanalizować ten plik .dmp

Otrzymałem taki oto wynik:

Microsoft ® Windows Debugger Version 6.11.0001.404 X86

Copyright © Microsoft Corporation. All rights reserved.

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 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) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Machine Name:

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720

Debug session time: Fri Dec 24 13:32:54.890 2010 (GMT+1)

System Uptime: 0 days 2:33:26.594

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

* 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 100000D0, {8, 2, 0, 8054805e}

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

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

*** WARNING: Unable to verify timestamp for fltmgr.sys

*** ERROR: Module load completed but symbols could not be loaded for fltmgr.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 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+7105e )

Followup: MachineOwner


A czy takie zachowanie może mieć związek z jakąś niezgodnścią sprzętową?

Przypomniałem sobie że kilka dni temu chciałem uruchomić oprogramowanie odpowiedzialne za ustawienia karty graficznej-dokładnie chodzi tu o ATI Tray Tools (moja karta to Radeon 4650 HD)i system się zawiesił.System na nic nie zareagował.Tylko pozostał ponowne uruchomienie komputera.

Bardzo proszę o pomoc.

Dzięki wielkie,

pozdrawiam.


(Piotrkijak) #2

Przetestuj sobie ram programem memtest, najlepiej każdą kość oddzielnie i zrób skanowanie dysku programem hdtune(zakładka error scan) z odhaczoną opcją quick scan. Jeżeli będą czerwone kwadraciki wyzeruj i zremapuj dysk według poradnika: http://helpc.eu/topic/3485-mhdd/, natomiast jeżeli memtest znajdzie chociaż jeden błąd, wtedy będziesz musiał wymienić kość na nową.


(Jjoasz) #3

masz macierz? pewnie jeden dysk sypnal bledami...