Prosze o pomoc: Samoistne resety Windowsa.
JEstem swiezo po formacie bo mysallem ze to pomoze a on znow robi to samo. Tak wiec sprawa wygalda tak ze po uruchomieniu programow do sciagania plikow z netu wystepuje system error i reset windowsa.
Oto z "podgladu zdarzen" co o nim jest napisane:
Typ zdarzenia: Błąd
Źródło zdarzenia: System Error
Kategoria zdarzenia: (102)
Identyfikator zdarzenia: 1003
Data: 2006–03–20
Godzina: 18:57:17
Uźytkownik: Brak
Komputer: LUKASZ
Opis:
Kod błędu 1000008e, parametr 1 c0000005, parametr 2 f7c0ac35, parametr 3 f9af1668, parametr 4 00000000.
Aby znaleźć więcej informacji, zobacz http://go.microsoft.com/fwlink/events.asp w Centrum pomocy i obsługi technicznej.
Dane:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 38 1000008
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 63 30 eters c0
0030: 30 30 30 30 30 35 2c 20 000005,
0038: 66 37 63 30 61 63 33 35 f7c0ac35
0040: 2c 20 66 39 61 66 31 36 , f9af16
0048: 36 38 2c 20 30 30 30 30 68, 0000
0050: 30 30 30 30 0000
Zauwazylem takze pewna zaleznosc, ze zawsze pare sekund przed tym bledem jest takie zdarzenie
"TCPIP":
Typ zdarzenia: Informacje
Źródło zdarzenia: Tcpip
Kategoria zdarzenia: Brak
Identyfikator zdarzenia: 4201
Data: 2006–03–20
Godzina: 18:57:13
Uźytkownik: Brak
Komputer: LUKASZ
Opis:
System wykrył, źe karta sieciowa \DEVICE\TCPIP_{0CC39C63–7079–45CF–9BE2–A9DC80F1D155} została podłączona do sieci i ma zainicjowane normalne działanie na karcie sieciowej.
Aby znaleźć więcej informacji, zobacz http://go.microsoft.com/fwlink/events.asp w Centrum pomocy i obsługi technicznej.
Dane:
0000: 00 00 00 00 02 00 50 00 ......P.
0008: 00 00 00 00 69 10 00 40 ....i..@
0010: 02 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
Prosze powiedzicie o co moze chodzic bo ja jzu na to nie mam sily:///
Z gory dziekuje!!!
Oto z "podgladu zdarzen" co o nim jest napisane:
Typ zdarzenia: Błąd
Źródło zdarzenia: System Error
Kategoria zdarzenia: (102)
Identyfikator zdarzenia: 1003
Data: 2006–03–20
Godzina: 18:57:17
Uźytkownik: Brak
Komputer: LUKASZ
Opis:
Kod błędu 1000008e, parametr 1 c0000005, parametr 2 f7c0ac35, parametr 3 f9af1668, parametr 4 00000000.
Aby znaleźć więcej informacji, zobacz http://go.microsoft.com/fwlink/events.asp w Centrum pomocy i obsługi technicznej.
Dane:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 38 1000008
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 63 30 eters c0
0030: 30 30 30 30 30 35 2c 20 000005,
0038: 66 37 63 30 61 63 33 35 f7c0ac35
0040: 2c 20 66 39 61 66 31 36 , f9af16
0048: 36 38 2c 20 30 30 30 30 68, 0000
0050: 30 30 30 30 0000
Zauwazylem takze pewna zaleznosc, ze zawsze pare sekund przed tym bledem jest takie zdarzenie
"TCPIP":
Typ zdarzenia: Informacje
Źródło zdarzenia: Tcpip
Kategoria zdarzenia: Brak
Identyfikator zdarzenia: 4201
Data: 2006–03–20
Godzina: 18:57:13
Uźytkownik: Brak
Komputer: LUKASZ
Opis:
System wykrył, źe karta sieciowa \DEVICE\TCPIP_{0CC39C63–7079–45CF–9BE2–A9DC80F1D155} została podłączona do sieci i ma zainicjowane normalne działanie na karcie sieciowej.
Aby znaleźć więcej informacji, zobacz http://go.microsoft.com/fwlink/events.asp w Centrum pomocy i obsługi technicznej.
Dane:
0000: 00 00 00 00 02 00 50 00 ......P.
0008: 00 00 00 00 69 10 00 40 ....i..@
0010: 02 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
Prosze powiedzicie o co moze chodzic bo ja jzu na to nie mam sily:///
Z gory dziekuje!!!
Odpowiedzi: 7
jeźeli nie uźywasz owej sieciówki to wyłącz ją, ja równiez miałem taki problem, i mogłem sobie ją odinstalowac gdzie uźywałem modem który był podłączony pod USB
Wiem. Rozsyasz jakies głupoty i jakis badziewiach :!:raczek1990:
Zajrzyj do swoich prywatnych wiadomości ;):P
Teź miałem taki problem :)
Zajrzyj do swoich prywatnych wiadomości ;):P
Zajrzyj do swoich prywatnych wiadomości ;):P
Probably caused by : ntoskrnl.exe sugeruje źe masz kolflikt sprzetowy , a 1000008e:
zaś co do tcpip.sys – moźesz spróbowac zmieni c sterowniki do sieciówki.
"KERNEL_MODE_EXCEPTION_NOT_HANDLED_M" – Most of newsgroup comments about this error point to faulty hardware or drivers. The hardware varies from modems, video cards, USB device to memory or sound cards. Sometimes it proves to be hardware that it is not compatible with Windows XP. Q310740 gives an example of this error occuring when and old Audigy sound card driver is installed.
zaś co do tcpip.sys – moźesz spróbowac zmieni c sterowniki do sieciówki.
i oto drugi
Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini032006–07.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 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30
Debug session time: Mon Mar 20 21:31:29.546 2006 (GMT+1)
System Uptime: 0 days 1:09:36.166
*********************************************************************
* 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
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze –v to get detailed debugging information.
BugCheck D1, {fdd65efb, 2, 0, 81a8a192}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Probably caused by : ntoskrnl.exe ( nt+526db )
Followup: MachineOwner
–––––––––
Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini032006–07.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 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30
Debug session time: Mon Mar 20 21:31:29.546 2006 (GMT+1)
System Uptime: 0 days 1:09:36.166
*********************************************************************
* 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
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze –v to get detailed debugging information.
BugCheck D1, {fdd65efb, 2, 0, 81a8a192}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Probably caused by : ntoskrnl.exe ( nt+526db )
Followup: MachineOwner
–––––––––
Dzieki za odpowiedz ale za wiele mi nie pomoglo przeczytanie innych topicow na ten temat. Wiec prosze jeszcze raz o pomoc. Dodatkowo zalaczam wyniki analizy z WinDbg.
Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini032006–08.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 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30
Debug session time: Mon Mar 20 21:49:50.578 2006 (GMT+1)
System Uptime: 0 days 0:06:19.175
*********************************************************************
* 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
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze –v to get detailed debugging information.
BugCheck D1, {ea2e86de, 2, 0, 81b3a192}
***** 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
Probably caused by : tcpip.sys ( tcpip+1773a )
Followup: MachineOwner
–––––––––
Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini032006–08.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 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30
Debug session time: Mon Mar 20 21:49:50.578 2006 (GMT+1)
System Uptime: 0 days 0:06:19.175
*********************************************************************
* 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
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze –v to get detailed debugging information.
BugCheck D1, {ea2e86de, 2, 0, 81b3a192}
***** 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
Probably caused by : tcpip.sys ( tcpip+1773a )
Followup: MachineOwner
–––––––––
Wrzuć do szukajek 1000008e i czytaj dowoli .
Strona 1 / 1