What does BSOD 468 (UCMUCSI_LIVEDUMP) mean?

 
Previous Next
WFP_INVALID_OPERATION DRIVER_PNP_WATCHDOG

UCMUCSI_LIVEDUMP

USB Type-C UCSI live dump for UCMUCSI_LIVEDUMP

UCMUCSI_LIVEDUMP is bug check code 0x000001D4. This live dump indicates that the UcmUcsi class extension encountered an error. Microsoft documents common examples such as UCSI command timeout or a client driver returning failure for a command.

How to read it in a dump for UCMUCSI_LIVEDUMP

  • Check UCSI command, connector, firmware, and client-driver status in the dump.
  • Differentiate Type-C policy, PD firmware, ACPI UCSI transport, and client driver behavior.
  • This value identifies a live dump and is not used as a conventional fatal bug check.

What to check for UCMUCSI_LIVEDUMP

  • Update BIOS/firmware, USB-C controller firmware, chipset, and Type-C drivers from the device vendor.
  • Check USB Type-C, docking, power delivery, and alternate-mode event logs.
  • Use Microsoft UCSI debugging guidance if command completion or firmware response is involved.

References for UCMUCSI_LIVEDUMP

Dump evidence for UCMUCSI_LIVEDUMP

For UCMUCSI_LIVEDUMP, preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. AllStat summarizes the condition as “UCMUCSI_LIVEDUMP”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.

Analysis order for UCMUCSI_LIVEDUMP

  • Run WinDbg !analyze -v, then inspect the documented meaning of each UCMUCSI_LIVEDUMP parameter instead of relying only on the probably-caused-by line.
  • For UCMUCSI_LIVEDUMP, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with ucmucsi / livedump.
  • For UCMUCSI_LIVEDUMP, keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.

Do not repeatedly reboot a machine affected by UCMUCSI_LIVEDUMP before collecting the dump and event logs. For UCMUCSI_LIVEDUMP, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.

Dump evidence for UCMUCSI_LIVEDUMP

For UCMUCSI_LIVEDUMP, preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. AllStat summarizes the condition as “UCMUCSI_LIVEDUMP”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.

Analysis order for UCMUCSI_LIVEDUMP

  • Run WinDbg !analyze -v, then inspect the documented meaning of each UCMUCSI_LIVEDUMP parameter instead of relying only on the probably-caused-by line.
  • For UCMUCSI_LIVEDUMP, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with ucmucsi / livedump.
  • For UCMUCSI_LIVEDUMP, keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.

Do not repeatedly reboot a machine affected by UCMUCSI_LIVEDUMP before collecting the dump and event logs. For UCMUCSI_LIVEDUMP, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.

Looking for a different code? Search another status or error code.