Sorry for the issue.
We just released GlassWire 2.3. Please try it and let me know if it solves the issue.
Also, these behaviors are often caused by GlassWire database corruptions. Please try going to add/remove programs and uninstalling GlassWire, then reinstalling with “clean install” checked (if it’s not a major problem to lose your history/settings) and it may solve the issue permanently.
OK, I did a clean install of the 2.3 version, and so far so good…
powerBI is up and running. I will try on my laptop too.
Thanks
Regards
I hope it continues to work OK. If not, you should see a .dmp file on your desktop related to GlassWire. Please email it to us using a cloud service.
https://www.glasswire.com/contact/
It might help us find and solve the issue.
Hi,
It is starting to do it again :
On Fri 02/07/2021 17:03:02 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070221-10125-01.dmp
This was probably caused by the following module: [ntoskrnl.exe]
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8066F4FB320)
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 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).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 02/07/2021 17:03:02 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]
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8066F4FB320)
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 using 2.3.323 version of Glasswire and my Windows is full updated.
I have no termal issues !
It is still happening when using PowerBI.
Thanks for your support
Regards,
F.
Thanks for your report. We will try to reproduce this issue and fix it and I apologize for the problem.
Hi,
It did it again, when using PowerBi :
On Wed 17/11/2021 11:22:54 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, 0xFFFFF8073D505330)
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()
My computer :
Computer name: XXXXXXX
Windows version: Windows 11, version 21H2, build: 22000.318
Windows dir: C:\WINDOWS
Hardware: XPS 13 9300, Dell Inc., 077Y9N
CPU: GenuineIntel Intel(R) Core™ i7-1065G7 CPU @ 1.30GHz 8664, level: 6
8 logical processors, active mask: 255
RAM: 16737030144 bytes (15,6GB)
Glasswire version : 2.3.363
Happen twice since I installed the new version :
On Wed 17/11/2021 16:58: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
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF80412D05330)
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 see you use a third party uninstaller, I think you sent a screenshot? Or was that someone else? Third party uninstallers often cause this issue.
It’s possible our driver is still installed and was never properly installed due to the third party uninstaller.
Nope, I do not have a third party uninstaller. The information I sent you was from WhoCrashed, which is a crash dump analyzer (very usefull to understand why you may have a BSOD, which is what happen to me when using GlassWire with PowerBI, both fully updated).
I just download the latest version available on your website, and during the installation process, it will automatically uninstall the previous version).
Sorry for the issue. Are you seeing a .dmp file on your desktop? If so, could you email it to us and include in the email that you’re sending the latest version?
Here is the dump file I get when getting watchdog violations using glasswire:
Microsoft (R) Windows Debugger Version 10.0.22549.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\050822-12218-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff80067400000 PsLoadedModuleList = 0xfffff8006802a290
Debug session time: Sun May 8 22:31:05.095 2022 (UTC - 7:00)
System Uptime: 0 days 0:05:59.812
Loading Kernel Symbols
…
…
…
…
Loading User Symbols
Loading unloaded module list
…
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800677f7d50 48894c2408 mov qword ptr [rsp+8],rcx ss:fffff8006ba2ee20=0000000000000133
0: kd> !analyze -v
*
Bugcheck Analysis *
*
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff800680fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn’t have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing “.symopt- 100”. Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: TickPeriods ***
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 5546
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 27468
Key : Analysis.Init.CPU.mSec
Value: 749
Key : Analysis.Init.Elapsed.mSec
Value: 40682
Key : Analysis.Memory.CommitPeak.Mb
Value: 95
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
FILE_IN_CAB: 050822-12218-01.dmp
BUGCHECK_CODE: 133
BUGCHECK_P1: 0
BUGCHECK_P2: 501
BUGCHECK_P3: 500
BUGCHECK_P4: fffff800680fb320
DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
TRAP_FRAME: fffff8006ba246d0 – (.trap 0xfffff8006ba246d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8d982d7e000 rbx=0000000000000000 rcx=fffff8006ba24bd0
rdx=fffff8fc6cc16bf0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800676a60ce rsp=fffff8006ba24860 rbp=0000000000000001
r8=0000000000000001 r9=0000000000000000 r10=0000000000000000
r11=fffff88000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac pe cy
nt!MiComputePxeWalkAction+0x1e:
fffff800676a60ce 4c89642458 mov qword ptr [rsp+58h],r12 ss:fffff8006ba248b8=0000000000000001
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: ChaosGate.exe
STACK_TEXT:
fffff8006ba24860 fffff800676a5b8f : 0000000000000001 0000000000000001 0000000000000000 0000000000000000 : nt!MiComputePxeWalkAction+0x1e
fffff8006ba248b0 fffff800676a5c8b : fffff8fc00000000 fffff8006804f480 0000000000000001 fffff8006ba24c30 : nt!MiWalkPageTablesRecursively+0x78f
fffff8006ba24950 fffff800676a5c8b : fffff8fc7e366000 fffff8006804f480 0000000000000002 fffff8006ba24c40 : nt!MiWalkPageTablesRecursively+0x88b
fffff8006ba249f0 fffff8006763f18b : 0000000000000000 fffff8006804f480 0000000000000003 fffff8006ba24c50 : nt!MiWalkPageTablesRecursively+0x88b
fffff8006ba24a90 fffff8006760673f : fffff8006ba24bd0 0000000000000000 0000000000000002 fffff8fc00000000 : nt!MiWalkPageTables+0x36b
fffff8006ba24b90 fffff80067608e5e : ffffb303d86b3e60 ffffb303d86b3e78 0000000000007200 0000000000000000 : nt!MiClearNonPagedPtes+0x277
fffff8006ba24dc0 fffff80067608c82 : ffffb303d86b3e40 fffff80068054658 0000000000001002 fffff80068054ef8 : nt!MmFreePoolMemory+0x1aa
fffff8006ba24e40 fffff80067712788 : ffffb303d86b3e40 fffff80068054658 0000000000001002 000000033059f200 : nt!RtlpHpEnvFreeVA+0x12
fffff8006ba24e70 fffff8006771263a : 0000000100200000 ffffb3059f200000 0000000100000001 0000000000000000 : nt!RtlpHpVaMgrRangeFree+0x54
fffff8006ba24ea0 fffff80067608c66 : ffffb30472c00000 ffffb30472a8d4a0 0000000000000000 0000000000000001 : nt!RtlpHpVaMgrCtxFree+0x6a
fffff8006ba24f00 fffff8006786adb7 : 0000000000000000 fffff8006ba25040 ffffb30472c00000 0000000000000000 : nt!RtlpHpFreeVA+0x8a
fffff8006ba24f40 fffff8006764bd8f : 0000000000100000 0000000100000000 0000000100000000 ffffffff00000000 : nt!RtlpHpLargeAlloc+0x15963b
fffff8006ba250b0 fffff80067db2094 : ffffb30400000000 0000000000000001 ffffb30444435747 ffffb30472b74a90 : nt!ExAllocateHeapPool+0xb0f
fffff8006ba251f0 fffff80080a1424e : ffffb30472b90390 ffffb30472b74a90 ffffb3049802bb20 ffffb30400000000 : nt!ExAllocatePoolWithTag+0x64
fffff8006ba25240 ffffb30472b90390 : ffffb30472b74a90 ffffb3049802bb20 ffffb30400000000 0000000000000000 : gwdrv+0x424e
fffff8006ba25248 ffffb30472b74a90 : ffffb3049802bb20 ffffb30400000000 0000000000000000 fffff80080a125b7 : 0xffffb30472b90390 fffff8006ba25250 ffffb3049802bb20 : ffffb30400000000 0000000000000000 fffff80080a125b7 ffffb30472ba4560 : 0xffffb30472b74a90
fffff8006ba25258 ffffb30400000000 : 0000000000000000 fffff80080a125b7 ffffb30472ba4560 ffffb3049802bb20 : 0xffffb3049802bb20 fffff8006ba25260 0000000000000000 : fffff80080a125b7 ffffb30472ba4560 ffffb3049802bb20 ffffb3049802bb20 : 0xffffb30400000000
STACK_COMMAND: .trap 0xfffff8006ba246d0 ; kb
SYMBOL_NAME: gwdrv+424e
MODULE_NAME: gwdrv
IMAGE_NAME: gwdrv.sys
BUCKET_ID_FUNC_OFFSET: 424e
FAILURE_BUCKET_ID: 0x133_DPC_gwdrv!unknown_function
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {229a5753-87e5-3d87-e2b9-50836a10c652}
Hi ，The issue has reoccurred on Windows 10 22H2, and I can provide log files. I am using GlassWire version 3.3.504, which is a great software that I really like. Microsoft’s solution was to uninstall the software. Have you fixed this issue?
These are some excerpts：
SYMBOL_NAME: gwdrv+424e
MODULE_NAME: gwdrv
IMAGE_NAME: gwdrv.sys
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 424e
FAILURE_BUCKET_ID: 0x133_DPC_gwdrv!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {229a5753-87e5-3d87-e2b9-50836a10c652}
You can dowload in here
I am a new user and I am unable to share my link.
All you can give me email i send it to you
Hi @Megumi_Lan
I apologize for the inconvenience. The DPC_WATCHDOG_VIOLATION error typically indicates a problem with a driver or hardware component. Try updating GW and system drivers. Even though you mentioned your drivers are fully updated, it’s worth double-checking. Visit your computer manufacturer’s website or the individual hardware component manufacturers’ websites to ensure you have the latest drivers installed for all your devices, including network adapter, motherboard chipset, and graphics card drivers. Also, please note, as a temporary troubleshooting step, try disabling/uninstalling GW to see if the error continues to exist. If the error doesn’t occur without GW, it could indicate an incompatibility issue between your system and GW. Throughout this process, PLEASE REMEMBER to create a backup of your important data before making any changes to your system. This will help ensure that your data remains safe throughout the troubleshooting process.
Best,
Katie
Can providing the corresponding diary files be helpful in solving this problem？
I haven’t encountered similar problems since I closed GlassWire.
To resolve this issue, it is recommended to update the gwdrv.sys driver from SecureMix LLC, the company behind GlassWire. It’s possible that an updated version of the driver is available, which may contain bug fixes or improvements to prevent this error from occurring.
I understand that you mentioned your Windows 10 operating system is fully updated, and all your drivers are up to date as well. However, it’s still worth checking for any updates specifically for the gwdrv.sys driver. You can visit the official website of GlassWire or SecureMix LLC to see if they have released any driver updates.