lisekx 0 Napisano 5 Grudnia 2017 Udostępnij Napisano 5 Grudnia 2017 Witam, od wczoraj mam problem z samoistnym resetem kompa i bluescreen'em. Nie instalowałem od miesiąca żadnych nowych programów.Komp:Windows 7Procesor: Intel Core i3 540, 3066 MHzPłyta główna: Gigabyte GA-P55-US3L ver.2.0Grafika: Gigabyte HD 7770 ver. 2.0Pamięć: Crucial 2x4GB DDR3-1600Dyski: SSD 250GB Crucial 250MX WDC 500GB WD5000AACS-00ZUB0 WDC 500GB WD5001AALS-00LWTA0Zasilacz: CHIEFTEC 450W GPS-450AA-101ABędę wdzięczny za pomoc. W pliku z raportem błędu mam coś takiego: Microsoft (R) Windows Debugger Version 6.11.0001.402 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\BLUE\Desktop\120517-11154-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 *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.23864.amd64fre.win7sp1_ldr.170707-0600 Machine Name: Kernel base = 0xfffff800`03014000 PsLoadedModuleList = 0xfffff800`03256750 Debug session time: Tue Dec 5 18:24:56.410 2017 (GMT+1) System Uptime: 0 days 0:19:08.752 ********************************************************************* * 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 *** 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 1E, {0, 0, 0, 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 <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+6f950 ) Followup: MachineOwner ---------Jeśli jeszcze jest coś potrzebne do zdiagnozowania problemu to dajcie znać Cytuj Link to post Share on other sites
lonialomax 806 Napisano 5 Grudnia 2017 Udostępnij Napisano 5 Grudnia 2017 Z tego debugera nic nie wynika brak symboli do poprawnego odczytu Mini Dump, Symbol search path is: *** Invalid *** Wrzuć plik Mini Dump na jakiś hosting plików. Cytuj Link to post Share on other sites
Pankracy666 312 Napisano 6 Grudnia 2017 Udostępnij Napisano 6 Grudnia 2017 Wyjmij jedną kość pamięci i sprawdź czy dzieje się to samo. Jeżeli tak to zrób identyczny zabieg z drugą kością - zobacz czy pojedynczo będzie w porządku. Druga rzecz obejrzyj kondensatory na płycie głównej czy nie są wybrzuszone (spuchnięte): Cytuj Link to post Share on other sites
lisekx 0 Napisano 6 Grudnia 2017 Autor Udostępnij Napisano 6 Grudnia 2017 Z tego debugera nic nie wynika brak symboli do poprawnego odczytu Mini Dump, Symbol search path is: *** Invalid *** Wrzuć plik Mini Dump na jakiś hosting plików. http://www110.zippyshare.com/v/RQ3PQuIX/file.html Cytuj Link to post Share on other sites
lonialomax 806 Napisano 6 Grudnia 2017 Udostępnij Napisano 6 Grudnia 2017 Blue-screen dotyczy problemu ze sterownikiem systemowym CLASSPNP.SYS a wywołuje go proces avp.exe. Czy Twój antywirus to Kaspersky? Jeżeli tak to odinstaluj go i sprawdź czy jest poprawa. Wcześniej ruchom Wiersz poleceń jako administrator i polecenie sfc /scannow. Wykonaj diagnostykę PC w/g http://forum.benchmark.pl/topic/192366-faq-diagnostyka-komputera/ Cytuj Link to post Share on other sites
lisekx 0 Napisano 6 Grudnia 2017 Autor Udostępnij Napisano 6 Grudnia 2017 Tak mój antywirus to Kaspersky, sfc /scannow znalazł jakieś pliki, których nie moze naprawić poprawne dane z debuggera Microsoft (R) Windows Debugger Version 6.11.0001.402 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\BLUE\Desktop\120617-13494-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 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.23864.amd64fre.win7sp1_ldr.170707-0600 Machine Name: Kernel base = 0xfffff800`0301d000 PsLoadedModuleList = 0xfffff800`0325f750 Debug session time: Wed Dec 6 01:33:30.170 2017 (GMT+1) System Uptime: 0 days 7:07:31.138 Loading Kernel Symbols ............................................................... ................................................................ ................................................ Loading User Symbols Loading unloaded module list ............ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {0, 0, 0, 0} Unable to load image \SystemRoot\system32\DRIVERS\klbackupdisk.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for klbackupdisk.sys *** ERROR: Module load completed but symbols could not be loaded for klbackupdisk.sys Cytuj Link to post Share on other sites
lonialomax 806 Napisano 6 Grudnia 2017 Udostępnij Napisano 6 Grudnia 2017 sfc /scannow znalazł jakieś pliki, których nie moze naprawić To czeka Cię reinstalacja systemu, albo naprawa plików systemu https://support.microsoft.com/pl-pl/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system 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ą.