Windows 10: How to analyze the BugCheck 0x133 DPC_WATCHDOG_VIOLATION

I follow Microsoft debugger learning to get data from BSOD crash minidumpBut it is impossible to know which device caused this BOSD?0: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DPC_WATCHDOG_VIOLATION 133Th

:)

 

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.

 

Bsod: Dpc_watchdog_violation

Sorry, I missed that, however, it's highly likely that W10 has already deleted it so my added comment is useful. Using a full kernel dump is also the only way to obtain information to debug a 0x133 bugcheck with parameter 1 = 1. The OP might not realise that so it is worth highlighting the importance of step 2b.

 

DPC_WATCHDOG_VIOLATION

On Fri 19/06/2020 10:07:05 PM your computer crashed or a problem was reported

crash dump file: C:\Windows\MEMORY.DMP

This was probably caused by the following module: mwac.sys (mwac+0x13a19)

Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)

Error: DPC_WATCHDOG_VIOLATION

file path: C:\Windows\system32\drivers\mwac.sys

product: Malwarebytes Web Protection

company: Malwarebytes

description: Malwarebytes Web Protection

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).

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mwac.sys (Malwarebytes Web Protection, Malwarebytes).

Google query: mwac.sys Malwarebytes DPC_WATCHDOG_VIOLATION