Random BSODing, DPC Watcdog error

Question

************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true EnableRedirectToChakraJsProvider : false

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.219 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 42

Microsoft (R) Windows Debugger Version 10.0.27704.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\092824-6343-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 26100 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff804`b5e00000 PsLoadedModuleList = 0xfffff804`b6cf4770
Debug session time: Sat Sep 28 15:37:47.399 2024 (UTC - 4:00)
System Uptime: 0 days 1:10:02.453
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.....
Loading User Symbols

Loading unloaded module list
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`b62b8b00 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff804`48394ab0=0000000000000133
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff804b6dc33a0, 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: 1843

    Key  : Analysis.Elapsed.mSec
    Value: 4608

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27704.1001

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Bugcheck.Code.TargetModel
    Value: 0x133

    Key  : Dump.Attributes.AsUlong
    Value: 21808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0x133_ISR_ndis!ndisReceiveWorkerThread

    Key  : Failure.Hash
    Value: {d41b3816-c7a1-7920-cb98-8c8f72c700f5}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 7497cf94

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

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

    Key  : Hypervisor.Flags.ValueHex
    Value: 24a10ef

    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  : Stack.Pointer
    Value: ISR

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff804b6dc33a0

BUGCHECK_P4: 0

FILE_IN_CAB:  092824-6343-01.dmp

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

DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffd401294ce200

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
fffff804`48394aa8 fffff804`b60b29a9     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff804`b6dc33a0 : nt!KeBugCheckEx
fffff804`48394ab0 fffff804`b60b0ada     : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00041a9c : nt!KeAccumulateTicks+0x589
fffff804`48394b20 fffff804`b60b0833     : 00000000`00000010 00000000`00041a9d 00000000`00027236 fffff804`44fe3180 : nt!KiUpdateRunTime+0xd6
fffff804`48394c70 fffff804`b60aed45     : 00000000`00000000 00000000`00000000 00000000`00000001 fffff804`b6d20630 : nt!KiUpdateTime+0x473
fffff804`48394e20 fffff804`b60ae35d     : 00000e85`ad1d9376 fffff804`44fe3180 fffff804`b6c10970 00000000`00000000 : nt!KeClockInterruptNotify+0x195
fffff804`48394f50 fffff804`b647520e     : fffff804`44fe3102 fffff804`b6c10970 fffff804`4838c830 00000009`c8dea490 : nt!KiCallInterruptServiceRoutine+0x2ed
fffff804`48394fb0 fffff804`b6475a1c     : 00000000`00000000 fffff804`4838c8b0 00000000`000058a0 00001f80`00000200 : nt!KiInterruptSubDispatchNoLockNoEtw+0x4e
fffff804`4838c830 fffff804`b60543c6     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x3c
fffff804`4838c9c0 fffff804`b605390e     : fffff804`00000000 fffff804`44fe3180 fffff804`00000000 00000000`00000000 : nt!KiCommitRescheduleContextEntry+0x146
fffff804`4838ca30 fffff804`b605a250     : 00000000`00000246 ffffd401`294ce200 ffffd401`00000000 00000000`00000000 : nt!KiEnterLongDpcProcessing+0x1ba
fffff804`4838cad0 fffff804`b6004f1b     : fffff804`44fe3180 00000000`00000028 fffff804`44fe3180 00000000`0000000f : nt!KiExecuteAllDpcs+0xf90
fffff804`4838cd20 fffff804`b647ae15     : 00000000`00000000 00000000`00000000 ffff8701`3d91f2e0 00000000`00000000 : nt!KiRetireDpcList+0x36b
fffff804`4838cfb0 fffff804`b647adbf     : ffff8701`3d91f3a0 fffff804`b60ed1d5 ffffffff`ffffff80 fffff804`b647a240 : nt!KxSwapStacksAndRetireDpcList+0x5
ffff8701`3d91f2e0 fffff804`b60ed1d5     : ffffffff`ffffff80 fffff804`b647a240 00000000`01000010 00000000`00000246 : nt!KiPlatformSwapStacksAndCallReturn
ffff8701`3d91f2f0 fffff804`b647a24f     : 00000000`00000000 fffff804`47d512c0 00000000`00000000 fffff804`47d512c0 : nt!KiDispatchInterrupt+0x65
ffff8701`3d91f320 fffff804`b61cff02     : 00000000`00000000 ffffd401`23548040 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x39f
ffff8701`3d91f4b0 fffff804`494725d8     : 00000000`00000000 ffffd401`38c48ac8 00000000`00000080 00000000`00000000 : nt!KzLowerIrql+0x22
ffff8701`3d91f4e0 fffff804`b625904a     : ffffd401`294ce200 ffffd401`294ce200 00000000`00000080 fffff804`49472430 : ndis!ndisReceiveWorkerThread+0x1a8
ffff8701`3d91f570 fffff804`b64741c4     : ffffa000`92f91180 ffffd401`294ce200 fffff804`b6258ff0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
ffff8701`3d91f5c0 00000000`00000000     : ffff8701`3d920000 ffff8701`3d919000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34

SYMBOL_NAME:  ndis!ndisReceiveWorkerThread+1a8

MODULE_NAME: ndis

IMAGE_NAME:  ndis.sys

IMAGE_VERSION:  10.0.26100.1742

STACK_COMMAND:  .process /r /p 0xffffd40123548040; .thread 0xffffd401294ce200 ; kb

BUCKET_ID_FUNC_OFFSET:  1a8

FAILURE_BUCKET_ID:  0x133_ISR_ndis!ndisReceiveWorkerThread

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {d41b3816-c7a1-7920-cb98-8c8f72c700f5}

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

Any clue? BSODs randomly when watching youtube. Brand new Beelink SEi14 with Widows 11 fresh install. Also freezes instantly while trying to run Capcut video editor, problem preexists trying to run that software.

Answer 1

Hi HarrisonUS,

Welcome to Microsoft Community.

Based on the original description, we understand that your device is experiencing frequent blue screen of death issues.

This could be related to different factors including, but not limited to, driver failures, component conflicts, corrupted account profile, corrupted system components.

The error type recorded in the dump file is DPC_WATCHDOG_VIOLATION (133), and the related processes are System and ndis.sys, which is part of the system component.

When the dump file records information related to system components, it usually means that the problem may be caused by other factors.

Linking to the NDIS Library - Windows drivers | Microsoft Learn

The system version of the device you are using is 10.0.26100.1742, which is related to Windows 11 24H2.

The stability of Windows Insider channels is unpredictable.

If possible, you can try to get some relatively old drivers from the device manufacturer.

Or, if possible, you can try some generic drivers.

Example of generic driver

At the browser level, hardware acceleration options are often a common factor that causes system crashes.

If you need to troubleshoot at the system level, you can try Windows built on different dates.

Discussion messages from community members in this thread mentioned channel to obtain some of the specific versions of Windows.

(The channel is not provided directly by Microsoft and you can refer to the previous few paragraphs for the communication process between Volunteer Moderator and the original poster.)

Disclaimer: Microsoft provides no assurances and/or warranties, implied or otherwise, and is not responsible for the information you receive from the third-party linked sites or any support related to technology.

Where can I download the windows 10 and/or 11 iso for ARM - Microsoft Community

If I misunderstand your situation, feel free to correct me and share the information.

Best Regards,

Kyo.Y - MSFT | Microsoft Community Technical Support