Zawieszanie Kompa I Restartowanie

[Infector]

Witam

Od paru miesiecy mam pewien problem.

Za kazdym razem gdy wlączam komputer doslownie po kilku minutach a czasem i sekundach komputer sie samoczynnie restartuje lub zawiesza. Gdy zrestartuje sie tak z 2- 3 razy potem działą przez pare godzin dobrze az w końcu znowu sie zwiesi lub restartuje.

Dzieje się tak na róznych wersjach windowsa (win 2000, xp prof. oraz xp sp.1)

 

Zainstalowalem program Microsoft Debugging Tools w celu odczytania informacji z pliku minidump.

Wydaje mi sie ze problem tkwi w pliku ntoskrnl.exe ale co dalej ?

 

Poniżej wklejam caly raport:

 

\\\\\\\\\\

Microsoft ® Windows Debugger Version 6.5.0003.7

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\WINDOWS\Minidump\Mini092305-03.dmp]

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

Product: WinNt

Kernel base = 0x804d0000 PsLoadedModuleList = 0x80545b28

Debug session time: Fri Sep 23 16:39:26.891 2005 (GMT+2)

System Uptime: 0 days 0:06:31.479

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

* 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 <symbol_path> 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 unloaded module list

...........

Loading User Symbols

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

* *

* Bugcheck Analysis *

* *

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

 

Use !analyze -v to get detailed debugging information.

 

BugCheck A, {cbffdf4, 2, 0, 804eba7a}

 

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

 

 

Followup: MachineOwner

---------

 

//////////

Prosze o pomoc.

[Infector]

i jeszce tak raport po wpisaniu w konsoli komendy !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

 

IRQL_NOT_LESS_OR_EQUAL (a)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high. This is usually

caused by drivers using improper addresses.

If a kernel debugger is available get the stack backtrace.

Arguments:

Arg1: 0cbffdf4, memory referenced

Arg2: 00000002, IRQL

Arg3: 00000000, value 0 = read operation, 1 = write operation

Arg4: 804eba7a, address which referenced memory

 

Debugging Details:

------------------

 

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

 

 

MODULE_NAME: nt

 

FAULTING_MODULE: 804d0000 nt

 

DEBUG_FLR_IMAGE_TIMESTAMP: 3b7de38f

 

READ_ADDRESS: unable to get nt!MmSpecialPoolStart

unable to get nt!MmSpecialPoolEnd

unable to get nt!MmPoolCodeStart

unable to get nt!MmPoolCodeEnd

0cbffdf4

 

CURRENT_IRQL: 2

 

FAULTING_IP:

nt+1ba7a

804eba7a 8b7508 mov esi,[ebp+0x8]

 

CUSTOMER_CRASH_COUNT: 3

 

DEFAULT_BUCKET_ID: DRIVER_FAULT

 

BUGCHECK_STR: 0xA

 

LAST_CONTROL_TRANSFER: from 00000000 to 804fc1bb

 

STACK_TEXT:

f9e4db78 00000000 0cbffdf4 00000002 00000000 nt+0x2c1bb

 

 

STACK_COMMAND: .bugcheck ; kb

 

FOLLOWUP_NAME: MachineOwner

 

BUCKET_ID: WRONG_SYMBOLS

 

Followup: MachineOwner

---------

[Infector]

Zasilacz 300W (podlaczone dwa dyski, flopy oraz dwie stacje cdrom)

Formata robiłem setki razy (zawsze partycje C - systemową) - zawsze stawiam system na sformatowanej partycji

[Infector]

Robiłem testy pamieci RAM. Raz wychodzily błedy na jednej kości raz na drugiej, a czasami wcale nie wykrywało.

Temperatura dysku, grafiki czy innych elementow raczej odpada bo jak pisalem na wstępie komputer sie zawiesza lub restartuje juz podczas ładowania systemu !

Edytowane 24 Września 2005 przez Infector

[Nyny]

Ja tez obstawiam w takim wypadku na 99% ram.

Moze sproboj wyjac 1 kostke potestowac kompa i jesli nic sie nie bedzie dzialo sprawdz druga. Calkiem mozliwe ze pamieci sa sprawne tylko "gryza" sie miedzysoba

[Infector]

Jak jechalem na jednej kostce to system odrazu sie resetowal, na drugiej to samo... wydaje mi sie ze to plyta głowna. Sprzedaje ten komputer kumplowi ale chcialem go przedtem troszke podreperowac