Tested and confirmed. Workaround is to disable lighting control on startup, restart after setting lighting. Closing the program completely does not resolve the issue until restart. Noticed that HWiNFO hangs during the "Analyzing Memory Configuration" phase longer than normal when the issue is occuring.So if you start HWiNFO after reboot all works well and if you then start the Lighting Control, HWiNFO will lose those sensors?
You’re not joking. I’m fairly confident RGBFusion causes the same issue when it connects to the G.skill. Lighting control programs need better universality. Hopefully this thread will serve as a workaround for another with the same issue in the future.That looks like the Lighting Control software is somehow blocking the entire SMBus which used to access sensors or memory DIMM information. What a piece of crap.