BSOD when I'm playing games

Question

While playing I would get a BSOD, the error being CLOCK_WATCHDOG_TIMEOUT
when I open event viewer to see what happened, I see this Error: The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000101 (0x000000000000000c, 0x0000000000000000, 0xffffd8812c152180, 0x0000000000000003). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 4c51274e-b78b-4720-8a37-be986e2e4d33.
I opened memory.dmp and I'm guessing the issue was caused by ntkrnlmp.exe
here is the full thing:

Microsoft (R) Windows Debugger Version 10.0.22473.1005 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.

************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff80674c00000 PsLoadedModuleList = 0xfffff8067582a1b0 Debug session time: Mon Dec 27 18:01:45.823 2021 (UTC - 8:00) System Uptime: 0 days 0:22:11.453 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ .............. Loading User Symbols PEB is paged out (Peb.Ldr = 000000467e3b4018). Type ".hh dbgerr001" for details Loading unloaded module list ............... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff80674ff70d0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff806`7967cc90=0000000000000101 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: 000000000000000c, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: ffffd8812c152180, The PRCB address of the hung processor. Arg4: 0000000000000003, The index of the hung processor.

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 2108

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 2204

Key  : Analysis.Init.CPU.mSec
Value: 312

Key  : Analysis.Init.Elapsed.mSec
Value: 1985

Key  : Analysis.Memory.CommitPeak.Mb
Value: 75

Key  : WER.OS.Branch
Value: vb\_release

Key  : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key  : WER.OS.Version
Value: 10.0.19041.1

FILE_IN_CAB: MEMORY.DMP

BUGCHECK_CODE: 101

BUGCHECK_P1: c

BUGCHECK_P2: 0

BUGCHECK_P3: ffffd8812c152180

BUGCHECK_P4: 3

FAULTING_PROCESSOR: 3

PROCESS_NAME: r5apex.exe

FAULTING_THREAD: ffffc48c9c543080

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

STACK_TEXT:
fffff8067967cc88 fffff8067501f36e : 0000000000000101 000000000000000c 0000000000000000 ffffd8812c152180 : nt!KeBugCheckEx fffff8067967cc90 fffff80674e1c3cd : 0000000000000000 fffff80671289180 0000000000000246 0000000000014cdd : nt!KeAccumulateTicks+0x2061be fffff8067967ccf0 fffff80674e1c971 : 0000000000014a00 000000000000c666 fffff80671289180 0000000000000001 : nt!KiUpdateRunTime+0x5d fffff8067967cd40 fffff80674e167e3 : fffff80671289180 0000000000000000 fffff80675831558 0000000000000000 : nt!KiUpdateTime+0x4a1 fffff8067967ce80 fffff80674e1f1a2 : fffff50696a368a0 fffff50696a36920 fffff50696a36900 000000000000000c : nt!KeClockInterruptNotify+0x2e3 fffff8067967cf30 fffff80674ede135 : 0000000319b246a8 fffff806758f39a0 fffff806758f3a50 0000000000000000 : nt!HalpTimerClockInterrupt+0xe2 fffff8067967cf60 fffff80674ff8b7a : fffff50696a36920 fffff806758f39a0 fffff50696a36df0 0000000000000000 : nt!KiCallInterruptServiceRoutine+0xa5 fffff8067967cfb0 fffff80674ff90e7 : 000000001e1effc1 fffff8067128c088 fffff50696a369d1 0000000000000001 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa fffff50696a368a0 fffff80674e3a300 : 0000000000000000 0000000000000000 0000000000000000 fffff80674f7261a : nt!KiInterruptDispatchNoLockNoEtw+0x37 fffff50696a36a30 fffff8067507a862 : 0000000000000002 fffff8067128bf38 0000000000000000 ffffd8812c09f088 : nt!KiIpiSendRequestEx+0xb0 fffff50696a36a70 fffff80674e1e6a4 : 0000000000000001 fffff50696a36c00 0000000000000000 0000000000000000 : nt!KxFlushNonGlobalTb+0x13a1be fffff50696a36ac0 fffff80674e3a470 : fffff50696a36be0 fffff50696a36c50 ffffc48c929a4900 ffffe98000000000 : nt!KeFlushTb+0x154 fffff50696a36b20 fffff80674e42143 : ffffc48c929a49c0 1a00000257f78867 0000000000000001 0000000000000000 : nt!MiFlushTbList+0xb0 fffff50696a36b50 fffff80674eb0ba0 : fffff50696a36e00 0000000000000000 0000000000000000 ffff894480768868 : nt!MiTerminateWsleCluster+0x363 fffff50696a36d00 fffff806751fa1ed : ffffc48c9756c280 ffffc48ca3377a98 0000000000000000 0000000000000000 : nt!MiDecommitPages+0x1200 fffff50696a378d0 fffff806751f9853 : fffff50696a37a50 0000000000000000 fffff50696a37a50 ffffc48ca3377a70 : nt!MiDecommitRegion+0x7d fffff50696a37950 fffff806751f9145 : 0000000000000000 000000460f0ce438 ffff1a13bd89ddfe fffff80674ffdecf : nt!MmFreeVirtualMemory+0x6d3 fffff50696a37aa0 fffff80675008ab8 : ffffc48c9756c280 fffff50696a37b80 000001da21859ab0 ffffc48c00000000 : nt!NtFreeVirtualMemory+0x95 fffff50696a37b00 00007ffd66fad134 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28 000000460f0cec78 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffd`66fad134

SYMBOL_NAME: nt!KeAccumulateTicks+2061be

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 2061be

FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_nt!KeAccumulateTicks

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f9e2f3e5-5717-d66f-239c-7b2e10a43f9e}

Followup: MachineOwner

I have done sfc /scannow, no issues found
I did a memtest to see if anything was wrong with my ram, no issues found
I did a driver verifier before, and my pc bluescreened twice testing the drivers i assume, and i thought the issue was solved but the issue continues. I try the driver verifier again and It goes smoothly, nothing wrong
My graphics driver is up to date, and I updated my bios so its up to date
When i would do a full system scan using my antivirus, bitdefender, it would bluescreen before the scan can be completed, doing a quick scan reveals nothing is wrong
I'm just puzzled and would appreciate some help on what to do next to fix this issue

Answer 1

Hello, I'm A&K. I'm glad to be able to help you.

Your dump file shows that the specified core of the multi-core processor failed to handle the interrupt. Usually, this happens when the processor becomes unresponsive or deadlocks.

I suggest you first check the heat dissipation of the processor and make sure that all components have been installed correctly.