[Laptop 13 Pro Core Ultra Series 3] USB-C monitor not restored after Modern Standby resume - UCSI failure (LiveKernelEvent 0x1D4) on every wake

Community Support
,
1

System: Framework Laptop 13 Pro (Intel Core Ultra Series 3), BIOS 03.02, Windows 11 25H2 build 26200.9457, Framework driver bundle 1.01, Intel graphics 32.0.101.8628.

Symptom: A USB-C DP Alt Mode monitor is never restored after the laptop resumes from Modern Standby. The monitor’s built-in USB hub stays enumerated and powered, so the cable and USB data path are fine; only the DisplayPort link is lost. Unplugging and replugging the cable restores it immediately, with no errors logged. Reproduced with two different monitors (SOTSU FlipAction Elite 16 and ASUS ZenScreen MQ149CD). Present since the machine was set up on 2026-09-07.

Evidence from Event Viewer: At the exact second of every Kernel-Power event 507 (“exiting Modern Standby”), Windows logs:

  • LiveKernelEvent 0x1D4 (UcmUcsiCx.sys, parameters 0 / 0x10 / 0x102)
  • LiveKernelEvent 0x141 (GPU watchdog)
  • Intel-Gfx-Display-External event 10
  • UcmUcsiCx event 1: “UcmUcsiCx device has encountered a failure” for ACPI\USBC000\0

Eight out of eight standby wakes today produced this set; several hundred 0x1D4 dumps since 09-07. When negotiation fails the monitor enumerates as a USB Billboard device, i.e. Alt Mode entry failed.

Software recovery does not work: pnputil /disable-device + /enable-device on ACPI\USBC000\0 and a graphics-driver restart (Win+Ctrl+Shift+B) each immediately re-trigger 0x1D4 + 0x141. So the PD/UCSI controller seems to fail on any re-initialisation with a device already attached, while a fresh physical plug negotiates cleanly.

Not a driver issue as far as I can tell: the GPU errors are downstream of the UCSI failure, and the latest Intel driver release notes don’t mention anything related.

The three resumes from hibernate in the last two weeks did not log the failure, so I am testing hibernate as a workaround.

Possibly related: FW13 Pro: suspend-then-hibernate system crash (s2idle resume platform resets, BIOS 3.02) is a different symptom on Linux, but also a resume-path issue on the same firmware.

I have the live kernel dumps from C:\Windows\LiveKernelReports (UcmUcsiCx.sys and WATCHDOG) if Framework wants them. Is anyone else on a 13 Pro / Core Ultra Series 3 seeing this, and is a PD/EC firmware fix planned?

2

Seeing the same thing in Ubuntu linux. I guess that rules out the OS.

3

Filing a ticket with support is going to get more traction so they have more data points on what errors users are experiencing. This sounds like a firmware issue with one of the subcomponents and will likely be ironed out with the dev team. Also filing this information on the Framework GitHub firmware issues area is a good place to submit detailed information like this so it can be tracked.

We are all end users here on the forums.

Welcome to the community @Joshua_Kerr.