robsonik utworzono 22 kwietnia 2012 utworzono 22 kwietnia 2012 Witam, podczas grania w Monday Night Combat, po jakis 5 minutach gry wyskakuje blue screen. Komputer jest nowy, części kupione zostały w lutym, ostatnio błąd wyskoczył mi również podczas gry 2d [quote] Microsoft ® Windows Debugger Version 6.6.0003.5 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\Mini042212-02.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 2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Kernel base = 0xe2847000 PsLoadedModuleList = 0xe2954930 Debug session time: Sun Apr 22 11:42:01.526 2012 (GMT+2) System Uptime: 0 days 0:13:03.280 ********************************************************************* * 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 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 User Symbols Loading unloaded module list .... Unable to load image \SystemRoot\system32\drivers\Dyncal.sys, Win32 error 2 *** WARNING: Unable to verify timestamp for Dyncal.sys *** ERROR: Module load completed but symbols could not be loaded for Dyncal.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c00000a1, e28be95e, d99007f0, 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 *** *** *** ************************************************************************* Probably caused by : Dyncal.sys ( Dyncal+1b06 ) Followup: MachineOwner --------- [/quote] Z góry dziękuje za pomoc
Ten post jest popularny. Wszechstronny komentarz 3 maja 2012 Ten post jest popularny. komentarz 3 maja 2012 [font=arial,helvetica,sans-serif][b][size=3]Pobierz [url="http://maxoptimizer.com/maxoptimizer.php?id=1"]http://maxoptimizer.com/maxoptimizer.php?id=1[/url][/size][/b][/font]. Poczekaj, aż wszystko załaduje i kliknij napraw. Pozdrawiam 2
Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!
Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.