CLOCK_WATCHDOG_TIMEOUT mavi ekran hatası

GameForce

Megapat
Katılım
24 Temmuz 2013
Mesajlar
125
Yer
İstanbul
Daha fazla  
Sistem Özellikleri
R5 5600X _ B450M-S2H _ 2x8 Patriot 3200Mhz _ IdCooling FrostFlowX 240 _ Asus Rog Strix Gtx1060 6GB
Cinsiyet
Erkek
Meslek
Bankacı
Arkadaşlar merhaba. Son iki üç gündür başlıkta belirttiğim sorun oluşuyor. 4 senedir mavi ekran vb. hiçbir sorun görmemiştim. Minidump dosyalarının linkini atıyorum.

minidump gdrive
 
Overclock, underclock, undervolt, BIOS altından Game Boost gibi özellikleri açıyorsan kapat.

Kod:
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: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffa28072745180, The PRCB address of the hung processor.
Arg4: 0000000000000003, The index of the hung processor.

Debugging Details:
------------------


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

DUMP_TYPE:  2

BUGCHECK_P1: 30

BUGCHECK_P2: 0

BUGCHECK_P3: ffffa28072745180

BUGCHECK_P4: 3

BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT

FAULTING_PROCESSOR: 3

CPU_COUNT: 4

CPU_MHZ: db0

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  taskhostw.exe

CURRENT_IRQL:  d

ANALYSIS_SESSION_HOST:  DESKTOP-ME9UFOB

ANALYSIS_SESSION_TIME:  04-09-2020 23:23:57.0485

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

LAST_CONTROL_TRANSFER:  from fffff8061ea3d7a0 to fffff8061e9c2380

STACK_TEXT:
fffff806`228bab08 fffff806`1ea3d7a0 : 00000000`00000101 00000000`00000030 00000000`00000000 ffffa280`72745180 : nt!KeBugCheckEx
fffff806`228bab10 fffff806`1e8b8e3c : fffff780`00000320 fffff806`1aa6f180 00000000`000004bf 00000000`000004bf : nt!KeAccumulateTicks+0x181520
fffff806`228bab70 fffff806`1f2b84b7 : 00000000`00000001 fffff388`e8206b40 fffff388`e8206bc0 00000000`0000000c : nt!KeClockInterruptNotify+0x98c
fffff806`228baf30 fffff806`1e82cc75 : 00000000`0b67ce89 fffff806`1f3260e0 fffff806`1f326190 00000000`00000000 : hal!HalpTimerClockInterrupt+0xf7
fffff806`228baf60 fffff806`1e9c3e1a : fffff388`e8206bc0 fffff806`1f3260e0 00000000`00000000 fffff806`1f3260e0 : nt!KiCallInterruptServiceRoutine+0xa5
fffff806`228bafb0 fffff806`1e9c4387 : 00000000`0e00ccab fffff388`e8206bc0 fffff806`1f3260e0 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff388`e8206b40 fffff806`1e8eaa10 : 00000000`00000000 fffff806`1aa6f180 00000000`00000000 ffff9ffc`031a2280 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff388`e8206cd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiFlushTbList+0x3a0


THREAD_SHA1_HASH_MOD_FUNC:  dc8736af616fc8dbbe5744546b76f6197d522250

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  2b8b17ad22dee7b86b6480445ff6939705889d89

THREAD_SHA1_HASH_MOD:  77b99fd8d0bba6459fea0474c255a54ffe46d91a

