Opened 10 years ago
Last modified 10 years ago
#13733 new defect
VBoxNetFlt.sys v4.3.20 BSOD “DRIVER_POWER_STATE_FAILURE” when hibernate/shutdown WIN7
| Reported by: | lorcan | Owned by: | |
|---|---|---|---|
| Component: | network | Version: | VirtualBox 4.3.20 |
| Keywords: | BSOD DRIVER_POWER_STATE_FAILURE | Cc: | |
| Guest type: | all | Host type: | Windows |
Description
I randomly (but often) get a BSOD (DRIVER_POWER_STATE_FAILURE) when I hibernate or shutdown my laptop (Windows 7 Home Premium).
I first get a black screen during about 10 minutes then I get the following BSOD.
I already got this issue randomly with previous versions of VirtualBox and I thought it was fixed when reinstalling a new version…
analyze -v output:
*******************************************************************************
* *
* 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: fffffa8005572700, Physical Device Object of the stack
Arg3: fffff80000b9c518, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa800feaa0a0, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: ntkrnlmp
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: ntkrnlmp
FAULTING_MODULE: fffff88010200000 VBoxNetFlt
IRP_ADDRESS: fffffa800feaa0a0
DEVICE_OBJECT: fffffa8007771050
DRIVER_OBJECT: fffffa8007756e70
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
DPC_STACK_BASE: FFFFF80000BA2FB0
STACK_TEXT:
fffff800`00b9c4c8 fffff800`0354c8d2 : 00000000`0000009f 00000000`00000003 fffffa80`05572700 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`034e785c : fffff800`00b9c600 fffff800`00b9c600 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`00b9c570 fffff800`034e76f6 : fffffa80`0e88fc58 fffffa80`0e88fc58 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c5e0 fffff800`034e75de : 000001b6`a883467f fffff800`00b9cc58 00000000`00b847c0 fffff800`0365ba88 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`034e73c7 : 00000060`dc5662c2 00000060`00b847c0 00000060`dc56620f 00000000`000000c0 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`034d48ca : fffff800`03657e80 fffff800`03665cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 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
---------
0: kd> lmvm VBoxNetFlt
start end module name
fffff880`10200000 fffff880`1022b000 VBoxNetFlt T (no symbols)
Loaded symbol image file: VBoxNetFlt.sys
Image path: \SystemRoot\system32\DRIVERS\VBoxNetFlt.sys
Image name: VBoxNetFlt.sys
Timestamp: Mon Nov 24 12:06:09 2014 (54731121)
CheckSum: 000271EA
ImageSize: 0002B000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Attachments (2)
Change History (7)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
The dump shows that the VBoxNetFlt driver hangs on processing IRP_MN_CANCEL_REMOVE_DEVICE. Unfortunately the most of structures in the dump are broken and I cannot extract more details about the issue. So try to collect the dump again, please. Before that I can recommend to switch on the verifier on your computer.
- To switch on verifier execute next command from command line:
verifier.exe /0xDBF /driver VBoxNetAdp.sys VBoxNetFlt.sys
- Restart computer.
- Reproduce the issue and collect the kernel memory dump again.
- After the dump collecting, switch off the verifier using command:
verifier.exe /reset
- Restart computer
follow-up: 4 comment:3 by , 10 years ago
Isn't the command:
verifier.exe /flags 0xDBF /driver VBoxNetAdp.sys VBoxNetFlt.sys
instead of:
verifier.exe /0xDBF /driver VBoxNetAdp.sys VBoxNetFlt.sys
?
comment:4 by , 10 years ago
Replying to lorcan:
Isn't the command:
verifier.exe /flags 0xDBF /driver VBoxNetAdp.sys VBoxNetFlt.sys
instead of:
verifier.exe /0xDBF /driver VBoxNetAdp.sys VBoxNetFlt.sys
?
Sorry, yes, you are right :) Thank you.
by , 10 years ago
| Attachment: | 030115-51792-01.zip added |
|---|
Minidump from February 28, 2015 (VirtualBox v4.3.22)
comment:5 by , 10 years ago
I added a new dump using the verifier with a newer version of VirtualBox (version 4.3.22) this time from my desktop computer (Win7 x64)
EDIT: this BSOD occured during the installation (updating) process of version 4.3.22


I forgot to mention that I sometimes have exactly the same BSOD error with
VBoxNetAdp.systoo.