Všechny komentáře k produktu:AMD Ryzen 5 3600

Nepravidelné BSOD s tímto procesorem

Přidávám se, mám Ryzen 5 3600 a mám podobné problémy - jak už někteří psali.Sestava je:
Ryzen 5 3600 + Noctua NH-U12A
GA-AB350M-Gaming 3 (desku jsem zkoušel i MSI MPG X570 GAMING EDGE WIFI - AMD X570)
MSI Radeon RX 5700 XT GAMING X, 8GB GDDR6
Samsung SSD 970 EVO, M.2 - 500GB
Crucial Ballistix Sport LT Grey DDR4 16GB (2x8) 3200MHz CL16 1.35V Single Ranked
Fortron AURUM 600WPočítač jede dejme tomu skoro týden v kuse bez problému, jak v zátěži, tak při běžné práci. Z toho začnou problémy, Windows nepravidělně padá do modré smrti, popř. freez - jak při nějakém brouzdání a jednoduché práci na internetu popř. v Office, tak třeba ve hře Diablo 3 - viz výpis z dumpu níže (CLOCK WATCHDOG TIMEOUT 101).ZKOUŠEL JSEM:
nový bios, ramky bez OC, test ramek, nový systém fresh install W10, nový disk, nová deska, nové ovladače, nové aktualizace W10 nic nepomohlo. ZATÍM ÚSPĚCH:
vyměnil jsem procesor a zatím už asi 9 dnů vše stabilní. Může být vadný procesor? Všechny CPU testy ale prošly bez problémů - uzná to czc jako reklamaci?CHYBU Arg1: 0000000000000010, Clock interrupt time out interval in nominal clock ticks. JSEM ZKOUŠEL GOOGLOVAT, ALE NIC SMYSLUPLNÉHO JSEM NENAŠEL...VIDÍM TO NA REKLAMACI TOHOTO CPU. POPŘ. POKUD BY NĚKDO MĚL JEŠTĚ NĚJAKOU RADU?
CRASH DUMP VÝPIS:CLOCK WATCHDOG TIMEOUT 101Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff802`3cc00000 PsLoadedModuleList = 0xfffff802`3d048150
Debug session time: Tue Mar 24 13:15:16.821 2020 (UTC + 1:00)
System Uptime: 0 days 1:56:41.500
Loading Kernel Symbols
...............................................................
................................................................
......................................................
Loading User SymbolsLoading unloaded module list
.............
For analysis of this file, run !analyze -v
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: 0000000000000010, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffc081fd579180, The PRCB address of the hung processor.
Arg4: 0000000000000003, The index of the hung processor.Debugging Details:
------------------KEY_VALUES_STRING: 1PROCESSES_ANALYSIS: 1SERVICE_ANALYSIS: 1STACKHASH_ANALYSIS: 1TIMELINE_ANALYSIS: 1DUMP_CLASS: 1DUMP_QUALIFIER: 401BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.SYSTEM_PRODUCT_NAME: AB350M-Gaming 3SYSTEM_SKU: Default stringSYSTEM_VERSION: Default stringBIOS_VENDOR: American Megatrends Inc.BIOS_VERSION: F50aBIOS_DATE: 11/27/2019BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.BASEBOARD_PRODUCT: AB350M-Gaming 3-CFBASEBOARD_VERSION: Default stringDUMP_TYPE: 1BUGCHECK_P1: 10BUGCHECK_P2: 0BUGCHECK_P3: ffffc081fd579180BUGCHECK_P4: 3FAULTING_PROCESSOR: 3BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_IDLE_THREADCPU_COUNT: cCPU_MHZ: e09CPU_VENDOR: AuthenticAMDCPU_FAMILY: 17CPU_MODEL: 71CPU_STEPPING: 0BLACKBOXBSD: 1 (!blackboxbsd)BLACKBOXNTFS: 1 (!blackboxntfs)BLACKBOXPNP: 1 (!blackboxpnp)BLACKBOXWINLOGON: 1DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULTPROCESS_NAME: SystemCURRENT_IRQL: dANALYSIS_SESSION_HOST: MK3DESKTOPANALYSIS_SESSION_TIME: 03-25-2020 15:09:07.0354ANALYSIS_VERSION: 10.0.18362.1 amd64freEXCEPTION_RECORD: 810000009f7f5900 -- (.exr 0x810000009f7f5900)
Cannot read Exception record @ 810000009f7f5900LAST_CONTROL_TRANSFER: from fffff8023cdee9b0 to fffff8023cdc14e0STACK_TEXT:
fffff802`41875b08 fffff802`3cdee9b0 : 00000000`00000101 00000000`00000010 00000000`00000000 ffffc081`fd579180 : nt!KeBugCheckEx
fffff802`41875b10 fffff802`3cc1f61c : fffff780`00000320 fffff802`3a0af180 00000000`0006d660 00000000`0006d660 : nt!KeAccumulateTicks+0x1cbf50
fffff802`41875b70 fffff802`3d6b74b7 : 00000000`00000001 fffff386`5a383510 fffff386`5a383590 00000000`0000000c : nt!KeClockInterruptNotify+0x98c
fffff802`41875f30 fffff802`3cc02a25 : 00000010`4d5b9538 fffff802`3d7250e0 fffff802`3d725190 00000000`00000000 : hal!HalpTimerClockInterrupt+0xf7
fffff802`41875f60 fffff802`3cdc2f7a : fffff386`5a383590 fffff802`3d7250e0 00000000`00000000 fffff802`3d7250e0 : nt!KiCallInterruptServiceRoutine+0xa5
fffff802`41875fb0 fffff802`3cdc34e7 : 00000000`1024d424 fffff386`5a383590 fffff802`3d7250e0 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff386`5a383510 fffff802`3ccb36e0 : 81000000`9f7f5900 fffff802`3a0af180 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff386`5a3836a0 fffff802`3ccc1f2f : ffff9800`083f3c70 81000000`9f7f5921 80000000`00000000 00000000`00000000 : nt!MiFlushTbList+0x3a0
fffff386`5a3837f0 fffff802`3cc073ab : 00000000`00009000 00000000`00009000 00000000`00009000 fffff386`5a383a40 : nt!MmSetAddressRangeModifiedEx+0x29f
fffff386`5a383940 fffff802`3cc8b7a9 : ffffad05`e40e57c8 00000000`00000000 ffffad05`00000001 00000000`00000000 : nt!CcFlushCachePriv+0x3ab
fffff386`5a383a90 fffff802`3ccbd095 : ffffad05`cf86e900 00000010`00000000 fffff802`3cc60c00 fffff386`5d509a90 : nt!CcWriteBehindInternal+0x209
fffff386`5a383b70 fffff802`3cd2a7a5 : ffffad05`d9ee1040 00000000`00000080 ffffad05`cf87a300 00000067`b4bbbdff : nt!ExpWorkerThread+0x105
fffff386`5a383c10 fffff802`3cdc8b2a : ffffc081`fda00180 ffffad05`d9ee1040 fffff802`3cd2a750 00000000`0000029e : nt!PspSystemThreadStartup+0x55
fffff386`5a383c60 00000000`00000000 : fffff386`5a384000 fffff386`5a37e000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2aTHREAD_SHA1_HASH_MOD_FUNC: c96e7c47af6d4a003410787da4013d47e3be2561THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 8ff6c0d339cf52b156eb41c5ad75ad310fb8da17THREAD_SHA1_HASH_MOD: a46c1b556d92394c8d3f63eb407b2ed053afd34aFOLLOWUP_IP:
nt!KeAccumulateTicks+1cbf50
fffff802`3cdee9b0 cc int 3FAULT_INSTR_CODE: cb8b48ccSYMBOL_STACK_INDEX: 1SYMBOL_NAME: nt!KeAccumulateTicks+1cbf50FOLLOWUP_NAME: MachineOwnerMODULE_NAME: ntIMAGE_NAME: ntkrnlmp.exeDEBUG_FLR_IMAGE_TIMESTAMP: 4f6eba0STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 1cbf50FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_IDLE_THREAD_INVALID_CONTEXT_nt!KeAccumulateTicksBUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_IDLE_THREAD_INVALID_CONTEXT_nt!KeAccumulateTicksPRIMARY_PROBLEM_CLASS: CLOCK_WATCHDOG_TIMEOUT_IDLE_THREAD_INVALID_CONTEXT_nt!KeAccumulateTicksTARGET_TIME: 2020-03-24T12:15:16.000ZOSBUILD: 18362OSSERVICEPACK: 0SERVICEPACK_NUMBER: 0OS_REVISION: 0SUITE_MASK: 272PRODUCT_TYPE: 1OSPLATFORM_TYPE: x64OSNAME: Windows 10OSEDITION: Windows 10 WinNt TerminalServer SingleUserTSOS_LOCALE: USER_LCID: 0OSBUILD_TIMESTAMP: 1972-08-22 02:24:00BUILDDATESTAMP_STR: 190318-1202BUILDLAB_STR: 19h1_releaseBUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202ANALYSIS_SESSION_ELAPSED_TIME: 1462ANALYSIS_SOURCE: KMFAILURE_ID_HASH_STRING: km:clock_watchdog_timeout_idle_thread_invalid_context_nt!keaccumulateticksFAILURE_ID_HASH: {b37ea922-6ea8-0080-e849-451291ca96f3}Followup: MachineOwner
---------