Resuming from Win10 Hibernation Can Cause BSOD


#1

I am running GlassWire Free 1.2.118 on Windows 10 version 1607 Build 14393.1770. Periodically, when I awaken my PC from hibernation, I get a BSOD (DPC_WATCHDOG_VIOLATION). I used the WhoCrashed utility to analyze the crash dump files and it implicates both ntoskrnl.exe and gwdrv.sys. Please assist.

Here is the output of the utility:

On Sun 10/22/2017 7:17:49 PM your computer crashed
crash dump file: C:\Windows\Minidump\102217-30609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F790)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF802D1E1A540)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sun 10/22/2017 7:17:49 PM your computer crashed
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, 0xFFFFF802D1E1A540)
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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (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: SecureMix LLC DPC_WATCHDOG_VIOLATION


#2

@HempOil

Sorry for the problem.

Do you have a .dmp file on your desktop? Please email it to us using a cloud type system https://www.glasswire.com/contact/. We can then investigate and fix it.


#3

Thanks for the guidance, Ken. I emailed my crash dump file to the bugs email address (bugsatglasswiredotcom). I eagerly await their feedback.


#4

@HempOil

Our team checked the dmp and they suggested to see if it’s possible to install the latest Windows updates? Is your Windows version up to date, can you check? If not please try the updates and let us know if it solves the problem.


#5

Hi Servo,

I am running Windows 10 Home version 1607, build 14393.1770. When I run Widows Updates, it says there is nothing pending.


#6

OK, let me see if the team has some other ideas. How much memory does that PC have? Thanks.


#7

Great, thank you. My laptop has 16GB of RAM.


#8

I had another BSOD yesterday after resuming from hibernate:

On Thu 11/9/2017 7:12:40 PM your computer crashed
crash dump file: C:\Windows\Minidump\110917-28640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F790)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF802943B7540)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Thu 11/9/2017 7:12:40 PM your computer crashed
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, 0xFFFFF802943B7540)
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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (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: SecureMix LLC DPC_WATCHDOG_VIOLATION


#9

And another one today:

On Sat 11/11/2017 6:23:49 PM your computer crashed
crash dump file: C:\Windows\Minidump\111117-37265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F790)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF80184DB2540)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sat 11/11/2017 6:23:49 PM your computer crashed
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, 0xFFFFF80184DB2540)
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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (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: SecureMix LLC DPC_WATCHDOG_VIOLATION