BlueScreen with v5.3.0 on Windows 7 64-bit Ultimate

I've been getting almost daily BSODs using over the last month or so. Running driver verifier caused a blue screen identifying networx.sys as the offending driver. Since removing networx from my system a week ago, the daily blue screens have not returned. Please see debug information below (may not be that helpful as I uninstalled the networx.sys driver, so some information may not be accessible to the debugger).

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


Loading Dump File [C:\Windows\Minidump\042614-51527-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: srv*
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02a4c000 PsLoadedModuleList = 0xfffff800`02c8f6d0
Debug session time: Sat Apr 26 16:12:01.844 2014 (UTC - 4:00)
System Uptime: 0 days 0:01:38.826
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {226, fffff880019f819c, fffff98011092ea0, 0}

Unable to load image \SystemRoot\system32\drivers\networx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for networx.sys
*** ERROR: Module load completed but symbols could not be loaded for networx.sys
Probably caused by : networx.sys ( networx+b19c )

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

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000000000226, An IRP dispatch handler has returned without passing down or completing this IRP,
	or someone forgot to return STATUS_PENDING.
Arg2: fffff880019f819c, The address in the driver's code where the error was detected.
Arg3: fffff98011092ea0, IRP address.
Arg4: 0000000000000000

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


BUGCHECK_STR:  0xc9_226

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  226

FAULTING_IP: 
networx+b19c
fffff880`019f819c 4883ec28        sub     rsp,28h

FOLLOWUP_IP: 
networx+b19c
fffff880`019f819c 4883ec28        sub     rsp,28h

IRP_ADDRESS: fffff98011092ea0

DEVICE_OBJECT: fffffa8005480970

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

LAST_CONTROL_TRANSFER:  from fffff80002f4e4ec to fffff80002ac1bc0

STACK_TEXT:  
fffff880`031aebd8 fffff800`02f4e4ec : 00000000`000000c9 00000000`00000226 fffff880`019f819c fffff980`11092ea0 : nt!KeBugCheckEx
fffff880`031aebe0 fffff800`02f5858a : fffff800`02f4cb00 fffff880`019f819c fffff980`11092ea0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`031aec20 fffff800`02f59593 : 00000000`00000226 fffffa80`06eff3b8 fffff980`11092ea0 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`031aec70 fffff800`02f648ac : fffff980`11092ea0 fffffa80`06eff300 fffffa80`06eff3b8 fffff880`019ee4f5 : nt!VfErrorReport1+0x63
fffff880`031aed10 fffff800`02f64c73 : fffffa80`06eff300 00000000`00000002 fffffa80`054463e0 fffff880`019f81c8 : nt!IovpCallDriver2+0x1bc
fffff880`031aed70 fffff800`02f6ad3e : fffff980`11092ea0 fffff980`11092ea0 00000000`00000002 fffffa80`054463e0 : nt!VfAfterCallDriver+0x353
fffff880`031aedc0 fffff800`02dc143c : 00000000`00000004 fffffa80`099f9cc8 fffffa80`05c30580 fffffa80`06eff300 : nt!IovCallDriver+0x57e
fffff880`031aee20 fffff800`02dbcdb8 : fffffa80`05480970 fffff800`00000000 fffffa80`099f9b10 fffffa80`00000000 : nt!IopParseDevice+0x14d3
fffff880`031aef80 fffff800`02dbdfd6 : 00000000`00000000 fffffa80`099f9b10 00000000`00000000 fffffa80`04492750 : nt!ObpLookupObjectName+0x588
fffff880`031af070 fffff800`02dbf8dc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`000007ff : nt!ObOpenObjectByName+0x306
fffff880`031af140 fffff800`02dcaed4 : fffff880`031af4f0 fffff880`c0100000 fffff880`031af540 fffff880`031af570 : nt!IopCreateFile+0x2bc
fffff880`031af1e0 fffff800`02ac0e53 : 00000000`00000001 fffff880`019e6300 00000000`00000000 fffff880`04087590 : nt!NtCreateFile+0x78
fffff880`031af270 fffff800`02abd410 : fffff880`04083cdd fffffa80`00000000 00000000`00000001 fffffa80`04fcbd90 : nt!KiSystemServiceCopyEnd+0x13
fffff880`031af478 fffff880`04083cdd : fffffa80`00000000 00000000`00000001 fffffa80`04fcbd90 00000000`000007ff : nt!KiServiceLinkage
fffff880`031af480 fffff880`040831ee : fffff880`00000590 fffffa80`04fcbb10 00000000`00000000 00000000`000007ff : netbt!NbtTdiOpenAddress+0x330
fffff880`031af5f0 fffff880`04053485 : fffffa80`c0a80166 fffffa80`04fcbb10 00000000`00000032 00000000`c0a80166 : netbt!NbtCreateAddressObjects+0x25f
fffff880`031af660 fffff880`04083392 : 00000000`00000000 00000000`00ffffff fffff880`031af7b8 00000000`00000000 : netbt!NbtSetNewAddress+0x1f7
fffff880`031af6e0 fffff880`04083416 : 00000000`ffffff00 fffffa80`04fec7c0 00000000`00000000 fffff880`031af7b8 : netbt!NbtAddressAdd+0x1db
fffff880`031af780 fffff880`019e3baf : fffffa80`054be990 00000000`abababab 00000000`00000001 fffffa80`04fec780 : netbt!TdiAddressNotification+0x12c
fffff880`031af800 fffff880`019e403d : fffff880`019e0000 fffffa80`04f67b80 00000000`abababab fffffa80`04f67b80 : TDI!TdiNotifyPnpClientList+0x17f
fffff880`031af860 fffff880`019e4411 : fffffa80`04f67b80 00000000`0000000c fffffa80`04fec700 fffffa80`04f67b80 : TDI!TdiExecuteRequest+0x3bd
fffff880`031af8b0 fffff880`019d3835 : 00000000`00000000 fffff880`019d9630 fffffa80`04fec780 fffffa80`056bf0d0 : TDI!TdiHandleSerializedRequest+0x2a1
fffff880`031af920 fffff880`019d4f9e : fffffa80`00000000 fffffa80`056bf0d0 00000000`00000000 fffff880`031afb70 : tdx!TdxProcessAddressChangeRoutine+0x305
fffff880`031afa00 fffff880`015067fd : fffff880`031afb60 fffff880`0176e9a0 fffff880`031afb70 00000000`00000000 : tdx!TdxNaAddressChangeEvent+0x8e
fffff880`031afa30 fffff880`01612f80 : fffff880`031afb60 fffffa80`052b0200 00000000`00000001 00000000`00000000 : NETIO!NsiParameterChange+0x8d
fffff880`031afb10 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!IppNotifyAddressChangeAtPassive+0x190


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  networx+b19c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: networx

IMAGE_NAME:  networx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  528b9a97

FAILURE_BUCKET_ID:  X64_0xc9_226_VRF_networx+b19c

BUCKET_ID:  X64_0xc9_226_VRF_networx+b19c

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xc9_226_vrf_networx+b19c

FAILURE_ID_HASH:  {95a44c3d-44d8-18c6-e0b3-d7f664b27ee9}

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

"tabernac" is a very bad word in Quebec, Canada. If you didn't intend to reflect this, you should change it to something more polite.

Apart from that, I have no idea what your problem is... did you try uninstalling and then re-installing with the TDI driver?

You could try the other driver...

You could use the portable version with the WinPCap 3.1 driver.