Windows 10: DPC_WATCHDOG_VIOLATION 133

while I was using my pc it just froze and then bluescreen out of nowhere. I opened the minidump file and this is what I got.


Microsoft R Windows Debugger Version 10.0.20153.1000 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\Minidump\110320-20546-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 19041 MP 4 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTSMachine Name:Kernel base = 0xfffff802`08e00000 PsLoadedModuleList = 0xfffff802`09a2a310Debug session time: Tue Nov 3 09:22:45.998 2020 UTC + 2:00System Uptime: 11 days 16:23:47.296Loading Kernel Symbols.......................................................................................................................................................................................Loading User SymbolsLoading unloaded module list..................................................For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff802`091f45a0 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffaa00`b5d41e20=00000000000001333: 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: 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: fffff80209afb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains additional information regarding this single DPC timeoutDebugging 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: 2562 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on RAZVANEL Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 5254 Key : Analysis.Memory.CommitPeak.Mb Value: 81 Key : Analysis.System Value: CreateObjectADDITIONAL_XML: 1OS_BUILD_LAYERS: 1DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage DumpBUGCHECK_CODE: 133BUGCHECK_P1: 0BUGCHECK_P2: 501BUGCHECK_P3: 500BUGCHECK_P4: fffff80209afb320DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDEDBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: steam.exeSTACK_TEXT: ffffaa00`b5d41e18 fffff802`09287a14 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckExffffaa00`b5d41e20 fffff802`09126993 : 0004eff3`1b2450ac ffffaa00`b5cef180 00000000`00000000 ffffaa00`b5cef180 : nt!KeAccumulateTicks+0x15dd24ffffaa00`b5d41e80 fffff802`0912647a : ffffbf0f`9c2d2d40 ffff920e`aaa57870 00000000`0dca5000 00000000`00000001 : nt!KeClockInterruptNotify+0x453ffffaa00`b5d41f30 fffff802`0902ecd5 : ffffbf0f`9c2d2d40 00000000`00000000 00000000`00000000 ffff0ea2`c050b35a : nt!HalpTimerClockIpiRoutine+0x1affffaa00`b5d41f60 fffff802`091f604a : ffff920e`aaa57870 ffffbf0f`9c2d2d40 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5ffffaa00`b5d41fb0 fffff802`091f65b7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfaffff920e`aaa577f0 fffff802`091302fc : 00000000`00000000 00000000`00000000 00000000`0000000e ffff920e`aaa579f8 : nt!KiInterruptDispatchNoLockNoEtw+0x37ffff920e`aaa57980 fffff802`091302c8 : ffffbf0f`9f7872f0 ffffaa00`b5cef180 00000000`00000003 fffff802`0b2d6e27 : nt!KxWaitForSpinLockAndAcquire+0x2cffff920e`aaa579b0 fffff802`0b2e987c : ffffbf0f`9f7861a0 ffffbf0f`9f7872f0 fffff802`0b39a448 ffffbf0f`9f7861a0 : nt!KeAcquireSpinLockRaiseToDpc+0x88ffff920e`aaa579e0 fffff802`0b336f56 : ffffbf0f`a1051010 ffff920e`aaa57aa0 ffffbf0f`9f7861a0 fffff802`09a23b50 : ndis!ndisReferenceMiniportNoCheck+0x30ffff920e`aaa57a30 fffff802`0b3137c1 : ffffbf0f`a10512b8 ffffbf0f`a1051010 00000000`00000000 00000000`ffffffff : ndis!ndisQueueDpcWorkItem+0x86ffff920e`aaa57ad0 fffff802`090e549e : ffffaa00`b5cf2240 ffffbf0f`9c5e4000 ffffaa00`b5cef180 ffffaa00`00000002 : ndis!ndisInterruptDpc+0x3c0d1ffff920e`aaa57bb0 fffff802`090e4784 : ffffaa00`b5cef180 00000000`00000000 00000000`00000008 00000000`024b8d5f : nt!KiExecuteAllDpcs+0x30effff920e`aaa57d20 fffff802`091fb5e5 : 00000000`00000000 ffffaa00`b5cef180 00000000`00000000 00000000`00ed0a80 : nt!KiRetireDpcList+0x1f4ffff920e`aaa57fb0 fffff802`091fb3d0 : 00000000`00000000 00000000`011a3000 00000000`1017fda0 00000000`1017ec40 : nt!KxRetireDpcList+0x5ffff920e`af8f79d0 fffff802`091faa9e : 00000000`21743786 ffffbf0f`a602f080 ffff920e`00000000 ffffbf0f`00000000 : nt!KiDispatchInterruptContinueffff920e`af8f7a00 00000000`5d1945f4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x2ee00000000`1091f288 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5d1945f4SYMBOL_NAME: ndis!ndisReferenceMiniportNoCheck+30MODULE_NAME: ndisIMAGE_NAME: ndis.sysIMAGE_VERSION: 10.0.19041.546STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 30FAILURE_BUCKET_ID: 0x133_DPC_ndis!ndisReferenceMiniportNoCheckOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {e2096108-c9bd-4fa8-ca90-9fae653f292c}Followup: MachineOwner---------

:)

 

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?