Windows 10: I got Blue Screen for weeks with DPC WATCHDOG VIOLATION error

After I update my Windows10 laptop, it had kept giving me Blue Screens with DPC WATCHDOG VIOLATION error, and I try to check my hardware and drivers but nothing changed.


here is the WinDbg shows for the last error minidump, you can also get all 3 dump fileshere. Those files record same error happened after I tried to reinstall my Windows system a few days ago.


Thanks for your help.



Microsoft R Windows Debugger Version 10.0.20153.1000 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\Minidump\080320-15250-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 12 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalEdition build lab: 18362.1.amd64fre.19h1_release.190318-1202Machine Name:Kernel base = 0xfffff804`4ca00000 PsLoadedModuleList = 0xfffff804`4ce48150Debug session time: Mon Aug 3 03:18:35.567 2020 UTC + 10:00System Uptime: 1 days 8:07:24.484Loading Kernel Symbols..................................................................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list................................For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff804`4cbc23c0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9780`820d8b10=00000000000001338: 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: fffff8044cf73358, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains additional information regarding this single DPC timeoutDebugging Details:------------------*** WARNING: Unable to verify timestamp for gwdrv.sys**************************************************************************** ****** ****** 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 ****** ******************************************************************************* WARNING: Unable to verify checksum for win32k.sysKEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 7156 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on TERRY-M15 Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 60446 Key : Analysis.Memory.CommitPeak.Mb Value: 86 Key : Analysis.System Value: CreateObject Key : WER.OS.Branch Value: 19h1_release Key : WER.OS.Timestamp Value: 2019-03-18T12:02:00Z Key : WER.OS.Version Value: 10.0.18362.1ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1BUGCHECK_CODE: 133BUGCHECK_P1: 0BUGCHECK_P2: 501BUGCHECK_P3: 500BUGCHECK_P4: fffff8044cf73358DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDEDTRAP_FRAME: ffffe10f7e89c440 -- .trap 0xffffe10f7e89c440NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=fffff8044cafd420 rbx=0000000000000000 rcx=ffffe10f7e89ca20rdx=ffff81c0e1e2cdf8 rsi=0000000000000000 rdi=0000000000000000rip=fffff8044cafd420 rsp=ffffe10f7e89c5d8 rbp=fffff8044ce69040 r8=0000000000000001 r9=0000000000000887 r10=fffff8044cafd420r11=0000000000000000 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei pl zr na po ncnt!MiDeleteNonPagedPoolPte:fffff804`4cafd420 4053 push rbxResetting default scopeBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemSTACK_TEXT: ffffe10f`7e89c5d8 fffff804`4ca732b7 : fffff804`4ce69040 ffff81c0`e1e2cdf8 00000000`00004000 00000000`00000000 : nt!MiDeleteNonPagedPoolPteffffe10f`7e89c5e0 fffff804`4ca73771 : ffffe10f`7e89ca20 ffffe10f`7e89ca20 00000000`00000000 00000000`00000000 : nt!MiWalkPageTablesRecursively+0x1e7ffffe10f`7e89c6a0 fffff804`4ca73771 : ffffe10f`7e89ca20 ffffe10f`0000001e ffff81c0`00000000 00000000`0000001e : nt!MiWalkPageTablesRecursively+0x6a1ffffe10f`7e89c760 fffff804`4ca72efc : ffffe10f`7e89ca20 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiWalkPageTablesRecursively+0x6a1ffffe10f`7e89c820 fffff804`4cae79aa : ffffe10f`7e89ca20 fffff804`00000002 00000000`00000001 fffff804`00000001 : nt!MiWalkPageTables+0x36cffffe10f`7e89c920 fffff804`4cae7870 : ffff878b`00000001 00000000`00005800 00000000`00005800 ffff8789`e4f61b20 : nt!MiClearNonPagedPtes+0xe6ffffe10f`7e89cb20 fffff804`4cae7696 : fffff804`4ce6e9f8 fffff804`4ce6e158 00000000`00001002 00000000`00000100 : nt!MmFreePoolMemory+0x1a8ffffe10f`7e89cbb0 fffff804`4cae75dc : fffff804`4ce6e9f8 fffff804`4ce6e158 00000000`00001002 00000000`78b0d800 : nt!RtlpHpEnvFreeVA+0x12ffffe10f`7e89cbe0 fffff804`4caea4de : 00000001`00200000 ffff878b`0d800000 00000000`00000001 00000000`00000000 : nt!RtlpHpVaMgrRangeFree+0x54ffffe10f`7e89cc10 fffff804`4cae7679 : ffff878a`d6400000 00000000`00000000 00000000`00000000 00000000`00000001 : nt!RtlpHpVaMgrCtxFree+0x6affffe10f`7e89cc70 fffff804`4cc393db : 00000000`40000000 ffff878a`d6400000 00000000`00000000 00000000`00000028 : nt!RtlpHpFreeVA+0x89ffffe10f`7e89ccb0 fffff804`4ca9abcc : 00000000`00000001 00000001`00000000 00000001`00000000 00000000`00000000 : nt!RtlpHpLargeAlloc+0x152cafffffe10f`7e89ce20 fffff804`4cd6f06d : ffffffff`00000000 00000000`00000000 00000000`00000000 00000000`fffffff5 : nt!ExAllocateHeapPool+0x56cffffe10f`7e89cf60 fffff804`6520424e : ffff878a`d63d63b0 ffff878a`d63c1090 ffff878a`f80f51b0 ffff878a`00000000 : nt!ExAllocatePoolWithTag+0x5dffffe10f`7e89cfb0 ffff878a`d63d63b0 : ffff878a`d63c1090 ffff878a`f80f51b0 ffff878a`00000000 00000000`00000000 : gwdrv+0x424effffe10f`7e89cfb8 ffff878a`d63c1090 : ffff878a`f80f51b0 ffff878a`00000000 00000000`00000000 fffff804`652025b7 : 0xffff878a`d63d63b0ffffe10f`7e89cfc0 ffff878a`f80f51b0 : ffff878a`00000000 00000000`00000000 fffff804`652025b7 ffff878a`f971b750 : 0xffff878a`d63c1090ffffe10f`7e89cfc8 ffff878a`00000000 : 00000000`00000000 fffff804`652025b7 ffff878a`f971b750 ffff878a`f80f51b0 : 0xffff878a`f80f51b0ffffe10f`7e89cfd0 00000000`00000000 : fffff804`652025b7 ffff878a`f971b750 ffff878a`f80f51b0 ffff878a`f80f51b0 : 0xffff878a`00000000STACK_COMMAND: .trap 0xffffe10f7e89c440 ; kbSYMBOL_NAME: gwdrv+424eMODULE_NAME: gwdrvIMAGE_NAME: gwdrv.sysBUCKET_ID_FUNC_OFFSET: 424eFAILURE_BUCKET_ID: 0x133_DPC_gwdrv!unknown_functionOS_VERSION: 10.0.18362.1BUILDLAB_STR: 19h1_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {229a5753-87e5-3d87-e2b9-50836a10c652}Followup: MachineOwner---------

:)

 

Help! Watchdog Violation

More info on that BSOD

How to Fix DPC_Watchdog_Violation Blue Screen error

 

DPC Watchdog Violation

I have an HP desktop that upgraded to windows 10. I continue to have the DPC Watchdog Violation blue screen. Any suggestions?

Don

PS I do not have a IDE ATA/ATAPI controllers on my device manager

 

Blue Screen of Display in Windows 10, Error message : DPC Watchdog Violation.

Original title: DPC Watchdog Violation

I have an laptop with Windows 10 and I seem to be getting the blue screen for this error every couple of weeks or so for the last month or two. I've read that it is usually a driver problem and lots of people have suggested that it could be from using the
touch pad, although I've always used a mouse.

Here is the dump file:

TinyUpload.com - best file hosting solution, with no limits, totaly free

Any help would be appreciated,

Thanks!