Exact same problem with the "Intel(R) PCI Express Root Port #5 - 7ABC" and thunderbolt issues.
I have a thunderbolt hub that was working fine with my Maximus Extreme z690 and 12900k. I upgraded to a 13900KS and now the hub has been going haywire.
USB 2.0 devices seem to work fine in it, but no USB 3.0 devices show up. Strangely, I do have a USB 3.2 hub plugged into it, and USB 2.0 devices plugged into that also work, but again, not USB 3.0 devices.
Also, in the thunderbolt control center, the Thunderbolt hub does not show up when these issues are occurring. On RARE occasions it will appear in the control center as connected, and in that case the hub works fine, including USB 3.0 devices. I am getting so annoyed.
I may have found a workaround after reading posts in other threads.
For me at least, my Thunderbolt hub seems to be working mostly normally as long as it is turned off when the computer boots.
If I open the Thunderbolt control center, the hub shows up, though strangely it still says "Connection Status: Not Connected", even though any devices connected to it seem to work fine. Before, it wouldn't show up at all. When doing this workaround, the PCIe Root Port #5 thing does not show the error in Device Manager.
I tested a few different scenarios:
â€¢ Hub off during cold boot (from power supply off / unplugged) and turned on after Windows boot = Works
â€¢ Hub on during Windows shutdown, but turned off during startup, and only turned on after Windows boots = Works
â€¢ Hub on during shutdown, and on during startup and Windows boot = Fails as with the PCIe #5 thing
After a fail occurs:
â€¢ Hub on during shutdown, but turned off before startup, and turned on after Windows boots = Works again
Therefore for me at least, my Hub will apparently work so long as it is turned off before startup and Windows boot.
One weird thing I've noticed is that even though I've installed the Intel Chipset drivers v10.1.19263.8344, which has raptorlake drivers inside (RaptorLakeSystem.inf or RaptorLakePCH-SSystem.inf) at v10.1.49.6, when I look in the device manager and sort by Driver, they are listed as using "alderlakepch-ssystem.inf" which are only 10.1.37.7 when you go to their properties. Wonder what the deal is with that.
I know that the latest chipset drivers v10.1.19284.8351 break the system on 13th gen, so perhaps when Intel finally fixes that and releases a new chipset driver this will be fixed?
I actually tried manually extracting out the RaptorLakePCH-SSystem.inf drivers from the installer and force installed them onto the 'PCIe #5' device, but it didn't seem to help. Also deleted the alderlake drivers and only kept the raptorlake ones using DriverStoreExplorer, but it wasn't using the raptorlake drivers, all the devices just showed up as generic PCIe devices.
I'm thinking this might be at least partly an Intel driver issue and their drivers just aren't working, and we'll have to wait for them to release the next version of the chipset drivers.
Hello Angstromboli, do you have a 13th or 12th gen CPU? I have a 12th gen CPU and have a similar issue and I am not sure which gen CPU OP has. Do you think what you mention about the chipset drivers would apply to 12th gen CPUs as well?
For me all this started when updating the BIOS to version 2004. 2103 and 2204, have not fix this issue since for me.
I am using a 13th gen processor, specifically a 13900KS on a Maximus Extreme Z690 board. If you're on 12th gen then perhaps then that suggests that the BIOS truly is the problem. I would read some of the other posts in this thread where they talk about contacting support for a "bridge" bios version that apparently lets you downgrade to a version prior to bios 2004.
I haven't tried it yet but might if they don't release a new bios soon. It's been over 3 months since the last version, which is the longest they've gone between BIOS updates.