Adriano567 utworzono 17 lutego 2014 utworzono 17 lutego 2014 Witam Mam problem z komputerem, bardzo często wywala mi blue screena, myślałem ze to od dysku twardego ale po zakupie nowego dalej to samo. Format również nie pomógł.Załączam zdj. blue screena oraz screeny SMART obu dysków. Zrobiłem jeszcze Memtesta, zero błędów. Podpis problemu: Nazwa zdarzenia problemu: BlueScreen Wersja systemu operacyjnego: 6.1.7600.2.0.0.256.48 Identyfikator ustawień regionalnych: 1045 Dodatkowe informacje o problemie: BCCode: 101 BCP1: 0000000000000021 BCP2: 0000000000000000 BCP3: FFFFF880009B1180 BCP4: 0000000000000004 OS Version: 6_1_7600 Service Pack: 0_0 Product: 256_1 Pliki pomagające opisać problem: C:\Windows\Minidump\021614-8564-01.dmp C:\Users\Adrian\AppData\Local\Temp\WER-10171-0.sysdata.xml 4 GB RAM GOODRAM 1333Mhz CL9 Gigabyte GeForce GTX650Ti OC 2GB ASUS M5A78L-M LX3 AMD FX-6300 3.5GHz 6MB Be Quiet 530W Windows 7 64-bit Samsung SSD 840 EVO 120GB Seagate ST3320613AS 320GB
Adrian93 komentarz 17 lutego 2014 komentarz 17 lutego 2014 (edytowane) Podaj specyfikacje kompa ok nie zauwazylem Podkrecales procesor ? lub cos innego
Adrian93 komentarz 17 lutego 2014 komentarz 17 lutego 2014 jakie napiecie ? Sprawdzales temperatury ? Jakie chlodzenie na cpu?
Adriano567 komentarz 17 lutego 2014 Autor komentarz 17 lutego 2014 jak to sprawdzić ? sorki za pytanie
Youki komentarz 17 lutego 2014 komentarz 17 lutego 2014 Przywróć ustawienia BIOS'u do ustawień fabrycznych i daj znać.
Adrian93 komentarz 17 lutego 2014 komentarz 17 lutego 2014 Wchodzisz w bios ustawienia procesora i szukasz opcji Vcore
Adriano567 komentarz 17 lutego 2014 Autor komentarz 17 lutego 2014 (edytowane) Ustawienia przywróciłem Temperatura procka 36 stopni, a napięcie VCORE 1,284V dam znać jeśli dalej będzie coś nie tak znów wywaliło tym razem podczas przeglądania stronek
Adriano567 komentarz 17 lutego 2014 Autor komentarz 17 lutego 2014 Load Setup Defaults w BIOSie :) jesli to nie tak to poproszę o instrukcje :)
Adrian93 komentarz 17 lutego 2014 komentarz 17 lutego 2014 wylacz kompa i wyciagnij bateryjke z plyty glownej na 10 minut https://www.google.pl/search?q=bateryjka+na+plycie+glownej&source=lnms&tbm=isch&sa=X&ei=U0gCU6OzDJTR4QS10oGICA&ved=0CAcQ_AUoAQ&biw=1600&bih=750#facrc=_&imgdii=_&imgrc=Bfn6WZfFonzLGM%253A%3B_WvVVAJkYbRK7M%3Bhttp%253A%252F%252Fi55.tinypic.com%252Fnvw5.jpg%3Bhttp%253A%252F%252Fwww.pmwfleet.pl%252Fviewtopic.php%253Ff%253D19%2526t%253D1404%3B800%3B667
Youki komentarz 17 lutego 2014 komentarz 17 lutego 2014 Tylko pózniej nie podkręcaj znów procesora tylko działaj na ustawieniach fabrycznych i daj znać czy problem występuje.
Adriano567 komentarz 17 lutego 2014 Autor komentarz 17 lutego 2014 tak teraz to juz dam sobie spokój ze wszystkim, nic nie kombinuje, BIOS zresetowany, poczekamy zobaczymy co dalej
Adrian93 komentarz 17 lutego 2014 komentarz 17 lutego 2014 Poprostu jesli chcesz podkrecac to troche z glową stopniowo i testy stabilnosci temperatury i db wszystko dobrze jesli chcesz to prosze http://www.youtube.com/watch?v=UbnpvOyJauw
Adriano567 komentarz 18 lutego 2014 Autor komentarz 18 lutego 2014 długo nie wytrzymał dzisiaj zaraz po uruchomieniu dosłownie 2 minuty blue screen
Youki komentarz 18 lutego 2014 komentarz 18 lutego 2014 Dokonaj analizy plików Minidump tak jak zostało to tutaj opisane http://www.forumpc.pl/tutorials/article/79-debugging-tools-for-windows-i-pliki-minidump/ Nie zapomnij o symbolach. Następnie wrzuć tutaj całość z Debuggera.
Adriano567 komentarz 18 lutego 2014 Autor komentarz 18 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\021814-8782-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 (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 Machine Name: Kernel base = 0xfffff800`02c56000 PsLoadedModuleList = 0xfffff800`02e996d0 Debug session time: Tue Feb 18 15:59:19.613 2014 (GMT+1) System Uptime: 0 days 0:00:37.955 Loading Kernel Symbols ............................................................... ................................................................ ................. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 101, {21, 0, fffff880009b2180, 4} Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CLOCK_WATCHDOG_TIMEOUT (101) An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval. This indicates that the specified processor is hung and not processing interrupts. Arguments: Arg1: 0000000000000021, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: fffff880009b2180, The PRCB address of the hung processor. Arg4: 0000000000000004, 0. Debugging Details: ------------------ BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_6_PROC CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: chrome.exe CURRENT_IRQL: d STACK_TEXT: fffff880`0a4eb438 fffff800`02d22a4a : 00000000`00000101 00000000`00000021 00000000`00000000 fffff880`009b2180 : nt!KeBugCheckEx fffff880`0a4eb440 fffff800`02cd56f7 : 00000000`00000000 fffff800`00000004 00000000`00002710 fffff880`0a4eb57a : nt! ?? ::FNODOBFM::`string'+0x4e3e fffff880`0a4eb4d0 fffff800`02c17895 : fffff800`02c3d460 fffff880`0a4eb680 fffff800`02c3d460 00000000`00000000 : nt!KeUpdateSystemTime+0x377 fffff880`0a4eb5d0 fffff800`02cc8113 : 00000000`0f632d90 fffffa80`00f770a0 00000000`00001000 fffff880`0a4eb601 : hal!HalpHpetClockInterrupt+0x8d fffff880`0a4eb600 fffff800`02d014b7 : fffffa80`06730a68 00000000`c0000034 fffff8a0`00010030 00000000`00000101 : nt!KiInterruptDispatchNoLock+0x163 fffff880`0a4eb790 fffff800`02d003cd : 00000000`00000000 00000000`00000001 fffffa01`c0000034 00000000`00000000 : nt!KxFlushEntireTb+0xc7 fffff880`0a4eb7d0 fffff800`02d249b0 : 00000000`00000001 fffff680`000493f0 00000000`00000001 00000000`00000001 : nt!KeFlushTb+0x119 fffff880`0a4eb850 fffff800`02cdb78f : fffff680`000493f0 fffff880`0a4eb900 00000000`00000000 fffffa80`05f8cec8 : nt! ?? ::FNODOBFM::`string'+0xada2 fffff880`0a4eb890 fffff800`02cd83fe : 00000000`00000001 00000000`0927e004 fffff880`0a4ebae0 fffff680`000493f0 : nt!MiResolveDemandZeroFault+0x1ff fffff880`0a4eb980 fffff800`02cc9cee : 00000000`00000001 00000000`0927e004 fffff880`0a4eba01 00000000`fffc8aee : nt!MmAccessFault+0x5de fffff880`0a4ebae0 00000000`6ea22309 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e 00000000`07faf8c4 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6ea22309 STACK_COMMAND: kb SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CLOCK_WATCHDOG_TIMEOUT (101) An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval. This indicates that the specified processor is hung and not processing interrupts. Arguments: Arg1: 0000000000000021, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: fffff880009b2180, The PRCB address of the hung processor. Arg4: 0000000000000004, 0. Debugging Details: ------------------ BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_6_PROC CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: chrome.exe CURRENT_IRQL: d STACK_TEXT: fffff880`0a4eb438 fffff800`02d22a4a : 00000000`00000101 00000000`00000021 00000000`00000000 fffff880`009b2180 : nt!KeBugCheckEx fffff880`0a4eb440 fffff800`02cd56f7 : 00000000`00000000 fffff800`00000004 00000000`00002710 fffff880`0a4eb57a : nt! ?? ::FNODOBFM::`string'+0x4e3e fffff880`0a4eb4d0 fffff800`02c17895 : fffff800`02c3d460 fffff880`0a4eb680 fffff800`02c3d460 00000000`00000000 : nt!KeUpdateSystemTime+0x377 fffff880`0a4eb5d0 fffff800`02cc8113 : 00000000`0f632d90 fffffa80`00f770a0 00000000`00001000 fffff880`0a4eb601 : hal!HalpHpetClockInterrupt+0x8d fffff880`0a4eb600 fffff800`02d014b7 : fffffa80`06730a68 00000000`c0000034 fffff8a0`00010030 00000000`00000101 : nt!KiInterruptDispatchNoLock+0x163 fffff880`0a4eb790 fffff800`02d003cd : 00000000`00000000 00000000`00000001 fffffa01`c0000034 00000000`00000000 : nt!KxFlushEntireTb+0xc7 fffff880`0a4eb7d0 fffff800`02d249b0 : 00000000`00000001 fffff680`000493f0 00000000`00000001 00000000`00000001 : nt!KeFlushTb+0x119 fffff880`0a4eb850 fffff800`02cdb78f : fffff680`000493f0 fffff880`0a4eb900 00000000`00000000 fffffa80`05f8cec8 : nt! ?? ::FNODOBFM::`string'+0xada2 fffff880`0a4eb890 fffff800`02cd83fe : 00000000`00000001 00000000`0927e004 fffff880`0a4ebae0 fffff680`000493f0 : nt!MiResolveDemandZeroFault+0x1ff fffff880`0a4eb980 fffff800`02cc9cee : 00000000`00000001 00000000`0927e004 fffff880`0a4eba01 00000000`fffc8aee : nt!MmAccessFault+0x5de fffff880`0a4ebae0 00000000`6ea22309 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e 00000000`07faf8c4 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6ea22309 STACK_COMMAND: kb SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CLOCK_WATCHDOG_TIMEOUT (101) An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval. This indicates that the specified processor is hung and not processing interrupts. Arguments: Arg1: 0000000000000021, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: fffff880009b2180, The PRCB address of the hung processor. Arg4: 0000000000000004, 0. Debugging Details: ------------------ BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_6_PROC CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: chrome.exe CURRENT_IRQL: d STACK_TEXT: fffff880`0a4eb438 fffff800`02d22a4a : 00000000`00000101 00000000`00000021 00000000`00000000 fffff880`009b2180 : nt!KeBugCheckEx fffff880`0a4eb440 fffff800`02cd56f7 : 00000000`00000000 fffff800`00000004 00000000`00002710 fffff880`0a4eb57a : nt! ?? ::FNODOBFM::`string'+0x4e3e fffff880`0a4eb4d0 fffff800`02c17895 : fffff800`02c3d460 fffff880`0a4eb680 fffff800`02c3d460 00000000`00000000 : nt!KeUpdateSystemTime+0x377 fffff880`0a4eb5d0 fffff800`02cc8113 : 00000000`0f632d90 fffffa80`00f770a0 00000000`00001000 fffff880`0a4eb601 : hal!HalpHpetClockInterrupt+0x8d fffff880`0a4eb600 fffff800`02d014b7 : fffffa80`06730a68 00000000`c0000034 fffff8a0`00010030 00000000`00000101 : nt!KiInterruptDispatchNoLock+0x163 fffff880`0a4eb790 fffff800`02d003cd : 00000000`00000000 00000000`00000001 fffffa01`c0000034 00000000`00000000 : nt!KxFlushEntireTb+0xc7 fffff880`0a4eb7d0 fffff800`02d249b0 : 00000000`00000001 fffff680`000493f0 00000000`00000001 00000000`00000001 : nt!KeFlushTb+0x119 fffff880`0a4eb850 fffff800`02cdb78f : fffff680`000493f0 fffff880`0a4eb900 00000000`00000000 fffffa80`05f8cec8 : nt! ?? ::FNODOBFM::`string'+0xada2 fffff880`0a4eb890 fffff800`02cd83fe : 00000000`00000001 00000000`0927e004 fffff880`0a4ebae0 fffff680`000493f0 : nt!MiResolveDemandZeroFault+0x1ff fffff880`0a4eb980 fffff800`02cc9cee : 00000000`00000001 00000000`0927e004 fffff880`0a4eba01 00000000`fffc8aee : nt!MmAccessFault+0x5de fffff880`0a4ebae0 00000000`6ea22309 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e 00000000`07faf8c4 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6ea22309 STACK_COMMAND: kb SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE Followup: MachineOwner --------- o to chodziło ?
Youki komentarz 18 lutego 2014 komentarz 18 lutego 2014 Dokonaj aktualizacji BIOS'u oraz sterowników do chipsetu. Service Pack'i masz zainstalowane do systemu ?
Adriano567 komentarz 18 lutego 2014 Autor komentarz 18 lutego 2014 Service Pack 1 Jak możesz to napisz mi jak dokładnie zaktualizować BIOS i chipset. Na dzisiaj już kończe jutro dalej będę męczyć
Youki komentarz 18 lutego 2014 komentarz 18 lutego 2014 http://www.asus.com/Motherboards/M5A78LM_LX3/#support Chipset, Audio,LAN pobierasz i instalujesz. BIOS pobierasz najnowszy.
Adriano567 komentarz 19 lutego 2014 Autor komentarz 19 lutego 2014 wszystko porobiłem, wytrzymał godzinke i znów blue screen
Adriano567 komentarz 19 lutego 2014 Autor komentarz 19 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\021914-10530-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 (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 Machine Name: Kernel base = 0xfffff800`02c4e000 PsLoadedModuleList = 0xfffff800`02e916d0 Debug session time: Wed Feb 19 17:31:30.015 2014 (GMT+1) System Uptime: 0 days 0:01:09.358 Loading Kernel Symbols ............................................................... ................................................................ .................. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 101, {21, 0, fffff880030a4180, 5} Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CLOCK_WATCHDOG_TIMEOUT (101) An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval. This indicates that the specified processor is hung and not processing interrupts. Arguments: Arg1: 0000000000000021, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: fffff880030a4180, The PRCB address of the hung processor. Arg4: 0000000000000005, 0. Debugging Details: ------------------ BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_6_PROC CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: svchost.exe CURRENT_IRQL: d STACK_TEXT: fffff880`053fe328 fffff800`02d1aa4a : 00000000`00000101 00000000`00000021 00000000`00000000 fffff880`030a4180 : nt!KeBugCheckEx fffff880`053fe330 fffff800`02ccd6f7 : 00000000`00000000 fffff800`00000005 00000000`00002710 fffff880`053fe450 : nt! ?? ::FNODOBFM::`string'+0x4e3e fffff880`053fe3c0 fffff800`02c0f895 : fffff800`02c35460 fffff880`053fe570 fffff800`02c35460 00000000`00000000 : nt!KeUpdateSystemTime+0x377 fffff880`053fe4c0 fffff800`02cc0113 : fffff800`02e3ee80 00000000`00000001 00000000`00000001 fffff800`02c4e000 : hal!HalpHpetClockInterrupt+0x8d fffff880`053fe4f0 fffff800`02c98939 : fffffa80`05a7d730 00000000`000efd20 fffff800`02ccdaa5 00000000`000406f8 : nt!KiInterruptDispatchNoLock+0x163 fffff880`053fe680 fffff800`02fced4f : 00000000`00000000 fffff880`053feb60 00000000`00000000 fffff800`02dce764 : nt!KeFlushProcessWriteBuffers+0x65 fffff880`053fe6f0 fffff800`02fcf3ad : 00000000`0018da70 fffff800`02fb9cce 00000000`00000000 fffff800`02cc2e8a : nt!ExpQuerySystemInformation+0x13af fffff880`053feaa0 fffff800`02cc2e53 : 00000000`00000000 fffff880`053feb60 ffffffff`fffe7960 000007fe`fb710b00 : nt!NtQuerySystemInformation+0x4d fffff880`053feae0 00000000`7729161a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0098f408 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7729161a STACK_COMMAND: kb SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE Followup: MachineOwner ---------
Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!
Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.