I noticed that the Device Manager has 4 of these “PCI Express Root Port” with malfunctions… The device status shows this:
"This device is currently waiting on another device or set of devices to start. (Code 51)
Dependencies:
USB4@_SB_.PC00.TDM1"
Any help at all would be great!
Thank you!
Welcome to the forums! Please update your post to include the following information.
Hello, I have the exact same issue:
I was using an eGPU until I was gone on vacation through 2023-08-18T10:00:00Z→2023-08-27T14:00:00Z.
When I got back home today plugging the Thunderbolt cable is only charging the laptop and nothing is happening.
Did Microsoft messed something up?
| CPU | 12th Gen Intel(R) Core™ i7-1260P 2.10 GHz |
| RAM | 64 GB |
| OS | Windows 11 Pro |
| Version | 22H2 |
| Build | 22621.2134 |
| Experience | Windows Feature Experience Pack 1000.22659.1000.0 |
Well I’ve finally managed to fix it by doing the following in order:
No idea what happened but I’m pretty sure this is a certified Windows moment.
@Vicky Oh my goodness, thank you so much. I don’t have a Framework laptop, but I’ve been struggling with this for weeks trying to figure out why my Razer Core X Chroma has randomly stopped working. I figured it was just an issue with my laptop not fully supporting Thunderbolt since it’s an AMD laptop with USB4. I was debating whether or not I was going to return the eGPU enclosure. I’ve reinstalled Windows 11 multiple times and it works initially (and ironically works perfectly in Ubuntu), but after using Windows for a bit longer it stops working. Installing Parsec was the issue. Looks like I’ll be using Moonlight with Sunshine over Tailscale going forward. After I uninstalled Parsec and restarted, I heard the USB connect sound multiple times lol.
I wasn’t able to find much in Event Viewer. Only real thing I noticed I was a malfunction on the PCI Express Root Port just like you:
This device is currently waiting on another device or set of devices to start. (Code 51)
Dependencies:
ACPI\PNP0A08\0
USB4@_SB_.PCI0.GP19.NHI1
Not a Framework user/owner (yet!) but I have had a similar issue with another AMD system the Minisforum UM790 Pro. Parsec was also the culprit for me. I tried updating the parsec drivers, stopping the service, etc. It didn’t seem to matter. Something about their drivers causes these issues. For me it’s not a massive deal since my device will be behind a TV for some emulation of old systems, but it’s for sure a strange thing. Hopefully AMD/Parsec can fix it soon. Thanks for sharing this because I felt like I was going crazy! If anyone finds a fix, please let me know!
