Restart – przyczyna 0*0000008E
Proszę o pomoc.mój komp się często restartował, przeszukałem wasze forum(chodziłem chyba wszędzie,poprzez wyszukiwarkę) próbując znaleźć nazwe sterownika o kodzie:STOP:0*0000008E (O*C0000005, 0*804DB655, 0*F979AB0C, 0*00000000).Nic nie znalazłem.Czy ktoś moźe wie jak odszukać nazwe tego sterownika.Zrobiłem Debugging tools,co mogę jeszcze zrobić,proszę o pomoc bo zaczynam sie w tym pomału gubić a nie błyszce wiedzą na temat komp.
Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini120205–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 = 0x8055a420
Debug session time: Fri Dec 2 13:39:36.218 2005 (GMT+1)
System Uptime: 0 days 3:45:37.803
*********************************************************************
* 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 unloaded module list
....................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze –v to get detailed debugging information.
BugCheck 1000007F, {8, 80042000, 0, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Followup: MachineOwner
–––––––––
Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini120205–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 = 0x8055a420
Debug session time: Fri Dec 2 13:39:36.218 2005 (GMT+1)
System Uptime: 0 days 3:45:37.803
*********************************************************************
* 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 unloaded module list
....................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze –v to get detailed debugging information.
BugCheck 1000007F, {8, 80042000, 0, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Followup: MachineOwner
–––––––––
Odpowiedzi: 2
Czołem!sprawdzałem strony które mi podałeś ale szukanie tam to jak studnia bez dna.Narazie zaktualizowałem sterowniki do karty graficznej,nie wiem czy to pomoźe.Jak narazie restartu przez te 3 dni nie było,moźe dlatego ze komp mi krótko pracował,nie miałem zaspecjalnie czasu.A odnosnie czasu,kiedy były restarty(2–3 razy dzinnie,czasami nawet 2 razy w ciągu 10 min.podczas normalnej pracy na kompie,chodzenia po internecie).Niewiem czy czasami powodem tych restartów moźe być karta sieciowa,bo jest ona zintegrowana z płyta gł.Jak ktoś cos wie na ten temat to prosze o odp.Podaje parametry mojego kompa:
proc. Celeron D325 2.53GHz
pamięć DDR 256MB/PC400
HDD WD 80 GB 7200
MB ABIT VT7 VIA PT880
karta graficzna:Radeon 9200 series
Radeon 9200 series–secondary
karta sieciowa–zintegrowana z płytą gł.:VIA Rhine IIfast ethernet adapter
proc. Celeron D325 2.53GHz
pamięć DDR 256MB/PC400
HDD WD 80 GB 7200
MB ABIT VT7 VIA PT880
karta graficzna:Radeon 9200 series
Radeon 9200 series–secondary
karta sieciowa–zintegrowana z płytą gł.:VIA Rhine IIfast ethernet adapter
Tak? Nic nie ma? a tutaj: http://forum.centrumxp.pl/viewtopic.php?t=42375&highlight=0x0000008e albo http://forum.centrumxp.pl/viewtopic.php?t=30805&highlight=0x0000008e bądz jeszcze tutaj http://forum.centrumxp.pl/viewtopic.php?t=26049&highlight=0x0000008e. To tylko czubek góry lodowej jaka została opisana na temat tego błedu... więc nie ściemniaj tylko czytaj.
Fajnie by było wiedzie jaki masz komputer jeszcze... to czasami jest przydatne (no i kiedy następują restarty).
Fajnie by było wiedzie jaki masz komputer jeszcze... to czasami jest przydatne (no i kiedy następują restarty).
Strona 1 / 1