There appears to be a conflict between SignalRGB and other software that accesses hardware information. This conflict does not effect the primary chipset sensors, but does effect the secondary chipset and embedded controller.
I have a Gigabyte X870E Aorus Xtreme AI Top motherboard. I’m on the latest BIOS version. This motherboard has 10 fan headers that are split among Chip 1 (ITE IT8696E), Chip 2 (ITE IT87952E), and an embedded controller.
When SignalRGB is open, the 2nd chipset & Embedded controller are not detected in either HWInfo64 or in FanControl. I tested this thoroughly by closing every single program I have and opening each individually.
I figured this is likely due to some setting in SignalRGB that is attempting to gain control of the hardware of the 2nd chip and/or the embedded controller. However, I’ve disabled every setting in SignalRGB that I thought may be related, without success.
Is there a setting that I’m missing that I should try enabling/disabling?