Çözüldü Render sırasında CLOCK_WATCHDOG_TIMEOUT mavi ekran

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.

umutcantkn132

Hectopat
Katılım
7 Şubat 2016
Mesajlar
10
Merhabalar video editlemeye sardım bu aralar render yaparken bilgisayarım mavi ekran veriyor. Biraz araştırıp DMP dosylarına okumaya baktım ama bir şey anlamadım. Yardım ederseniz çok sevinirim


 
Son düzenleyen: Moderatör:
Çözüm
İşlemcide overclock gözüküyor.
BIOS'a gir Exit kısmından Load Defaults yap farklı bir ayara dokunmadan kaydet çık.
"CPUID HWMonitor" sıcaklıkları bu program ile kontrol et.

Ayrıca MSI, AMD OverDrive yazılımlarını kaldır.
Bak şimdi bu hatayı sana şöyle basit bir dille anlatıyım, şimdi senin bir araban var ve devir saatinde dakikada 5000 devirin üstünde kırmızı alan var, oraya birkaç saniyeliğine girebilirsin fakat 1 saat boyunca orada gidemezsin çünkü pistonlar sıcaktan yatak sarabilir.

Hah seninde durumun böyle;
İşlemciye overclock yapmışsın normal kullanımda problem olmamış fakat render sırasında sürekli gittiği noktaya kadar kadar gitmiş sonra iflas etmiş.

Demem o ki ya hız aşırtmayı kapat ya da kararlı bir hız aşırtma yap.

Processor Version AMD Athlon(tm) X4 860K Quad Core Processor
Processor Voltage 90h - 1.6V
External Clock 100MHz
Max Speed 4600MHz
Current Speed 4600MHz

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: ffffc480f9540180, 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:  10.0.17134.472 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER:  MSI

SYSTEM_PRODUCT_NAME:  MS-7721

SYSTEM_SKU:  To be filled by O.E.M.

SYSTEM_VERSION:  9.0

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  V8.4

BIOS_DATE:  08/10/2016

BASEBOARD_MANUFACTURER:  MSI

BASEBOARD_PRODUCT:  A68HM-E33 V2 (MS-7721)

BASEBOARD_VERSION:  9.0

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

DUMP_TYPE:  2

BUGCHECK_P1: 30

BUGCHECK_P2: 0

BUGCHECK_P3: ffffc480f9540180

BUGCHECK_P4: 3

BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT

FAULTING_PROCESSOR: 3

CPU_COUNT: 4

CPU_MHZ: 11ef

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 30

CPU_STEPPING: 1

BLACKBOXBSD: 1 (!blackboxbsd)


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  GameOverlayUI.

CURRENT_IRQL:  d

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  01-25-2020 02:20:44.0382

ANALYSIS_VERSION: 10.0.18362.1 x86fre

EXCEPTION_RECORD:  ffff978a2f0e5c40 -- (.exr 0xffff978a2f0e5c40)
ExceptionAddress: fffff801a8c67f40 (nt!MiSystemPartition)
   ExceptionCode: 00000000
  ExceptionFlags: 00000000
NumberParameters: 25310976
   Parameter[0]: fffff90001823400
   Parameter[1]: ffffc480f9605000
   Parameter[2]: ffff978a2f0e5d60
   Parameter[3]: 0000000000080bcf
   Parameter[4]: 0000000000000001
   Parameter[5]: fffff80000000000
   Parameter[6]: 0000000000000001
   Parameter[7]: fffff900018236d0
   Parameter[8]: 0000000000000000
   Parameter[9]: 0000000000000050
   Parameter[10]: 0000000000000000
   Parameter[11]: fffff80100000050
   Parameter[12]: 0000000000080bc0
   Parameter[13]: 0000000000000000
   Parameter[14]: 0000000100000000

LAST_CONTROL_TRANSFER:  from fffff801a8a6e07e to fffff801a8a430a0

