[SOLVED] DPC_Watchdog_Violation Crash Help

Oct 10, 2019
1
0
10
Hi,

I have uploaded my minidump to be viewed

Minidump

My BIOS is up to date along with my Win 10 1903

Could someone please look into this dump?

Thanks,

Dusty
 
Solution
@gardenman

DateDriverDescription
Jan 07 1978bridge.sys
is going to be part of windows, the date is a give away :)

Curious it shows up as it is:
Bridge.sys or also referred to as MAC Bridge Driver, is a driver for Windows, specifically for MAC bridge ports that are installed with the tunneling software for sharing of internet connections, such as WiFi and 3G networks.
https://www.reviversoft.com/processes/bridge.sys
So maybe BSOD is tied into Tunnelbear? See if there is a newer version.

I would remove this
Dec 23 2013SmartDefragDriver.sysSmart Defrag driver (IObit)...

gardenman

Splendid
Moderator
Hi, I ran the dump file through the debugger and got the following information: https://pste.eu/p/mu6C.html

File information:100919-99890-01.dmp (Oct 9 2019 - 22:54:38)
Bugcheck:SYNTHETIC_WATCHDOG_TIMEOUT (1CA)
Probably caused by:ntkrnlmp.exe (Process: System)
Uptime:0 Day(s), 3 Hour(s), 11 Min(s), and 51 Sec(s)

Possible Motherboard page: https://www.gigabyte.com/Motherboard/GA-78LMT-USB3-rev-60#ov
It appears you have the latest BIOS already installed.

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

Colif

Win 11 Master
Moderator
@gardenman

DateDriverDescription
Jan 07 1978bridge.sys
is going to be part of windows, the date is a give away :)

Curious it shows up as it is:
Bridge.sys or also referred to as MAC Bridge Driver, is a driver for Windows, specifically for MAC bridge ports that are installed with the tunneling software for sharing of internet connections, such as WiFi and 3G networks.
https://www.reviversoft.com/processes/bridge.sys
So maybe BSOD is tied into Tunnelbear? See if there is a newer version.

I would remove this
Dec 23 2013SmartDefragDriver.sysSmart Defrag driver (IObit) http://www.iobit.com/


None of the above mentioned in error but all too old for win 10 and may have caused it.
Dump doesn't really point at one in particular

It must be a new BSOD code as I have only seen it twice in recent weeks. Its likely to be a driver causing it.

Do you need both EaseUS & Iobit looking after hdd?
 
Solution