This did happen, although very rarely, 2 users from our 30k users got the BSOD. From the below minidump info, it's to do with power state of the net filter driver. They tested VirtualBox 3.1.2, and got same BSOD.
I checked the logs, seems this bug was fixed somewhat, but it still exists. =========== minidump info ============ Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\vpxware\bugs\010710-43695-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?ffffffff`83329ad4? WARNING: Whitespace at end of path element Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols ;C:\virtualbox-dev\vbox\out\win.x86\debug\bin Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.x86fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0x83203000 PsLoadedModuleList = 0x8334b810 Debug session time: Thu Jan 7 08:49:01.115 2010 (GMT-8) System Uptime: 0 days 2:55:27.660 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ..... Loading User Symbols Loading unloaded module list ........... 0: kd> !analyze -v ERROR: FindPlugIns 8007007b ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_POWER_STATE_FAILURE (9f) A driver is causing an inconsistent power state. Arguments: Arg1: 00000003, A device object has been blocking an Irp for too long a time Arg2: 89883590, Physical Device Object of the stack Arg3: 83329ae0, Functional Device Object of the stack Arg4: 8b064450, The blocked IRP Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for VBoxNetFlt.sys *** ERROR: Module load completed but symbols could not be loaded for VBoxNetFlt.sys DRVPOWERSTATE_SUBCODE: 3 IRP_ADDRESS: 8b064450 DEVICE_OBJECT: e5286028 DRIVER_OBJECT: 879ff7e8 IMAGE_NAME: VBoxNetFlt.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4afb6d6d MODULE_NAME: VBoxNetFlt FAULTING_MODULE: c7154000 VBoxNetFlt CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 8323f054 to 832dfd10 STACK_TEXT: 83329a94 8323f054 0000009f 00000003 89883590 nt!KeBugCheckEx+0x1e 83329b00 8323e8e8 83329ba0 00000000 83336280 nt!PopCheckIrpWatchdog+0x1f5 83329b38 8326d04d 83344a20 00000000 50398a21 nt!PopCheckForIdleness+0x73 83329b7c 8326cff1 8332cd20 83329ca8 00000002 nt!KiProcessTimerDpcTable+0x50 83329c68 8326ceae 8332cd20 83329ca8 00000000 nt!KiProcessExpiredTimerList+0x101 83329cdc 8326b20e 000a4c1d 89807b48 83336280 nt!KiTimerExpiration+0x25c 83329d20 8326b038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb 83329d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: 0x9F_IMAGE_VBoxNetFlt.sys BUCKET_ID: 0x9F_IMAGE_VBoxNetFlt.sys Followup: MachineOwner --------- _______________________________________________ vbox-dev mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-dev
