[win xp] błąd 0x1000008e

**Posty:** 106 · przez **danielc1** 02 Paź 2008, 18:09

Witam. Ostatnio pojawił się u mnie BS.m Oto kody błędów:
Nastąpił ponowny rozruch komputera po operacji wykrywania błędów. Wyniki tej operacji były następujące: 0x1000008e (0xc000001d, 0x805bbd01, 0xa7669afc, 0x00000000). Zrzut zapisano w: C:\WINDOWS\Minidump\Mini100208-01.dmp.

Czym są spowodowane te błędy??

**Posty:** 8001 · przez **Okocza** 02 Paź 2008, 18:39

po 1 jaki komputer, zmieniałeś coś ostatnio :?:

**Posty:** 106 · przez **danielc1** 02 Paź 2008, 19:00

Półtora roku temu kupowałem nową kartę graficzną- GF7600GS Silent od ASUSA.

Totaj log z DToW:

Kod: Zaznacz wszystko: Microsoft (R) Windows Debugger Version 6.9.0003.113 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini100208-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 0n2 *** 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 3) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Kernel base = 0x804d7000 PsLoadedModuleList = 0x80553fc0 Debug session time: Thu Oct 2 17:56:05.890 2008 (GMT+2) System Uptime: 0 days 7:38:15.512 ********************************************************************* * 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 0n2 *** 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 1000008E, {c000001d, 805bbd01, a7669afc, 0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. *** WARNING: Unable to verify timestamp for rdbss.sys *** ERROR: Module load completed but symbols could not be loaded for rdbss.sys ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* ********************************************************************* * 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+ * ********************************************************************* ********************************************************************* * 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+ * ********************************************************************* Probably caused by : hardware ( rdbss+54a ) Followup: MachineOwner ---------

**Posty:** 8001 · przez **Okocza** 02 Paź 2008, 19:06

danielc1 napisał(a):GF7600GS Silent od ASUSA.

czyżbyś wcześniej nie miał przypadkiem ATi :?:

Jeśli tak przeinstaluj sterowniki, stare usuwając a nowe instalując na nowo.

Użyj Driver Cleaner'a żeby usunąć pozostałości po ATI

**Posty:** 106 · przez **danielc1** 02 Paź 2008, 19:18

NIe miałem karty ATI. Miałem GF FX 5500.

**Posty:** 8001 · przez **Okocza** 02 Paź 2008, 19:23

danielc1 napisał(a):Miałem GF FX 5500.

możliwe że zostało się po tym jeszcze.

**Posty:** 106 · przez **danielc1** 02 Paź 2008, 19:40

Po wymianie kilka razy był formatowany dysk.

**Posty:** 8001 · przez **Okocza** 02 Paź 2008, 19:42

w takim wypadku odinstaluj stare, zastosuj Driver Cleanera i zainstaluj nowsze.

**Posty:** 106 · przez **danielc1** 02 Paź 2008, 22:38

Ok. Przeinstaluję. Wcześniej nie miałem takich problemów :evil:

Jeśli będzie się powtarzać BSOD to napiszę posta. Dzięki.