Sam resetujący się system. Raport Everest i Debugging Tools

Od dłuższego czasu resetuje mi się sam komp. Tak jak we wszystkich innych tego typu przypadkach pierw wyświetla się niebieskie okno. Przeczytałem tematu o tym problemie i sporzadziłem potrzebne infa które pomogą rozwikłać problem czemu komp sam się resetuje kiedy chce.

Raport EVERESTa:

http://mpog.athost.net/Report.htm

Raporty Microsoft Debugging Toolsa:

Z dnia 21 czerwca:

Microsoft (R) Windows Debugger Version 6.6.0003.5

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 2

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

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30

Debug session time: Wed Jun 21 20:34:11.639 2006 (GMT+2)

System Uptime: 0 days 0:56:47.226

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

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

*** 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 nv4_disp.dll, Win32 error 2

*** WARNING: Unable to verify timestamp for nv4_disp.dll

*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll

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

* *

* Bugcheck Analysis *

* *

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


Use !analyze -v to get detailed debugging information.


BugCheck 1000008E, {c0000005, bfafaabd, f8f12ae8, 0}


***** Kernel symbols are WRONG. Please fix symbols to do analysis.


Probably caused by : hardware ( nv4_disp+13fabd )


Followup: MachineOwner

---------

Z dnia 22 czerwca:

Microsoft (R) Windows Debugger Version 6.6.0003.5

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 2

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

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30

Debug session time: Thu Jun 22 12:39:23.900 2006 (GMT+2)

System Uptime: 0 days 0:50:32.490

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

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

*** 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 win32k.sys, Win32 error 2

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

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

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

* *

* Bugcheck Analysis *

* *

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


Use !analyze -v to get detailed debugging information.


BugCheck 10000050, {8bfffd66, 0, bf839ba1, 0}


***** Kernel symbols are WRONG. Please fix symbols to do analysis.


Probably caused by : win32k.sys ( win32k+39ba1 )


Followup: MachineOwner

---------

Chciałbym po prostu wiedzieć czy trzeba dokupić jakąś nową część czy może reintal systemu pomoże.

Jeśli trzeba coś dodać, jakiś report proszę pisać.

Komp lata ma.

Konserwacja kompa.

Czy instalowałeś ostatnio sterowniki do karty grafiki.

Sprawdź pamięć:

http://forum.dobreprogramy.pl/viewtopic.php?t=50125

Ale problemem może być przetaktowana pamięć - FSB pamięci przestaw na 100 i zapisz bios Save.

Masz dwa moduły PC100 i jeden PC133 - a pamięć pracuje asynchronicznie na FSB 133.

Dalej:

  • zasilacz też nie rewelacja

  • zmniejsz temperaturę CPU

  • zobacz jak tam temperatura karty grafiki - palec - stosuj do niej ster 56.72.

  • jak tam szkodniki

  • jak dokładałeś pamięć - to nie wszystkie płyty lubią jak mają obsadzone wszystkie banki

no i może i warto świeży system postawić - wybór należy do Ciebie.

http://forum.dobreprogramy.pl/viewtopic.php?t=25048