Windows 10: DPC_WATCHDOG_VIOLATION 133

Whenever I connect my Lenovo Y500 with ethernet cable Win 10 at random time system crash and BSOD appear with DPC_WATCHDOG_VIOLATION.

I tried to debug the memory.dmp you can download it from here but could not figure out fix. Here is the output of analysis.


[COLOR=rgba30, 30, 30, 1]Microsoft R Windows Debugger Version 10.0.20153.1000 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\MEMORY.DMP]Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 19041 MP 8 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTSEdition build lab: 19041.1.amd64fre.vb_release.191206-1406Machine Name:Kernel base = 0xfffff807`05400000 PsLoadedModuleList = 0xfffff807`0602a2f0Debug session time: Sat Jan 30 01:11:19.324 2021 UTC + 5:30System Uptime: 0 days 0:10:03.156Loading Kernel Symbols.......................................................................Page 114428 not present in the dump file. Type ".hh dbgerr004" for details.........................................................................................................................................Loading User SymbolsPEB is paged out Peb.Ldr = 000000ec`6b667018. Type ".hh dbgerr001" for detailsLoading unloaded module list..........For analysis of this file, run [/COLOR][COLOR=rgba0, 0, 255, 1]!analyze -v[/COLOR][COLOR=rgba30, 30, 30, 1]nt!KeBugCheckEx:fffff807`057f5780 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8800`2dbf3e20=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: fffff807060fa320, 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.mSec Value: 4468 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on JEET-CHAUDHARI Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 21801 Key : Analysis.Memory.CommitPeak.Mb Value: 78 Key : Analysis.System Value: CreateObject Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1BUGCHECK_CODE: 133BUGCHECK_P1: 1BUGCHECK_P2: 1e00BUGCHECK_P3: fffff807060fa320BUGCHECK_P4: 0DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDEDTRAP_FRAME: ffffec854fdaa5d0 -- [/COLOR][COLOR=rgba0, 0, 255, 1].trap 0xffffec854fdaa5d0[/COLOR][COLOR=rgba30, 30, 30, 1]NOTE: The trap frame does not contain all registers.[/COLOR][COLOR=rgba0, 0, 255, 1]Some register values may be zeroed or incorrect.[/COLOR][COLOR=rgba30, 30, 30, 1]rax=000000003c562f7d rbx=0000000000000000 rcx=ffffec854fdaa7acrdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000rip=fffff8070564456c rsp=ffffec854fdaa768 rbp=ffff88002dfed180 r8=0000000000000020 r9=00000000000000ff r10=0000000000000000r11=fffff80705400000 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei ng nz na po ncnt!KeYieldProcessorEx+0x1c:fffff807`0564456c c3 retResetting default scopeBLACKBOXBSD: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxbsd[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXNTFS: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxntfs[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXPNP: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxpnp[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXWINLOGON: 1PROCESS_NAME: msedge.exeSTACK_TEXT: ffff8800`2dbf3e18 fffff807`0583aa0c : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff807`060fa320 : nt!KeBugCheckExffff8800`2dbf3e20 fffff807`0566f9a3 : 00000135`f659afbe ffff8800`2dfed180 00000000`00000000 ffff8800`2dfed180 : nt!KeAccumulateTicks+0x1c880cffff8800`2dbf3e80 fffff807`0566f48a : ffff9d02`610c79a0 ffffec85`4fdaa650 00000000`00000000 fffff807`0176bac0 : nt!KeClockInterruptNotify+0x453ffff8800`2dbf3f30 fffff807`05727ef5 : ffff9d02`610c79a0 fffff807`057146b7 00000000`00000000 00000000`00000000 : nt!HalpTimerClockIpiRoutine+0x1affff8800`2dbf3f60 fffff807`057f722a : ffffec85`4fdaa650 ffff9d02`610c79a0 00000000`00000001 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5ffff8800`2dbf3fb0 fffff807`057f7797 : ffff9d02`00000000 00001f80`007f0224 00000000`3c5582f5 ffffec85`4fdaa7ac : nt!KiInterruptSubDispatchNoLockNoEtw+0xfaffffec85`4fdaa5d0 fffff807`0564456c : fffff807`05667208 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37ffffec85`4fdaa768 fffff807`05667208 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeYieldProcessorEx+0x1cffffec85`4fdaa770 fffff807`05665a1c : ffffec85`00000008 00000000`00000000 000000ec`00000000 00000000`00000000 : nt!KiCancelTimer+0x2b8ffffec85`4fdaa820 fffff807`05664d7f : ffff9d02`65dc1080 00000000`00000000 ffffec85`4fdaa9e0 00000000`00000000 : nt!KiSwapThread+0x6ccffffec85`4fdaa8d0 fffff807`05664623 : ffff8800`000000ff fffff807`00000000 00078405`b19bbd01 ffff9d02`65dc11c0 : nt!KiCommitThreadWait+0x14fffffec85`4fdaa970 fffff807`05a2c6a1 : ffff9d02`6a19eee0 00000000`00000006 00000000`00000001 00000000`00000000 : nt!KeWaitForSingleObject+0x233ffffec85`4fdaaa60 fffff807`05a2c74a : ffff9d02`65dc1080 000000ec`76fff5b8 00000000`00000000 000002b5`72b5faf0 : nt!ObWaitForSingleObject+0x91ffffec85`4fdaaac0 fffff807`058071b8 : 00000000`00000000 00000000`00000001 ffffec85`4fdaab18 ffffffff`fffe2b40 : nt!NtWaitForSingleObject+0x6affffec85`4fdaab00 00007ffb`36fcc034 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28000000ec`76fff588 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`36fcc034SYMBOL_NAME: nt!KeAccumulateTicks+1c880cMODULE_NAME: [/COLOR][COLOR=rgba0, 0, 255, 1]nt[/COLOR][COLOR=rgba30, 30, 30, 1]IMAGE_NAME: [COLOR=rgba0, 0, 0, 1]ntkrnlmp.exe[/COLOR] STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 1c880cFAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicksOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}Followup: MachineOwner---------[/COLOR]

:)

 

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?

 

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.

 

Some tutorials needed

Hey, there isnt any 110/33.. etc

The is list is like this: [133/33,134/34,135/34...]
my default is 133/33 but now i step it to 134/34 and my CPU becomes 2.41Ghz...

Running with no problems... should I step up again?