restartowanie komputera
Mój komputer od pewnego czasu sam się restartuje, nie wiem co jest grane. Nie uruchamia sie ponownie, tylko od razu tak jak reset. Wie ktoś o co moźe z tym chodzić?
Odpowiedzi: 20
a jest taka moźliwość źeby po błędzie komputer się nie resetował?? da się gdzieś to ustawić?
dzieki. zakonczylem instalacje sterownikow i komp sie nie restertuje :wink:
No widzisz. Jak chcesz, to potrafisz :P .
Musze dodac:
upade zrob.
Musze dodac:
upade zrob.
aha starczy jak zainstaluje te nowe sterowniki, czy stare teź muszę odinstalować?
ok działa, bo ja jakiś inny znalazłem i nie mogłem ściągnać. thx.
Jak to "nia dziala" ? Wszystko dziala.
http://support.dlink.com/downloads/
http://support.dlink.com/downloads/
tylko jest taki problem źe się nie da ich ściągnąć z dlink.com... link nie działa, wiesz moźe skąd mógłbym je ściągnąć?
Nowsze, starsze – wsio ryba. Wazne, zeby systemowi pasowaly.
czyli muszę sterowniki na nowsze przeinstalować?
D–link – sterowniki.mat1989:Probably caused by : airplus.sys
usunąłem firewall ale błąd dalej wyskakuje. natomiast ten drugi juź nie; pozostał taki:
Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini031506–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 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 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Wed Mar 15 16:31:53.890 2006 (GMT+1)
System Uptime: 0 days 0:00:54.484
*********************************************************************
* 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 NDIS.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for NDIS.sys
*** ERROR: Module load completed but symbols could not be loaded for NDIS.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze –v to get detailed debugging information.
BugCheck 100000D1, {2f223d63, 2, 0, 82417192}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** WARNING: Unable to verify timestamp for psched.sys
*** ERROR: Module load completed but symbols could not be loaded for psched.sys
*** WARNING: Unable to verify timestamp for airplus.sys
*** ERROR: Module load completed but symbols could not be loaded for airplus.sys
Probably caused by : airplus.sys ( airplus+bbb )
Followup: MachineOwner
–––––––––
mat1989:ale przedtem teź miałem zone alarm tylko niźszą wersję i normalnie chodziło.
Moźe dlatego normalnie chodziło.
mat1989:a tak się zapytam czym byś radził zastąpić?
Na początku sugeruję włączyć firewalla wbudowanego w Windowsa. Dopiero po jakimś czasie (gdy wszystko będzie działało poprawnie) zdecyduj co dalej – albo zostaw tego wbudowanego albo rozejrzyj sie po forum, bo tematów o tym jaki firewall najlepszy to przewinęło się na forum parę(naście).
ale przedtem teź miałem zone alarm tylko niźszą wersję i normalnie chodziło. a tak się zapytam czym byś radził zastąpić?
Probably caused by : vsdatant.sys ( vsdatant+1de2f )
ZoneAlarm. Masz odinstaluj, zastąp czymś innym i sprawdź.
Loading Dump File [C:\WINDOWS\Minidump\Mini031106–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 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 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Sat Mar 11 14:19:36.875 2006 (GMT+1)
System Uptime: 0 days 1:16:19.469
*********************************************************************
* 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 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 10000050, {ff0cc000, 0, 82335102, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for NDIS.sys
*** ERROR: Module load completed but symbols could not be loaded for NDIS.sys
*** WARNING: Unable to verify timestamp for psched.sys
*** ERROR: Module load completed but symbols could not be loaded for psched.sys
Probably caused by : vsdatant.sys ( vsdatant+20b4b )
Followup: MachineOwner
–––––––––
następny plik i w sumie są tylko te dwa bugi bo reszta się powtarza.
mam tam kilka plików,
sprawdziłem z ostatnią datą i przedstawia się następująco:
sprawdziłem z ostatnią datą i przedstawia się następująco:
Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini031106–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 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 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Sat Mar 11 13:02:58.359 2006 (GMT+1)
System Uptime: 0 days 0:08:51.955
*********************************************************************
* 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 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 100000D1, {76206e6f, 2, 0, 82363192}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Probably caused by : vsdatant.sys ( vsdatant+1de2f )
Followup: MachineOwner
–––––––––
btw :D –> http://forum.centrumxp.pl/viewtopic.php?t=48063 identyczny problem i moźliwe rozwiązanie
Kolego, przeczytaj jeszcze raz post Rebego i zrob to, co zasugerowal. Dopiero wtedy mozemy zabrac sie za pomoc na ktora czekasz.
np strona : http://www.sxc.hu/
a sterowniki z płytki od producenta.
a sterowniki z płytki od producenta.
Jakie sterowniki i jaka strona ?
Ty jestes DragonN ?
Ty jestes DragonN ?