Running SignalRGB with hardware monitoring programs such as hwmonitor and cpu-z causes the entire system to stop after 2 to 3 minutes.
Am I the only one experiencing this problem?
Is this problem a bug? Is there anything I can do about it?
Or it’s an unavoidable compatibility issue, so I was wondering if the only solution is not to run the hardware monitoring program together.
All SignalRGB self-monitoring features are currently off.
Since I am currently using a motherboard without an Argb terminal, I am using the Razer ARGB Controller by connecting it to the motherboard USB 2.0 header.