I HAVE BSOD CLOCK WATCHDOG TIMEOUT

KAJO 0 Reputation points
2025-03-20T20:01:35.1466667+00:00

Hello i build pc with this specs Mainboard: a520 m-a pro with ryzen 5 4500 2x16 gb of viper ram i still have bsod when i use bios for compatible for ryzen 5 4500 i reinstalled windows i have updated everything this is my dmp BTW i cant turn on core isolation bc than have hyper v bsod

*******************************************************************************
*                                                                             *
*                        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: ffffbf805a040180, The PRCB address of the hung processor.
Arg4: 0000000000000006, The index of the hung processor.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1468

    Key  : Analysis.Elapsed.mSec
    Value: 1468

    Key  : Analysis.IO.Other.Mb
    Value: 21

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 25

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27793.1000

    Key  : Analysis.Version.Description
    Value: 10.2410.02.02 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2410.2.2

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0x101

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x101

    Key  : Bugcheck.Code.TargetModel
    Value: 0x101

    Key  : Failure.Bucket
    Value: CLOCK_WATCHDOG_TIMEOUT_nt!HsaIommuSendCommand

    Key  : Failure.Hash
    Value: {54e6e4aa-6e10-ccab-c9a8-469106c87ec0}

    Key  : Hypervisor.Enlightenments.Value
    Value: 0

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x0

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 0

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 0

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 0

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 0

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 0

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 0

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 0

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 16908288

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x1020000

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 0

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 0

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 0

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 0

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 0

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 0

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 0

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 0

    Key  : Hypervisor.RootFlags.Value
    Value: 0

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 0x0

    Key  : SecureKernel.HalpHvciEnabled
    Value: 0

    Key  : Stack.Pointer
    Value: Invalid

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  101

BUGCHECK_P1: 10

BUGCHECK_P2: 0

BUGCHECK_P3: ffffbf805a040180

BUGCHECK_P4: 6

FILE_IN_CAB:  MEMORY.DMP

FAULTING_THREAD:  ffff958d3fba5080

FAULTING_PROCESSOR: 6

PROCESS_NAME:  UplayWebCore.exe

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

BAD_STACK_POINTER:  ffffd1068c076350

STACK_TEXT:  
ffffd106`8c076350 fffff805`1bee4686     : fffff7f8`0001b000 fffff7f8`0021e000 00000000`00000000 00000000`00000000 : nt!HsaIommuSendCommand+0x1da
ffffd106`8c0763d0 fffff805`1bee46ac     : fffff805`1c649d50 00000000`00000200 fffff7f8`00009038 00000000`00000000 : nt!HsaInvalidateRemappingTableEntries+0x5a
ffffd106`8c076420 fffff805`1bec6078     : fffff805`1c649d50 00000000`00000006 00000bdc`650f8ad6 fffff805`1bc6f9ab : nt!HsaInvalidateRemappingTableEntry+0xc
ffffd106`8c076450 fffff805`1bebc261     : 00000000`00000000 ffffd106`8c076520 ffff958d`388ff930 ffff958d`388ff930 : nt!HalpIommuUpdateRemappingTableEntry+0x94
ffffd106`8c0764b0 fffff805`1be86366     : ffff958d`388ff990 fffff805`1c62b150 ffff958d`388ff908 fffff7f8`0000d970 : nt!HalpInterruptSetRemappedDestination+0xd9
ffffd106`8c076530 fffff805`1bd26223     : ffff958d`388ff8e0 ffff958d`364bec90 00000000`00000000 00000000`00000000 : nt!HalpInterruptSetDestination+0x10ea06
ffffd106`8c076580 fffff805`1bc6f758     : ffff958d`388ff8e0 fffff805`1bc67aba 00000000`00000002 ffffffff`ffffffff : nt!KiIntSteerSetDestination+0x63
ffffd106`8c0765c0 fffff805`1bc6f622     : 00000000`00000000 00000000`00000002 00000000`00000006 ffffd106`8c076790 : nt!KiIntSteerDistributeInterrupts+0xd8
ffffd106`8c076600 fffff805`1bc6f377     : 00000000`00000006 0f0f0f0f`00000000 00000000`00000006 ffffd106`8c076e80 : nt!KeIntSteerPeriodic+0xd2
ffffd106`8c076710 fffff805`1bd427a0     : ffffd106`8c076e80 ffffbf80`5a040180 00000bdc`650f8ad6 ffffbf80`5a040180 : nt!PpmParkSteerInterrupts+0x447
ffffd106`8c076b40 fffff805`1bc1f4de     : ffffbf80`5a043240 ffff958d`367de000 ffffd106`8c076e70 ffffbf80`00000002 : nt!PpmCheckRun+0x40
ffffd106`8c076bb0 fffff805`1bc1e7c4     : ffffbf80`5a040180 ffec037e`00000000 00000000`00000002 00000000`00000004 : nt!KiExecuteAllDpcs+0x30e
ffffd106`8c076d20 fffff805`1be066b5     : 48084789`48527508 ffffbf80`5a040180 00000000`00000000 00000000`53e9f480 : nt!KiRetireDpcList+0x1f4
ffffd106`8c076fb0 fffff805`1be064a0     : 00000000`00000000 00000000`0115e568 ffffd106`8dd48b18 00000000`00000000 : nt!KxRetireDpcList+0x5
ffffd106`8dd48ad0 fffff805`1be0589d     : 00000000`6a77b5ec 00007ffd`715d9720 ffffd106`8dd48b18 ffffffff`ffa02cc0 : nt!KiDispatchInterruptContinue
ffffd106`8dd48b00 00000000`64d044c1     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x2fd
00000000`0115d9d4 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x64d044c1


SYMBOL_NAME:  nt!HsaIommuSendCommand+1da

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

STACK_COMMAND:  .process /r /p 0xffff958d44ab6080; .thread 0xffff958d3fba5080 ; kb

BUCKET_ID_FUNC_OFFSET:  1da

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_nt!HsaIommuSendCommand

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {54e6e4aa-6e10-ccab-c9a8-469106c87ec0}

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

Windows 10 Compatibility
Windows 10 Compatibility
Windows 10: A Microsoft operating system that runs on personal computers and tablets.Compatibility: The extent to which hardware or software adheres to an accepted standard.
515 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Hania Lian - MSFT 23,106 Reputation points Microsoft External Staff
    2025-03-21T01:58:59.3133333+00:00

    Hello,

    According to the error code CLOCK_WATCHDOG_TIMEOUT (101),

    we recommend you refer to this link for troubleshooting:

    https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x101---clock-watchdog-timeout

    Have a nice day.

    Best Regards,

    Hania Lian

    ============================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.