FOLLOWUP_IP:
nt!KeAccumulateTicks+181520
fffff806`1ea3d7a0 cc              int     3

FAULT_INSTR_CODE:  cb8b48cc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KeAccumulateTicks+181520

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  10.0.18362.720

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  181520

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

PRIMARY_PROBLEM_CLASS:  CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

TARGET_TIME:  2020-04-08T22:45:00.000Z

OSBUILD:  18362

OSSERVICEPACK:  720

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  5c52

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:clock_watchdog_timeout_invalid_context_nt!keaccumulateticks

FAILURE_ID_HASH:  {95498f51-33a9-903b-59e5-d236937d8ecf}

Followup:     MachineOwner
---------
MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
    x86 Processors
        If the processor has ONLY MCE feature available (For example Intel
        Pentium), the parameters are:
        1 - Low  32 bits of P5_MC_TYPE MSR
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of P5_MC_ADDR MSR
        4 - Low  32 bits of P5_MC_ADDR MSR
        If the processor also has MCA feature available (For example Intel
        Pentium Pro), the parameters are:
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
    IA64 Processors
        1 - Bugcheck Type
            1 - MCA_ASSERT
            2 - MCA_GET_STATEINFO
                SAL returned an error for SAL_GET_STATEINFO while processing MCA.
            3 - MCA_CLEAR_STATEINFO
                SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
            4 - MCA_FATAL
                FW reported a fatal MCA.
            5 - MCA_NONFATAL
                SAL reported a recoverable MCA and we don't support currently
                support recovery or SAL generated an MCA and then couldn't
                produce an error record.
            0xB - INIT_ASSERT
            0xC - INIT_GET_STATEINFO
                  SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
            0xD - INIT_CLEAR_STATEINFO
                  SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
            0xE - INIT_FATAL
                  Not used.
        2 - Address of log
        3 - Size of log
        4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
    AMD64 Processors
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 0000000000000000
Arg2: fffff800824c7b10
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

DUMP_TYPE:  2

BUGCHECK_P1: 0

BUGCHECK_P2: fffff800824c7b10

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BUGCHECK_STR:  0x9C_GenuineIntel

CPU_COUNT: 4

CPU_MHZ: db0

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  f

ANALYSIS_SESSION_HOST:  DESKTOP-ME9UFOB

ANALYSIS_SESSION_TIME:  04-09-2020 23:23:52.0611

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

BAD_STACK_POINTER:  fffff800824c7ad8

LAST_CONTROL_TRANSFER:  from fffff8007d1a6a01 to fffff8007d3c2380

STACK_TEXT:
fffff800`824c7ad8 fffff800`7d1a6a01 : 00000000`0000009c 00000000`00000000 fffff800`824c7b10 00000000`00000000 : nt!KeBugCheckEx
fffff800`824c7ae0 fffff800`7d1a6f8d : 00000000`00000004 fffff800`824c7e50 00000000`00000000 00000000`00000000 : hal!HalpMcaReportError+0x11d
fffff800`824c7c40 fffff800`7d1a5fd8 : 00000000`00000000 fffff800`824c7ed0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x131
fffff800`824c7c70 fffff800`7d1a71b7 : ffffdb8e`29ad66c0 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHandleMachineCheck+0x5c
fffff800`824c7ca0 fffff800`7d4a4e40 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x37
fffff800`824c7cd0 fffff800`7d3d13ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x10
fffff800`824c7d00 fffff800`7d3d1071 : fffff38f`00000000 fffff800`7d3d0fae 00000000`2aef7fb8 00000000`00000000 : nt!KxMcheckAbort+0x7a
fffff800`824c7e40 fffff800`7d2eaa10 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x271
fffff38f`279517f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiFlushTbList+0x3a0


THREAD_SHA1_HASH_MOD_FUNC:  788f9a4c82de3ca85eada12c2b5e756fc63495af

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  9f57f439dcb4e99ae9894a8fd5f4934b1e6e6a8b

THREAD_SHA1_HASH_MOD:  506c850979dac13492582d626871aa072d9f4433

FOLLOWUP_IP:
nt!KiHandleMcheck+10
fffff800`7d4a4e40 0fb705f3f52c00  movzx   eax,word ptr [nt!KiSpeculationFeatures+0x2 (fffff800`7d77443a)]

FAULT_INSTR_CODE:  f305b70f

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  nt!KiHandleMcheck+10

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  10.0.18362.720

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  10

FAILURE_BUCKET_ID:  0x9C_GenuineIntel_STACKPTR_ERROR_nt!KiHandleMcheck

BUCKET_ID:  0x9C_GenuineIntel_STACKPTR_ERROR_nt!KiHandleMcheck

PRIMARY_PROBLEM_CLASS:  0x9C_GenuineIntel_STACKPTR_ERROR_nt!KiHandleMcheck

TARGET_TIME:  2020-04-08T23:01:38.000Z

OSBUILD:  18362

OSSERVICEPACK:  720

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  609

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x9c_genuineintel_stackptr_error_nt!kihandlemcheck

FAILURE_ID_HASH:  {f10d6786-a78f-4993-4f62-7de145ea1ce2}

Followup:     MachineOwner
---------

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: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffb7001c545180, The PRCB address of the hung processor.
Arg4: 0000000000000003, The index of the hung processor.

Debugging Details:
------------------


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

DUMP_TYPE:  2

BUGCHECK_P1: 30

BUGCHECK_P2: 0

BUGCHECK_P3: ffffb7001c545180

BUGCHECK_P4: 3

BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT

FAULTING_PROCESSOR: 3

CPU_COUNT: 4

CPU_MHZ: db0

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  KillerService.exe

CURRENT_IRQL:  d

ANALYSIS_SESSION_HOST:  DESKTOP-ME9UFOB

ANALYSIS_SESSION_TIME:  04-09-2020 23:23:40.0595

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

LAST_CONTROL_TRANSFER:  from fffff80302a3d7a0 to fffff803029c2380

STACK_TEXT:
fffff803`086bab08 fffff803`02a3d7a0 : 00000000`00000101 00000000`00000030 00000000`00000000 ffffb700`1c545180 : nt!KeBugCheckEx
fffff803`086bab10 fffff803`028b8e3c : fffff780`00000320 fffff803`009e4180 00000000`00001540 00000000`00001540 : nt!KeAccumulateTicks+0x181520
fffff803`086bab70 fffff803`0275e4b7 : 00000000`00000000 fffff40d`b8b66eb0 fffff40d`b8b66f30 00000000`0000000c : nt!KeClockInterruptNotify+0x98c
fffff803`086baf30 fffff803`0282cc75 : 00000000`32c28824 fffff803`027cc0e0 fffff803`027cc190 00000011`573fe340 : hal!HalpTimerClockInterrupt+0xf7
fffff803`086baf60 fffff803`029c3e1a : fffff40d`b8b66f30 fffff803`027cc0e0 00000000`00000050 fffff803`027cc0e0 : nt!KiCallInterruptServiceRoutine+0xa5
fffff803`086bafb0 fffff803`029c4387 : 00000000`00000000 fffff40d`b8b66f30 fffff803`027cc0e0 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff40d`b8b66eb0 fffff803`028150aa : 00000000`00000000 fffff40d`b8b67a01 00000000`00000001 fffff40d`b8b67148 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff40d`b8b67040 fffff803`02eb8e06 : 00000000`00000000 fffff40d`b8b67a80 00000000`00000000 00000000`00000000 : nt!KeFlushProcessWriteBuffers+0xd2
fffff40d`b8b67140 fffff803`02eab458 : 00000000`00000000 00000000`00010000 00000000`00000000 00000000`00000000 : nt!ExpGetProcessInformation+0x166
fffff40d`b8b677b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExpQuerySystemInformation+0x818


THREAD_SHA1_HASH_MOD_FUNC:  9db8d451ab24286281e815db14378c3a79ee75ae

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  59d43866c93ed9fb513a27753fd3548fafe9fb1d

THREAD_SHA1_HASH_MOD:  692dc177616b23b31c5615392ac069be10b8455d

FOLLOWUP_IP:
nt!KeAccumulateTicks+181520
fffff803`02a3d7a0 cc              int     3

FAULT_INSTR_CODE:  cb8b48cc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KeAccumulateTicks+181520

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  10.0.18362.720

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  181520

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

PRIMARY_PROBLEM_CLASS:  CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

TARGET_TIME:  2020-04-08T23:03:53.000Z

OSBUILD:  18362

OSSERVICEPACK:  720

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  ae51

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:clock_watchdog_timeout_invalid_context_nt!keaccumulateticks

FAILURE_ID_HASH:  {95498f51-33a9-903b-59e5-d236937d8ecf}

Followup:     MachineOwner
---------
 
Bu hatayı ben işlemciye verdiğim voltaj yetersiz gelmeye başladığında alıyordum.(Aynı işlemciyi kullanıyorum Z170 tomahawk anakart ile) İşlemciniz dört yıl içerisinde kullandığınız hız aşırtmaya bağlı olarak yıpranmış olabilir.
 
Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…