STACK_TEXT:
fffff801`aaeb4b78 fffff801`a8a6e07e : 00000000`00000101 00000000`00000030 00000000`00000000 ffffc480`f9540180 : nt!KeBugCheckEx
fffff801`aaeb4b80 fffff801`a88da1ed : 00000000`00000000 fffff801`a7764180 00000000`00000246 00000000`0006215d : nt!KeAccumulateTicks+0x19037e
fffff801`aaeb4be0 fffff801`a88db2d3 : fffff780`00000340 fffff801`a7764180 00000000`0006215d 00000000`00000000 : nt!KiUpdateRunTime+0x5d
fffff801`aaeb4c30 fffff801`a880e883 : 00001a42`d999d8b4 00000000`0000ffff 00000000`00000000 ffff978a`2f0e59b0 : nt!KeClockInterruptNotify+0x8f3
fffff801`aaeb4f40 fffff801`a89a0a65 : fffff801`a886fcb0 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpTimerClockInterrupt+0x63
fffff801`aaeb4f70 fffff801`a8a4495a : ffff978a`2f0e5a30 fffff801`a886fcb0 00000000`00000000 00000000`00000005 : nt!KiCallInterruptServiceRoutine+0xa5
fffff801`aaeb4fb0 fffff801`a8a44e47 : 00000000`00000001 fffff801`a886fcb0 ffff978a`2f0e5a18 ffff978a`2f0e59e3 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffff978a`2f0e59b0 fffff801`a89a166b : ffff978a`2f0e5c40 00000000`00000000 00000000`00000001 fffff801`a8d75105 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff978a`2f0e5b40 fffff801`a8d929b5 : 00000000`00000000 00000000`0686e510 fffff801`a8c67f40 fffff900`01823700 : nt!KeFlushProcessWriteBuffers+0xa3
ffff978a`2f0e5c40 fffff801`a8d5a37f : 00000000`64253f00 00000000`00010400 fffff801`a8d01240 00000000`00000000 : nt!ExpGetProcessInformation+0x115
ffff978a`2f0e6260 fffff801`a8d59aab : 00000000`00000000 ffff878b`20b632c0 00000000`00000102 ffffffff`ff676980 : nt!ExpQuerySystemInformation+0x7bf
ffff978a`2f0e6ac0 fffff801`a8a53743 : ffffad81`87323080 00000000`00000000 ffff978a`2f0e6ad8 ffffad81`874b7a20 : nt!NtQuerySystemInformation+0x2b
ffff978a`2f0e6b00 00007ff9`d302b064 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0686e4e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`d302b064


THREAD_SHA1_HASH_MOD_FUNC:  0a1f1e79dca7352a1c96c0f8d788eeeb9b6a52ef

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  5480946e0af3a2d236aa6c632a39b508deb839ae

THREAD_SHA1_HASH_MOD:  1166d71a3fb5575574472e2aabc58e021cca44df

