Share via

Watchdog BSOD error

Anonymous
2024-03-05T19:54:08+00:00

I'm having issues with a BSOD and watchdog errors causing my computer to freeze and restart. I'm trying to figure out what to do and how to fix this so this can stop! Here's the debugging dmp file: 

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff8063bf26340, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2296

    Key  : Analysis.Elapsed.mSec
    Value: 6291

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Failure.Bucket
    Value: 0x133_VRF_ISR_nt!KeAccumulateTicks

    Key  : Failure.Hash
    Value: {97c10473-e1fe-86be-098e-36b30a3d924f}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    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: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    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: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 21631230

    Key  : Hypervisor.Flags.ValueHex
    Value: 14a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8063bf26340

BUGCHECK_P4: 0

FILE_IN_CAB:  030424-18265-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  ffffd1856822d750 -- (.trap 0xffffd1856822d750)
Unable to read trap frame at ffffd185`6822d750

BLACKBOXACPI: 1 (!blackboxacpi)

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffff9880`e0ab0c88 fffff806`3b480939     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff806`3bf26340 : nt!KeBugCheckEx
ffff9880`e0ab0c90 fffff806`3b4801a1     : 0002691f`b0e248c1 ffff9880`e0ab0d58 00000000`00e42bb2 00000000`00000000 : nt!KeAccumulateTicks+0x239
ffff9880`e0ab0cf0 fffff806`3b47e231     : 00000000`00000000 00000000`00000000 ffff9880`e0a96180 00000000`00000000 : nt!KiUpdateRunTime+0xd1
ffff9880`e0ab0ea0 fffff806`3b47dc5a     : fffff806`3be69e40 00000000`00000001 00000000`00000001 00000000`00000002 : nt!KeClockInterruptNotify+0xc1
ffff9880`e0ab0f40 fffff806`3b52df3c     : 00000220`005afeec ffffc004`a9b789e0 ffffc004`a9b78a90 ffffc004`b4999e48 : nt!HalpTimerClockInterrupt+0x10a
ffff9880`e0ab0f70 fffff806`3b62353a     : ffffd185`6822d7d0 ffffc004`a9b789e0 fffff806`3c72f038 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x9c
ffff9880`e0ab0fb0 fffff806`3b623de7     : ffffd185`6822d7d0 ffffc004`b4999e48 00000000`00000000 00000000`b9b91488 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffd185`6822d750 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37

SYMBOL_NAME:  nt!KeAccumulateTicks+239

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.3235

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  239

FAILURE_BUCKET_ID:  0x133_VRF_ISR_nt!KeAccumulateTicks

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {97c10473-e1fe-86be-098e-36b30a3d924f}

Followup:     MachineOwner
---------
Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Jonathan Deives 74,060 Reputation points Independent Advisor
    2024-03-06T00:23:59+00:00

    The minidump files do not indicate any driver or hardware causes.

    Try to force Windows to show failed drivers and produce minidump files, turn on Driver Verifier.

    Make the BSOD happen 3 times and after that see if the files were created.

    Before you run Driver Verifier, please create a new System Restore Point.

    https://answers.microsoft.com/en-us/windows/for...

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-03-05T21:17:37+00:00

    Was this answer helpful?

    0 comments
  3. Jonathan Deives 74,060 Reputation points Independent Advisor
    2024-03-05T20:25:16+00:00

    My name is Jonathan Deives. I'm an Independent Advisor and I will be happy to help you today..

    See if your computer is creating minidump files.

    These files are in "C:\Windows\Minidump".

    Copy any minidump files you have to your desktop and store them in a ZIP file. Then upload the ZIP file to the cloud (OneDrive, Google Drive, Dropbox), choose to share it, and get the link.

    Post the link to the ZIP file here.

    Was this answer helpful?

    0 comments