Windows 10: BSOD: 'DPC_WATCHDOG_VIOLATION' at random times, even when idle

Laptop is a Dell Inspiron 15, the model no. is 3541, with a AMD A6-6310 APU, and 4 GB of DDR3 RAM. Windows 10 x64.

Started getting the BSOD 'DPC_WATCHDOG_VIOLATION' a few weeks ago, and it annoyed me so much I re-installed Windows 10 about 2 weeks ago thinking that would stop the issue. Lo and behold, the issue surfaced while streaming a Youtube video.
I observed it afterwards, and realized it would freeze for a few seconds before the BSOD. I know this because the music would stop, the OS would stop responding to input, then a few seconds later, BSOD.

So far, my rudimentary troubleshooting revealed that the BSOD is being caused by 'hal.dll'...and that's where my expertise has hit a wall. I have no idea what to check next.

I have attached the required zip file for your perusal.
I'd appreciate any assitance in solving this one.

:)

 

BSOD after Creators' Update - DMP files attached

I get random BSODs since the Creators' Update. Sometimes they occur even when my laptop is idle.

I've run Driver Verifier, rebooted and got a BSOD immediately, indicating the culprit is dam.sys

DMP file and MSINFO32 output available at https://infinityqs4-my.sharepoint.c...yqs_com/Documents/bsod-dam.zip?csf=1&e=gXH2A2

 

random Freezing leads to BSOD. I give up.

Stop code is random.

like CRITICAL_PROCESS_DIED, BAD_SYSTEM_CONFIG_INFO, DPC_WATCHDOG_VIOLATION..

I've got multiple BSOD and the stop code is that random.

right now after multiple debugging the issue, I hypothetically assume it's my nvme fault.

I've ordered a new nvme drive and gonna retest the system if this will works.

 

It would be worth looking for an updated driver for your Network Adaptor

Code: ffffdb01`2978f218 fffff800`03469ef0Unable to load image \SystemRoot\System32\drivers\athw10x.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for athw10x.sys *** ERROR: Module load completed but symbols could not be loaded for athw10x.sys athw10x+0x389ef0 0: kd> lmvm athw10x Browse full module list start end module name fffff800`030e0000 fffff800`03512000 athw10x T (no symbols) Loaded symbol image file: athw10x.sys Image path: \SystemRoot\System32\drivers\athw10x.sys Image name: athw10x.sys Browse all global symbols functions data Timestamp: Mon May 18 07:33:25 2015 (555987B5) CheckSum: 0042668C ImageSize: 00432000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]

 

Hmmm... looks like the wifi adapter.
I'll definitely look into that.

 

Installed a newer Dell 1707 WiFi+Bluetooth driver...but it BSOD'ed again while streaming YouTube.

I attached another zip file.
In the meantime, I'm going to look for a newer version of that driver.

 

Tried yet another driver, but I'm still getting BSODs.

Attached the latest crash logs...

 

The latest crash dump shows the same driver with the same date as I posted before. Can you check in device manager to see if you updated the right one? It should be athw10x.sys

 

This 3rd driver package was issued in 2015 .
The 1st two I tried were issued in 2014.

Dell probably used the same file version in the latest driver package.
Unfortunately, there's no newer version available on Dell's website for that device.

So it's that same offending file?

 

My search on athw10x.sys suggests it is a Qualcomm Atheros Network adaptor. Are you changing the right one?

 

Yeah, I did try the Dell 1705, and then two versions of the 1707 driver, which is Wifi+Bluetooth.

I'll try looking for a newer driver on Atheros' website.



EDIT: Found the Dell 1901 driver, that *should* be compatible.

Fingers crossed.

 

So I've left the laptop streaming YouTube for more than 24 hours now and no BSOD...so it seems that updating that wi-fi driver did the trick, but I'm gonna leave it streaming for 48 hrs more. If it passes, then I'll consider this issue solved. *Smile

 

Laptop is still happily streaming away. No BSODs for the last 3 days.

I'm gonna mark this one officially as solved.


Thanks @philc43

 

Well, maybe I spoke too soon. After 6 days without issue, the same BSOD returned in force today... 4 times already. *Sad

*sigh*

Latest dump files attached.

 

Hello again *Smile

Well the same driver file is triggering errors but I can see that it is a different date. See below:

Code: ffffab00`e5461848 fffff80e`a4beb920Unable to load image \SystemRoot\System32\drivers\athw8x.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for athw8x.sys *** ERROR: Module load completed but symbols could not be loaded for athw8x.sys athw8x+0x3eb920 0: kd> lmvm athw8x Browse full module list start end module name fffff80e`a4800000 fffff80e`a4c27000 athw8x T (no symbols) Loaded symbol image file: athw8x.sys Image path: \SystemRoot\System32\drivers\athw8x.sys Image name: athw8x.sys Browse all global symbols functions data Timestamp: Thu Jan 28 09:52:54 2016 (56A9E4F6) CheckSum: 0040EC70 ImageSize: 00427000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote] Looking at your event log it seems that just prior to the first of the new crashes, you ran the network diagnostic troubleshooter a few times. I am wondering if this has reset your network adaptor in some way and caused the crashes to start. You could try and reset your computer to a system restore point just prior to 25th April when this happened.