Bluescreen DRIVER_VERIFIER_DETECTED_VIOLATION

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: C:\symbols;SRV*C:\symbols*//http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18933.amd64fre.win7sp1_gdr.150715-0600
Machine Name:
Kernel base = 0xfffff800`0324c000 PsLoadedModuleList = 0xfffff800`03493730
Debug session time: Fri Oct  2 18:12:11.975 2015 (UTC + 2:00)
System Uptime: 0 days 0:18:30.865
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7efdf018).  Type ".hh dbgerr001" for details
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, 394, fffffa800a3c7b10, fffff880089f9154}

*** ERROR: Module load completed but symbols could not be loaded for ENTECH64.sys
Probably caused by : ENTECH64.sys ( ENTECH64+1154 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 0000000000000394, Handle value being referenced.
Arg3: fffffa800a3c7b10, Address of the current process.
Arg4: fffff880089f9154, Address inside the driver that is performing the incorrect reference.

Debugging Details:
------------------


BUGCHECK_STR:  0xc4_f6

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  dllhost.exe

CURRENT_IRQL:  0

DEVICE_OBJECT: 0000000000000004

LAST_CONTROL_TRANSFER:  from fffff800037544ec to fffff800032bf5c0

STACK_TEXT:  
fffff880`082f13b8 fffff800`037544ec : 00000000`000000c4 00000000`000000f6 00000000`00000394 fffffa80`0a3c7b10 : nt!KeBugCheckEx
fffff880`082f13c0 fffff800`03769aa4 : 00000000`00000394 fffffa80`0a3c7b10 00000000`00000002 00000000`00000044 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`082f1400 fffff800`035fe380 : 00000000`00000000 fffff880`082f1630 00000000`00000000 00000000`000f0000 : nt!VfCheckUserHandle+0x1b4
fffff880`082f14e0 fffff800`03598e25 : 00000000`00000000 00000000`000f001f 00000000`00000000 fffff800`00000000 : nt! ?? ::NNGAKEGL::`string'+0x19c6e
fffff880`082f15b0 fffff800`03769838 : 00000000`000f001f 00000000`00000002 fffff880`082f16b0 fffff800`032bae10 : nt!ObReferenceObjectByHandle+0x25
fffff880`082f1600 fffff880`089f9154 : 00000000`fa100000 00000000`00000002 00000000`000f001f 00000000`fa100000 : nt!VerifierObReferenceObjectByHandle+0x48
fffff880`082f1650 fffff880`089f93aa : fffff880`082f1828 fffff800`0375d3d7 00000000`00000018 00000000`00000000 : ENTECH64+0x1154
fffff880`082f1770 fffff800`03770d46 : fffff980`5af3aee0 00000000`00000002 00000000`00000000 00000000`00000028 : ENTECH64+0x13aa
fffff880`082f17b0 fffff800`035c86db : 00000000`00000002 fffffa80`06531f20 00000000`00000001 fffffa80`0678fe00 : nt!IovCallDriver+0x566
fffff880`082f1810 fffff800`035dc477 : 00000000`00000004 00000000`00000000 fffffa80`06531f20 00000000`000003f4 : nt!IopSynchronousServiceTail+0xfb
fffff880`082f1880 fffff800`035dc4e6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0xbe4
fffff880`082f1a00 fffff800`032be853 : 00000000`00000000 fffffa80`0aef9f00 00000000`746c6644 fffff880`082f1af8 : nt!NtDeviceIoControlFile+0x56
fffff880`082f1a70 00000000`73382e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0295ed78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73382e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ENTECH64+1154
fffff880`089f9154 8bf0            mov     esi,eax

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  ENTECH64+1154

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ENTECH64

IMAGE_NAME:  ENTECH64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  40641784

FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_ENTECH64+1154

BUCKET_ID:  X64_0xc4_f6_VRF_ENTECH64+1154

Followup: MachineOwner