UCMUCSI_FAILURE

Code: 0x1d8 (472)

As HRESULT:

S: 0 (Success)
C: 0 (Microsoft-defined)
N: 0 (Not an NTSTATUS value)
Facility: 0x000 (FACILITY_NULL: Default)
Code: 0x01d8 (472)

As NTSTATUS:

Sev: 0 (STATUS_SEVERITY_SUCCESS)
C: 0 (Microsoft-defined)
Facility: 0x000 (Default)
Code: 0x01d8 (472)

Parameters

Parameter	Description
1	Type of failure. VALUES: 0x0 : A UCSI command has timed out because the firmware did not respond to the command in time. 0x1 : A UCSI command execution failed either because the client driver returned failure or because the firmware returned an error code.
2	The UCSI command value.
3	If non-zero, the pointer to additional information (use `dt UcmUcsiCx!UCMUCSICX_TRIAGE`).
4	Reserved.

Description

The UCMUCSI_FAILURE bug check has a value of 0x000001D8. It indicates that the UCSI class extension has encountered an error.

Important
This article is for programmers. If you're a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.

Cause

The UcmUcsi driver has encountered an error. The driver has found settings to trigger a system crash instead of a livedump.

Resolution

A UCSI Command typically fails when UCSI firmware is not responsive and UcmUcsiCx times out on a UCSI command or the UCSI firmware has indicated an error in response to a critical UCSI command sent by UcmUcsiCx.

Run !rcdrkd.rcdrlogdump UcmUcsiCx for more information on the cause of this failure.

For more information on analyzing this bug check, see this blog post - Debugging UCSI firmware failures.

Associated Modules

Module	Code	Found in	Description
ESENT.dll	0x1d8	8.11011	%1 (%2) %3The shadow header page of file %4 was damaged. The primary header page (%5 bytes) was used instead.
EventCreate.exe	0x1d8	78.11011	%1
kernel32.dll	0x1d8	11	The storage stack returned STATUS_ACCESS_DENEID for the current operation.
webservices.dll	0x1d8	78.11011	The maximum number of attributes of %1 for an element in the document was exceeded.
4 entries