Ekran śmierci,czy mam się tym martwić


(Mirra273) #1

Witam,mam następujące pytanie .Robiłem komp wujkowi ,czyli wyczyściłem go zmieniłem pastę ,i dołożyłem dwa wentylatory.

Nie miałem na raz wszystkiego czego potrzebowałem wiec najpierw było czyszczenie i pasta, potem były wentylatory i jeszcze porządek w kablach.

Po pierwszym zabiegu komp chodził normalnie lecz po drugi po jego podłączeniu było wszystko ok ,ale po przysunięciu biurka z komputerem do ściany komp się zresetował , potem normalnie odpalił (biurko odsunięte) komp odpalił ale pojawił się ekran śmierci no to zresetowałem i jak nie przysuwałem biurka to komp działa normalnie.Lecz za każdym razem kiedy przysuwałem biurko to ekran śmierci i reset.W końcu po kilki resetach komp odpala normalnie i po przesuwaniu i odsuwaniu biurka nic się nie dzieje.I teraz tu moje pytanie czy mam się przejmować tym błędem czy jak wszystko będzie w porządku to zostawić to tak jak jest??

Bardzo proszę o pomoc bo przed tymi zabiegami ani razu nie ukazywał się ekran śmierci.


(Szubi993) #2

Wać pan poda identyfikator tego blue screena.

No nie mogę, nie jesteś jedyną ofiarą tej sklejki drewna :lol:


(Mirra273) #3

Może mnie źle zrozumiałeś gdy przesuwałem biurko to właśnie wtedy i tylko wtedy dy komp się resetował i był ekran śmierci,tak jakby jakiś kabel gdy biurko jest ruszane coś robił i komp reset albo ekran śmierci,a i jeszcze może to coś wam powie ,zanalazłem to

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86

Copyright (c) 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: Sun Feb 6 19:34:50.234 2011 (GMT+1)

System Uptime: 0 days 0:01:24.828

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

* 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

.....

Unable to load image afd.sys, Win32 error 0n2

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

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

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

* *

* Bugcheck Analysis *

* *

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


Use !analyze -v to get detailed debugging information.


BugCheck 100000D1, {6c02ce5c, 2, 1, b69c5254}


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

******

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

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

******

******

***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 : afd.sys ( afd+f254 )


Followup: MachineOwner

---------

(Szubi993) #4

Zrozumiałem Cię doskonale, nie martw się :smiley:

75% loga to warning nt. nieprawidłowych znaków :lol:

A chodziło tylko o to

Probably caused by : afd.sys ( afd+f254 )


Followup: MachineOwner

Zwykle taki problem się pojawia, kiedy sterownik nawala, albo kiedy RAM nawala.

Zrób profilaktycznie test pamięci programem Memtest86+. Może coś ciekawego odkryjemy.


(Mirra273) #5

Dobra dzisiaj zrobię testy i zobaczymy (dodam ze robiłem test stabilności sytemu ORTHOSEM i nic się nie działko)