Windows 10: BSOD DPC Watchdog violation : why? can someone help?

Hi,


My computer has started since friday 10 july 2020 to have random BSOD due to a "DPC watchdog violation" error.


I read multiple threads and applied most of their explanations.


A what i have tried


- sfc scannow command : all is okay

- chdsk at reboot : all is okay

- hd tune on every disk drive: all is okay

- update all the drivers. The only one I canno't update is the latest realtek HD definition" package because each time i start downloading it from realtek website, the speed is so slow that it would take 4+ hours and it fails everytime I tried 4 times to download it. The package is 252 mo.

- memory test from windows : no problem

- intel processeur tool : all okay

- windows update = up to date, nothing to install



B what is "new" on my pc from what i know:

- I bought a logitech G402 hyperion fury and installed the latest driver. I noticed during the step to clean AMD drivers before installing the latest driver that the mouse is not recognized in windows safe mode but it works well in normal mode. I'm not sure it is related but i prefer to say

- in begin july I know windows installed the windows version 2004 a big update like the infamous creator fall from many months/years ago i don't remember exactly ^^. That was updated like yesterday and i had a crash again today while on discord.



C My personal impression at the time of the crash

First crash i was in a demanding game but well it was the only crash in that game so... shadow of the tomb raider.

Second, i was playing RPG on discord and had word, excel, firefox with gdrive docs and discord, besides adobe reader open.

Third, I was listening to a video on youtube and playing pathfinder kingmaker at the same time something I have done like 70 hours during the last week.

Fourth, i had just started the computer and music bee music player was the only thing running actively on the pc.


Fifth, same as second.


The computer "freezes" the mouse don't move, the sound is bugged


D computer


Computer name: PC-NEXTGEN
Windows version: Windows 10 , 10.0, build: 19041
Windows dir: C:\WINDOWS
Hardware: ASRock, P67 Pro3 SE
CPU: GenuineIntel IntelR CoreTM i5-2500K CPU @ 3.30GHz Intel8664, level: 6
4 logical processors, active mask: 15
RAM: 17159372800 bytes 16,0GB

It's a computer i have since april 2012 approximatly.


E Crashdump analysis


what the crash dump analysis tools say: I used two:

- WinDBg which seems to be an official microsoft tool

- whocrashed




From WinDBg




1 crash from 10 july

