VBoxNetFlt bug

[sandos]

I got a bluescreen after installing 2.1.0. I had a vm that had been running for some time, using host mode networking with my ethernet NIC selected as opposed to a TAP device as in 2.0. It was working flawlessly. My machine probably had some memory pressure when this happened, much too many apps going at once. Machine was basically crawling at this point.

I have a mini-dump from the crash. Not sure if this helps any.

Code: Select all

STACK_TEXT:  
9c05f9dc 8054b583 00000019 00000020 87694750 nt!KeBugCheckEx+0x1b
9c05fa2c f70f05e8 87694758 00000000 9c05fa58 nt!ExFreePoolWithTag+0x2a3
9c05fa3c 9ad12ff8 87694758 00000000 00000000 NDIS!NdisFreeMemory+0x3b
WARNING: Stack unwind information not available. Following frames may be wrong.
9c05fa58 9ad13ddf 87d6d44c 9c05fa84 9ad11fe7 VBoxNetFlt+0x1ff8
9c05fa64 9ad11fe7 87d6d3f0 89a7fc48 00000000 VBoxNetFlt+0x2ddf
9c05fa84 86f3f06d 00000003 89a7fc48 875ab6b8 VBoxNetFlt+0xfe7
9c05faa8 86f3f17a 89a7fc48 875ab6b8 8782d218 0x86f3f06d
9c05fac4 9ad25334 8782d218 875ab6b8 876a7dd0 0x86f3f17a
9c05fbc4 805390d1 9c05fbdc c0523cc8 9c05fc00 VBoxDrv+0x1334
9c05fc40 804ef19f 874942b0 87898018 806e6410 nt!ExInsertTailNBQueue+0xa3
9c05fd34 8054162c 00000f80 00000000 00000000 nt!IopfCallDriver+0x31
9c05fd34 874942b0 00000f80 00000000 00000000 nt!KiFastCallEntry+0xfc
9c05fcd4 00000000 87887028 00000000 00000000 0x874942b0

Code: Select all

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: 87694750, The pool entry we were looking for within the page.
Arg3: 87694870, The next pool entry.
Arg4: 0a240001, (reserved)

[sandos]

Seems they are already on it:

http://www.virtualbox.org/ticket/2832

[mirak]

I have this problem also when I use host nic, however I don't even get a blue screen, I just have a systèm hang, and must reboot manually

[The MAZZTer]

You can try checking to be sure that the host interface upgrade made by the 2.1.0 installer worked fully (mine didn't because I futzed with some network stuff after the install, caused a few problems before I forced an uninstall and reinstall to fix it).

VBoxNetFlt is the new provider for the Host Interface networking. The TAP driver is no longer necessary. Open up device manager and confirm that the VirtualBox TAP driver is indeed gone (the default name is VirtualBox Host Interface 1 IIRC but you could create and name as many as you wanted).

Now go to View > Show hidden devices and you should see Network Filter Drivers on your adapters. Your main adapter (or a Network Bridge that contains your main adapter) should have a "VirtualBox Host Interface Networking Driver Miniport". If not you will have to uninstall and reinstall VBox... doing a repair install will not fix it.*

* - You likely have one, since it is running and crashing.

[mirak]

I forgot to say I am on XP