BAD_POOL_CALLER Upon Booting Windows Vista => fixed in SVN

[Zian Choy]

Virtualbox crashed my computer today when I resumed the computer from hibernation. Here's the !analyze -v output from WinDbg:

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

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this
is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 0000110b, (reserved)
Arg3: 080d0003, Memory contents of the pool block
Arg4: 872fb4f8, Address of the block of pool being deallocated

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


POOL_ADDRESS:  872fb4f8 Nonpaged pool

FREED_POOL_TAG:  VBNF

BUGCHECK_STR:  0xc2_7_VBNF

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 824fc00c to 824db0e3

STACK_TEXT:  
88d63754 824fc00c 000000c2 00000007 0000110b nt!KeBugCheckEx+0x1e
88d637cc 82a81370 872fb4f8 00000000 88d637f8 nt!ExFreePoolWithTag+0x17f
88d637dc 8c2a8b6d 872fb4f8 00000000 00000000 ndis!NdisFreeMemory+0x16
WARNING: Stack unwind information not available. Following frames may be wrong.
88d637f8 8c2a8ff8 84e4915c 84e49368 84e49100 VBoxNetFlt+0x2b6d
88d63818 8c2a9447 8c2b5630 00000000 84e49100 VBoxNetFlt+0x2ff8
88d6383c 8c2a720d 84e49100 88d6396c 88d63898 VBoxNetFlt+0x3447
88d6385c 8c2a7349 8c2b5630 88d63898 88d63888 VBoxNetFlt+0x120d
88d63880 8c2a9d04 8c2b5630 88d63898 88d63990 VBoxNetFlt+0x1349
88d63980 8c2aa2ad 88d639a0 869f7b88 00000000 VBoxNetFlt+0x3d04
88d639a8 82b504b1 88d63a44 88d639d0 8627a454 VBoxNetFlt+0x42ad
88d63a3c 82b50129 00000000 84243f00 82ab0918 ndis!ndisInitializeBinding+0x23b
88d63ac8 82b5ef67 8630a0e8 00000000 00000000 ndis!ndisCheckAdapterBindings+0x170
88d63aec 82b5f1e1 00000000 8592b560 00000000 ndis!ndisIMInitializeDeviceInstance+0x93
88d63b0c 8c0e1329 861c0b98 873e75d8 8592b560 ndis!NdisIMInitializeDeviceInstanceEx+0x100
88d63b58 82b504b1 88d63bf4 88d63b80 8613c68c dne2000+0xa329
88d63bec 82b50129 00000000 853da030 00000000 ndis!ndisInitializeBinding+0x23b
88d63c78 82b65e89 8623c0e8 00000000 00000000 ndis!ndisCheckAdapterBindings+0x170
88d63d34 82b4e013 848e59c8 8623c0e8 88d63d7c ndis!ndisDevicePowerOn+0x515
88d63d44 82446445 848e59c8 00000000 8427fd78 ndis!ndisWorkItemHandler+0xe
88d63d7c 825e3b18 848e59c8 536a4906 00000000 nt!ExpWorkerThread+0xfd
88d63dc0 8243ca2e 82446348 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
VBoxNetFlt+2b6d
8c2a8b6d 8b8694010000    mov     eax,dword ptr [esi+194h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  VBoxNetFlt+2b6d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: VBoxNetFlt

IMAGE_NAME:  VBoxNetFlt.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  497765d0

FAILURE_BUCKET_ID:  0xc2_7_VBNF_VBoxNetFlt+2b6d

BUCKET_ID:  0xc2_7_VBNF_VBoxNetFlt+2b6d

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

1: kd> lmvm VBoxNetFlt
start    end        module name
8c2a6000 8c2b9b00   VBoxNetFlt   (export symbols)       VBoxNetFlt.sys
    Loaded symbol image file: VBoxNetFlt.sys
    Image path: \SystemRoot\system32\DRIVERS\VBoxNetFlt.sys
    Image name: VBoxNetFlt.sys
    Timestamp:        Wed Jan 21 10:13:36 2009 (497765D0)
    CheckSum:         000164D2
    ImageSize:        00013B00
    Translations:     0000.04b0 0000.04e0 0409.04b0 0409.04e0

[garyng]

Just to add, this is not just Vista. I experienced the same error on Vista SP1, Windows Server 2008.

I didn't recall see that frequent BSOD in the 2.0.x version but not out of 80% of the time I resume from sleep/hibernation, the host crash with this BAD_POOL_CALLER.

[Mike]

Hello,

I too would like to confirm that this bug does exist, and I am experiencing the exact same issue. Shortly after installing VirtualBox 2.1.2, I have been experiencing BSOD's on my Vista 32-bit host after Hibernation and Sleep. The BSOD error I experience is a BAD_POOL_CALLER, just like the first post.

Please note, this is the first time I have experienced this problem. I have not experienced these errors on previous versions of VirtualBox. Thus far, I have not experienced this problem on my Vista x64 notebook.

I am going to uninstall VirtualBox to see if it will serve as a temporary remedy to the issues I have been experiencing.

Below is my analyze -v output from WinDbg:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 0000110b, (reserved)
Arg3: 080d0006, Memory contents of the pool block
Arg4: 85fdc7d0, Address of the block of pool being deallocated

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

GetPointerFromAddress: unable to read from 81b52868
Unable to read MiSystemVaType memory at 81b32420

POOL_ADDRESS: GetPointerFromAddress: unable to read from 81b52868
Unable to read MiSystemVaType memory at 81b32420
 85fdc7d0 

BUGCHECK_STR:  0xc2_7

CUSTOMER_CRASH_COUNT:  4

DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 81b0900c to 81ae80e3

STACK_TEXT:  
a62516cc 81b0900c 000000c2 00000007 0000110b nt!KeBugCheckEx+0x1e
a6251744 89c18370 85fdc7d0 00000000 a6251770 nt!ExFreePoolWithTag+0x17f
a6251754 94e0bb6d 85fdc7d0 00000000 00000000 ndis!NdisFreeMemory+0x16
WARNING: Stack unwind information not available. Following frames may be wrong.
a6251770 94e0bff8 85aee43c 85aee648 85aee3e0 VBoxNetFlt+0x2b6d
a6251790 94e0c447 94e18630 00000000 85aee3e0 VBoxNetFlt+0x2ff8
a62517b4 94e0a20d 85aee3e0 a62518e4 a6251810 VBoxNetFlt+0x3447
a62517d4 94e0a349 94e18630 a6251810 a6251800 VBoxNetFlt+0x120d
a62517f8 94e0cd04 94e18630 a6251810 a6251908 VBoxNetFlt+0x1349
a62518f8 94e0d2ad a6251918 85f8ef28 00000000 VBoxNetFlt+0x3d04
a6251920 89ce74b1 a62519bc a6251948 853ca144 VBoxNetFlt+0x42ad
a62519b4 89ce7129 00000000 83d43590 89c47918 ndis!ndisInitializeBinding+0x23b
a6251a40 89cf5f67 85729140 00000000 00000000 ndis!ndisCheckAdapterBindings+0x170
a6251a64 89cf61e1 00000000 8550e760 00000000 ndis!ndisIMInitializeDeviceInstance+0x93
a6251a84 8f9cdaec 854a3428 862578b0 8550e760 ndis!NdisIMInitializeDeviceInstanceEx+0x100
a6251b58 89ce74b1 a6251bf4 a6251b80 854c5f8c VMNetSrv+0x2aec
a6251be0 860ac708 01251c78 a6251c78 89ce7129 ndis!ndisInitializeBinding+0x23b
a6251bec 89ce7129 00000000 83d5c6b0 00000000 0x860ac708
a6251c78 89cfce89 853a1438 00000000 00000000 ndis!ndisCheckAdapterBindings+0x170
a6251d34 89ce5013 852e58d8 853a1438 a6251d7c ndis!ndisDevicePowerOn+0x515
a6251d44 81a53445 852e58d8 00000000 860c8d78 ndis!ndisWorkItemHandler+0xe
a6251d7c 81bf0b18 852e58d8 2ec6f67d 00000000 nt!ExpWorkerThread+0xfd
a6251dc0 81a49a2e 81a53348 80000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
VBoxNetFlt+2b6d
94e0bb6d ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  VBoxNetFlt+2b6d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: VBoxNetFlt

IMAGE_NAME:  VBoxNetFlt.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  497765d0

FAILURE_BUCKET_ID:  0xc2_7_VBoxNetFlt+2b6d

BUCKET_ID:  0xc2_7_VBoxNetFlt+2b6d

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

Any and all help would be greatly appreciated!

Thank You

[Mike]

As a follow up, upon uninstalling VirtualBox, my BSOD's have stopped.

[pentagonik]

To all who have problems (Bluescreens) with the VBoxNetFlt component: Please send me a mail at <my nickname> at sun dot com. I'll then send you a link to a new test version.

[Zian Choy]

I tried installing and using the build from pentagonik and the stop errors have stopped.

[Zian Choy]

I'm using Vista Ultimate 32-bit.

[Mike]

Hi,

I installed the latest test version, and I am having a problem with starting an Ubuntu image using the host interface network option. I receive the following error (not a BSOD) when starting the VM: VERR_INTNET_FLT_IF_NOT_FOUND

However, LAN interface works. I have made an attachment of the screenshot with the error.

So far, I have not yet experienced a BSOD, however, I will report if I do. I'm running Vista Home Premium 32-bit.

[Mike]

VERR_INTNET_FLT_IF_NOT_FOUND error with host interface enabled

[misha]

Replying to Mikee99: Does this happen with the latest test build only? Do you see the list of network interfaces in the VirtualBox Network properties for your VM? Could you also attach a Log file here?

Thanks

[Mike]

Replying to misha:

Hello, the build of VirtualBox that exhibits the VERR is the latest test build I downloaded from the email. I attached a screenshot of my network settings. Everything listed there (with the exception of the Host Interface selection) are the default settings.

I have also tried changing the adapter type, however, every selection yields similar results.

[Mike]

Network Settings. All of which exhibit the previous attached error with the test build 2.1.51

[Joel Hershberger]

I have downloaded and installed the test build. It installed without any problems and I could not get a BSOD no matter how I was running the vm and using hibernate or sleep modes. I am running Vista Ultimate SP1 32 bit.

[misha]

Replying to Mikee99: Could you attach a log file as well?
Another thing that would be very useful is <windir>/inf/setupapi.dev.log and <windir>/inf/setupapi.app.log files.
Those should contain the info regarding the driver installation. In case they are pretty big, you could post only the last parts of them concerning the latest VBox installs.

[misha]

Replying to Mikee99: It seems I was able to reproduce your issue. This is the installation issue, and it seems the fix should be trivial. I'll post an update here once I have some results.

[Mike]

setupapi.app.log with info pertaining only to the vbox test build.

[Mike]

setupapi.dev.log file with only the info pertaining to the VBOX test build

[Mike]

Replying to misha:

Hello misha. I have attached the two log files requested. Are there any more log files that you would like to see?

Thank You

[mattsnowboard]

Replying to Mikee99:

Hello,

I too would like to confirm that this bug does exist, and I am experiencing the exact same issue. Shortly after installing VirtualBox 2.1.2, I have been experiencing BSOD's on my Vista 32-bit host after Hibernation and Sleep. The BSOD error I experience is a BAD_POOL_CALLER, just like the first post.

Please note, this is the first time I have experienced this problem. I have not experienced these errors on previous versions of VirtualBox. Thus far, I have not experienced this problem on my Vista x64 notebook.

I am going to uninstall VirtualBox to see if it will serve as a temporary remedy to the issues I have been experiencing.

Any and all help would be greatly appreciated!

Thank You

Same Problem. And I wasn't able to successfully downgrade to 2.1.0. I am using Vista 32 though.

[misha]

To all who have problems with VERR_INTNET_FLT_IF_NOT_FOUND when using host interface networking with the recent test version or VBoxNetFlt Bluescreens with the 2.1.2:

Please send me a mail at Mikhail dot Sennikovsky at sun dot com. I'll then send you a link to a new test version containing a fox.

[Mike]

Replying to misha:

Hello,

I have installed the new build, and I am pleased to say that I no longer receive both the BSOD, or the host interface networking problem.

Bravo.

[mattsnowboard]

The test build is working here, no more BSOD

[misha]

I think this bug can be considered fixed

[misha]

sorry, should not have closed it..