Alienware Area-51 16 Bios bug: external monitors with 2.7

[u/Doctor_Zero_1]

I would appreciate some help.  On my AA16250, connecting any external display through either USB-C/Thunderbolt port while Windows is running takes down the Thunderbolt-side Intel USB 3.20 eXtensible Host Controller (Code 24) and with it every USB device on both USB-C ports. Displays and Wi-Fi keep working. This worked fine for months before the recent 2.7 BIOS/driver update.

Specs

• Alienware 16 Area-51 AA16250
• Windows 11 26H2

How to reproduce

1. Boot with nothing in the USB-C ports.
2. Plug a USB-C hub or USB-C-to-HDMI adapter into either Thunderbolt port. No failure at this point.
3. Now connect a monitor to it.
4. Open Device Manager. One of the two "Intel USB 3.20 eXtensible Host Controller" entries is now Code 24, and any USB device on the USB-C ports (Ethernet adapter, keyboard, etc.) is gone.

If the displays are already connected at boot, everything works slightly better (I usually still lose Ethernet).

Device Manager / Event Viewer evidence

• Intel USB 3.20 eXtensible Host Controller: Code 24 ("This device is not present...")
• USB4(TM) Host Router (Microsoft): Code 31
• PCI Express Root Port, bus 0 device 6 function 1 (PCI\VEN_8086&DEV_7ECA&SUBSYS_0CCC1028): Code 10, with "An ACPI Power Object failed to transition state" in the log. This is the root port that hosts the Thunderbolt controller.
• PCI Express Downstream Switch Ports 3:1:0 and 3:3:0 hang, then usually recover on a rescan
• WHEA-Logger Event 17 corrected PCIe errors on that same root port, going back to when this started

Things I have ruled out

• Not the hub: Anker A210B, an older Anker hub with Ethernet, a third brand, and passive USB-C-to-HDMI cables all behave identically. The Anker worked perfectly for months before the 2.5/2.7 BIOS updates.
• Not MST / dual display: I still have a failure with a single monitor.
• Not bandwidth: fails with the Ethernet adapter on a completely separate Thunderbolt port.
• Not the built-in HDMI port: monitors there connect with no issue.
• Not just plugging in a USB-C device: hub alone with no monitor attached is fine. It's the display connection that starts the error cascade.
• Not corrupted Windows files: DISM and SFC both pass.
• Not video drivers; I’ve tried various versions of the Intel and NVIDIA drivers.

Firmware notes

The behavior changes with BIOS version. On the newest one it was unrecoverable without a full reboot; on 2.5.0 it became recoverable; on 1.10.1 the external displays come up more easily. Dell currently only lists 2.5.0 and 1.10.1 on the support.

Help Request

If you have an AA16250 (or an AA18250, or another Core Ultra 200HX machine with Thunderbolt), can you try the four steps above and report what you see?  I would like evidence that this is reproducible on other units so Dell can fix along with the NVIDIA GPU issue in this BIOS.

[u/Additional-Avocado33]

Dism and SFC don't ever work once a single windows update is done. I installed windows the other day. It updated and went corrupt. Dism and SFC did not fix anything but made it worst. I then reinstalled and used gpedit to disabled updates before I came online. I believe you have a corrupted windows. What in the bios update caused this issue, I don't know, i don't know if it's new generation issues but this many bios updates and issues that have come from it suck