Multiple blue screens traced to VBox USB subsystem

Discussions related to using VirtualBox on Windows hosts.
Post Reply
LukaBloomRox
Posts: 2
Joined: 16. Dec 2023, 02:53

Multiple blue screens traced to VBox USB subsystem

Post by LukaBloomRox »

Hello, VBox experts.

I'm getting at least two blue screens every day, tracable back to the VBox USB subsystem.
Any idea on next steps?

Many thanks !

Code: Select all

OS Name	Microsoft Windows 11 Home
Version	10.0.22631 Build 22631
Other OS Description 	Not Available
OS Manufacturer	Microsoft Corporation
System Name	KHAPMYLES
System Manufacturer	ASUSTeK COMPUTER INC.
System Model	ASUS TUF Gaming F15 FX507ZU4_FX507ZU
System Type	x64-based PC
System SKU	
Processor	12th Gen Intel(R) Core(TM) i7-12700H, 2300 Mhz, 14 Core(s), 20 Logical Processor(s)
BIOS Version/Date	American Megatrends International, LLC. FX507ZU4.321, 2023-07-19
SMBIOS Version	3.5
Embedded Controller Version	0.69
BIOS Mode	UEFI
BaseBoard Manufacturer	ASUSTeK COMPUTER INC.
BaseBoard Product	FX507ZU4
BaseBoard Version	1.0
Platform Role	Mobile
Secure Boot State	On
PCR7 Configuration	Elevation Required to View
Windows Directory	C:\Windows
System Directory	C:\Windows\system32
Boot Device	\Device\HarddiskVolume1
Locale	United States
Hardware Abstraction Layer	Version = "10.0.22621.2506"
User Name	KhapMyles\smdea
Time Zone	Eastern Standard Time
Installed Physical Memory (RAM)	32.0 GB
Total Physical Memory	31.6 GB
Available Physical Memory	6.29 GB
Total Virtual Memory	67.6 GB
Available Virtual Memory	26.9 GB
Page File Space	36.0 GB
Page File	C:\pagefile.sys
Kernel DMA Protection	On
Virtualization-based security	Running
Virtualization-based security Required Security Properties	
Virtualization-based security Available Security Properties	Base Virtualization Support, Secure Boot, DMA Protection, UEFI Code Readonly, Mode Based Execution Control, APIC Virtualization
Virtualization-based security Services Configured	Hypervisor enforced Code Integrity
Virtualization-based security Services Running	Hypervisor enforced Code Integrity
Windows Defender Application Control policy	Enforced
Windows Defender Application Control user mode policy	Off
Device Encryption Support	Elevation Required to View
A hypervisor has been detected. Features required for Hyper-V will not be displayed.	



Result of analysis of most recent minidump:

Code: Select all

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

Microsoft (R) Windows Debugger Version 10.0.25877.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\MylesDropbox\Dropbox\Advocacy\VirtualBox\121423-19921-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 22621 MP (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff800`74600000 PsLoadedModuleList = 0xfffff800`752134a0
Debug session time: Thu Dec 14 12:29:37.335 2023 (UTC - 5:00)
System Uptime: 0 days 0:25:52.352
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................................................
........
Loading User Symbols

Loading unloaded module list
..........................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`74a16b00 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff58f`6bbe3840=00000000000000ca
4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PNP_DETECTED_FATAL_ERROR (ca)
PnP encountered a severe error, either as a result of a problem in a driver or
a problem in PnP itself.  The first argument describes the nature of the
problem, the second argument is the address of the PDO.  The other arguments
vary depending on argument 1.
Arguments:
Arg1: 0000000000000002, Invalid PDO
	An API which requires a PDO has been called with either an FDO,
	a PDO which hasn't been initialized yet (returned to PnP in a
	QueryDeviceRelation/BusRelations), or some random piece of
	memory.
