This seems to be related to 2.1(or 2.1.2) as once I upgraded my old 2.0.x, I see this frequently when I put the host to sleep mode(on notebook) then resume. Didn't recall I see it as often in the past(occasional may be).
This happens on 2008 server host or Vista SP1 host.
Not sure if the client matters as I have both linux as well as XP client.
This error makes virtualbox almost not usable on a laptop setup.
Frequent BSOD of BAD_POOL_CALLER after resuming host
-
garyng2000
- Posts: 3
- Joined: 26. Jan 2009, 20:58
Frequent BSOD of BAD_POOL_CALLER after resuming host
I too have started getting this error. I am running Vista Ultimate (Host) and XP Pro and Windows 7 (guest). I have ended up disabling sleep mode on the host as to not get this error. I also recently upgraded to v2.1.2 from v2.1.0. I have never had this error prior to this version. I wasn't using v2.1.0 very long though. Only used that version for about a week. Before that I was using v1.6.6.
-
strichards
- Posts: 14
- Joined: 20. Nov 2008, 14:27
I have received this also.
Code: Select all
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini012209-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: c:\windows\symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows Kernel Version 6002 (Service Pack 2.113) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x82647000 PsLoadedModuleList = 0x8275ec70
Debug session time: Thu Jan 22 18:52:31.040 2009 (GMT-5)
System Uptime: 0 days 11:19:23.405
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
............................................................................................................................
........................................................................................................................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C2, {7, 110b, 80d0005, 98e406a0}
Unable to load image NDIS.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NDIS.SYS
Unable to load image VBoxNetFlt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for VBoxNetFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for VBoxNetFlt.sys
Unable to load image VMNetSrv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for VMNetSrv.sys
*** ERROR: Module load completed but symbols could not be loaded for VMNetSrv.sys
Probably caused by : VBoxNetFlt.sys ( VBoxNetFlt+2b6d )
Followup: MachineOwner
---------
0: 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: 080d0005, Memory contents of the pool block
Arg4: 98e406a0, Address of the block of pool being deallocated
Debugging Details:
------------------
POOL_ADDRESS: 98e406a0
FREED_POOL_TAG: VBNF
BUGCHECK_STR: 0xc2_7_VBNF
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: @?u?à
LAST_CONTROL_TRANSFER: from 82734184 to 82714c09
STACK_TEXT:
8975f6d4 82734184 000000c2 00000007 0000110b nt!ObDuplicateObject+0x24b
8975f748 83211c6d 98e406a0 00000000 8975f774 nt!RtlpCreateStack+0xd4
8975f758 8ebdcb6d 98e406a0 00000000 00000000 NDIS!RtlCopyMdlToBuffer+0x8d
WARNING: Stack unwind information not available. Following frames may be wrong.
8975f774 8ebdcff8 8bcce47c 8bcce688 8bcce420 VBoxNetFlt+0x2b6d
8975f794 8ebdd447 8ebe9630 00000000 8bcce420 VBoxNetFlt+0x2ff8
8975f7b8 8ebdb20d 8bcce420 8975f8e8 8975f814 VBoxNetFlt+0x3447
8975f7d8 8ebdb349 8ebe9630 8975f814 8975f804 VBoxNetFlt+0x120d
8975f7fc 8ebddd04 8ebe9630 8975f814 8975f90c VBoxNetFlt+0x1349
8975f8fc 8ebde2ad 8975f91c a930cc58 00000000 VBoxNetFlt+0x3d04
8975f924 832e0493 8975f9c0 8975f94c 8bdb0cd4 VBoxNetFlt+0x42ad
8975f9b8 832e010b 00000000 84a4a1c0 83240918 NDIS!ndisInitializeBinding+0x21d
8975fa44 832eef67 8d72a438 00000000 00000000 NDIS!ndisCheckAdapterBindings+0x152
8975fa68 832ef1e1 00000000 99bb1760 00000000 NDIS!ndisIMInitializeDeviceInstance+0x93
8975fa88 831bda83 8d72a010 91d81758 99bb1760 NDIS!NdisIMInitializeDeviceInstanceEx+0x100
8975fa98 8bdbaad0 8bd38438 8975fbec 8bd7d544 VMNetSrv+0x2a83
8975fa9c 8bd38438 8975fbec 8bd7d544 00000000 0x8bdbaad0
8975faa0 8975fbec 8bd7d544 00000000 00000000 0x8bd38438
8975faa4 8bd7d544 00000000 00000000 00000000 0x8975fbec
8975fbec 832e010b 00000000 84e6eb70 00000000 0x8bd7d544
8975fc78 832f5e89 8bd38438 00000000 00000000 NDIS!ndisCheckAdapterBindings+0x152
8975fd34 832de013 98e6a048 8bd38438 8975fd7c NDIS!ndisDevicePowerOn+0x515
8975fd44 826dceba 98e6a048 00000000 84a87d78 NDIS!ndisWorkItemHandler+0xe
8975fd7c 82817e13 98e6a048 819cb360 00000000 nt!MiQueryAddressState+0x34
8975fdc0 826ffdc6 826dcdbd 00000001 00000000 nt!CmGetSystemControlValues+0x8b
8975fdcc 00000000 00000000 00000000 00000000 nt!ObQueryObjectAuditingByHandle+0x9b
STACK_COMMAND: kb
FOLLOWUP_IP:
VBoxNetFlt+2b6d
8ebdcb6d ?? ???
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
---------
Hi everyone,
A ticket regarding this issue has been created here: http://www.virtualbox.org/ticket/3168
The more attention the ticket gets, the quicker it can be fixed.
A ticket regarding this issue has been created here: http://www.virtualbox.org/ticket/3168
The more attention the ticket gets, the quicker it can be fixed.