malamb utworzono 6 grudnia 2010 utworzono 6 grudnia 2010 (edytowane) witam, mam problem z laptopem, co jakiś czas wyskakuje blue screen i następuje reset. tak wygląda zrzut z raportu: Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [E:\Users\Gosi\Desktop\120610-26161-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 \SystemRoot\system32\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 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02a4e000 PsLoadedModuleList = 0xfffff800`02c8be50 Debug session time: Mon Dec 6 10:19:59.422 2010 (GMT+1) System Uptime: 0 days 0:09:59.545 ********************************************************************* * 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 \SystemRoot\system32\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 A, {0, 2, 0, fffff80002adfa83} ***** 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+91a83 ) Followup: MachineOwner --------- czy możliwe jest, że to wirus? wcześniej przeinstalowałam na nowo system, bo laptop się resetował tuż po starcie, teraz restartuje się tylko raz na jakiś czas... proszę o pomoc
raazor90 komentarz 8 grudnia 2010 komentarz 8 grudnia 2010 Brak symboli! Wykonaj: [quote][b]UWAGA:[/b] Jeśli na ekranie pojawi się komunikat: Cytat [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]
Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!
Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.