Arg2: ffff9d81c3fc7060, Purported PDO.
Arg3: 0000000000000000, Driver object.
Arg4: 0000000000000000

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 639

    Key  : Analysis.Elapsed.mSec
    Value: 7811

    Key  : Analysis . IO.Other.Mb
    Value: 0

    Key  : Analysis . IO.Read.Mb
    Value: 0

    Key  : Analysis . IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 93

    Key  : Analysis.Init.Elapsed.mSec
    Value: 7276

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 106

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xca

    Key  : Dump.Attributes.AsUlong
    Value: 1808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0xCA_2_VBoxUSBMon!unknown_function

    Key  : Failure.Hash
    Value: {f383f969-2d54-027f-581d-9ff3d707fa92}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 21631230

    Key  : Hypervisor.Flags.ValueHex
    Value: 14a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7


BUGCHECK_CODE:  ca

BUGCHECK_P1: 2

BUGCHECK_P2: ffff9d81c3fc7060

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FILE_IN_CAB:  121423-19921-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

DEVICE_OBJECT: ffff9d81c3fc7060

DRIVER_OBJECT: ffff9d81be776cc0

IMAGE_NAME:  VBoxUSBMon.sys

FAULTING_MODULE: fffff8007bc90000 UsbHub3

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
fffff58f`6bbe3838 fffff800`74eafb3d     : 00000000`000000ca 00000000`00000002 ffff9d81`c3fc7060 00000000`00000000 : nt!KeBugCheckEx
fffff58f`6bbe3840 fffff800`90c439e8     : ffff9d81`c8ff55b0 ffff9d81`c3fc7060 ffff9d81`c3f48290 00000000`00000001 : nt!IoGetDevicePropertyData+0x2176ed
fffff58f`6bbe3890 ffff9d81`c8ff55b0     : ffff9d81`c3fc7060 ffff9d81`c3f48290 00000000`00000001 00000000`00000600 : VBoxUSBMon+0x39e8
fffff58f`6bbe3898 ffff9d81`c3fc7060     : ffff9d81`c3f48290 00000000`00000001 00000000`00000600 ffff9d81`c3f483a4 : 0xffff9d81`c8ff55b0
fffff58f`6bbe38a0 ffff9d81`c3f48290     : 00000000`00000001 00000000`00000600 ffff9d81`c3f483a4 fffff58f`6bbe38d4 : 0xffff9d81`c3fc7060
fffff58f`6bbe38a8 00000000`00000001     : 00000000`00000600 ffff9d81`c3f483a4 fffff58f`6bbe38d4 fffff58f`6bbe38d0 : 0xffff9d81`c3f48290
fffff58f`6bbe38b0 00000000`00000600     : ffff9d81`c3f483a4 fffff58f`6bbe38d4 fffff58f`6bbe38d0 00000000`00000180 : 0x1
fffff58f`6bbe38b8 ffff9d81`c3f483a4     : fffff58f`6bbe38d4 fffff58f`6bbe38d0 00000000`00000180 ffffb003`d4edb000 : 0x600
fffff58f`6bbe38c0 fffff58f`6bbe38d4     : fffff58f`6bbe38d0 00000000`00000180 ffffb003`d4edb000 00000000`00000001 : 0xffff9d81`c3f483a4
fffff58f`6bbe38c8 fffff58f`6bbe38d0     : 00000000`00000180 ffffb003`d4edb000 00000000`00000001 00000000`00000000 : 0xfffff58f`6bbe38d4
fffff58f`6bbe38d0 00000000`00000180     : ffffb003`d4edb000 00000000`00000001 00000000`00000000 00000000`00020000 : 0xfffff58f`6bbe38d0
fffff58f`6bbe38d8 ffffb003`d4edb000     : 00000000`00000001 00000000`00000000 00000000`00020000 00000000`00000000 : 0x180
fffff58f`6bbe38e0 00000000`00000001     : 00000000`00000000 00000000`00020000 00000000`00000000 00000000`0000ffff : 0xffffb003`d4edb000
fffff58f`6bbe38e8 00000000`00000000     : 00000000`00020000 00000000`00000000 00000000`0000ffff 00000000`000000ff : 0x1


SYMBOL_NAME:  VBoxUSBMon+39e8

MODULE_NAME: VBoxUSBMon

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  39e8

FAILURE_BUCKET_ID:  0xCA_2_VBoxUSBMon!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f383f969-2d54-027f-581d-9ff3d707fa92}

Followup:     MachineOwner
---------
fth0
Volunteer
Posts: 5678
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Multiple blue screens traced to VBox USB subsystem

Post by fth0 »

I'd suggest to create a ticket in the Bugtracker.
LukaBloomRox
Posts: 2
Joined: 16. Dec 2023, 02:53

Re: Multiple blue screens traced to VBox USB subsystem

Post by LukaBloomRox »

I got another blue screen today :

Code: Select all

Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\123023-19031-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 22621 MP (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff801`5ec00000 PsLoadedModuleList = 0xfffff801`5f8134a0
Debug session time: Sat Dec 30 22:51:21.742 2023 (UTC - 5:00)
System Uptime: 10 days 1:41:50.130
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck CA, {2, ffffbd049ead9dd0, 0, 0}

*** WARNING: Unable to verify timestamp for VBoxUSBMon.sys
*** ERROR: Module load completed but symbols could not be loaded for VBoxUSBMon.sys
Probably caused by : VBoxUSBMon.sys ( VBoxUSBMon+39e8 )

Followup:     MachineOwner
---------

9: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PNP_DETECTED_FATAL_ERROR (ca)
PnP encountered a severe error, either as a result of a problem in a driver or
a problem in PnP itself.  The first argument describes the nature of the
problem, the second argument is the address of the PDO.  The other arguments
vary depending on argument 1.
Arguments:
Arg1: 0000000000000002, Invalid PDO
	An API which requires a PDO has been called with either an FDO,
	a PDO which hasn't been initialized yet (returned to PnP in a
	QueryDeviceRelation/BusRelations), or some random piece of
	memory.
Arg2: ffffbd049ead9dd0, Purported PDO.
Arg3: 0000000000000000, Driver object.
Arg4: 0000000000000000

Debugging Details:
------------------


KEY_VALUES_STRING: 1


STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.22621.2861 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER:  ASUSTeK COMPUTER INC.

SYSTEM_PRODUCT_NAME:  ASUS TUF Gaming F15 FX507ZU4_FX507ZU

SYSTEM_VERSION:  1.0

BIOS_VENDOR:  American Megatrends International, LLC.

BIOS_VERSION:  FX507ZU4.321

BIOS_DATE:  07/19/2023

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  FX507ZU4

BASEBOARD_VERSION:  1.0

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

DUMP_TYPE:  2

BUGCHECK_P1: 2

BUGCHECK_P2: ffffbd049ead9dd0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BUGCHECK_STR:  0xCA_2

DEVICE_OBJECT: ffffbd049ead9dd0

DRIVER_OBJECT: ffffbd048fe18e00

IMAGE_NAME:  VBoxUSBMon.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  643d68fd

FAULTING_MODULE: fffff8018a170000 UsbHub3

CPU_COUNT: 14

CPU_MHZ: a80

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9a

CPU_STEPPING: 3

CPU_MICROCODE: 6,9a,3,0 (F,M,S,R)  SIG: 421'00000000 (cache) 421'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  KHAPMYLES

ANALYSIS_SESSION_TIME:  12-30-2023 23:46:15.0439

ANALYSIS_VERSION: 10.0.17763.132 amd64fre

LAST_CONTROL_TRANSFER:  from fffff8015f4afb3d to fffff8015f016b00

STACK_TEXT:  
fffff58a`73325838 fffff801`5f4afb3d : 00000000`000000ca 00000000`00000002 ffffbd04`9ead9dd0 00000000`00000000 : nt!KeBugCheckEx
fffff58a`73325840 fffff801`77e139e8 : ffffbd04`f8d7d5e0 ffffbd04`9ead9dd0 ffffbd04`b637a010 00000000`00000001 : nt!IoGetDevicePropertyData+0x2176ed
fffff58a`73325890 ffffbd04`f8d7d5e0 : ffffbd04`9ead9dd0 ffffbd04`b637a010 00000000`00000001 00000000`00000600 : VBoxUSBMon+0x39e8
fffff58a`73325898 ffffbd04`9ead9dd0 : ffffbd04`b637a010 00000000`00000001 00000000`00000600 ffffbd04`b637a124 : 0xffffbd04`f8d7d5e0
fffff58a`733258a0 ffffbd04`b637a010 : 00000000`00000001 00000000`00000600 ffffbd04`b637a124 fffff58a`733258d4 : 0xffffbd04`9ead9dd0
fffff58a`733258a8 00000000`00000001 : 00000000`00000600 ffffbd04`b637a124 fffff58a`733258d4 fffff58a`733258d0 : 0xffffbd04`b637a010
fffff58a`733258b0 00000000`00000600 : ffffbd04`b637a124 fffff58a`733258d4 fffff58a`733258d0 00000000`00000740 : 0x1
fffff58a`733258b8 ffffbd04`b637a124 : fffff58a`733258d4 fffff58a`733258d0 00000000`00000740 00000000`00000000 : 0x600
fffff58a`733258c0 fffff58a`733258d4 : fffff58a`733258d0 00000000`00000740 00000000`00000000 00000000`00760000 : 0xffffbd04`b637a124
fffff58a`733258c8 fffff58a`733258d0 : 00000000`00000740 00000000`00000000 00000000`00760000 ffffbd04`b6379fe0 : 0xfffff58a`733258d4
fffff58a`733258d0 00000000`00000740 : 00000000`00000000 00000000`00760000 ffffbd04`b6379fe0 ffffbd04`b6379fe8 : 0xfffff58a`733258d0
fffff58a`733258d8 00000000`00000000 : 00000000`00760000 ffffbd04`b6379fe0 ffffbd04`b6379fe8 fffff801`5ee5d3a7 : 0x740


THREAD_SHA1_HASH_MOD_FUNC:  24187000e79989317d2277fe92f793acb122ef88

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  76d76611f5506b19412c62eb33c2c4946c3c1161

THREAD_SHA1_HASH_MOD:  ef5dc2f6d773331baf3d04bf930672a39fe33643

FOLLOWUP_IP: 
VBoxUSBMon+39e8
fffff801`77e139e8 ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  VBoxUSBMon+39e8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: VBoxUSBMon

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  39e8

