Opened 9 years ago
Last modified 9 years ago
#14042 new defect
VBoxNetFlt crashing windows 7 on resume
| Reported by: | microwheels | Owned by: | |
|---|---|---|---|
| Component: | host support | Version: | VirtualBox 4.3.26 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Windows |
Description (last modified by )
My system started bugchecking after I installed virtualbox 4.3.26 r98988 on my Windows 7 SP1 Enterprise system (64 bit). The first one happened when I awoke the machine after putting it into sleep mode with my vm running. After that, I made sure to shut down the vm before going into sleep mode but that doesn't prevent the crash.
Please find the crash dump analysis below. Note that while the analyzer is blaming the multi-process NT kernel, the faulting module is VBoxNetFlt. That indicates the filter driver is not handling the power state change correctly.
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*C:\Debug\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*C:\Debug\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.22948.amd64fre.win7sp1_ldr.150202-1521
Machine Name:
Kernel base = 0xfffff800`02e60000 PsLoadedModuleList = 0xfffff800`030a3890
Debug session time: Thu Apr 9 16:19:23.133 2015 (UTC - 6:00)
System Uptime: 2 days 7:16:36.599
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa800d99d980, fffff800047063d8, fffffa80134bee10}
*** ERROR: Symbol file could not be found. Defaulted to export symbols for VBoxNetFlt.sys -
Probably caused by : ntkrnlmp
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800d99d980, Physical Device Object of the stack
Arg3: fffff800047063d8, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa80134bee10, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: ntkrnlmp
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: ntkrnlmp
FAULTING_MODULE: fffff88000dc6000 VBoxNetFlt
IRP_ADDRESS: fffffa80134bee10
DEVICE_OBJECT: fffffa8011208050
DRIVER_OBJECT: fffffa8013c3c5d0
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
DPC_STACK_BASE: FFFFF8000470CFB0
STACK_TEXT:
fffff800`04706388 fffff800`02f448e2 : 00000000`0000009f 00000000`00000003 fffffa80`0d99d980 fffff800`047063d8 : nt!KeBugCheckEx
fffff800`04706390 fffff800`02edeb3c : fffff800`047064c0 fffff800`047064c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x336b0
fffff800`04706430 fffff800`02ede9d6 : fffff800`03086140 00000000`00c2a48e 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`047064a0 fffff800`02ede8be : 000001cf`53374f3b fffff800`04706b18 00000000`00c2a48e fffff800`03054448 : nt!KiProcessExpiredTimerList+0xc6
fffff800`04706af0 fffff800`02ede6a7 : 00000079`dd9484c1 00000079`00c2a48e 00000079`dd9484d7 00000000`0000008e : nt!KiTimerExpiration+0x1be
fffff800`04706b90 fffff800`02ecbb8a : fffff800`03050e80 fffff800`0305ecc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`04706c40 00000000`00000000 : fffff800`04707000 fffff800`04701000 fffff800`04706c00 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION:
FAILURE_BUCKET_ID: X64_0x9F_3_POWER_DOWN_IMAGE_ntkrnlmp
BUCKET_ID: X64_0x9F_3_POWER_DOWN_IMAGE_ntkrnlmp
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x9f_3_power_down_image_ntkrnlmp
FAILURE_ID_HASH: {11a584ac-cfbe-b229-0d33-15c5fd69f706}
Followup: MachineOwner
---------

