Sporadic blue-screen on Windows 11 all tracing back to VBox

[lukabloomrox]

I haven't yet been able to pin down the reason for these failures. I could get 2-3 failures per day, or only one per week, but they are most definitely happening more or less continuously.

[lukabloomrox]

Minidumps may be found at the following link (since they are too big to attach to this ticket)

​https://www.dropbox.com/scl/fo/j8smg7mopnkpod49mc45o/h?rlkey=8g9utr7omzlkw3mewi3a2nlts&dl=0

[lukabloomrox]

Here's the most latest minidump analysis:

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
---------

[lukabloomrox]

Here's the system configuration of the host Windows PC:

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	11.7 GB
Total Virtual Memory	79.6 GB
Available Virtual Memory	45.3 GB
Page File Space	48.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.	

[lukabloomrox]

PS. I installed VBox 7.12 after raising this ticket, if I continue to see these issues I'll post back.

[lukabloomrox]

I am running VB 7.0.12 r 159484 (Qt5.15.2) and am still seeing the issue.

I am not running any third party antivirus software, only Windows Defender.