FOLLOWUP_IP:
nt!KeAccumulateTicks+19037e
fffff801`a8a6e07e cc              int     3

FAULT_INSTR_CODE:  cb8b48cc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KeAccumulateTicks+19037e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5c135351

IMAGE_VERSION:  10.0.17134.472

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  19037e

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:  2018-12-30T14:46:18.000Z

OSBUILD:  17134

OSSERVICEPACK:  472

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:  2018-12-14 09:53:05

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.17134.472

ANALYSIS_SESSION_ELAPSED_TIME:  13f2

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
---------
 
Bak şimdi bu hatayı sana şöyle basit bir dille anlatıyım, şimdi senin bir araban var ve devir saatinde dakikada 5000 devirin üstünde kırmızı alan var, oraya birkaç saniyeliğine girebilirsin fakat 1 saat boyunca orada gidemezsin çünkü pistonlar sıcaktan yatak sarabilir.

Hah seninde durumun böyle;
İşlemciye overclock yapmışsın normal kullanımda problem olmamış fakat render sırasında sürekli gittiği noktaya kadar kadar gitmiş sonra iflas etmiş.

Demem o ki ya hız aşırtmayı kapat ya da kararlı bir hız aşırtma yap.



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: ffffc480f9540180, 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:  10.0.17134.472 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER:  MSI

SYSTEM_PRODUCT_NAME:  MS-7721

SYSTEM_SKU:  To be filled by O.E.M.

SYSTEM_VERSION:  9.0

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  V8.4

BIOS_DATE:  08/10/2016

BASEBOARD_MANUFACTURER:  MSI

BASEBOARD_PRODUCT:  A68HM-E33 V2 (MS-7721)

BASEBOARD_VERSION:  9.0

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

DUMP_TYPE:  2

BUGCHECK_P1: 30

BUGCHECK_P2: 0

BUGCHECK_P3: ffffc480f9540180

BUGCHECK_P4: 3

BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT

FAULTING_PROCESSOR: 3

CPU_COUNT: 4

CPU_MHZ: 11ef

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 30

CPU_STEPPING: 1

BLACKBOXBSD: 1 (!blackboxbsd)


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  GameOverlayUI.

CURRENT_IRQL:  d

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  01-25-2020 02:20:44.0382

ANALYSIS_VERSION: 10.0.18362.1 x86fre

EXCEPTION_RECORD:  ffff978a2f0e5c40 -- (.exr 0xffff978a2f0e5c40)
ExceptionAddress: fffff801a8c67f40 (nt!MiSystemPartition)
   ExceptionCode: 00000000
  ExceptionFlags: 00000000
NumberParameters: 25310976
   Parameter[0]: fffff90001823400
   Parameter[1]: ffffc480f9605000
   Parameter[2]: ffff978a2f0e5d60
   Parameter[3]: 0000000000080bcf
   Parameter[4]: 0000000000000001
   Parameter[5]: fffff80000000000
   Parameter[6]: 0000000000000001
   Parameter[7]: fffff900018236d0
   Parameter[8]: 0000000000000000
   Parameter[9]: 0000000000000050
   Parameter[10]: 0000000000000000
   Parameter[11]: fffff80100000050
   Parameter[12]: 0000000000080bc0
   Parameter[13]: 0000000000000000
   Parameter[14]: 0000000100000000

LAST_CONTROL_TRANSFER:  from fffff801a8a6e07e to fffff801a8a430a0

STACK_TEXT:
fffff801`aaeb4b78 fffff801`a8a6e07e : 00000000`00000101 00000000`00000030 00000000`00000000 ffffc480`f9540180 : nt!KeBugCheckEx
fffff801`aaeb4b80 fffff801`a88da1ed : 00000000`00000000 fffff801`a7764180 00000000`00000246 00000000`0006215d : nt!KeAccumulateTicks+0x19037e
fffff801`aaeb4be0 fffff801`a88db2d3 : fffff780`00000340 fffff801`a7764180 00000000`0006215d 00000000`00000000 : nt!KiUpdateRunTime+0x5d
fffff801`aaeb4c30 fffff801`a880e883 : 00001a42`d999d8b4 00000000`0000ffff 00000000`00000000 ffff978a`2f0e59b0 : nt!KeClockInterruptNotify+0x8f3
fffff801`aaeb4f40 fffff801`a89a0a65 : fffff801`a886fcb0 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpTimerClockInterrupt+0x63
fffff801`aaeb4f70 fffff801`a8a4495a : ffff978a`2f0e5a30 fffff801`a886fcb0 00000000`00000000 00000000`00000005 : nt!KiCallInterruptServiceRoutine+0xa5
fffff801`aaeb4fb0 fffff801`a8a44e47 : 00000000`00000001 fffff801`a886fcb0 ffff978a`2f0e5a18 ffff978a`2f0e59e3 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffff978a`2f0e59b0 fffff801`a89a166b : ffff978a`2f0e5c40 00000000`00000000 00000000`00000001 fffff801`a8d75105 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff978a`2f0e5b40 fffff801`a8d929b5 : 00000000`00000000 00000000`0686e510 fffff801`a8c67f40 fffff900`01823700 : nt!KeFlushProcessWriteBuffers+0xa3
ffff978a`2f0e5c40 fffff801`a8d5a37f : 00000000`64253f00 00000000`00010400 fffff801`a8d01240 00000000`00000000 : nt!ExpGetProcessInformation+0x115
ffff978a`2f0e6260 fffff801`a8d59aab : 00000000`00000000 ffff878b`20b632c0 00000000`00000102 ffffffff`ff676980 : nt!ExpQuerySystemInformation+0x7bf
ffff978a`2f0e6ac0 fffff801`a8a53743 : ffffad81`87323080 00000000`00000000 ffff978a`2f0e6ad8 ffffad81`874b7a20 : nt!NtQuerySystemInformation+0x2b
ffff978a`2f0e6b00 00007ff9`d302b064 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0686e4e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`d302b064


THREAD_SHA1_HASH_MOD_FUNC:  0a1f1e79dca7352a1c96c0f8d788eeeb9b6a52ef

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  5480946e0af3a2d236aa6c632a39b508deb839ae

THREAD_SHA1_HASH_MOD:  1166d71a3fb5575574472e2aabc58e021cca44df

FOLLOWUP_IP:
nt!KeAccumulateTicks+19037e
fffff801`a8a6e07e cc              int     3

FAULT_INSTR_CODE:  cb8b48cc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KeAccumulateTicks+19037e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5c135351

IMAGE_VERSION:  10.0.17134.472

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  19037e

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:  2018-12-30T14:46:18.000Z

OSBUILD:  17134

OSSERVICEPACK:  472

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:  2018-12-14 09:53:05

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.17134.472

ANALYSIS_SESSION_ELAPSED_TIME:  13f2

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
---------
CPU'ya overclock yapmadım acaba termal macununu bitmiş olabilir mi?
İşlemciye nasıl overclock yapılacağını bilmiyorum. BIOS üzerinden hallediliyor ise oradan geri düşerebilirim sanırım.
 
Son düzenleyen: Moderatör:
Uyarı! Bu konu 5 yıl önce açıldı.
Muhtemelen daha fazla tartışma gerekli değildir ki bu durumda yeni bir konu başlatmayı öneririz. Eğer yine de cevabınızın gerekli olduğunu düşünüyorsanız buna rağmen cevap verebilirsiniz.

Geri
Yukarı