Windows 10: Difficulty tracking down cause of DPC Watchdog Violation BSOD

Discus and support Difficulty tracking down cause of DPC Watchdog Violation BSOD in Windows 10 BSOD Crashes and Debugging to solve the problem; I built a new PC a few weeks ago and have been having some intermittent BSOD issues, all the same DPC Watchdog Violation. It happens most frequently... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by LariputtomusMcFly, Mar 9, 2021.

  1. Difficulty tracking down cause of DPC Watchdog Violation BSOD


    I built a new PC a few weeks ago and have been having some intermittent BSOD issues, all the same DPC Watchdog Violation. It happens most frequently when running games, although I can also force it to happen with almost 100% consistency by attempting to share my screen on Discord.


    I've tried doing a fresh windows install, rolling-back and re-installing graphics drivers, and removing my USB3 expansion PCIE card, all to no avail. I keep windows up to date.



    This is what I get when I run the debugger:


    ******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DPC_WATCHDOG_VIOLATION 133The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVELor above.Arguments:Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending component can usually be identified with a stack trace.Arg2: 0000000000000501, The DPC time count in ticks.Arg3: 0000000000000500, The DPC time allotment in ticks.Arg4: fffff8053c2fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains additional information regarding this single DPC timeout



    BUGCHECK_CODE: 133BUGCHECK_P1: 0BUGCHECK_P2: 501BUGCHECK_P3: 500BUGCHECK_P4: fffff8053c2fb320DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDEDTRAP_FRAME: fffff182b144de60 -- .trap 0xfffff182b144de60NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=00000000ffffffff rbx=0000000000000000 rcx=0000800000000000rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000rip=fffff8054dff154b rsp=fffff182b144dff0 rbp=fffff182b144e0c9 r8=0000000000000410 r9=00000000003e0000 r10=0000000000000400r11=00000000c9e38ed8 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei pl zr na po ncUSBXHCI!Isoch_Stage_MapIntoRing+0x4fb:fffff805`4dff154b 83f801 cmp eax,1Resetting default scopeBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1PROCESS_NAME: SystemSTACK_TEXT: ffffe180`ccb33e18 fffff805`3ba3ac88 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckExffffe180`ccb33e20 fffff805`3b86f9a3 : 0000024e`9b639bad ffffe180`ccb19180 00000000`00000000 ffffe180`ccb19180 : nt!KeAccumulateTicks+0x1c8a88ffffe180`ccb33e80 fffff805`3b86f48a : ffff9008`1fed4d40 fffff182`b144dee0 00000000`00000000 00000000`00000216 : nt!KeClockInterruptNotify+0x453ffffe180`ccb33f30 fffff805`3b927ef5 : ffff9008`1fed4d40 00000000`00000000 00000000`00000000 ffff72a5`bfa8ed2f : nt!HalpTimerClockIpiRoutine+0x1affffe180`ccb33f60 fffff805`3b9f752a : fffff182`b144dee0 ffff9008`1fed4d40 00000000`00000007 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5ffffe180`ccb33fb0 fffff805`3b9f7a97 : ffff9008`31baa600 ffff9008`3bbb9e70 00000000`00000002 00000000`01000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfafffff182`b144de60 fffff805`4dff154b : 00000000`00000000 00000000`00000009 fffff805`3b9f1b70 00000000`00000100 : nt!KiInterruptDispatchNoLockNoEtw+0x37fffff182`b144dff0 fffff805`4dff1029 : ffff9008`2c662250 00000000`00000000 ffff9008`3f364b00 fffff805`4dff1000 : USBXHCI!Isoch_Stage_MapIntoRing+0x4fbfffff182`b144e130 fffff805`3b99c109 : 00000000`00000000 ffff9008`3f364b50 00000000`00000000 00000000`00000000 : USBXHCI!Isoch_EvtDmaCallback+0x19fffff182`b144e160 fffff805`3b99c033 : ffff9008`3f364b50 ffff9008`2d450ba0 00000000`00000060 00000000`00000000 : nt!HalpAllocateAdapterCallbackV3+0xa9fffff182`b144e1e0 fffff805`3ba68fab : ffff9008`3bbb9e10 ffff9008`3bbb9e00 00000000`00000000 ffff9008`2d450ba0 : nt!HalpBuildScatterGatherList+0x1affffff182`b144e260 fffff805`4dff3830 : ffff9008`3bbb9e10 ffff9008`2d7cd060 ffff9008`3bbb9e00 ffff9008`2d450ba0 : nt!HalGetScatterGatherList+0x164a2bfffff182`b144e2f0 fffff805`4dff2c2b : 00000000`00000003 ffff9008`3bbb9e10 ffff9008`3bbb9e00 00000000`00000000 : USBXHCI!Isoch_MapStage+0xd0fffff182`b144e360 fffff805`409c790d : ffff9008`3bbb9e10 00000000`00000000 00006ff7`c44465c8 ffff9008`3bbb9e10 : USBXHCI!Isoch_WdfEvtIoQueueReadyNotification+0x14bfffff182`b144e3d0 fffff805`409c78a1 : 00000000`00000000 ffff9008`3bbb9a30 fffff182`b144e538 00000000`00000000 : Wdf01000!FxIoQueueIoState::Invoke+0x3d [minkernel\wdf\framework\shared\inc\private\common\FxIoQueueCallbacks.hpp @ 305] fffff182`b144e400 fffff805`409b89e5 : ffff9008`3bbb9a30 fffff182`b144e4c9 ffff9008`2d72ab00 fffff805`3b8ec5ca : Wdf01000!FxIoQueue:Difficulty tracking down cause of DPC Watchdog Violation BSOD :processReadyNotify+0x6d [minkernel\wdf\framework\shared\irphandlers\io\fxioqueue.cpp @ 4852] fffff182`b144e460 fffff805`409b5d4e : ffff9008`3bbb9a30 ffff9008`3bbb9a02 00000000`00000000 00000000`00000002 : Wdf01000!FxIoQueue:Difficulty tracking down cause of DPC Watchdog Violation BSOD :DispatchEvents+0x5a5 [minkernel\wdf\framework\shared\irphandlers\io\fxioqueue.cpp @ 2871] fffff182`b144e530 fffff805`409c3436 : 00000000`00000002 ffff9008`2c662020 00000000`00000000 00000000`00000000 : Wdf01000!FxIoQueue::QueueRequest+0xae [minkernel\wdf\framework\shared\irphandlers\io\fxioqueue.cpp @ 2371] fffff182`b144e5a0 fffff805`409c2eec : ffff9008`2d8e8140 00000000`00000000 00000000`00000000 fffff805`3b915000 : Wdf01000!FxPkgIo:Difficulty tracking down cause of DPC Watchdog Violation BSOD :DispatchStep2+0x486 [minkernel\wdf\framework\shared\irphandlers\io\fxpkgio.cpp @ 482] fffff182`b144e640 fffff805`4e093916 : 00006ff7`d3a77548 ffff9008`2d7cd060 ffff9008`38df2240 ffff9008`37f929c0 : Wdf01000!imp_WdfDeviceWdmDispatchIrpToIoQueue+0x17c [minkernel\wdf\framework\shared\core\km\fxdeviceapikm.cpp @ 495] fffff182`b144e6a0 fffff805`4e093288 : 00000000`00000018 00000000`00000000 fffff805`3b9f1b70 00006ff7`d3a77548 : ucx01000!UrbHandler_USBPORTStyle_Legacy_IsochTransfer+0x266fffff182`b144e770 fffff805`4e092285 : 00000000`00000001 00000000`00000000 ffff9008`37104e98 ffff9008`37f92e38 : ucx01000!Urb_USBPORTStyle_ProcessURB+0x7b8fffff182`b144e830 fffff805`409ba976 : ffff9008`2c588ab0 00000000`00000000 00000000`00000000 00000000`00220003 : ucx01000!RootHub_Pdo_EvtInternalDeviceControlIrpPreprocessCallback+0xb5fffff182`b144e8c0 fffff805`3b852f55 : 00000000`00220003 ffff9008`2d59dd60 00000000`00000000 ffff9008`37f929c0 : Wdf01000!FxDevice:Difficulty tracking down cause of DPC Watchdog Violation BSOD :DispatchWithLock+0x266 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1447] fffff182`b144e920 fffff805`40acb58d : ffff9008`2d59dd60 ffff9008`37f929c0 ffff9008`20010a40 ffff9008`00000030 : nt!IofCallDriver+0x55fffff182`b144e960 fffff805`40ac10d5 : ffff9008`239957f0 00000000`00000007 ffff9008`37f92e38 00000000`00000fff : ACPI!ACPIIrpDispatchDeviceControl+0xadfffff182`b144e9a0 fffff805`3b852f55 : 00000000`00000007 00000000`00000000 fffff182`b144eac9 ffff9008`396efd90 : ACPI!ACPIDispatchIrp+0xc5fffff182`b144ea20 fffff805`50a680d7 : 00000000`00000001 00000000`73556f49 ffff9008`3c5d62f0 00000000`00000000 : nt!IofCallDriver+0x55fffff182`b144ea60 fffff805`409ba976 : ffff9008`37f929c0 ffff9008`37f929c0 ffff9008`37f929c0 ffff9008`3c5d62f0 : UsbHub3!HUBPDO_EvtDeviceWdmIrpPreprocess+0x11d7fffff182`b144eb30 fffff805`3b852f55 : 00000000`0000000a ffff9008`3cc7ce10 00000000`00000000 ffff9008`37f929c0 : Wdf01000!FxDevice:Difficulty tracking down cause of DPC Watchdog Violation BSOD :DispatchWithLock+0x266 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1447] fffff182`b144eb90 fffff805`40acb58d : ffff9008`3cc7ce10 ffff9008`37f929c0 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x55fffff182`b144ebd0 fffff805`40ac10d5 : ffff9008`3a1aabf0 00000000`00000007 ffff9008`37f92e80 00000000`000000c0 : ACPI!ACPIIrpDispatchDeviceControl+0xadfffff182`b144ec10 fffff805`3b852f55 : 00000000`00000007 ffff9008`37f929c0 fffff182`b144ed89 ffff9008`397ad958 : ACPI!ACPIDispatchIrp+0xc5fffff182`b144ec90 fffff805`51111d9c : 00000000`00000001 ffff9008`37f929c0 fffff182`b144ed89 00000000`00000000 : nt!IofCallDriver+0x55fffff182`b144ecd0 fffff805`511119b6 : 00000000`00000200 00000000`00000000 fffff805`5112b008 ffff9008`397ad958 : usbccgp!DispatchPdoUrb+0x28cfffff182`b144edf0 fffff805`511112a6 : ffff9008`37f929c0 ffff9008`397ad950 ffff9008`397ad958 00000000`00000000 : usbccgp!DispatchPdoInternalDeviceControl+0x1c6fffff182`b144ee60 fffff805`3b852f55 : ffff9008`397ad800 00000000`0000bb01 00000000`00000000 ffff9008`00000000 : usbccgp!USBC_Dispatch+0x296fffff182`b144ef30 fffff805`409b35a7 : ffff9008`33626a00 ffff9008`3e0077a0 fffff182`b144f058 fffff182`b144f008 : nt!IofCallDriver+0x55fffff182`b144ef70 fffff805`409b1ca2 : fffff182`b144f001 ffff9008`38df4401 fffff182`b144f058 00000000`00000002 : Wdf01000!FxIoTarget::Send+0x17 [minkernel\wdf\framework\shared\inc\private\km\FxIoTargetKm.hpp @ 268] fffff182`b144efa0 fffff805`90b2a96d : ffff9008`39028f00 ffff9008`38df4430 ffff9008`3e0077a0 00000000`00000004 : Wdf01000!imp_WdfRequestSend+0x1d2 [minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 2090] fffff182`b144f020 fffff805`90b29bd2 : ffff9008`3981fd20 ffff9008`3da7db20 ffff9008`3981fd20 00000000`00000001 : nimc3usb+0xa96dfffff182`b144f0b0 fffff805`90b28062 : 00006ff7`c1656dd8 fffff805`90b25dc8 00000000`00000030 ffff62a7`c25f237f : nimc3usb+0x9bd2fffff182`b144f0e0 fffff805`90b25e0a : ffffffff`ffffffff ffff9008`397dba00 00000000`00000002 fffff805`3b83650b : nimc3usb+0x8062fffff182`b144f110 fffff805`409b9248 : ffff9008`3e9a9220 fffff805`40a47eb8 ffff9008`3569fdf0 fffff805`409c905a : nimc3usb+0x5e0afffff182`b144f140 fffff805`409bc854 : 00006ff7`c1656dd8 ffff9008`3e9a9220 ffff9008`3e9a9220 00000000`00000000 : Wdf01000!FxRequestBase::CompleteSubmitted+0xe8 [minkernel\wdf\framework\shared\core\fxrequestbase.cpp @ 530] fffff182`b144f1d0 fffff805`3b916f56 : ffff9008`3c5c7290 ffff9008`397dba02 ffff9008`397dba20 00001c21`00c00000 : Wdf01000!FxIoTarget::_RequestCompletionRoutine+0xe4 [minkernel\wdf\framework\shared\targets\general\fxiotarget.cpp @ 2448] fffff182`b144f240 fffff805`3b84885e : ffff9008`397dba20 fffff182`b144f2f9 00000000`00000000 ffff9008`397dbee3 : nt!IopUnloadSafeCompletion+0x56fffff182`b144f270 fffff805`3b848727 : 00000000`00000001 00000000`00000000 ffff9008`3525da30 00000000`00000002 : nt!IopfCompleteRequest+0x11efffff182`b144f360 fffff805`409b811a : 00000000`00000000 ffff9008`2d72ab00 ffff9008`397dba20 ffff9008`311ac010 : nt!IofCompleteRequest+0x17fffff182`b144f390 fffff805`409b5bbf : 00000000`00000002 fffff182`b144f4c8 ffff9008`397dba20 00000000`00000000 : Wdf01000!FxRequest::CompleteInternal+0x23a [minkernel\wdf\framework\shared\core\fxrequest.cpp @ 869] fffff182`b144f420 fffff805`4dff265e : ffff9008`3b2b7700 ffff9008`3b2b7560 00000000`00000002 ffff9008`3525de10 : Wdf01000!imp_WdfRequestComplete+0x8f [minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 436] fffff182`b144f480 fffff805`4dff20e6 : fffff182`b144f728 ffff9008`3525de10 fffff182`00000030 00000000`00000001 : USBXHCI!Isoch_Stage_CompleteTD+0x47efffff182`b144f540 fffff805`4dff1ef0 : fffff182`b144f700 fffff182`b144f600 00000000`00000000 fffff182`00000000 : USBXHCI!Isoch_ProcessTransferEventWithED1+0x1d6fffff182`b144f620 fffff805`4dff6570 : 00000000`00000004 fffff182`b144f6f8 00000000`00000008 fffff182`b144f700 : USBXHCI!Isoch_EP_TransferEventHandler+0x10fffff182`b144f650 fffff805`4dff60a5 : 00000000`00000780 00006ff7`d2832f00 ffff9008`2d469a90 ffff9008`3943ad10 : USBXHCI!Endpoint_TransferEventHandler+0xb0fffff182`b144f6b0 fffff805`4dff5d7c : ffff9008`2d490328 ffffe180`ccb19180 00006ff7`d2bacfd8 fffff182`b144f7d0 : USBXHCI!Interrupter_DeferredWorkProcessor+0x315fffff182`b144f7b0 fffff805`409b38f5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : USBXHCI!Interrupter_WdfEvtInterruptDpc+0xcfffff182`b144f7e0 fffff805`3b80781e : ffffe180`ccb1c240 00000000`00000000 fffff182`b144fae0 ffffe180`ccb19180 : Wdf01000!FxInterrupt::_InterruptDpcThunk+0xa5 [minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp @ 404] fffff182`b144f820 fffff805`3b806b04 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30efffff182`b144f990 fffff805`3b9f95ee : ffffffff`00000000 ffffe180`ccb19180 ffffe180`ccb24640 ffff9008`3c4b3080 : nt!KiRetireDpcList+0x1f4fffff182`b144fc20 00000000`00000000 : fffff182`b1450000 fffff182`b1449000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e

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

    SYMBOL_NAME: USBXHCI!Isoch_Stage_MapIntoRing+4fbMODULE_NAME: USBXHCIIMAGE_NAME: USBXHCI.SYSIMAGE_VERSION: 10.0.19041.662STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 4fbFAILURE_BUCKET_ID: 0x133_DPC_USBXHCI!Isoch_Stage_MapIntoRingOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {3306663a-e5a1-0654-e582-221154dc73f3}Followup: MachineOwner---------
    The most recent DMP file can be found here


    Any help would be incredibly appreciated!

    :)
     
    LariputtomusMcFly, Mar 9, 2021
    #1

  2. BSOD- DPC Watchdog violation

    BSOD - DPC watchdog violation how to fix?
     
    JamesJagow, Mar 9, 2021
    #2
  3. BSOD DPC WATCHDOG VIOLATION

    According to what I found from your minidump file, ndis.sys is caused this
    DPC WATCHDOG VIOLATION BSOD error on your Windows computer.It's a
    NDIS 6.20 Wrapper Driver and installed onto your computer through Windows Update. As far as I know, you have installed new Windows updates lately.

    You can uninstall those updates out of your computer, restart your PC and check again the result. Remember to do these steps in Safe Mode.

    For more solutions to fix DPC watchdog violation BSOD error in case the above method doesn't work, check it out the following link below:

    Bagaimana Memperbaiki Kesalahan Pelanggaran DPC Watchdog Di Windows
     
    JokerKingLove, Mar 9, 2021
    #3
  4. Difficulty tracking down cause of DPC Watchdog Violation BSOD

    brandonwh64, Mar 9, 2021
    #4
