pa44wlak1 utworzono 31 sierpnia 2010 utworzono 31 sierpnia 2010 (edytowane) Mam Problem co 30 minut do kilku godzin, dni mam blue screena Mam Viste 32 bit Po otwarciu pliku minidump programem WINDbg wyświetla się to : Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\Mini083110-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 Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Machine Name: Kernel base = 0x83411000 PsLoadedModuleList = 0x83528c70 Debug session time: Tue Aug 31 14:49:27.992 2010 (GMT+2) System Uptime: 0 days 0:19:45.773 ********************************************************************* * 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, {c0000005, 83644d32, a53e1bd4, 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 *** *** *** ************************************************************************* ********************************************************************* * 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 : ntoskrnl.exe ( nt+233d32 ) Followup: MachineOwner --------- Nie wiem co zrobić proszę o pomoc !!!
raazor90 komentarz 6 września 2010 komentarz 6 września 2010 Brak symboli! Wykonaj poniższe czynności: [quote] [b]UWAGA:[/b] Jeśli na ekranie pojawi się komunikat: [quote]***** Kernel symbols are WRONG. Please fix symbols to do analysis.[/quote] Oznacza to, że musimy [b]pobrać symbole[/b] do swojego systemu dzięki którym odczytamy [b]w całości[/b] plik minidump - na tym etapie jest on niekompletny i może wskazywać nie ten plik co trzeba. Zamykamy Debuggera. Po ponownym jego uruchomieniu klikamy [i]File[/i] -> [i]Symbol File Path[/i] -> wpisujemy: [b]SRV*c:\symbols*http://msdl.microsoft.com/download/symbols[/b] Następnie wciskamy [ctrl] + [D] i wskazujemy znów nasz plik minidump. Trzeba poczekać aż Debugger ściągnie sobie wszystkie symbole i przeanalizuje cały plik. Należy pamiętać że ten proces może nieco potrwać - symbole mogą ważyć nawet ponad 10MB, także trzeba uzbroić się w cierpliwość. 6. Wklejamy część [b]minidumpa[/b], o której mowa, na forum. [/quote]
pa44wlak1 komentarz 7 września 2010 Autor komentarz 7 września 2010 Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\Mini090710-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458 Machine Name: Kernel base = 0x83450000 PsLoadedModuleList = 0x83567c70 Debug session time: Tue Sep 7 17:44:46.250 2010 (GMT+2) System Uptime: 0 days 0:09:27.386 Loading Kernel Symbols ............................................................... ................................................................ ..................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, 83683d32, a0954bd4, 0} Probably caused by : ntkrpamp.exe ( nt!NtQueryInformationThread+2a4 ) Followup: MachineOwner --------- CO TERAZ ???
raazor90 komentarz 8 września 2010 komentarz 8 września 2010 Test pamięci RAM bootowalnym MemTest86+ przez min. 6 godzin dla każdej kości (osobno!)
Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!
Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.