Opened 12 years ago
Closed 9 years ago
#11730 closed defect (obsolete)
BSoD in VBoxNetAdp.sys with STOP 0x9F
| Reported by: | bigjohn | Owned by: | |
|---|---|---|---|
| Component: | network/hostif | Version: | VirtualBox 4.2.12 |
| Keywords: | Cc: | ||
| Guest type: | Windows | Host type: | Windows |
Description (last modified by )
started to happen after I updated to 4.2.12 recently.
WinDbg shows this:
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800c779700, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, Functional Device Object of the stack
Arg4: fffffa802db99e10, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IRP_ADDRESS: fffffa802db99e10
DEVICE_OBJECT: fffffa800fece050
DRIVER_OBJECT: fffffa800ff91c50
IMAGE_NAME: VBoxNetAdp.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5167d67e
MODULE_NAME: VBoxNetAdp
FAULTING_MODULE: fffff88003083000 VBoxNetAdp
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80003b008c2 to fffff80003a90c00
STACK_TEXT:
fffff800`00b9c388 fffff800`03b008c2 : 00000000`0000009f 00000000`00000003 fffffa80`0c779700 fffff800`00b9c3d8 : nt!KeBugCheckEx
fffff800`00b9c390 fffff800`03a9b84c : fffff800`00b9c4c0 fffff800`00b9c4c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`00b9c430 fffff800`03a9b6e6 : fffff800`03c40f20 00000000`0102ee6a 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`03a9b5ce : 00000268`5b46c05a fffff800`00b9cb18 00000000`0102ee6a fffff800`03c0efc8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`03a9b3b7 : 0000009c`23d535c1 0000009c`0102ee6a 0000009c`23d535a4 00000000`0000006a : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`03a8890a : fffff800`03c0be80 fffff800`03c19cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_IMAGE_VBoxNetAdp.sys
BUCKET_ID: X64_0x9F_IMAGE_VBoxNetAdp.sys
Followup: MachineOwner
---------
0: kd> lmvm VBoxNetAdp
start end module name
fffff880`03083000 fffff880`030aa000 VBoxNetAdp (no symbols)
Loaded symbol image file: VBoxNetAdp.sys
Image path: \SystemRoot\system32\DRIVERS\VBoxNetAdp.sys
Image name: VBoxNetAdp.sys
Timestamp: Fri Apr 12 05:40:14 2013 (5167D67E)
CheckSum: 0002AC27
ImageSize: 00027000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Change History (4)
comment:1 by , 12 years ago
comment:2 by , 11 years ago
I had the same problem (but it's gone now, without I have really done something).
I'll post a complete kernel dump here:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\070314-27565-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`002b76c2?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`08437c32?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c3c0?
Symbol search path is: symsrv*symsrv.dll*c:\localsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`03058000 PsLoadedModuleList = 0xfffff800`0329b890
Debug session time: Thu Jul 3 20:22:22.486 2014 (UTC + 2:00)
System Uptime: 0 days 12:05:52.703
Loading Kernel Symbols
...............................................................
................................................................
..............................................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa8007057bb0, fffff80000b9c3d8, fffffa80074137c0}
Unable to load image \SystemRoot\system32\DRIVERS\VBoxNetAdp.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for VBoxNetAdp.sys
*** ERROR: Module load completed but symbols could not be loaded for VBoxNetAdp.sys
Probably caused by : ntkrnlmp
Followup: MachineOwner
---------
And with !analyze -v:
******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_POWER_STATE_FAILURE (9f) A driver is causing an inconsistent power state. Arguments: Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time Arg2: fffffa8007057bb0, Physical Device Object of the stack Arg3: fffff80000b9c3d8, Functional Device Object of the stack Arg4: fffffa80074137c0, The blocked IRP Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 3 IMAGE_NAME: ntkrnlmp DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: ntkrnlmp FAULTING_MODULE: fffff88000db9000 VBoxNetAdp IRP_ADDRESS: fffffa80074137c0 DEVICE_OBJECT: fffffa800a397050 DRIVER_OBJECT: fffffa800a37e220 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 STACK_TEXT: fffff800`00b9c388 fffff800`0313d8d2 : 00000000`0000009f 00000000`00000003 fffffa80`07057bb0 fffff800`00b9c3d8 : nt!KeBugCheckEx fffff800`00b9c390 fffff800`030d885c : fffff800`00b9c4c0 fffff800`00b9c4c0 00000000`00000000 00000000`00000003 : nt! ?? ::FNODOBFM::`string'+0x33af0 fffff800`00b9c430 fffff800`030d86f6 : fffffa80`0a93c758 fffffa80`0a93c758 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c fffff800`00b9c4a0 fffff800`030d85de : 00000065`676f3757 fffff800`00b9cb18 00000000`002a998e fffff800`0324c448 : nt!KiProcessExpiredTimerList+0xc6 fffff800`00b9caf0 fffff800`030d83c7 : 00000018`b371f8c5 00000018`002a998e 00000018`b371f83d 00000000`0000008e : nt!KiTimerExpiration+0x1be fffff800`00b9cb90 fffff800`030c58ca : fffff800`03248e80 fffff800`03256cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277 fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: X64_0x9F_3_IMAGE_ntkrnlmp BUCKET_ID: X64_0x9F_3_IMAGE_ntkrnlmp Followup: MachineOwner ---------
comment:3 by , 11 years ago
| Description: | modified (diff) |
|---|
comment:4 by , 9 years ago
| Resolution: | → obsolete |
|---|---|
| Status: | new → closed |
Please reopen if still relevant with a recent VirtualBox release.
Note:
See TracTickets
for help on using tickets.
The issue has already been reported and Work is in progress for it.
Are there any third party network filters installed like Antivirus etc and whats the network card you are using.
What is the host and guest version and are you using bridged networking.?
Request you to please post a complete kernel dump file.