Microsoft R Windows Debugger Version 10.0.20153.1000 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [E:\Mes Documents\Downloads\071020-7093-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 SingleUserTS PersonalEdition build lab: 19041.1.amd64fre.vb_release.191206-1406Machine Name:Kernel base = 0xfffff801`3e600000 PsLoadedModuleList = 0xfffff801`3f22a2b0Debug session time: Fri Jul 10 09:47:47.444 2020 UTC + 2:00System Uptime: 0 days 2:30:31.656Loading Kernel Symbols.......................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list.........For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff801`3e9dda20 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffb800`39bfce20=0000000000000133Loading Dump File [E:\Mes Documents\Downloads\071020-7093-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableCan't set dump file contextsMachineInfo::SetContext failed - Thread: 00000226838EF5C0 Handle: 4 Id: 4 - Error == 0x8000FFFF************* 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 SingleUserTS PersonalEdition build lab: 19041.1.amd64fre.vb_release.191206-1406Machine Name:Kernel base = 0xfffff801`3e600000 PsLoadedModuleList = 0xfffff801`3f22a2b0Debug session time: Fri Jul 10 09:47:47.444 2020 UTC + 2:00System Uptime: 0 days 2:30:31.656Loading Kernel Symbols.......................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list.........nt!KeBugCheckEx:fffff801`3e9dda20 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffb800`39bfce20=0000000000000133Loading Dump File [E:\Mes Documents\Downloads\071020-7093-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableCan't set dump file contextsMachineInfo::SetContext failed - Thread: 0000022688399740 Handle: 4 Id: 4 - Error == 0x8000FFFF************* 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 SingleUserTS PersonalEdition build lab: 19041.1.amd64fre.vb_release.191206-1406Machine Name:Kernel base = 0xfffff801`3e600000 PsLoadedModuleList = 0xfffff801`3f22a2b0Debug session time: Fri Jul 10 09:47:47.444 2020 UTC + 2:00System Uptime: 0 days 2:30:31.656Loading Kernel Symbols.......................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list.........nt!KeBugCheckEx:fffff801`3e9dda20 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffb800`39bfce20=00000000000001332:3: 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: fffff8013f2fa318, 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 ****** ******************************************************************************* WARNING: Unable to verify checksum for win32k.sysKEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 6608 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on PC-NEXTGEN Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 10425 Key : Analysis.Memory.CommitPeak.Mb Value: 152 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: 0BUGCHECK_P2: 501BUGCHECK_P3: 500BUGCHECK_P4: fffff8013f2fa318DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDEDTRAP_FRAME: ffffce0dc8645370 -- .trap 0xffffce0dc8645370NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000081000010 rbx=0000000000000000 rcx=ffffb80039be3180rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000rip=fffff8013e912117 rsp=ffffce0dc8645500 rbp=ffffce0dc86455d9 r8=ffff890ed15d4de0 r9=0000000000000000 r10=fffff8013e9120d0r11=ffff890ec137a260 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei pl zr na po ncnt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x47:fffff801`3e912117 4885d2 test rdx,rdxResetting default scopeBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemSTACK_TEXT: ffffb800`39bfce18 fffff801`3ea593ee : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckExffffb800`39bfce20 fffff801`3e8ca2ed : 00001b14`c3a76e31 00000000`00000000 ffffce0d`c8645300 ffffb800`39be3180 : nt!KeAccumulateTicks+0x18bf6effffb800`39bfce80 fffff801`3e8ca16a : ffff890e`bf8a7d40 ffffce0d`c86453f0 00000001`0008d1ea 00000000`00000000 : nt!KeClockInterruptNotify+0xbdffffb800`39bfcf30 fffff801`3e808705 : ffff890e`bf8a7d40 00000000`00000000 00000000`00000000 ffff3f4b`d9ba694d : nt!HalpTimerClockIpiRoutine+0x1affffb800`39bfcf60 fffff801`3e9df4ca : ffffce0d`c86453f0 ffff890e`bf8a7d40 00000000`00000200 a9cb30f8`5fe5ec59 : nt!KiCallInterruptServiceRoutine+0xa5ffffb800`39bfcfb0 fffff801`3e9dfa37 : 00000000`00000000 ffff890e`c1419a50 ffff890e`c1381220 fffff801`3e9dfa44 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfaffffce0d`c8645370 fffff801`3e912117 : 00000000`00000010 00000000`00000286 ffffce0d`c8645528 00000000`00000018 : nt!KiInterruptDispatchNoLockNoEtw+0x37ffffce0d`c8645500 fffff801`429f9fd5 : ffff890e`c1381220 fffff780`00000008 00000000`00000000 00001f80`00fc0001 : nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x47ffffce0d`c8645530 fffff801`429f84d7 : 00000000`00000000 00000000`00989680 00000000`00000003 00000014`fb5d193d : tcpip!TcpProcessExpiredTcbTimers+0x3c5ffffce0d`c8645640 fffff801`3e83a69e : ffffb800`39be6240 00000000`00000000 ffffce0d`c8645b20 ffffb800`39be3180 : tcpip!TcpPeriodicTimeoutHandler+0x3f7ffffce0d`c8645860 fffff801`3e839984 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30effffce0d`c86459d0 fffff801`3e9e158e : 00000000`00000000 ffffb800`39be3180 ffffb800`39bee140 ffff890e`c91dc080 : nt!KiRetireDpcList+0x1f4ffffce0d`c8645c60 00000000`00000000 : ffffce0d`c8646000 ffffce0d`c8640000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9eSYMBOL_NAME: tcpip!TcpProcessExpiredTcbTimers+3c5MODULE_NAME: tcpipIMAGE_NAME: tcpip.sysIMAGE_VERSION: 10.0.19041.264STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 3c5FAILURE_BUCKET_ID: 0x133_DPC_tcpip!TcpProcessExpiredTcbTimersOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {b2c048e2-40cc-72ec-1f4e-be3c621268dd}Followup: MachineOwner---------

2 crash from 12 july

Microsoft R Windows Debugger Version 10.0.20153.1000 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [E:\Mes Documents\Downloads\071220-8078-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 SingleUserTS PersonalEdition build lab: 19041.1.amd64fre.vb_release.191206-1406Machine Name:Kernel base = 0xfffff804`63400000 PsLoadedModuleList = 0xfffff804`6402a2b0Debug session time: Sun Jul 12 16:22:23.560 2020 UTC + 2:00System Uptime: 0 days 7:00:32.390Loading Kernel Symbols.........................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list..........For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff804`637dda20 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffe200`66b7fe20=00000000000001332: 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: fffff804640fa318, 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 ****** ******************************************************************************* WARNING: Unable to verify checksum for win32k.sysKEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 6077 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on PC-NEXTGEN Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 9840 Key : Analysis.Memory.CommitPeak.Mb Value: 96 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: 0BUGCHECK_P2: 501BUGCHECK_P3: 500BUGCHECK_P4: fffff804640fa318DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDEDTRAP_FRAME: fffff983a1637390 -- .trap 0xfffff983a1637390NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=ffff940defb76501 rbx=0000000000000000 rcx=ffff940defb76000rdx=000000000180b674 rsi=0000000000000000 rdi=0000000000000000rip=fffff804668d33c4 rsp=fffff983a1637528 rbp=fffff983a16375d9 r8=0000000000000000 r9=0000000000000006 r10=000000000000003fr11=0000000000000000 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei pl zr na po ncNETIO!RtlGetNextExpiredTimerWheelEntry+0x14:fffff804`668d33c4 488bc2 mov rax,rdxResetting default scopeBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemSTACK_TEXT: ffffe200`66b7fe18 fffff804`638593ee : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckExffffe200`66b7fe20 fffff804`636ca2ed : 00004b98`3f37a64e 00000000`00000000 fffff983`a1637400 ffffe200`66b29180 : nt!KeAccumulateTicks+0x18bf6effffe200`66b7fe80 fffff804`636ca16a : ffff940d`ef0a70e0 fffff983`a1637410 fffff983`0018a419 00000000`00000000 : nt!KeClockInterruptNotify+0xbdffffe200`66b7ff30 fffff804`63608705 : ffff940d`ef0a70e0 00000000`00000000 00000000`00000000 ffffcce7`6bca892b : nt!HalpTimerClockIpiRoutine+0x1affffe200`66b7ff60 fffff804`637df4ca : fffff983`a1637410 ffff940d`ef0a70e0 00000000`00000200 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5ffffe200`66b7ffb0 fffff804`637dfa37 : ffff940d`00000000 00001f80`007d0244 00000000`81000010 ffffe200`66b29180 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfafffff983`a1637390 fffff804`668d33c4 : fffff804`669fa018 ffff940d`ef091050 fffff780`00000008 00000000`02f1aa6a : nt!KiInterruptDispatchNoLockNoEtw+0x37fffff983`a1637528 fffff804`669fa018 : ffff940d`ef091050 fffff780`00000008 00000000`02f1aa6a fffff804`63400000 : NETIO!RtlGetNextExpiredTimerWheelEntry+0x14fffff983`a1637530 fffff804`669f84d7 : 00000000`00000000 00000000`00989680 00000000`00000002 0000003a`b3c12118 : tcpip!TcpProcessExpiredTcbTimers+0x408fffff983`a1637640 fffff804`6363a69e : ffffe200`66b2c240 00000000`00000000 fffff983`a1637b20 ffffe200`66b29180 : tcpip!TcpPeriodicTimeoutHandler+0x3f7fffff983`a1637860 fffff804`63639984 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30efffff983`a16379d0 fffff804`637e158e : 00000000`00000000 ffffe200`66b29180 ffffe200`66b34140 ffff940d`fc499080 : nt!KiRetireDpcList+0x1f4fffff983`a1637c60 00000000`00000000 : fffff983`a1638000 fffff983`a1632000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9eSYMBOL_NAME: NETIO!RtlGetNextExpiredTimerWheelEntry+14MODULE_NAME: NETIOIMAGE_NAME: NETIO.SYSIMAGE_VERSION: 10.0.19041.208STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 14FAILURE_BUCKET_ID: 0x133_DPC_NETIO!RtlGetNextExpiredTimerWheelEntryOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {8e9233be-ae85-3ff1-48dc-2cfd1ffc6d4d}Followup: MachineOwner---------


3 crash from 14 july


Microsoft R Windows Debugger Version 10.0.20153.1000 AMD64

Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [E:\Mes Documents\Downloads\071420-7687-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 SingleUserTS PersonalEdition build lab: 19041.1.amd64fre.vb_release.191206-1406Machine Name:Kernel base = 0xfffff804`51800000 PsLoadedModuleList = 0xfffff804`5242a2b0Debug session time: Tue Jul 14 16:15:36.795 2020 UTC + 2:00System Uptime: 0 days 7:30:33.484Loading Kernel Symbols.........................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list.........For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff804`51bdda20 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffc581`1adfce20=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: fffff804524fa318, 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: 5734 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on PC-NEXTGEN Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 7468 Key : Analysis.Memory.CommitPeak.Mb Value: 84 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: 0BUGCHECK_P2: 501BUGCHECK_P3: 500BUGCHECK_P4: fffff804524fa318DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDEDTRAP_FRAME: fffffc8e77c4c6f0 -- .trap 0xfffffc8e77c4c6f0NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=ffff9b0a37da1410 rbx=0000000000000000 rcx=ffff9b0a2bf7c000rdx=00000000019c31ec rsi=0000000000000000 rdi=0000000000000000rip=fffff80457bfa113 rsp=fffffc8e77c4c880 rbp=fffffc8e77c4c929 r8=ffff9b0a37da1410 r9=0000000000000000 r10=000000000000003fr11=ffff9b0a2bf7c458 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei pl nz na po nctcpip!TcpProcessExpiredTcbTimers+0x503:fffff804`57bfa113 e909ffffff jmp tcpip!TcpProcessExpiredTcbTimers+0x411 fffff804`57bfa021Resetting default scopeBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: Kingmaker.exeDPC_STACK_BASE: FFFFFC8E77C4CFB0STACK_TEXT: ffffc581`1adfce18 fffff804`51c593ee : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckExffffc581`1adfce20 fffff804`51aca2ed : 000050fd`04987dd0 00000000`00000000 fffffc8e`77c4c700 ffffc581`1ade3180 : nt!KeAccumulateTicks+0x18bf6effffc581`1adfce80 fffff804`51aca16a : ffff9b0a`2b482d40 fffffc8e`77c4c770 00000000`001a665f 00000174`00000000 : nt!KeClockInterruptNotify+0xbdffffc581`1adfcf30 fffff804`51a08705 : ffff9b0a`2b482d40 00000000`00000000 00000000`00000000 ffff8796`a99a70f9 : nt!HalpTimerClockIpiRoutine+0x1affffc581`1adfcf60 fffff804`51bdf4ca : fffffc8e`77c4c770 ffff9b0a`2b482d40 00000000`00000200 662a6465`d977020e : nt!KiCallInterruptServiceRoutine+0xa5ffffc581`1adfcfb0 fffff804`51bdfa37 : 00000000`00000006 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfafffffc8e`77c4c6f0 fffff804`57bfa113 : ffff9b0a`2b490d00 fffff780`00000008 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37fffffc8e`77c4c880 fffff804`57bf84d7 : 00000000`00000000 00000000`00989680 00000000`00000003 0000003e`e549bd6e : tcpip!TcpProcessExpiredTcbTimers+0x503fffffc8e`77c4c990 fffff804`51a3a69e : ffffc581`1ade6240 00000000`00000000 fffffc8e`77c4ce70 ffffc581`1ade3180 : tcpip!TcpPeriodicTimeoutHandler+0x3f7fffffc8e`77c4cbb0 fffff804`51a39984 : ffffc581`1ade3180 60e73abd`00000000 00000000`00000002 00000000`00000004 : nt!KiExecuteAllDpcs+0x30efffffc8e`77c4cd20 fffff804`51be4a65 : 9a65ef35`b0e0506e ffffc581`1ade3180 00000000`00000000 00000174`857ad050 : nt!KiRetireDpcList+0x1f4fffffc8e`77c4cfb0 fffff804`51be4850 : 00000000`00000000 fffffc8e`78bdaad0 00000000`00000004 ffffbe99`cbf81489 : nt!KxRetireDpcList+0x5fffffc8e`78bdaad0 fffff804`51be3f1e : 00000000`00006fcb 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinuefffffc8e`78bdab00 00007ff9`2306330d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x2ee0000006b`227ffa60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`2306330dSYMBOL_NAME: tcpip!TcpProcessExpiredTcbTimers+503MODULE_NAME: tcpipIMAGE_NAME: tcpip.sysIMAGE_VERSION: 10.0.19041.264STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 503FAILURE_BUCKET_ID: 0x133_DPC_tcpip!TcpProcessExpiredTcbTimersOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {b2c048e2-40cc-72ec-1f4e-be3c621268dd}Followup: MachineOwner---------


4 4th crash from 15 july:





Microsoft R Windows Debugger Version 10.0.20153.1000 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [E:\Mes Documents\Downloads\071520-7234-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: srv*Executable search path is: Windows 10 Kernel Version 19041 MP 4 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalEdition build lab: 19041.1.amd64fre.vb_release.191206-1406Machine Name:Kernel base = 0xfffff800`33800000 PsLoadedModuleList = 0xfffff800`3442a2b0Debug session time: Wed Jul 15 08:12:46.685 2020 UTC + 2:00System Uptime: 0 days 0:59:10.141Loading Kernel Symbols.......................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list........For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff800`33bdda20 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffcd80`76bfce20=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: fffff800344fa318, 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 ****** ******************************************************************************* WARNING: Unable to verify checksum for win32k.sysKEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 7327 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on PC-NEXTGEN Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 44757 Key : Analysis.Memory.CommitPeak.Mb Value: 97 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: 0BUGCHECK_P2: 501BUGCHECK_P3: 500BUGCHECK_P4: fffff800344fa318DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDEDTRAP_FRAME: fffff484e6e45370 -- .trap 0xfffff484e6e45370NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000081000010 rbx=0000000000000000 rcx=ffffcd8076be3180rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000rip=fffff80033b12117 rsp=fffff484e6e45500 rbp=fffff484e6e455d9 r8=ffffba8fcf3abfa0 r9=0000000000000000 r10=fffff80033b120d0r11=ffffba8fc437c398 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei pl zr na po ncnt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x47:fffff800`33b12117 4885d2 test rdx,rdxResetting default scopeBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemSTACK_TEXT: ffffcd80`76bfce18 fffff800`33c593ee : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckExffffcd80`76bfce20 fffff800`33aca2ed : 00000aaa`8eaa0031 00000000`00000000 fffff484`e6e45300 ffffcd80`76be3180 : nt!KeAccumulateTicks+0x18bf6effffcd80`76bfce80 fffff800`33aca16a : ffffba8f`c2883d40 fffff484`e6e453f0 fffff484`00037789 00000000`00000000 : nt!KeClockInterruptNotify+0xbdffffcd80`76bfcf30 fffff800`33a08705 : ffffba8f`c2883d40 00000000`00000000 00000000`00000000 ffffb6e1`240bd679 : nt!HalpTimerClockIpiRoutine+0x1affffcd80`76bfcf60 fffff800`33bdf4ca : fffff484`e6e453f0 ffffba8f`c2883d40 00000000`00000200 bba84759`afbb88af : nt!KiCallInterruptServiceRoutine+0xa5ffffcd80`76bfcfb0 fffff800`33bdfa37 : 00000000`00000000 00000000`00000000 ffffba8f`c2890220 fffff800`33bdfa44 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfafffff484`e6e45370 fffff800`33b12117 : ffffffff`ffffffd2 fffff800`361fa113 00000000`00000010 00000000`00000206 : nt!KiInterruptDispatchNoLockNoEtw+0x37fffff484`e6e45500 fffff800`361f9fd5 : ffffba8f`c2890220 fffff780`00000008 00000000`00000000 fffff800`33800000 : nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x47fffff484`e6e45530 fffff800`361f84d7 : 00000000`00000000 00000000`00989680 00000000`00000003 00000008`381f70c3 : tcpip!TcpProcessExpiredTcbTimers+0x3c5fffff484`e6e45640 fffff800`33a3a69e : ffffcd80`76be6240 00000000`00000000 fffff484`e6e45b20 ffffcd80`76be3180 : tcpip!TcpPeriodicTimeoutHandler+0x3f7fffff484`e6e45860 fffff800`33a39984 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30efffff484`e6e459d0 fffff800`33be158e : 00000000`00000000 ffffcd80`76be3180 00000000`00000000 ffffcd80`76bee140 : nt!KiRetireDpcList+0x1f4fffff484`e6e45c60 00000000`00000000 : fffff484`e6e46000 fffff484`e6e40000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9eSYMBOL_NAME: tcpip!TcpProcessExpiredTcbTimers+3c5MODULE_NAME: tcpipIMAGE_NAME: tcpip.sysIMAGE_VERSION: 10.0.19041.264STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 3c5FAILURE_BUCKET_ID: 0x133_DPC_tcpip!TcpProcessExpiredTcbTimersOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10

Microsoft R Windows Debugger Version 10.0.20153.1000 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [E:\Mes Documents\Downloads\071820-11156-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 SingleUserTS PersonalMachine Name:Kernel base = 0xfffff800`3ac00000 PsLoadedModuleList = 0xfffff800`3b82a310Debug session time: Sat Jul 18 17:35:32.581 2020 UTC + 2:00System Uptime: 0 days 11:02:39.953Loading Kernel Symbols.........................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list.........For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff800`3afddb60 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8a81`96075e20=0000000000000133

FAILURE_ID_HASH: {b2c048e2-40cc-72ec-1f4e-be3c621268dd}Followup: MachineOwner

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


5 Last crash from today:



Microsoft R Windows Debugger Version 10.0.20153.1000 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [E:\Mes Documents\Downloads\071820-11156-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 SingleUserTS PersonalMachine Name:Kernel base = 0xfffff800`3ac00000 PsLoadedModuleList = 0xfffff800`3b82a310Debug session time: Sat Jul 18 17:35:32.581 2020 UTC + 2:00System Uptime: 0 days 11:02:39.953Loading Kernel Symbols.........................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list.........For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff800`3afddb60 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8a81`96075e20=00000000000001331: 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: fffff8003b8fa318, 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: 3608 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on PC-NEXTGEN Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 5890 Key : Analysis.Memory.CommitPeak.Mb Value: 84 Key : Analysis.System Value: CreateObject Key : Dump.Attributes.InsufficientDumpfileSize Value: 1 Key : Dump.Attributes.RequiredDumpfileSize Value: 0x4e3f6617ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1DUMP_FILE_ATTRIBUTES: 0xc Insufficient Dumpfile Size Kernel Generated Triage DumpBUGCHECK_CODE: 133BUGCHECK_P1: 0BUGCHECK_P2: 501BUGCHECK_P3: 500BUGCHECK_P4: fffff8003b8fa318DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDEDBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemSTACK_TEXT: ffff8a81`96075e18 fffff800`3b0594e6 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckExffff8a81`96075e20 fffff800`3aeca30d : 00007718`ee3fd958 00000000`00000000 ffffc881`72029300 ffff8a81`96080180 : nt!KeAccumulateTicks+0x18c046ffff8a81`96075e80 fffff800`3aeca18a : ffffd982`b7e7a480 ffffc881`720293f0 ffffc881`0026d3fd 00000000`00000000 : nt!KeClockInterruptNotify+0xbdffff8a81`96075f30 fffff800`3ae08725 : ffffd982`b7e7a480 00000000`00000000 00000000`00000000 ffff2b57`c8669a91 : nt!HalpTimerClockIpiRoutine+0x1affff8a81`96075f60 fffff800`3afdf60a : ffffc881`720293f0 ffffd982`b7e7a480 00000000`00000200 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5ffff8a81`96075fb0 fffff800`3afdfb77 : 00000000`00000000 ffffd982`b897ba00 00000000`025e62bf fffff800`3afdfb84 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfaffffc881`72029370 fffff800`3aed02e6 : 00000000`00000010 00000000`00000212 ffffc881`72029528 00000000`00000018 : nt!KiInterruptDispatchNoLockNoEtw+0x37ffffc881`72029500 fffff800`3e139d17 : fffff780`00000008 fffff780`00000008 ffff8a81`967bc148 fffff800`3af8d301 : nt!KeAcquireSpinLockAtDpcLevel+0x36ffffc881`72029530 fffff800`3e1384d7 : 00000000`00000000 00000000`00989680 00000000`00000001 0000005c`86daaa2d : tcpip!TcpProcessExpiredTcbTimers+0x107ffffc881`72029640 fffff800`3ae3a6be : ffff8a81`96083240 00000000`00000000 ffffc881`72029b20 ffff8a81`96080180 : tcpip!TcpPeriodicTimeoutHandler+0x3f7ffffc881`72029860 fffff800`3ae399a4 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30effffc881`720299d0 fffff800`3afe16ce : 00000000`00000000 ffff8a81`96080180 ffff8a81`9608b140 ffffd982`c742f080 : nt!KiRetireDpcList+0x1f4ffffc881`72029c60 00000000`00000000 : ffffc881`7202a000 ffffc881`72024000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9eSYMBOL_NAME: tcpip!TcpProcessExpiredTcbTimers+107MODULE_NAME: tcpipIMAGE_NAME: tcpip.sysIMAGE_VERSION: 10.0.19041.264STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 107FAILURE_BUCKET_ID: 0x133_DPC_tcpip!TcpProcessExpiredTcbTimersOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {b2c048e2-40cc-72ec-1f4e-be3c621268dd}Followup: MachineOwner---------



Same here but from program "whocrashed":


Crash Dump Analysis


Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Sat 18-07-20 17:35:32 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\071820-11156-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3DDB60
Bugcheck code: 0x133 0x0, 0x501, 0x500, 0xFFFFF8003B8FA318
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 15-07-20 21:18:32 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\071520-7500-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3DDB60
Bugcheck code: 0x133 0x0, 0x501, 0x500, 0xFFFFF805192FA318
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 15-07-20 08:12:46 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\071520-7234-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3DDA20
Bugcheck code: 0x133 0x0, 0x501, 0x500, 0xFFFFF800344FA318
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 14-07-20 16:15:36 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\071420-7687-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3DDA20
Bugcheck code: 0x133 0x0, 0x501, 0x500, 0xFFFFF804524FA318
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 12-07-20 16:22:23 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\071220-8078-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3DDA20
Bugcheck code: 0x133 0x0, 0x501, 0x500, 0xFFFFF804640FA318
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 10-07-20 09:47:47 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\071020-7093-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3DDA20
Bugcheck code: 0x133 0x0, 0x501, 0x500, 0xFFFFF8013F2FA318
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



Currently the crash are "rare" but annoying still. They don't prevent me to use my computer, but they disrupt the workflow.


F Can someone help me?


I also posted this in french but after 3 days no answer so after a crash today I tried this in english to have more people looking for it, I hope

:)

 

BSOD- DPC Watchdog violation

BSOD - DPC watchdog violation how to fix?

 

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:

https://usefulpcguide.com/17082/dpc-watchdog-violation/

 

Help! Watchdog Violation

More info on that BSOD

How to Fix DPC_Watchdog_Violation Blue Screen error