Ticket #3370 (closed defect: obsolete)

Opened 14 years ago

Last modified 8 years ago

VBoxNetFlt: Conflict with the Trend Micro Anti-Virus driver

Reported by: willyo Owned by:
Component: network Version: VirtualBox 2.1.4
Keywords: Cc:
Guest type: Linux Host type: Windows

Description (last modified by frank) (diff)

After installing 2.1.4 + the USB driver + the network driver on my Vista

(with up-to-date patches) on my Sony VAIO laptop I get a BSOD every so often (1-2 hours) even without creating/running a VM.

(The same problem also occurred with 2.1.2).

After uninstalling and then re-installing 2.1.4 w/o the network driver there were no further crashes.

I've attached a minidump. I'm not familiar with interpreting Winows crash-dumps but I did try dumpchk.

The dumpchk output says (among other things) "Probably caused by : tmwfp.sys ( tmwfp+22d1d )"

tmwfp.sys is a driver for my Trend-Micro Anti-Virus so that's why I began to suspect some interaction between the VirtualBox network driver and other network drivers.

(I also have WinPcap installed on my machine).

The crash repeated quite consistently (4x in 3 hours) so if if there's any magic which might be done before/after a crash to get more/useful information, please let me know.

Having now read the manual in more detail, I see that I do not need the network driver for my setup, so this is not a show-stopper for me.


Mini021609-04.dmp Download (135.0 KB) - added by willyo 14 years ago.

Change History

Changed 14 years ago by willyo


comment:1 Changed 14 years ago by willyo

I guess "internal host" in the above should actually be "Host Interface". (I'm just learning the VirtualBox lingo....).

comment:2 Changed 14 years ago by sandervl73

  • priority changed from minor to critical

comment:3 Changed 14 years ago by sandervl73

  • priority changed from critical to major
  • Summary changed from Vista BSODs when "internal host" network driver installed to VBoxNetFlt: Conflict with the Trend Micro Anti-Virus driver

Conflict with the Trend Micro Anti-Virus driver

803ea350 aee2ed1d 00000000 00000001 87116c68 tmwfp+0x20c6e
803ea6ac aee2846b 00000000 b2c96218 87116c68 tmwfp+0x22d1d
803ea6e0 aee284bc 00000003 00000000 00000000 tmwfp+0x1c46b
803ea710 87db8409 803eab04 803eaa28 b5b21808 tmwfp+0x1c4bc
803ea758 87db804f 00000030 803eab04 803eaa28 NETIO!ProcessCallout+0x10e
803ea7c8 87db81e9 00000030 803eab04 803eaa28 NETIO!ArbitrateAndEnforce+0xaa
803ea8ac 87e77344 00000030 803eab04 803eaa28 NETIO!KfdClassify+0x16f
803ea8d4 87e66b72 803eab04 803eaa28 b5b21808 tcpip!WfpAleClassify+0x36
803eab70 87e665d8 94753e88 00000030 87ebd2c8 tcpip!WfpAlepAuthorizeSend+0x4c0
803eacd0 87e7761c 94753e88 803e0002 00000011 tcpip!WfpAleAuthorizeSend+0x1e0
803ead2c 87e75c19 94753e88 803e0002 00000011 tcpip!WfpAleConnectAcceptIndicate+0x56
803ead9c 87e650c7 803eafac 00000011 803e0002 tcpip!ProcessALEForTransportPacket+0xf3
803eae20 87e64c0f 803eafac 00000011 803e0002 tcpip!ProcessAleForNonTcpOut+0x5c
803eaf70 87e63cd4 00000011 00000000 00008900 tcpip!WfpProcessOutTransportStackIndication+0x200
803eaff4 87e63b28 00000000 00000000 00000000 tcpip!IppInspectLocalDatagramsOut+0xbf
803eaff4 00000000 00000000 00000000 00000000 tcpip!IppSendDatagramsCommon+0x522}}}

comment:4 Changed 13 years ago by Technologov

This issue seems pretty serious, as it results in host BSOD, so I suggest upping it's priority to blocker.

How are those drivers connected ?


comment:5 Changed 8 years ago by frank

  • Status changed from new to closed
  • Resolution set to obsolete
  • Description modified (diff)
Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use