VMware Workstation

 View Only
  • 1.  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)

    Posted 15 days ago

    Host: Lenovo ThinkPad 20YU003XGE, Windows 11 Pro 25H2 build 26200.9711, Lenovo ThinkPad Thunderbolt 4 Dock (40B0).
    VMware Workstation 26.0.1 build 25688693 (free). Drivers: vmusb.sys 4.3.3.0, hcmon.sys 8.11.18.0, vmx86.sys 26.5.0.0, vmci.sys 9.8.32.0, vmnet*.sys 26.5.0.1.

    This is not new to 26.0.1. The same class of host crash has been happening for a long time across older VMware Workstation versions as well. Pattern: whenever the Thunderbolt dock changes (reconnect / power cycle / different dock state) or the set of USB devices attached to the dock changes, the host often hits this bugcheck on the first reboot, and sometimes on the second reboot as well.

    What happened most recently (28 Oct 2026, times CET/UTC+1):
    - One VM running (Debian 13 guest, USB controller present, usb.generic.autoconnect = FALSE, no device passed through).
    - 07:05:20–07:05:24 the dock's USB devices re-enumerated (hcmon logged "Detected unrecognized USB driver" for TsUsbFlt/qcude/MhiHost; vmware-vmx logged several "USB: New set of N USB devices"; the UI showed the USB arbitrator "connect device" dialog several times).
    - ~07:06:35 host bugcheck 0x0000007E, P1 = 0xFFFFFFFFC0000005 (access violation), auto-reboot, full memory dump written.
    - After reboot hcmon (start type Auto) shows as Stopped.
    - Windbg !analyze -v for the faulting module is still pending (will update this thread once available). Related community reports exist for hcmon + Thunderbolt docks / 0x7E, but I did not find one matching Workstation 26.0.1 + ThinkPad TB4 Dock 40B0 with this recurring dock/device-change reboot pattern.

    Current workaround: toggle VMware Workstation USB passthrough by starting/stopping the VMware USB Arbitration Service and the hcmon driver via two PowerShell scripts (enable vs disable), launched from desktop shortcuts. That avoids the host BSOD until a proper fix exists; the crash still returns when USB passthrough is left enabled and the Thunderbolt dock or attached devices change across reboots.

    Question: Known long-standing issue with vmusb/hcmon across Workstation versions on Win11 during dock/USB re-enumeration and the following 1st/2nd reboot? Any fix or workaround besides disabling USB arbitration?
    I can attach !analyze -v text, vmware.log, and Kernel-Power 41 details; minidump on request via DM.



  • 2.  RE: 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)

    Broadcom Employee
    Posted 14 days ago
    Edited by Dhairya Tomar 14 days ago

    Boris Huertgen

    Request you to recreate this issue and share full support bundle of the VM and full crash dumps(.dmp) of the host where Workstation is installed.




  • 3.  RE: 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)

    Posted 13 days ago

    @Dhairya Tomar - Happy to share the full VM support bundle and the host MEMORY.DMP.

    I am on free VMware Workstation 26.0.1 with no Broadcom support entitlement, so I cannot open a support case and cannot use supportftp.broadcom.com.

    Please send a private upload path (SFTP, secure OneDrive/Dropbox/SharePoint link, or similar). I will upload as soon as I have it. Bundle and dumps are already prepared on the host.




  • 4.  RE: 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)

    Posted 11 days ago

    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.



  • 5.  RE: 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)

    Posted 10 days ago

    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




  • 6.  RE: 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)

    Posted 9 days ago

    Claus, I'd update the monitor/hub firmware even though you believe it's not hardware: https://www.dell.com/support/product-details/en-gb/product/u4025qw-monitor/drivers




  • 7.  RE: 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)

    Posted 9 days ago

    All up to date.




  • 8.  RE: 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)

    Posted 3 days ago
    Edited by Boris Huertgen 3 days ago

    Update – the crash happened again today (9 Nov 2026), this time 17 seconds after boot.

    !analyze -v (full kernel dump, MEMORY.DMP)

    • BUGCHECK_CODE: 0x7E (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED)
    • P1: 0xFFFFFFFFC0000005 (access violation), P2: hcmon+0x459d
    • MODULE_NAME / IMAGE_NAME: hcmon / hcmon.sys 8.11.18.0 (timestamp 2026-05-07, 69FC2D11)
    • FAILURE_BUCKET_ID: AV_hcmon!unknown_function
    • PROCESS_NAME: System, System Uptime: 0:00:17

    Stack (top)

    hcmon+0x459d
    nt!PnpNotifyDriverCallback+0x54
    nt!IoRegisterPlugPlayNotification+0x337
    hcmon+0x1145d
    hcmon+0x11570
    nt!PnpCallDriverEntry+0x54
    nt!IopLoadDriver+0x6f2
    nt!IopLoadUnloadDriver+0x7b
    nt!ExpWorkerThread+0x29f

    Key finding

    The crash is inside hcmon's DriverEntry. hcmon calls IoRegisterPlugPlayNotification, and Windows immediately invokes the PnP notification callback for already-present device interfaces – that callback (hcmon+0x459d) dereferences an invalid pointer. So it is not only a runtime dock re-enumeration issue: with hcmon set to Automatic start, a changed dock/device set at boot is enough to bugcheck the host before any user-mode workaround can run. Same offset (hcmon+0x459d) as the crash on 28 Oct. The graphics driver (igdkmd64) is not involved.

    Additional details

    • Status code: rbx holds 0xC0000022 (STATUS_ACCESS_DENIED). A preceding call failed and hcmon continued with an invalid pointer. Today's values: read access to 0x2f, rdx=0x27, instruction mov rdx,[rdx+8].
    • Two triggers, same offset: on 28 Oct the stack went through PnpNotifyDeviceClassChange (runtime, device change); today through DriverEntry (boot). Both fault at hcmon+0x459d.
    • Suspected device (hypothesis): qcude and MhiHost from the “Detected unrecognized USB driver” messages belong to a Qualcomm/Quectel WWAN modem; a Quectel UDE device is attached via USB on this host. My hypothesis is that hcmon fails on UDE (USB Device Emulation) devices.
    • Correction: the values in my earlier reply (read access to 0x30, rdx=0x28) are from the 28 Oct crash; today's dump shows 0x2f / 0x27.

    Next step on my side

    Switching hcmon and the VMware USB Arbitration Service to manual start and only starting them on demand via script when USB passthrough is needed.

    Broadcom/VMware: can you confirm this is a known defect in hcmon 8.11.18.0 and whether a fixed build is planned? I can provide the full dump via DM.




  • 9.  RE: 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)

    Broadcom Employee
    Posted yesterday

    Boris Huertgen Based on the information you have provided, internal team is looking into the same. We will let you know in case anything additional is required.