Hi @Dhairya Tomar,
Follow-up with a completed host dump analysis (full MEMORY.DMP, WinDbg/cdb !analyze -v). The raw dump and a sanitized support bundle are ready; I still need a private upload path (SFTP or secure share). Free Workstation has no entitlement, so Case FTP / Wolken Create Case is not available on my account.
Host / product
- ThinkPad 20YU003XGE, Win11 Pro 25H2 (build 26200.x), ThinkPad Thunderbolt 4 Dock 40B0
- VMware Workstation 26.0.1 build 25688693 (free)
- Crash: 2026-10-28 ≈ 07:05 CEST
Drivers
- hcmon.sys 8.11.18.0 (build-25410970, PE timestamp 2026-05-07) - VMware USB monitor
- vmusb.sys 4.3.3.0 (2026-07-10)
!analyze summary
- BUGCHECK_CODE: 0x7E (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED)
- Exception: 0xC0000005 (Access Violation)
- Faulting IP: hcmon+0x459d
- MODULE_NAME / IMAGE_NAME: hcmon / hcmon.sys
- FAILURE_BUCKET_ID: AV_hcmon!unknown_function
- SYMBOL_NAME: hcmon+459d
- PROCESS_NAME: System (PnP worker)
Call stack (abbreviated)
nt!KeBugCheckEx
…
nt!KiPageFault
hcmon+0x459d
nt!PnpNotifyDriverCallback+0x54
nt!PnpNotifyDeviceClassChange+0xac
nt!PnpDeviceEventWorker+0x2d9
nt!ExpWorkerThread
So the fault is inside the VMware kernel driver hcmon while Windows delivers a PnP device-class-change notification - not a guest crash and not a generic XHCI bugcheck.
Trigger context (same second)
- vmware-*.log: rapid "USB: New set of N USB devices" (14→4), dock devices flapping; log stops abruptly (~07:05:24) with no clean shutdown
- System event log: many Provider hcmon "Detected unrecognized USB driver" for TsUsbFlt / qcude / MhiHost
- USB Arbitrator UI prompts around the same time; some devices already redirected (USB\VID_0E0F&PID_0001…)
Working theory (needs Broadcom private symbols to confirm): race / stale pointer in hcmon's PnP notify callback during Thunderbolt-dock USB re-enumeration while devices appear/disappear quickly (including VMware-redirected instances).
Additional fault detail
- Faulting instruction at hcmon+0x459d: mov rdx, qword ptr [rdx+8]
- Exception: attempt to read from address 0000000000000030; registers at fault: rdx=0000000000000028 (so rdx+8 → 0x30), rax=0, rsi=0
- Interpretation: NULL/near-NULL structure dereference (classic AV on [base+0x8] with base≈0x28)
- No public Broadcom symbols: ln shows hcmon without symbols, so the function name is unknown and no source line is available without private PDBs
- hcmon module range: fffff803`18e20000 – fffff803`18e35000
@Claus Boerschig - your Thunderbolt hub hang under VM load + Teams/Zoom looks related to USB/arbitration stress; my case ends in a host BSOD in hcmon rather than a hub freeze. Happy to compare notes.
Dhairya: please send a private upload path and I will upload (1) sanitized vm-support and (2) full host MEMORY.DMP / zip. I will not post the dump publicly.
Thanks,
Boris
Original Message:
Sent: Nov 01, 2026 05:21 AM
From: Claus Boerschig
Subject: Host BSOD 0x7E (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, c0000005) on Win11 25H2 after Thunderbolt 4 dock USB re-enumeration – Workstation 26.0.1 (vmusb/hcmon suspected)
Hello everyone,
I am experiencing similar phenomena and would like to briefly describe them.
Hardware: DELL Precision 7780 with an i9 processor and 128GB of RAM. The Precision is connected via Thunderbolt to the hub integrated into a DELL U4025QW monitor. Peripherals such as a KVM switch, camera, speakerphone, etc., are connected to this hub.
Host: Windows 11 26H2
Software: VMware Workstation 26.0.1.25688693
When I run a medium-to-high workload within VMware Workstation - while applications like Microsoft Teams, Zoom et. al. are also running - the hub crashes. Everything connected to the hub becomes completely unresponsive, while the devices connected directly to the laptop continue to function. None of the running VMs have a virtual USB or sound controller that would allow for the attachment of USB devices.
This does not happen when Workstation is running alone under a very high load, nor does it occur when Teams accesses USB devices while Workstation is not running. It seems also not to be a hardware problem.
I have been observing this behavior for some time, including with previous versions of Windows and Workstation. Stopping the Arbitration Service, as well as stopping HCMON or VMUSB, does not help.
At this stage, I can only describe the phenomenon, but I have the impression that VMware is "taking over" the USB bus.
After a restart of the notebook, everything is running smoothly again.