Networks driver cause BSD

Started by mostafa

mostafa

Networks driver cause BSD   16 February 2013, 03:20

hello
my pc have crashed (BSD) several times in past few days
analyses showed that networks driver caused it, dump files are uploaded to my dropbox:
dropbox.com/sh/ura6cuf7rna2bbu/6rpIq43WsJ
SoftPerfect Support forum - Andrew avatar image

Networks driver cause BSD   17 February 2013, 13:26

Unfortunately I have no control over and cannot fix this issue as it's caused by a third-party driver NetWorx uses. There is a workaround though:

1. Backup your usage.

2. Uninstall NetWorx.

3. Reinstall NetWorx with the Install LAN traffic filtering driver option unticked.

4. Install WinPCap if you need to filter out local traffic. Restart NetWorx and choose your network adapter marked "Ignore LAN traffic:"

Networks driver cause BSD   30 March 2013, 02:58

I didn't have the above problem, but thought I'd post somewhere that a new WinPCap is out for the first time in a long time:
http://www.winpcap.org/misc/changelog.htm#changelog_4_1_3

Networks driver cause BSD   31 March 2013, 05:16

I don't get this talk about Wincap. Isn't it not necessary anymore, in the last versions?

I already uninstalled Wincap and all seems OK!

Networks driver cause BSD   31 March 2013, 05:24

Many people already have it from other programs, such as Wireshark, so in that case it's smart to use (also, for a while, the home-grown one was a little unstable). Neither driver is needed if you don't care about excluding local traffic.

Reply to this topic

Sometimes you can find a solution faster if you try the forum search, have a look at the knowledge base, or check the software user manual to see if your question has already been answered.

Our forum rules are simple:

  • Be polite.
  • Do not spam.
  • Write in English. If possible, check your spelling and grammar.

Author:

Email:

Subject

A brief and informative title for your message, approximately 4–8 words:

     

Spam prevention: please enter the following code in the input field below.

 **    **  **    **  ********   **     **  **     ** 
 **   **    **  **   **     **  **     **  **     ** 
 **  **      ****    **     **  **     **  **     ** 
 *****        **     **     **  **     **  **     ** 
 **  **       **     **     **   **   **    **   **  
 **   **      **     **     **    ** **      ** **   
 **    **     **     ********      ***        ***    

Message: