Windows 10: DPC_WATCHDOG_VIOLATION 133 Keeps Occuring

Hi. I keep getting the DPC WATCHDOG VIOLATION and I don't know how to fix it. I've tried updating the drivers but nothing helps.


Most recent crash dump:


Microsoft R Windows Debugger Version 10.0.19528.1000 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\Minidump\063020-7234-01.dmp]Mini Kernel Dump File: Only registers and stack trace are available************* Path validation summary **************Response Time ms LocationDeferred srv*Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 18362 MP 6 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS Personal18362.1.amd64fre.19h1_release.190318-1202Machine Name:Kernel base = 0xfffff801`69400000 PsLoadedModuleList = 0xfffff801`69848190Debug session time: Tue Jun 30 11:38:16.208 2020 UTC + 8:00System Uptime: 0 days 19:01:29.953Loading Kernel Symbols...........................................................................................................................................................................................Loading User SymbolsLoading unloaded module list......For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff801`695c23a0 48894c2408 mov qword ptr [rsp+8],rcx ss:ffff9700`75ad1b10=00000000000001334: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DPC_WATCHDOG_VIOLATION 133The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVELor above.Arguments:Arg1: 0000000000000001, The system cumulatively spent an extended period of time at DISPATCH_LEVEL or above. The offending component can usually be identified with a stack trace.Arg2: 0000000000001e00, The watchdog period.Arg3: fffff80169973358, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains additional information regarding the cumulative timeoutArg4: 0000000000000000Debugging 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.Sec Value: 3 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-837NQBP Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 4 Key : Analysis.Memory.CommitPeak.Mb Value: 69 Key : Analysis.System Value: CreateObjectADDITIONAL_XML: 1BUGCHECK_CODE: 133BUGCHECK_P1: 1BUGCHECK_P2: 1e00BUGCHECK_P3: fffff80169973358BUGCHECK_P4: 0DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDEDCUSTOMER_CRASH_COUNT: 1PROCESS_NAME: chrome.exeSTACK_TEXT: ffff9700`75ad1b08 fffff801`695fcb6b : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff801`69973358 : nt!KeBugCheckExffff9700`75ad1b10 fffff801`69448637 : 0000b4ed`eb8fa5fa ffff9700`75a79180 00000000`00000286 fffffd0e`3a23ef60 : nt!KeAccumulateTicks+0x1b136bffff9700`75ad1b70 fffff801`69eba291 : 00000000`00000002 ffff8201`512d5500 fffffd0e`3a23efe0 ffff8201`512d55b0 : nt!KeClockInterruptNotify+0xc07ffff9700`75ad1f30 fffff801`69537385 : ffff8201`512d5500 fffff801`6951b7a7 ffff8201`512d5600 00000000`00000000 : hal!HalpTimerClockIpiRoutine+0x21ffff9700`75ad1f60 fffff801`695c3e2a : fffffd0e`3a23efe0 ffff8201`512d5500 00000000`00000001 ffff8201`512d5500 : nt!KiCallInterruptServiceRoutine+0xa5ffff9700`75ad1fb0 fffff801`695c4397 : 00000000`b6d671f4 fffffd0e`3a23efe0 ffff8201`512d5500 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfafffffd0e`3a23ef60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37SYMBOL_NAME: nt!KeAccumulateTicks+1b136bMODULE_NAME: ntIMAGE_NAME: ntkrnlmp.exeIMAGE_VERSION: 10.0.18362.900STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 1b136bFAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicksOS_VERSION: 10.0.18362.1BUILDLAB_STR: 19h1_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}Followup: MachineOwner---------4: kd> lmvm ntBrowse full module liststart end module namefffff801`69400000 fffff801`69eb7000 nt pdb symbols C:\ProgramData\Dbg\sym\ntkrnlmp.pdb\0A0AB369CCAF2C2B44D37A82A8E6C16D1\ntkrnlmp.pdb Loaded symbol image file: ntkrnlmp.exe Mapped memory image file: C:\ProgramData\Dbg\sym\ntoskrnl.exe\4FF75719ab7000\ntoskrnl.exe Image path: ntkrnlmp.exe Image name: ntkrnlmp.exe Browse all global symbols functions data Image was built with /Brepro flag. Timestamp: 4FF75719 This is a reproducible build file hash, not a timestamp CheckSum: 00986144 ImageSize: 00AB7000 File version: 10.0.18362.900 Product version: 10.0.18362.900 File flags: 0 Mask 3F File OS: 40004 NT Win32 File type: 1.0 App File date: 00000000.00000000 Translations: 0409.04b0 Information from resource tables: CompanyName: Microsoft Corporation ProductName: Microsoft® Windows® Operating System InternalName: ntkrnlmp.exe OriginalFilename: ntkrnlmp.exe ProductVersion: 10.0.18362.900 FileVersion: 10.0.18362.900 WinBuild.160101.0800 FileDescription: NT Kernel & System LegalCopyright: © Microsoft Corporation. All rights reserved.

:)

 

DPC_WATCHDOG_VIOLATION

Hi,

It is possible that the error DPC_WATCHDOG_VIOLATION may occur if the iastor.sys driver is incompatible with Windows 10. To isolate your issue, we'd like to gather more information:

• Have you made any recent changes before this issue occurred?
• What troubleshooting steps have you done so far?

Any response will be highly appreciated.

 

DPC_WATCHDOG_VIOLATION

The minidump files showed two different errors, a DPC_WATCHDOG_VIOLATION (133) error and a SYSTEM_SERVICE_EXCEPTION (3b) error.

The DPC_WATCHDOG_VIOLATION may be caused by a wireless driver, the athwnx.sys.

Which wireless adapter do you have and which driver is installed?

Also, what ASUS software is installed?

 

Bug Check 0x133 DPC_WATCHDOG_VIOLATION

Hi Kristopher,

Usually, Blue Screen of Death (BSOD) with error message DPC_WATCHDOG_VIOLATION is caused by a hardware issue or system file corruption. For us to isolate your concern, we need answers to the following:

• Did you make any changes on your computer prior to the issue?
• Does the issue occur when you're doing a specific activity?
• Have you taken any troubleshooting steps so far?

Meanwhile, we recommend that you follow the steps on this
article on how to troubleshoot blue screen errors.

Keep us posted and we'll be willing to assist you further.