gniazdo utworzono 20 lutego 2014 utworzono 20 lutego 2014 Witam Mam problem podczas grania w diablo 3 Lub siedzenia na internecie i jednoczesnie słuchania muzyki wyskakuje mi Blue screen Taki jak na Zdjęciu Mój sprzęt to Procesor : AMD FX(tm)- 6300 six-core processor 3.5 Ghz Pamięć ram 8 gb DDR3 1600mhz 1 kostka Karta graficzna GTX- 650 1gb Płyta głowna Assus M5A78L-M LX3 zasilacz MMODECOM 500w LOGIC Dysk HDD WD 1.5 TB NIe znam sie za bardzo na komputerach więc przosze o pomoc Dodam że dysk i pamiec ram sprawdzałęm i nie ma żadnego błedu Programami Hd Tunne i Men test
Youki komentarz 20 lutego 2014 komentarz 20 lutego 2014 Masz możliwość wziąć od kogoś inny zasilacz i sprawdzić jak wygląda sytuacja ? Dokonaj analizy plików Minidump tak jak jest to tutaj opisane Nie zapomnij o symbolach. Następnie wrzuć całość tutaj 1
gamex komentarz 20 lutego 2014 komentarz 20 lutego 2014 to przełuż ram do innego slota a zasilacz też wymien na corsiar vs 450w
gniazdo komentarz 20 lutego 2014 Autor komentarz 20 lutego 2014 Microsoft (R) Windows Debugger Version 6.11.0001.402 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\022014-23010-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 Personal Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 Machine Name: Kernel base = 0xfffff800`02a10000 PsLoadedModuleList = 0xfffff800`02c536d0 Debug session time: Thu Feb 20 18:40:17.180 2014 (GMT+1) System Uptime: 0 days 1:33:05.476 ********************************************************************* * 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 101, {21, 0, fffff880009b3180, 4} ***** 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 Followup: MachineOwner --------- Musze jesze zrobic te symbole czy nie Nie mam innego zasilacza żeby sprawdzić Zmieniałem sloot pamieci lecz cały czas to samo
Youki komentarz 20 lutego 2014 komentarz 20 lutego 2014 ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Pisałem, o symbolach.. Zamykamy Debuggera. Po ponownym jego uruchomieniu klikamy File -> Symbol File Path -> wpisujemy:SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
gniazdo komentarz 20 lutego 2014 Autor komentarz 20 lutego 2014 Microsoft (R) Windows Debugger Version 6.11.0001.402 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\022014-23010-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsof...ownload/symbols Executable search path is: SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store 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 Personal Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 Machine Name: Kernel base = 0xfffff800`02a10000 PsLoadedModuleList = 0xfffff800`02c536d0 Debug session time: Thu Feb 20 18:40:17.180 2014 (GMT+1) System Uptime: 0 days 1:33:05.476 SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store 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 . SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store . SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store ............................................................. ................................................................ ........... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 101, {21, 0, fffff880009b3180, 4} SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store ***** Kernel symbols are WRONG. Please fix symbols to do analysis. SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store ************************************************************************* *** *** *** *** *** 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 : ntoskrnl.exe Followup: MachineOwner ---------
Youki komentarz 20 lutego 2014 komentarz 20 lutego 2014 Ile razy to wkleiłeś ? :D Tak czy inaczej przełóż pamięci tak jak kolega wyżej pisze oraz odpowiedz na pytanie asz możliwość wziąć od kogoś inny zasilacz i sprawdzić jak wygląda sytuacja ?
gniazdo komentarz 20 lutego 2014 Autor komentarz 20 lutego 2014 Przekładałem Pamięc ram do 2 slota lecz nie pomaga a zasilacz jaki najlepeij to jutro pożycze od kolegi może
Youki komentarz 20 lutego 2014 komentarz 20 lutego 2014 Sprawdz jeszcze pamięci RAM za pomocą programu memtest86+
gniazdo komentarz 21 lutego 2014 Autor komentarz 21 lutego 2014 Nie Wykryto żadnych błedów men testem 86+ Tak samo Hd Tune Tez żadnego erros scan i healt tez dobry był przekładałem do innego sloca pameiic ram lecz to samo jest . A komputer przyszedł z servisu i mowili ze wszsyskto czy macie jakieś pomysły czu nie bo jeśli nie to w poniedzialek jesze raz wysle komputer do servisu
Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!
Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.