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: ffff9280937b9180, The PRCB address of the hung processor.
Arg4: 0000000000000006, 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: 10
BUGCHECK_P2: 0
BUGCHECK_P3: ffff9280937b9180
BUGCHECK_P4: 6
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT
FAULTING_PROCESSOR: 6
CPU_COUNT: c
CPU_MHZ: e09
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 17
CPU_MODEL: 8
CPU_STEPPING: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: VideoCardMonitorII.exe
CURRENT_IRQL: d
ANALYSIS_SESSION_HOST: DESKTOP-18V31A3
ANALYSIS_SESSION_TIME: 01-14-2020 15:33:02.0394
ANALYSIS_VERSION: 10.0.18362.1 x86fre
LAST_CONTROL_TRANSFER: from fffff802807ee9b0 to fffff802807c14e0
STACK_TEXT:
fffff802`884d8b08 fffff802`807ee9b0 : 00000000`00000101 00000000`00000010 00000000`00000000 ffff9280`937b9180 : nt!KeBugCheckEx
fffff802`884d8b10 fffff802`8061f61c : fffff780`00000320 fffff802`7e329180 00000000`0018ed39 00000000`0018ed39 : nt!KeAccumulateTicks+0x1cbf50
fffff802`884d8b70 fffff802`8055e4b7 : 00000000`00000000 ffff9000`ca355fb0 ffff9000`ca356030 00000000`0000000c : nt!KeClockInterruptNotify+0x98c
fffff802`884d8f30 fffff802`80602a25 : 0000003b`6e297d7d fffff802`805cc0e0 fffff802`805cc190 00000000`00000000 : hal!HalpTimerClockInterrupt+0xf7
fffff802`884d8f60 fffff802`807c2f7a : ffff9000`ca356030 fffff802`805cc0e0 00000000`00000050 fffff802`805cc0e0 : nt!KiCallInterruptServiceRoutine+0xa5
fffff802`884d8fb0 fffff802`807c34e7 : 00000000`00000000 ffff9000`ca356030 fffff802`805cc0e0 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff9000`ca355fb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
THREAD_SHA1_HASH_MOD_FUNC: 5e958d63ed6cce864bfe4c595207e0e484aa7e7c
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: f55fc7fa5def861e987888d8bf693792e75e3eb0
THREAD_SHA1_HASH_MOD: e2266a530ca7fbace00cfa9add8dc0ac4504d759
FOLLOWUP_IP:
nt!KeAccumulateTicks+1cbf50
fffff802`807ee9b0 cc int 3
FAULT_INSTR_CODE: cb8b48cc
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KeAccumulateTicks+1cbf50
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 12dcb470
IMAGE_VERSION: 10.0.18362.535
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 1cbf50
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-01-13T18:06:27.000Z
OSBUILD: 18362
OSSERVICEPACK: 535
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: 1980-01-11 18:53:20
BUILDDATESTAMP_STR: 190318-1202
BUILDLAB_STR: 19h1_release
BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202
ANALYSIS_SESSION_ELAPSED_TIME: 60c1
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
---------
drive.google.com
Msi Gaming App programında OC modu seçili belki bunun bir etkisi olabilir. Teşekkürler.