Thema:

Difficulty tracking down cause of DPC Watchdog Violation BSOD

Loading...
  1. Difficulty tracking down cause of DPC Watchdog Violation BSOD - Similar Threads - Difficulty tracking down

  2. DPC WATCHDOG VIOLATION - tracking down issues

    in Windows 10 Gaming
    DPC WATCHDOG VIOLATION - tracking down issues: DPC Watchdog violation - bsod - 1min to 4 days between issue, causing freeze for 3-5mins, then restarting.041024-8656-01.zipAny help to understand what is causing the issue is appreciated...
  3. DPC WATCHDOG VIOLATION - tracking down issues

    in Windows 10 Software and Apps
    DPC WATCHDOG VIOLATION - tracking down issues: DPC Watchdog violation - bsod - 1min to 4 days between issue, causing freeze for 3-5mins, then restarting.041024-8656-01.zipAny help to understand what is causing the issue is appreciated...
  4. DPC Watchdog Violation BSOD

    in Windows 10 BSOD Crashes and Debugging
    DPC Watchdog Violation BSOD: Hello,My PC has been crashing for a couple weeks now. First instance happened while I was watching Netflix after installing latest NVIDIA driver v512.95 then I rolled back to v472.12 but issue still remains with crashes happened every reboot while watching movies, web...
  5. DPC watchdog violation BSOD

    in Windows 10 Software and Apps
    DPC watchdog violation BSOD: SYMBOL_NAME: mtkwl6ex+335ceMODULE_NAME: mtkwl6exIMAGE_NAME: mtkwl6ex.sysSTACK_COMMAND: .cxr; .ecxr ; kbBUCKET_ID_FUNC_OFFSET: 335ceFAILURE_BUCKET_ID: 0x133_ISR_mtkwl6ex!unknown_functionOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows...
  6. DPC Watchdog Violation causes

    in AntiVirus, Firewalls and System Security
    DPC Watchdog Violation causes: Can the DPC Watchdog Violation BSOD occurs by my computer overheating? When it started happening my mouse started freezing along with it. https://answers.microsoft.com/en-us/protect/forum/all/dpc-watchdog-violation-causes/a604687f-271d-4709-a106-0bbd52b719b4
  7. DPC Watchdog Violation causing BSOD

    in Windows 10 BSOD Crashes and Debugging
    DPC Watchdog Violation causing BSOD: My system is crashing repeatedly with BSOD error. Link to mindump and msinfo32 file: https://1drv.ms/u/s!ArYxG7K1uoYsgYZVdUsx17w0P2EVXw?e=3WAkEE FYI, I had opened the dump file and it had shown that the error was caused by driver:ntoskrnl.exe, so I followed some...
  8. DPC Watchdog Violation BSOD

    in Windows 10 BSOD Crashes and Debugging
    DPC Watchdog Violation BSOD: Hello, I've been recently getting BSODs with error code DPC Watchdog Violation when waking PC up from sleep mode. My log files and system info can be found here: https://1drv.ms/u/s!Ap87I0ekZbOF3WhuIjiI--QnKxbn?e=oOiOh8 Thanks, Daniel...
  9. BSOD-DPC Watchdog Violation

    in Windows 10 BSOD Crashes and Debugging
    BSOD-DPC Watchdog Violation: Hi, my computer crashed 5 times in the past two months with a DPC Watchdog Violation coded blue screen error. I uploaded the DMP file of the latest crash, the output of Msinfo, and my computer specifications assuming that it may help diagnose the crash. It would help a lot...
  10. BSOD (DPC Watchdog Violations)

    in Windows 10 BSOD Crashes and Debugging
    BSOD (DPC Watchdog Violations): Good Evening everyone! I will start this out by saying I am not an 85 year old grandmother trying to get on Facebook. I have been using computer since I was 8 (1993) and I am, for the first time, at a total loss. I keep getting intermittent BSOD (DPC Watchdog Violations). I...