BSOD on gwdrv.sys when using Driver Verifier tool by Microosft

Hi, I’m trying to figure out some driver related conflicts and malfunctions in my Windows 10 (1703 Build 15063.138) PC and so as recommended by Microsoft I used the built-in tool called Driver Verfier.

So I configure the verfier tool and restart my machine and right when windows logo shows up, BOOM!! BSOD saying DRIVER_VERIFIER_DETECTED_VIOLATION. Then I went and looked into the dump file (attached) created by this verifier tool, in order to analyze it, and this came up:

STACK_COMMAND: kb
FOLLOWUP_IP:
gwdrv+1d25
fffff80c`552e1d25 488bd0 mov rdx,rax
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: gwdrv+1d25
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: gwdrv
IMAGE_NAME: gwdrv.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5567e7ec
FAILURE_BUCKET_ID: X64_0xc4_2000_VRF_gwdrv+1d25
BUCKET_ID: X64_0xc4_2000_VRF_gwdrv+1d25
Followup: MachineOwner

Any idea why should this be happening? Is there something out of ordinary with the GlassWire driver component?

Helps are greatly appreciated.

@sa3er

Our drivers were tested with the driver verifier tool under strict conditions years ago, and with new updates. Please email us your crash dump using a cloud service https://www.glasswire.com/contact/ to our “bugs” email.

1 Like