FAILURE_BUCKET_ID:  0xCA_2_VBoxUSBMon!unknown_function

BUCKET_ID:  0xCA_2_VBoxUSBMon!unknown_function

PRIMARY_PROBLEM_CLASS:  0xCA_2_VBoxUSBMon!unknown_function

TARGET_TIME:  2023-12-31T03:51:21.000Z

OSBUILD:  22621

OSSERVICEPACK:  2861

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.22621.2861

ANALYSIS_SESSION_ELAPSED_TIME:  3e1

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xca_2_vboxusbmon!unknown_function

FAILURE_ID_HASH:  {f383f969-2d54-027f-581d-9ff3d707fa92}

Followup:     MachineOwner
---------
Last edited by scottgus1 on 31. Dec 2023, 15:20, edited 1 time in total.
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Multiple blue screens traced to VBox USB subsystem

Post by scottgus1 »

Please put large walls of text in CODE tags, see the forum formatting </> button.

This doesn't happen often on folks' Virtualbox. There could be another app plugging into USB on your host, like Wireshark's USB monitor or over-aggressive 3rd-party antivirus. Or the USB ports' driver is incompatible.

First, make a reliable restorable complete host disk image for backup purposes.

Then try uninstalling any 3rd-party security software, including web-safety nanny software or banking software, (complete uninstall not just disable) for a test. Also try looking for updated USB drivers for the motherboard and other USB add-on cards.

Then:
  1. Uninstall Virtualbox and reboot.
  2. Go to "C:\Windows\System32\drivers", look for any files called 'Vbox*.sys' (there could be up to 5) and delete them.
  3. Reboot again.
  4. Don't reinstall any 3rd-party security or anti-malware software. Built-in Windows Defender is OK to keep running.
  5. Reinstall Virtualbox using right-click-Run-As-Administrator.
If the above does not restore solid host operation sans BSODs, then you can uninstall/reinstall Virtualbox again with the USB option disabled. See what happens then.
fth0
Volunteer
Posts: 5678
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Multiple blue screens traced to VBox USB subsystem

Post by fth0 »

FWIW, in #21946 Sporadic blue-screen on Windows 11 all tracing back to VBox you entered VirtualBox 7.0.8 in the Version field. Since the current VirtualBox version is 7.0.12, this might reduce the likelihood of somebody looking into it, so I'd suggest to upgrade to the current version.
Post Reply