Witam
MOja konfiguracja jest w podpisie. Mam System swieżo po formacie. Antivirus Avira Premium Security wersja 30 dniowa.
Oto log z programu Debugging Tools for Windows 32-bit Version
Microsoft ® Windows Debugger Version 6.11.0001.404 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] 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 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0x81e33000 PsLoadedModuleList = 0x81f4ac70 Debug session time: Sun May 24 20:02:04.484 2009 (GMT+2) System Uptime: 0 days 0:01:18.141 ********************************************************************* * 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 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, {c0000005, 8207ad42, 9acc4a4c, 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Probably caused by : hardware ( nt+247d42 ) Followup: MachineOwner ---------
Wszystkie sterowniki mam najnowsze. Do ATI RAdona mam wersję 9.5. Blue Screen pojawił mi się dwa razy tylko przy wyłączaniu VISTY. W grach typu GTA4 wszystko śmiga bez problemu.
Proszę o pomoc
ja taki sam problem miałem zmieniłem pamieć ram i pomogło, ja miałem problem z ram, jak masz jakąś pamięć to sprawć
błąd powoduje sprzęt,
Probably caused by : hardware ( nt+247d42 )
poza tym chyba coś nie tak z sterownikami do karty graficznej,
BugCheck 1000008E, {c0000005, 8207ad42, 9acc4a4c, 0}
odinstaluj je i zainstaluj najnowsze ze strony producenta
Witam
Więc tak problem z niebieskimi ekranami podczas wyłączania Visty wsystąpił tylko na sterach 9.5. Miałem dwa systemy w jednym blue screen był spowodowany starymi sterami od modemu Speed Touch 330 (teraz jest ok)
Zainstalowałem po raz kolejny i tylko nęka mnie blue screen na wyłączaniu Visty.
Być może ma to związek z sterami od grafy 9.5 (tylko że wedle sugestii są najnowsze zainstalowane).
Boje się je odinstalwoać. Bo stery od Ati radoeona są niedopracowane, kiedyś odinstalowałem i zainstalowałem nowsze i za każdym razem wystąpił problem z ponownym zainstalowaniem. Może macie jakąś instrukcję jak prawidłowo odinstalować stery.
Pamięci sprawdzałem 0,5 roku temu GOLDMEMORY i zero błędów.
Mam podkręconego kompa. Może to powodować błąd. Z tym że na starym systemie blue screen na wyłączaniu kompa nie wystepował.
Procesor C2D e7300 2,66 GHZ mam podkręcony na 3.30
Nie wiem jakie napięcie ustawić na RAMIE (obecnie jst na auto)
Ogólnie temperatury są w normie.
Dziwie się że może to być wina sterownika grafy skoro podczas gier błąd nie wystepuje, a wydajność w porównaniu do starego systemu i sterów 8.8 wzrosła może z 15%.
Będę wdzięczny za dalszą pomoc.
Być może problem tkwi w złym podkręceniu kompa
A możecie mi powiedzieć od czego jest plik:
ntoskrnl.exe
Teraz przy włączaniu kompa pojawił się niebieski ekran i ten plik go spowodował.