NetWorx blue screen

Are you saying that the same crash occurs both with the TDI and WFP driver?

Andrew, yes, I've had issues with both the drivers - the crash occurrence with the TDI driver has been much, much lower than the WFP driver, however.

In that case if may be a generic incompatibility with the combination of software on your machine. If you do need to exclude local traffic, you can try the following workaround:

1. Backup your usage and uninstall NetWorx.
2. Download and install WinPCap.
3. Install latest NetWorx again leaving the "LAN Traffic Filtering Driver" option unticked.
4. When NetWorx starts, you should be able to choose one of your adapters prefixed with "Ignore LAN Traffic" from the drop-down list in the NetWorx settings.

In this case NetWorx will be using the WinPCap driver, rather its own custom driver and you shouldn't have any stability issues again.

Thanks Andrew - I do need to exclude local traffic, will try out the workaround you mentioned.

BTW, just had another crash.

On Fri 28-Feb-14 3:42:30 PM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: networx.sys (networx+0x7862) 
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\drivers\networx.sys
product: NetFilter SDK
company: NetFilterSDK.com
description: NetFilter SDK TDI Hook Driver (WPP)
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 be caused by a 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: networx.sys (NetFilter SDK TDI Hook Driver (WPP), NetFilterSDK.com). 
Google query: NetFilterSDK.com DPC_WATCHDOG_VIOLATION

I can upload the memory dump & minidump files, in case you're interested.

Thanks again

Andrew, does the router monitoring via UPnP require your LAN traffic filtering device?

Quote

Sathya

I can upload the memory dump & minidump files, in case you're interested.

Yes, please. I will forward it to the driver's developer for analysis.

Quote

sathyabhat

Andrew, does the router monitoring via UPnP require your LAN traffic filtering device?

No, it doesn't require any drivers and it works by periodic polling of the router.

Quote

Andrew

Yes, please. I will forward it to the driver's developer for analysis.

Sorry for the delay. The dump files can be obtained from jere: https://www.dropbox.com/sh/7lmuvlqajkwvnxs/Z_7zkXg4-9

Thank you, I have forwarded this to the developer for analysis.

I've got the exact same issue: http://pressf1.pcworld.co.nz/showthread.php?138121-New-Business-Desktop
I've just updated to 5.3.3 so hopefully it's fixed

+1 for receiving the 0x133 blue screens due to Networx new version. I have just installed it. Only my Windows 8.1 machine is affected, not Win 7.

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x133
PROCESS_NAME: networx.exe
CURRENT_IRQL: d
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
LAST_CONTROL_TRANSFER: from fffff803161adb2c to fffff8031616dfa0

I haven't read through the whole thread but will do so shortly.

My dump files: https://onedrive.live.com/redir?resid=D717EF6C53DE8923!545&authkey=!APQd94gpM9prnk4&ithint=folder%2c

Unfortunately there isn't much we can do as the BSOD is caused by a third-party driver package that NetWorx relies upon.

If you had previously chosen the TDI driver to install, try reinstalling the latest version of NetWorx at which time choose the WFP driver to install and reboot. If you had chosen the WFP driver, try installing TDI instead and reboot. If both the drivers cause a BSOD and you still need to exclude local traffic, please use the workaround with WinPCap described above.