aleksander12 65 Napisano 16 Sierpnia 2012 Udostępnij Napisano 16 Sierpnia 2012 Witam!! Mam problem z takim bluescreenem zainstalowałem debugging tools for windows i oto co mi pokazał z plikiu minidump , jednak ja nic z tego nie rozumiem czy ktoś obeznany w temacie domyśla się co moze być przyczyną tego bluescreena???? 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 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030 Kernel base = 0xfffff800`02e00000 PsLoadedModuleList = 0xfffff800`03044670 Debug session time: Thu Aug 16 11:06:39.281 2012 (GMT+2) System Uptime: 0 days 0:00:33.077 ********************************************************************* * 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 .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff8800d40e104, 0, fffff88008d089b4, 2} ***** 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 *** *** *** ************************************************************************* Unable to load image \??\C:\Windows\system32\drivers\IOMap64.sys, Win32 error 2 *** WARNING: Unable to verify timestamp for IOMap64.sys *** ERROR: Module load completed but symbols could not be loaded for IOMap64.sys Probably caused by : IOMap64.sys ( IOMap64+19b4 ) Followup: MachineOwner Cytuj Link to post Share on other sites
Vercruysse 148 Napisano 16 Sierpnia 2012 Udostępnij Napisano 16 Sierpnia 2012 Zobacz na tej stronie http://support.microsoft.com/kb/903251/pl Cytuj Link to post Share on other sites
aleksander12 65 Napisano 16 Sierpnia 2012 Autor Udostępnij Napisano 16 Sierpnia 2012 Nie mam wirusa sprawdziłem Cytuj Link to post Share on other sites
Vercruysse 148 Napisano 17 Sierpnia 2012 Udostępnij Napisano 17 Sierpnia 2012 Taki błąd niekoniecznie musi być od wirusa.Przetestuj pamięć programem diagnostycznym,jeśli Ci się chce zrób kilka razy.Dokładnie chodzi oto że jedno skanowanie może czasem nie wykryć błędów pamięci.Druga przyczyna to sterowniki lub antywirus,wystarczy przeinstalować na nowszą wersję. Cytuj Link to post Share on other sites
Recommended Posts
Dołącz do dyskusji
Możesz dodać zawartość już teraz a zarejestrować się później. Jeśli posiadasz już konto, zaloguj się aby dodać zawartość za jego pomocą.