[SOLVED] BSOD: "DPC Watchdog Violation" on two identical laptops ?

TheComputerSaysNo

Commendable
Mar 27, 2019
3
0
1,510
0
I had a dell studio 16. After a month it started giving this "DPC Watchdog Violation" BSOD at random, up to 5 or 6 times a day. There was another issue so Dell replaced it.

Again this system is giving me this error after a few weeks, currently 3 times a day-ish.

I've tried numerous fixes but having no luck. Any ideas how to nail this down as I can't afford to have it randomly crashing ?

Thanks!
 

Colif

Win 11 Master
Moderator
Try updating sound drivers

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .
 
Reactions: Mandark

Colif

Win 11 Master
Moderator
Try updating sound drivers

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .
 
Reactions: Mandark

gardenman

Distinguished
Moderator
Hi, I ran the dump files through the debugger and got the following information: https://jsfiddle.net/2ztd496k/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.
File information:112721-9406-01.dmp (Nov 26 2021 - 23:40:02)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Driver warnings:*** WARNING: Unable to verify timestamp for SmbCo10X64.sys
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 3 Hour(s), 47 Min(s), and 04 Sec(s)

File information:112721-15109-01.dmp (Nov 26 2021 - 19:52:04)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Driver warnings:*** WARNING: Unable to verify timestamp for SmbCo10X64.sys
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 15 Hour(s), 40 Min(s), and 44 Sec(s)

File information:112621-9953-01.dmp (Nov 25 2021 - 22:04:14)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Driver warnings:*** WARNING: Unable to verify timestamp for SmbCo10X64.sys
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 43 Min(s), and 36 Sec(s)

File information:112621-9281-01.dmp (Nov 25 2021 - 21:20:02)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Driver warnings:*** WARNING: Unable to verify timestamp for SmbCo10X64.sys
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 16 Min(s), and 48 Sec(s)

File information:112621-9062-01.dmp (Nov 26 2021 - 01:27:40)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Driver warnings:*** WARNING: Unable to verify timestamp for SmbCo10X64.sys
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 3 Hour(s), 22 Min(s), and 51 Sec(s)
All 5 dumps point to the following driver as being an issue:
Aug 03 2021SmbCo10X64.sysSB Traffic Control Callout driver (Rivet Networks, LLC.)
The description may be incorrect. This might be a "Killer Networking" driver. Or some type of networking driver. Update it if possible.

System: Dell Inspiron 16 7610
BIOS version: 1.1.3 (09/24/2021)
Motherboard: 1J0MWF Version A01
RAM: 16 GB - (2x8) of M471A1G44AB0-CWE
CPU: 11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 

Drew125

Distinguished
Nov 3, 2014
206
10
18,715
11
Your issue is modern sleep (S0) most likey. There are horror stories of dell not working with S0 well. The old sleep S3 shut off and had little power use, but off. S0 puts the pc in a "Low power" State that when input is detected it springs back like your phone. Think of it as a kinda idle state, very low power use but still connected and listening for input. Ive got 2 pcs at work now, Same issue. Its a MS issue with the S0 state and dell. See the link below.

https://www.dell.com/community/XPS/Please-fix-modern-standby-issues/td-p/7738292
 

ASK THE COMMUNITY

TRENDING THREADS