Windows 10: DPC_WATCHDOG_VIOLATION and IRQL_NOT_LESS_OR_EQUAL BSOD FIX

Hello Microsoft Community, I recently had a problem with my computer, it was crashing a whole bunch with two unique errors, those errors are DPC_WATCHDOG_VIOLATION and IRQL_NOT_LESS_OR_EQUAL. I have looked into the crash reports (mini dump files) and found out a file named ntoskrnl.exe was what crashed for the watchdog error. The other crash report talked about a file named netwtw04.sys. The crash report was talking about a driver that was causing the issue. I then opened Device Manager and found the driver that it was referencing. The driver is Intel® Dual Band Wireless-AC 3168, it was outdated, so I updated the driver and no crashes so far after the driver update.


The computer that I was having these issues with is Rhodium Desktop AMD Ryzen 3, Nvidia GeForce GTX 1050. The manufacturer is CybertronPC.


If you are having these issues are similar, I recommend to update your Network Adapters. Hope this helps!

:)

 

BSOD DPC_WATCHDOG_VIOLATION, IRQL_NOT_LESS_OR_EQUAL

Crash dumps are enabled on your computer.

On Sun 1/3/2016 6:16:56 PM GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\010416-19859-01.dmp

This was probably caused by the following module: hal.sys (hal+0x88B3)

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

Error: DPC_WATCHDOG_VIOLATION

Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a 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: hal.sys .

Google query: hal.sys DPC_WATCHDOG_VIOLATION

On Sun 1/3/2016 6:16:56 PM GMT your computer crashed

crash dump file: C:\WINDOWS\memory.dmp

This was probably caused by the following module: hal.sys (hal+0x88B3)

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

Error: DPC_WATCHDOG_VIOLATION

Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a 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: hal.sys .

Google query: hal.sys DPC_WATCHDOG_VIOLATION

On Sun 1/3/2016 4:33:48 PM GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\010316-23281-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x127C80)

Bugcheck code: 0xA (0x14, 0xFF, 0x0, 0xFFFFFFFF820D251D)

Error: IRQL_NOT_LESS_OR_EQUAL

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

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

 

IRQL_Not_Less_Or_Equal

sigh
If your computer auto restarts on BSOD find the setting in windows to make it stop.
Second step is to look for the error code of the BSOD.
Perhaps easier would be to use an online application such as bluescreen viewer.
Once you know which driver is causing the problem you can look further into fixing it.

 

Windows 10 build 10586 BSOD DPC_WATCHDOG_VIOLATION

Check (enable) it then do Step #5 & test.

The above notwithstanding...

Are you still getting the DPC_WATCHDOG_VIOLATION BSODs or...?