Gigabyte X870E Xtreme AI Top Inconsistently Missing 2nd Chipset & EC

[Slickrick]

My motherboard, Gigabyte X870E Xtreme AI Top, has two chipsets and an embedded controller for its various fans / sensors. Unfortunately, only the first chipset, ITE IT8696E, is showing. The 2nd chipset (ITE IT87952E) and the embedded controller are not being detected. When I first built this PC and when I reinstalled windows a few weeks ago, they did show up a few times.
I have a screenshot of it:

but I no longer see the 2nd chipset and the EC in the above screenshot. I've attached my debug file (compressed).

Also, I did see a post that looked similar, Gigabyte Aorus X870E Xtreme Ai Top chipset temperatures missing. In that post, I see Martin mentioned that this has already been discussed in the forum, but I can't seem to find the original discussion. I did try disabling the "Allow the computer to turn off this device to save power" in device manager for the USB eXtensible Host Controllers, but I don't see anything specifically named USB xHCI controller.


I've installed the latest chipset from AMD as well as the latest from Gigabyte. I'm on the latest BIOS version as well.

 

[Martin]

Are you perhaps running some other hardware monitoring or fan or RGB control software? Loss of those sensors can happen if such software performs an improper access to hardware.
Try to fully power off the system and reboot.

 

[Slickrick]

I prevented all possible startup apps, which did successfully show the missing Chip & EC in HWInfo. I then began re-adding my startup apps, 1 by 1. I've confirmed that SignalRGB is causing a conflict. Even with all the settings in SignalRGB turned off (Enable Onboard Devices, Automatically close conflicting programs, all partner permissions off, Enable Fan Control, Enable Motherboard Fan Control). I'll try to figure out if there's something I'm missing, but that's an issue with SignalRGB, not HWInfo.

Thanks for the help!
In case you're interested, here's the HWInfo debug file from starting up SignalRGB and then starting up HWInfo.

 

[Martin]

Please report this to SignalRGB.

 

[Slickrick]

Please report this to SignalRGB.

Will do! Thanks again for leading me to the root cause. This also helped me figure out separate issue with FanControl software too.