Restart Przy Właczonej Sieci

[Agrest]

witam

pomożcie dobrzy ludzie

dzieje sie tak - komp się restartuje po jakichś 15-20 minutach od właczenia sieci LAN - twardy reset

system świeżo postawiony winxp + SP1 + zone alarm +kaspersky + mksonline

nic nie wykazują (wcześniej system zadbany ZA + avast + mksonline)

napięcia w miare w normie ATX mierzone miernikiem

płyta Asrock k7v88 + Sempron 1,5 Ghz (temp ~ 40 st C + samsung 80 + riva tnt 2 + cd-rom + fdd

zasilacz deer 350 + jakaś sieciówka realteka+ 256 MB goodram (sprawdzony memtestem - ok)

ostatnio się to zrobiło a komp ma 10 mies

help

P.S.

jutro postaram się o jakiś raport

i pewnie stery od myszy odpadają ??

a może stery od karty sieciowej ??

ale wcześniej się tak nie robilo dopiero jakies 2 tyg temu

już sciągam debugera

P.S. 2

po obciążeniu 3dmarkiem jest ok

jakiś nowy vir ?? baza dziś aktualizowana :|

madrzy ludzie help <ściana>

Edytowane 17 Maja 2005 przez Agrest

[Ouara]

1. zobacz co Ci powie debugger

2. ja miałem problem z mks 2005 jak wywaliłem to zrobiło się lepiej ;)

3. spróbuj zmienić sieciówkę

[Nyny]

Ja bym ci jednak polecil zainstalowac SP2. Teraz juz bez tego dodatku nie ma sie co porywac na internet bo dziadostwa naleci odrazu.

Najlepiej instaluj szybko SP2 + wszystkie łaty z windows update. Po tej operacji przeskanuj jeszcze raz kompa antywirusami

[Agrest]

oto minidump

 

Microsoft ® Windows Debugger Version 6.4.0007.2

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\WINDOWS\Minidump\Mini051705-01.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 (Service Pack 1) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30

Debug session time: Tue May 17 17:26:10.890 2005 (GMT+2)

System Uptime: 0 days 0:21:41.457

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

* 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

Unable to load image vsdatant.sys, Win32 error 2

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

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

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

* *

* Bugcheck Analysis *

* *

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

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 1000008E, {c0000005, f5e4b31b, f5c44b1c, 0}

 

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

 

Probably caused by : vsdatant.sys ( vsdatant+2a31b )

 

Followup: MachineOwner

---------

 

i drugi

 

 

 

Microsoft ® Windows Debugger Version 6.4.0007.2

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\WINDOWS\Minidump\Mini051705-02.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 (Service Pack 1) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30

Debug session time: Tue May 17 19:56:45.937 2005 (GMT+2)

System Uptime: 0 days 1:10:28.492

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

* 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

Unable to load image vsdatant.sys, Win32 error 2

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

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

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

* *

* Bugcheck Analysis *

* *

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

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 1000008E, {c0000005, f5e2331b, f59beb1c, 0}

 

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

 

Probably caused by : vsdatant.sys ( vsdatant+2a31b )

 

Followup: MachineOwner

---------

 

no iteraz niw zab nie wiem o co chodzi

pomóżcie ;)

[Nyny]

No i juz wiadomo o co chodzi:

vsdatant.sys i wszystko jasne.

Wywal tego pieprzonego zone alarma i klopot powinien zniknac.

Juz mialem kiedys podobny problem z tym firewallem na forum dobrze ze debugger jest :)

Napisz co i jak jak odinstalujesz ten sciek

[Agrest]

witam

Nyny miał rację

odinstalowałem ZA ver.4.5 i ...

po problemie

a poniewaz sie przyzwyczailem do tego firewalla zainstalowalem wersję 5.5 :D

tak czy siak Nyny rządzi ;)

wielkie dzięki :D

geniusz debugera :D

jeszcze raz big thx

[Nyny]

Ciesze sie ze moglem pomoc. Bo jak wiadomo debugger nie zawsze działa P