GLASSWIRE and WATCHDOG VIOLATION

Hi,
Glasswire driver (gwdrv) create a BSOD with this error message DPC_WATCHDOG_VIOLATION.
Here the message from WhoCrashed :slight_smile:

On Tue 24/07/2018 11:59:22 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: gwdrv.sys (gwdrv+0x424e)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8030B279378)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\drivers\gwdrv.sys
product: GlassWire
company: SecureMix LLC
description: GlassWire Driver
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: gwdrv.sys (GlassWire Driver, SecureMix LLC).
Google query: gwdrv.sys SecureMix LLC DPC_WATCHDOG_VIOLATION

I am on Windows 10, which is fully updated, all my drivers are completely updated to, and also, no thermal issu (never above 50°)
Thanks for your support.
Regards

@fdecourt

If you go to the top left GlassWire menu and choose “About” what version does it show? Thanks.

Hi,
I have version 2.0.123

Did you get a .dmp file on your desktop after you crashed @fdecourt? If not it’s probably not GlassWire that caused the problem.

If you do have a .dmp please email it to https://www.glasswire.com/contact/ using a cloud service like Dropbox, etc…

Not sure if I should bring up a dead post or start a new one, but I’ve had this similar issue recently with the newer builds of glasswire. I would get BSODs with DPC_WATCHDOG_VIOLATION on my surface pro 5.

The dump shows very similar to above, gwdrv.sys causing the issue. I love glasswire, but after numerous BSODs at random points (after hibernation, just working, after a fresh start, etc). i uninstalled it and have gone about 5 days so far without the DPC BSOD (or any BSOD). after usual usage.

Not sure if others are having this issue still, but I had to uninstall for my sanity. I hope maybe there is a cause or fix to get this working again.

@unreal

We very recently released an update of GlassWire. If you go to our top left menu and choose “About” what version do you have?

Also, the most common reason for crashes lately is database corruptions (which is unusual) and the fix is to uninstall GlassWire, reboot, and do a “clean install” option with our installer.

Also for anyone else, if you use Wacom be sure you’re using your latest Wacom drivers. We had another customer with a similar issue and he found it was related to an older Wacom driver, but this won’t apply to everyone of course. I just wanted to post it just in case it’s helpful to someone else reading this.

Well, I could try it again. I had whatever release was in the past 3 weeks. This was a replacement Surface which I’ve had since May 21, 2019. So it was a fresh DB as of then.

Regarding Wacom, that’s interesting. But I don’t believe the Surface uses those drives. I think it has its own pen drivers. everything is up to date though.

I’ll try the newest version and a fresh install again and see how it goes!

@unreal

Please email us the .dmp using a cloud service like Google Drive https://www.glasswire.com/contact/ and we can make suggestions, before you do a clean install.

If you don’t care about your history or settings though, it can’t hurt to do a clean install.

I guess windows deletes dmp files after a while. They seem to be gone. I’ll try fresh and if I get another, I’ll send it on by. Thank you!

@unreal

If GlassWire crashed then it will drop the .dmp to your desktop.