Opened 9 years ago
Last modified 9 years ago
#14112 new defect
BSoD in VBoxNetAdp6.sys with STOP 0x9F
Reported by: | ohm | Owned by: | |
---|---|---|---|
Component: | other | Version: | |
Keywords: | Cc: | ||
Guest type: | other | Host type: | Windows |
Description
Version: VirtualBox 5.0 Beta 2 (previously same error in VBoxNetAdp.sys in 4.3.26, 4.2.?). I'm trying out the beta to try to get past this annoying error. The last few times I've followed steps similar to
http://dottech.org/101997/how-to-uninstall-virtualbox-drivers-on-windows/
to remove all traces of any drivers/any registry settings I could find to remove any prior copy of VirtualBox
This issue is most similar to: https://www.virtualbox.org/ticket/11730
Win7x64 Host, Bridged Networking turned on, the VirtualBox program isn't running when the crash occurs.
Network Adapters:
- Intel(R)82567V-2 Gigabit Network Connection on latest driver: 10.0.6.0 ( confirmed via windows and HP websites )
- VirtualBox Host-Only Ethernet Adapter
Minidump for v5.0 Beta2:
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\051315-86174-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`0ec26c32? DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`0023a662? DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9a500? ************* Symbol Path validation summary ************** Response Time (ms) Location Deferred symsrv*symsrv.dll*c:\extracts\ms debuggger\symbols*http://msdl.microsoft.com/downloads/symbols Symbol search path is: symsrv*symsrv.dll*c:\extracts\ms debuggger\symbols*http://msdl.microsoft.com/downloads/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.18839.amd64fre.win7sp1_gdr.150427-0707 Machine Name: Kernel base = 0xfffff800`02c1b000 PsLoadedModuleList = 0xfffff800`02e62730 Debug session time: Wed May 13 06:57:38.999 2015 (UTC - 7:00) System Uptime: 0 days 21:49:09.234 Loading Kernel Symbols ............................................................... ................................................................ ........................................ Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 9F, {3, fffffa8009aa44d0, fffff80000b9a518, fffffa8014ff7010} Unable to load image \SystemRoot\system32\DRIVERS\VBoxNetAdp6.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for VBoxNetAdp6.sys *** ERROR: Module load completed but symbols could not be loaded for VBoxNetAdp6.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: fffffa8009aa44d0, Physical Device Object of the stack Arg3: fffff80000b9a518, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: fffffa8014ff7010, The blocked IRP Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 3 IMAGE_NAME: ntkrnlmp DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: ntkrnlmp FAULTING_MODULE: fffff8800413e000 VBoxNetAdp6 IRP_ADDRESS: fffffa8014ff7010 DEVICE_OBJECT: fffffa800c4cd050 DRIVER_OBJECT: fffffa800c1f1ce0 CUSTOMER_CRASH_COUNT: 1 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: FFFFF80000BA0FB0 STACK_TEXT: fffff800`00b9a4c8 fffff800`02cfe510 : 00000000`0000009f 00000000`00000003 fffffa80`09aa44d0 fffff800`00b9a518 : nt!KeBugCheckEx fffff800`00b9a4d0 fffff800`02c9b72c : fffff800`00b9a600 fffff800`00b9a600 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x324a0 fffff800`00b9a570 fffff800`02c9b5c6 : fffffa80`0d4d5748 fffffa80`0d4d5748 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c fffff800`00b9a5e0 fffff800`02c9b4ae : 000000b6`e2fdfdf7 fffff800`00b9ac58 00000000`004cd4a7 fffff800`02e12768 : nt!KiProcessExpiredTimerList+0xc6 fffff800`00b9ac30 fffff800`02c9b297 : 00000031`e222c6c4 00000031`004cd4a7 00000031`e222c6c3 00000000`000000a7 : nt!KiTimerExpiration+0x1be fffff800`00b9acd0 fffff800`02c875ca : fffff800`02e0ee80 fffff800`02e1ccc0 00000000`00000000 fffff880`013b24c0 : nt!KiRetireDpcList+0x277 fffff800`00b9ad80 00000000`00000000 : fffff800`00b9b000 fffff800`00b95000 fffff800`00b9ad40 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 VBoxNetAdp6 start end module name fffff880`0413e000 fffff880`04161000 VBoxNetAdp6 T (no symbols) Loaded symbol image file: VBoxNetAdp6.sys Image path: \SystemRoot\system32\DRIVERS\VBoxNetAdp6.sys Image name: VBoxNetAdp6.sys Timestamp: Tue Apr 14 11:38:41 2015 (552D5EB1) CheckSum: 0001F0DE ImageSize: 00023000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 0: kd> !irp fffffa8014ff7010 1 Irp is active with 3 stacks 2 is current (= 0xfffffa8014ff7128) No Mdl: No System Buffer: Thread 00000000: Irp stack trace. Flags = 00000000 ThreadListEntry.Flink = fffffa8014ff7030 ThreadListEntry.Blink = fffffa8014ff7030 IoStatus.Status = c00000bb IoStatus.Information = 00000000 RequestorMode = 00000000 Cancel = 00 CancelIrql = 0 ApcEnvironment = 00 UserIosb = 00000000 UserEvent = 00000000 Overlay.AsynchronousParameters.UserApcRoutine = 00000000 Overlay.AsynchronousParameters.UserApcContext = 00000000 Overlay.AllocationSize = 00000000 - 00000000 CancelRoutine = 00000000 UserBuffer = 00000000 &Tail.Overlay.DeviceQueueEntry = fffffa8014ff7088 Tail.Overlay.Thread = 00000000 Tail.Overlay.AuxiliaryBuffer = 00000000 Tail.Overlay.ListEntry.Flink = fffffa80139c8eb8 Tail.Overlay.ListEntry.Blink = fffff80002e44bc0 Tail.Overlay.CurrentStackLocation = fffffa8014ff7128 Tail.Overlay.OriginalFileObject = 00000000 Tail.Apc = 00000000 Tail.CompletionKey = 00000000 cmd flg cl Device File Completion-Context [ 0, 0] 0 0 00000000 00000000 00000000-00000000 Args: 00000000 00000000 00000000 00000000 >[ 16, 3] 0 e1 fffffa800c4cd050 00000000 fffff80002ee1210-fffffa800ec22a30 Success Error Cancel pending \Driver\VBoxNetAdp nt!PopSystemIrpCompletion Args: 00015400 00000000 00000005 00000003 [ 0, 0] 0 0 00000000 00000000 00000000-fffffa800ec22a30 Args: 00000000 00000000 00000000 00000000 0: kd> !devobj fffffa800c4cd050 f fffff80002e45070: Unable to get value of ObpRootDirectoryObject Device object (fffffa800c4cd050) is for: InfoMask field not found for _OBJECT_HEADER at fffffa800c4cd020 \Driver\VBoxNetAdp DriverObject fffffa800c1f1ce0 Current Irp 00000000 RefCount 0 Type 00000017 Flags 00002050 DevExt fffffa800c4cd1a0 DevObjExt fffffa800c4ce8e0 ExtensionFlags (0x00000800) DOE_DEFAULT_SD_PRESENT Characteristics (0x00000100) FILE_DEVICE_SECURE_OPEN AttachedTo (Lower) fffffa8009aa44d0 \Driver\PnpManager Device queue is not busy. 0: kd> !drvobj fffffa800c1f1ce0 f fffff80002e45070: Unable to get value of ObpRootDirectoryObject fffff80002e45070: Unable to get value of ObpRootDirectoryObject Driver object (fffffa800c1f1ce0) is for: \Driver\VBoxNetAdp Driver Extension List: (id , addr) Device Object list: fffffa800c4cd050 DriverEntry: fffff8800413f860 VBoxNetAdp6 DriverStartIo: 00000000 DriverUnload: fffff880016aecd0 ndis!ndisMUnloadEx AddDevice: 00000000 Dispatch routines: [00] IRP_MJ_CREATE fffff88001608920 ndis!ndisCreateIrpHandler [01] IRP_MJ_CREATE_NAMED_PIPE fffff8800169e490 ndis!ndisDummyIrpHandler [02] IRP_MJ_CLOSE fffff88001608160 ndis!ndisCloseIrpHandler [03] IRP_MJ_READ fffff8800169e490 ndis!ndisDummyIrpHandler [04] IRP_MJ_WRITE fffff8800169e490 ndis!ndisDummyIrpHandler [05] IRP_MJ_QUERY_INFORMATION fffff8800169e490 ndis!ndisDummyIrpHandler [06] IRP_MJ_SET_INFORMATION fffff8800169e490 ndis!ndisDummyIrpHandler [07] IRP_MJ_QUERY_EA fffff8800169e490 ndis!ndisDummyIrpHandler [08] IRP_MJ_SET_EA fffff8800169e490 ndis!ndisDummyIrpHandler [09] IRP_MJ_FLUSH_BUFFERS fffff8800169e490 ndis!ndisDummyIrpHandler [0a] IRP_MJ_QUERY_VOLUME_INFORMATION fffff8800169e490 ndis!ndisDummyIrpHandler [0b] IRP_MJ_SET_VOLUME_INFORMATION fffff8800169e490 ndis!ndisDummyIrpHandler [0c] IRP_MJ_DIRECTORY_CONTROL fffff8800169e490 ndis!ndisDummyIrpHandler [0d] IRP_MJ_FILE_SYSTEM_CONTROL fffff8800169e490 ndis!ndisDummyIrpHandler [0e] IRP_MJ_DEVICE_CONTROL fffff8800169e020 ndis!ndisDeviceControlIrpHandler [0f] IRP_MJ_INTERNAL_DEVICE_CONTROL fffff8800169e490 ndis!ndisDummyIrpHandler [10] IRP_MJ_SHUTDOWN fffff8800169e490 ndis!ndisDummyIrpHandler [11] IRP_MJ_LOCK_CONTROL fffff8800169e490 ndis!ndisDummyIrpHandler [12] IRP_MJ_CLEANUP fffff8800169e490 ndis!ndisDummyIrpHandler [13] IRP_MJ_CREATE_MAILSLOT fffff8800169e490 ndis!ndisDummyIrpHandler [14] IRP_MJ_QUERY_SECURITY fffff8800169e490 ndis!ndisDummyIrpHandler [15] IRP_MJ_SET_SECURITY fffff8800169e490 ndis!ndisDummyIrpHandler [16] IRP_MJ_POWER fffff88001652c60 ndis!ndisPowerDispatch [17] IRP_MJ_SYSTEM_CONTROL fffff88001672ee0 ndis!ndisWMIDispatch [18] IRP_MJ_DEVICE_CHANGE fffff8800169e490 ndis!ndisDummyIrpHandler [19] IRP_MJ_QUERY_QUOTA fffff8800169e490 ndis!ndisDummyIrpHandler [1a] IRP_MJ_SET_QUOTA fffff8800169e490 ndis!ndisDummyIrpHandler [1b] IRP_MJ_PNP fffff880016bc560 ndis!ndisPnPDispatch
Here's a 4.3.26 example:
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\040715-17799-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 ?fffff8a0`0023dc32? DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`02dcfc32? DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`042d4500? ************* Symbol Path validation summary ************** Response Time (ms) Location Deferred symsrv*symsrv.dll*c:\extracts\ms debuggger\symbols*http://msdl.microsoft.com/downloads/symbols Symbol search path is: symsrv*symsrv.dll*c:\extracts\ms debuggger\symbols*http://msdl.microsoft.com/downloads/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.18741.amd64fre.win7sp1_gdr.150202-1526 Machine Name: Kernel base = 0xfffff800`02c08000 PsLoadedModuleList = 0xfffff800`02e4c890 Debug session time: Mon Apr 6 20:24:15.313 2015 (UTC - 7:00) System Uptime: 12 days 4:51:38.831 Loading Kernel Symbols ............................................................... ................................................................ ........................................ Loading User Symbols Loading unloaded module list ..................... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 9F, {3, fffffa8009aa6060, fffff800042d4518, fffffa800d2fdd60} 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 --------- 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: fffffa8009aa6060, Physical Device Object of the stack Arg3: fffff800042d4518, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: fffffa800d2fdd60, The blocked IRP Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 3 IMAGE_NAME: ntkrnlmp DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: ntkrnlmp FAULTING_MODULE: fffff88005279000 VBoxNetAdp IRP_ADDRESS: fffffa800d2fdd60 DEVICE_OBJECT: fffffa800c321050 DRIVER_OBJECT: fffffa800aa7ae70 CUSTOMER_CRASH_COUNT: 1 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: FFFFF800042DAFB0 STACK_TEXT: fffff800`042d44c8 fffff800`02cedb92 : 00000000`0000009f 00000000`00000003 fffffa80`09aa6060 fffff800`042d4518 : nt!KeBugCheckEx fffff800`042d44d0 fffff800`02c88cfc : fffff800`042d4600 fffff800`042d4600 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0 fffff800`042d4570 fffff800`02c88b96 : fffff800`02e2f140 00000000`04073b69 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c fffff800`042d45e0 fffff800`02c88a7e : 00000996`bb12dbac fffff800`042d4c58 00000000`04073b69 fffff800`02dfcfa8 : nt!KiProcessExpiredTimerList+0xc6 fffff800`042d4c30 fffff800`02c88867 : 0000029d`89aab1c1 0000029d`04073b69 0000029d`89aab16a 00000000`00000069 : nt!KiTimerExpiration+0x1be fffff800`042d4cd0 fffff800`02c74bca : fffff800`02df9e80 fffff800`02e07cc0 00000000`00000000 fffff880`012234c0 : nt!KiRetireDpcList+0x277 fffff800`042d4d80 00000000`00000000 : fffff800`042d5000 fffff800`042cf000 fffff800`042d4d40 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 VBoxNetAdp start end module name fffff880`05279000 fffff880`052a1000 VBoxNetAdp T (no symbols) Loaded symbol image file: VBoxNetAdp.sys Image path: \SystemRoot\system32\DRIVERS\VBoxNetAdp.sys Image name: VBoxNetAdp.sys Timestamp: Mon Mar 16 09:35:44 2015 (55070660) CheckSum: 00030F13 ImageSize: 00028000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 0: kd> !irp fffffa800d2fdd60 1 Irp is active with 3 stacks 2 is current (= 0xfffffa800d2fde78) No Mdl: No System Buffer: Thread 00000000: Irp stack trace. Flags = 00000000 ThreadListEntry.Flink = fffffa800d2fdd80 ThreadListEntry.Blink = fffffa800d2fdd80 IoStatus.Status = c00000bb IoStatus.Information = 00000000 RequestorMode = 00000000 Cancel = 00 CancelIrql = 0 ApcEnvironment = 00 UserIosb = 00000000 UserEvent = 00000000 Overlay.AsynchronousParameters.UserApcRoutine = 00000000 Overlay.AsynchronousParameters.UserApcContext = 00000000 Overlay.AllocationSize = 00000000 - 00000000 CancelRoutine = 00000000 UserBuffer = 00000000 &Tail.Overlay.DeviceQueueEntry = fffffa800d2fddd8 Tail.Overlay.Thread = 00000000 Tail.Overlay.AuxiliaryBuffer = 00000000 Tail.Overlay.ListEntry.Flink = fffffa800de5fd68 Tail.Overlay.ListEntry.Blink = fffff80002e2ed20 Tail.Overlay.CurrentStackLocation = fffffa800d2fde78 Tail.Overlay.OriginalFileObject = 00000000 Tail.Apc = 00000000 Tail.CompletionKey = 00000000 cmd flg cl Device File Completion-Context [ 0, 0] 0 0 00000000 00000000 00000000-00000000 Args: 00000000 00000000 00000000 00000000 >[ 16, 3] 0 e1 fffffa800c321050 00000000 fffff80002ecb210-fffffa800d27ba50 Success Error Cancel pending \Driver\VBoxNetAdp nt!PopSystemIrpCompletion Args: 00015400 00000000 00000005 00000003 [ 0, 0] 0 0 00000000 00000000 00000000-fffffa800d27ba50 Args: 00000000 00000000 00000000 00000000 0: kd> !devobj fffffa800c321050 f fffff80002e2f1d0: Unable to get value of ObpRootDirectoryObject Device object (fffffa800c321050) is for: InfoMask field not found for _OBJECT_HEADER at fffffa800c321020 \Driver\VBoxNetAdp DriverObject fffffa800aa7ae70 Current Irp 00000000 RefCount 0 Type 00000017 Flags 00002050 DevExt fffffa800c3211a0 DevObjExt fffffa800c3228e0 ExtensionFlags (0x00000800) DOE_DEFAULT_SD_PRESENT Characteristics (0x00000100) FILE_DEVICE_SECURE_OPEN AttachedTo (Lower) fffffa8009aa6060 \Driver\PnpManager Device queue is not busy. 0: kd> !drvobj fffffa800aa7ae70 f fffff80002e2f1d0: Unable to get value of ObpRootDirectoryObject fffff80002e2f1d0: Unable to get value of ObpRootDirectoryObject Driver object (fffffa800aa7ae70) is for: \Driver\VBoxNetAdp Driver Extension List: (id , addr) Device Object list: fffffa800c81f4d0: Could not read device object DriverEntry: fffff8800527e0e0 VBoxNetAdp DriverStartIo: 00000000 DriverUnload: fffff880017c04a0 ndis!ndisMUnload AddDevice: 00000000 Dispatch routines: [00] IRP_MJ_CREATE fffff88001716920 ndis!ndisCreateIrpHandler [01] IRP_MJ_CREATE_NAMED_PIPE fffff880017ac490 ndis!ndisDummyIrpHandler [02] IRP_MJ_CLOSE fffff88001716160 ndis!ndisCloseIrpHandler [03] IRP_MJ_READ fffff880017ac490 ndis!ndisDummyIrpHandler [04] IRP_MJ_WRITE fffff880017ac490 ndis!ndisDummyIrpHandler [05] IRP_MJ_QUERY_INFORMATION fffff880017ac490 ndis!ndisDummyIrpHandler [06] IRP_MJ_SET_INFORMATION fffff880017ac490 ndis!ndisDummyIrpHandler [07] IRP_MJ_QUERY_EA fffff880017ac490 ndis!ndisDummyIrpHandler [08] IRP_MJ_SET_EA fffff880017ac490 ndis!ndisDummyIrpHandler [09] IRP_MJ_FLUSH_BUFFERS fffff880017ac490 ndis!ndisDummyIrpHandler [0a] IRP_MJ_QUERY_VOLUME_INFORMATION fffff880017ac490 ndis!ndisDummyIrpHandler [0b] IRP_MJ_SET_VOLUME_INFORMATION fffff880017ac490 ndis!ndisDummyIrpHandler [0c] IRP_MJ_DIRECTORY_CONTROL fffff880017ac490 ndis!ndisDummyIrpHandler [0d] IRP_MJ_FILE_SYSTEM_CONTROL fffff880017ac490 ndis!ndisDummyIrpHandler [0e] IRP_MJ_DEVICE_CONTROL fffff880017ac020 ndis!ndisDeviceControlIrpHandler [0f] IRP_MJ_INTERNAL_DEVICE_CONTROL fffff880017ac490 ndis!ndisDummyIrpHandler [10] IRP_MJ_SHUTDOWN fffff880017ac490 ndis!ndisDummyIrpHandler [11] IRP_MJ_LOCK_CONTROL fffff880017ac490 ndis!ndisDummyIrpHandler [12] IRP_MJ_CLEANUP fffff880017ac490 ndis!ndisDummyIrpHandler [13] IRP_MJ_CREATE_MAILSLOT fffff880017ac490 ndis!ndisDummyIrpHandler [14] IRP_MJ_QUERY_SECURITY fffff880017ac490 ndis!ndisDummyIrpHandler [15] IRP_MJ_SET_SECURITY fffff880017ac490 ndis!ndisDummyIrpHandler [16] IRP_MJ_POWER fffff88001760c60 ndis!ndisPowerDispatch [17] IRP_MJ_SYSTEM_CONTROL fffff88001780ee0 ndis!ndisWMIDispatch [18] IRP_MJ_DEVICE_CHANGE fffff880017ac490 ndis!ndisDummyIrpHandler [19] IRP_MJ_QUERY_QUOTA fffff880017ac490 ndis!ndisDummyIrpHandler [1a] IRP_MJ_SET_QUOTA fffff880017ac490 ndis!ndisDummyIrpHandler [1b] IRP_MJ_PNP fffff880017ca560 ndis!ndisPnPDispatch
I've experienced 8 similar crashes since March 3/25 using different versions of VirtualBox. It would seem that if you need to reproduce this error somewhat reliably, my machine can do it.
Some additional information:
This crash usually happens overnight. However, this morning when I came in, I noticed my PC had no internet connection. Unplugging/reconnecting the ethernet cable didn't refresh it, so I decided to restart my computer. The restart was taking a while to shutdown the computer. However at that point, I had to leave my cube and help someone else with an issue elsewhere. When I came back to login I noticed another 9F Minidump had been created.
In attempting to recreate this crash, it might be worth looking into breaking or interrupting the internet connection to the PC used for testing and then hibernating and/or restarting the computer.
The cmd/flg are the same but the addresses might be slightly different, so I've included another report from WinDbg(x64):