szczepan997 utworzono 27 kwietnia 2013 utworzono 27 kwietnia 2013 Witam, grałem sobie w World of tanks i nagle pojawił się bluescreen: Podpis problemu: Nazwa zdarzenia problemu: BlueScreen Wersja systemu operacyjnego: 6.1.7601.2.1.0.256.1 Identyfikator ustawień regionalnych: 1045 Dodatkowe informacje o problemie: BCCode: 1e BCP1: FFFFFFFFC0000005 BCP2: FFFFF88004ACA2B4 BCP3: 0000000000000000 BCP4: 000000000000FF7E OS Version: 6_1_7601 Service Pack: 1_0 Product: 256_1 Pliki pomagające opisać problem: C:\Windows\Minidump\042713-29998-01.dmp C:\Users\Kamil\AppData\Local\Temp\WER-51449-0.sysdata.xml zdjęcie: http://www.tinypic.pl/jd6u9pvl7jr5
Youki komentarz 27 kwietnia 2013 komentarz 27 kwietnia 2013 Podaj pełną konfigurację Twojego PC wraz z marką i mocą zasilacza. Pokaż plik z folderu minidump --> http://www.forumpc.pl/tutorials/article/79-debugging-tools-for-windows-i-pliki-minidump/
szczepan997 komentarz 27 kwietnia 2013 Autor komentarz 27 kwietnia 2013 (edytowane) Procek: AMD Phenom II X6 1075t wkrecony na 3.5GHz w Turbo 4GHz Karta graficzna: AMD RADEON HD 6850 OC 1GB Gigabyte Płyta główna: ASUS M4A88T-V EVO/USB3 Pamięć RAM: Patriot Viper Series CL7 DDR3 1333MHz 6GB DYSK twardy( na którym jest sytsem): WDC WD5000AADS-00S9B0Zasilacz: Be Quiet! Pure Power L8 630W Modularny Microsoft (R) Windows Debugger Version 6.11.0001.402 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\042713-29998-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 7601 (Service Pack 1) MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533 Machine Name: Kernel base = 0xfffff800`03857000 PsLoadedModuleList = 0xfffff800`03a9a670 Debug session time: Sat Apr 27 22:32:26.952 2013 (GMT+2) System Uptime: 0 days 2:24:43.700 ********************************************************************* * 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 1E, {ffffffffc0000005, fffff88004aca2b4, 0, ff7e} Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for dxgkrnl.sys *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys ***** 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 : dxgkrnl.sys ( dxgkrnl+22b4 )
Youki komentarz 28 kwietnia 2013 komentarz 28 kwietnia 2013 Wstępnie to usuń Directa, wyczyść rejestr po nim i zainstaluj najnowszego. Blad był jednorazowy ? Spakuj ten plik i wrzuć na jakiś dysk internetowy, pobiore go sobie i sprawdzę dokładnie co i jak u siebie.
szczepan997 komentarz 28 kwietnia 2013 Autor komentarz 28 kwietnia 2013 (edytowane) ten błąd pojawił się tylko wczoraj, ale okolo tygodnia temu pojawil sie inny: http://www.tinypic.pl/qfjq308c92yc wrzucić plik minidump czy ten dxgkrnl.sys?
Youki komentarz 28 kwietnia 2013 komentarz 28 kwietnia 2013 Wrzuć cały plik. Masz płytkę z Windowsem w celu naprawy systemu?
szczepan997 komentarz 28 kwietnia 2013 Autor komentarz 28 kwietnia 2013 http://www.sendspace.pl/file/4463572448dba01f923683e/042713-29998-01 mam płyte.
Youki komentarz 28 kwietnia 2013 komentarz 28 kwietnia 2013 Instalowałeś, aktualizowałeś coś ostatnio ?
Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!
Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.