On version 2.5.17+1c4b6a9f the rgb in my Kingston Fury Renegade RAM sticks sticks is no longer avalaible in SignalRGB.
Checking SignalRGB log I have detected the following:
10/05/25 15:57:52.337 [17088-Thread (pooled)] SignalRGB.root.INFO - Intel ICH8 Bus - 0xefa0 - Checking Ram stick part number: KF560C32-16
10/05/25 15:57:52.337 [17088-Thread (pooled)] SignalRGB.root.INFO - Intel ICH8 Bus - 0xefa0 - System Does Not Have Fury Ram Installed!
Has anyone the same issue?
Have you tried rebooting the system? Sometimes a full restart fixes things like that.
I have tried restarting the system. I have also reinstalled the application and run it as an administrator, but I couldn’t get it to work.
It does work for me in version 2.4.57.
I’d recommend going ahead with creating a ticket through our contact page. Sounds like it might be a bug 
I’m running 2x Kingston FURY Beast 32GB/6000 here and did have that version running ok, that said another update must have just taken place, and after a boot I now see 2.5.18+85205fe6.
I just tried a few themes and all seems ok so far.
I’m handling the possible issue with support.
It might just be affecting the Renegade RAM model.
I’ve rolled back to version 2.4.57, where it does work. Here’s the log:
10/11/25 10:35:52.878 [4264-Thread (pooled)] SignalRGB.root.INFO - Intel ICH8 Bus - 0xefa0 - Address 97 passed quick write test with result 0
10/11/25 10:35:53.007 [4264-Thread (pooled)] SignalRGB.root.INFO - Intel ICH8 Bus - 0xefa0 - Fury Identifier Return: 70,85,82,89
10/11/25 10:35:53.039 [4264-Thread (pooled)] SignalRGB.root.INFO - Intel ICH8 Bus - 0xefa0 - Model Byte: true