# My Kingston Fury Renegade memory sticks are not recognised as RGB devices **URL:** \ **Category:** Support\ **Tags:** issues\ **Created:** [February 20, 2023, 2:33pm UTC](https://forum.signalrgb.com/t/my-kingston-fury-renegade-memory-sticks-are-not-recognised-as-rgb-devices/196 "2023-02-20T14:33:46Z")\ **Posts on this page:** 18\ **Page:** 2
**Author:** ![JohanvdHoven](https://avatars.discourse-cdn.com/v4/letter/j/51bf81/32.png) [@JohanvdHoven](https://forum.signalrgb.com/u/JohanvdHoven)\ **Post date:** [June 17, 2023, 4:13pm UTC](https://forum.signalrgb.com/t/my-kingston-fury-renegade-memory-sticks-are-not-recognised-as-rgb-devices/196/22 "2023-06-17T16:13:54Z")
I tries completely removing and reinstalling the app too but the memory sticks are not recognized as RGB devices. Thank your for mentioning the workaround to make the program start with elevated rights. I have been experimenting with this before and will remember your solution. ---
**Author:** ![Arelius](https://avatars.discourse-cdn.com/v4/letter/a/3d9bf3/32.png) [@Arelius](https://forum.signalrgb.com/u/Arelius)\ **Post date:** [June 18, 2023, 7:55pm UTC](https://forum.signalrgb.com/t/my-kingston-fury-renegade-memory-sticks-are-not-recognised-as-rgb-devices/196/23 "2023-06-18T19:55:47Z")
Are your RBG on for your ram sticks or off? Even though mine where on… before what I did and make it work. (I did not mention this before, but I did before reinstall SignalRGB) Install the Kingstone’s own app and turned my RGB off (that worked… I needed to see if the rams were functioning properly…) and then on, and then uninstalled that app and installed SignalRGB again and did what I did as mentions above. Sorry for not sharing the whole story before. Maybe this has nothing to do with anything and won’t help in your case, but I felt I need to share that. ---
**Author:** ![JohanvdHoven](https://avatars.discourse-cdn.com/v4/letter/j/51bf81/32.png) [@JohanvdHoven](https://forum.signalrgb.com/u/JohanvdHoven)\ **Post date:** [June 18, 2023, 9:06pm UTC](https://forum.signalrgb.com/t/my-kingston-fury-renegade-memory-sticks-are-not-recognised-as-rgb-devices/196/24 "2023-06-18T21:06:22Z")
RGB is working (the light is on) on my RAM sticks now but I will install the Kingston tool and switch RGB off and then on again like you described 😀 ---
**Author:** ![HarDBR](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.signalrgb.com/hardbr/32/282_2.png) [@HarDBR](https://forum.signalrgb.com/u/HarDBR)\ **Post date:** [June 19, 2023, 12:02pm UTC](https://forum.signalrgb.com/t/my-kingston-fury-renegade-memory-sticks-are-not-recognised-as-rgb-devices/196/25 "2023-06-19T12:02:49Z")
@JohanvdHoven I would say that is happening because of a conflict on the board addresses, could you send me your latest log? You can find logs here: [https://srgbmods.net/s?p=view/logs](https://srgbmods.net/s?p=view/logs) ---
**Author:** ![JohanvdHoven](https://avatars.discourse-cdn.com/v4/letter/j/51bf81/32.png) [@JohanvdHoven](https://forum.signalrgb.com/u/JohanvdHoven)\ **Post date:** [June 20, 2023, 4:13pm UTC](https://forum.signalrgb.com/t/my-kingston-fury-renegade-memory-sticks-are-not-recognised-as-rgb-devices/196/26 "2023-06-20T16:13:27Z")
I installed the proper Kingston tool ([Kingston FURY CTRL RGB Control Software - Kingston Technology](https://www.kingston.com/en/gaming/fury-ctrl)) and checked if I could switch off the RGB function on the RAM sticks. That worked, the lights went out. I rebooted the computer and when SignalRGB started (I have a delayed start scheduled with elevated rights) it recognised the Kingston RAM sticks and I can now setup the RGB lights properly. Thank you @Arelius ! ---
**Author:** ![Arelius](https://avatars.discourse-cdn.com/v4/letter/a/3d9bf3/32.png) [@Arelius](https://forum.signalrgb.com/u/Arelius)\ **Post date:** [June 20, 2023, 8:16pm UTC](https://forum.signalrgb.com/t/my-kingston-fury-renegade-memory-sticks-are-not-recognised-as-rgb-devices/196/27 "2023-06-20T20:16:45Z")
Glad I could contribute 😉 ---
**Author:** ![Doodle](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.signalrgb.com/doodle/32/472_2.png) [@Doodle](https://forum.signalrgb.com/u/Doodle)\ **Post date:** [August 5, 2023, 12:34pm UTC](https://forum.signalrgb.com/t/my-kingston-fury-renegade-memory-sticks-are-not-recognised-as-rgb-devices/196/28 "2023-08-05T12:34:39Z")
Hi My Fury renegade was working with Signal, but I had a slow frame rate.I found a new BIOS that was released last month. Since updating to the latest version, Signal will not recognise it. So, that advice “Make sure your BIOS is up to date” is a load of tosh. ---
**Author:** ![MrG8901](https://avatars.discourse-cdn.com/v4/letter/m/9fc348/32.png) [@MrG8901](https://forum.signalrgb.com/u/MrG8901)\ **Post date:** [January 7, 2025, 12:39am UTC](https://forum.signalrgb.com/t/my-kingston-fury-renegade-memory-sticks-are-not-recognised-as-rgb-devices/196/29 "2025-01-07T00:39:21Z")
RGB lights not functioning correctly and it also failed to write to plugins. Following errors im getting with the Kingston Hyper Fury RAM [Tue Jan 7 11:38:15 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:15 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:15 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:15 2025] plugin.info - Failed To Write Byte within 5 attempts! [Tue Jan 7 11:38:15 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:15 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:15 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:15 2025] plugin.info - Failed To Write Byte within 5 attempts! [Tue Jan 7 11:38:15 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:15 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:15 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:15 2025] plugin.info - Failed To Write Byte within 5 attempts! [Tue Jan 7 11:38:15 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:16 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:16 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:16 2025] plugin.info - Failed To Write Byte within 5 attempts! [Tue Jan 7 11:38:16 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:16 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:16 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:16 2025] plugin.info - Failed To Write Byte within 5 attempts! [Tue Jan 7 11:38:16 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:17 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:17 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:17 2025] plugin.info - Failed To Write Byte within 5 attempts! [Tue Jan 7 11:38:17 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:17 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:17 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:17 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:17 2025] plugin.info - Failed To Write Byte within 5 attempts! [Tue Jan 7 11:38:17 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:17 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:17 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:17 2025] plugin.info - Failed To Write Byte within 5 attempts! [Tue Jan 7 11:38:17 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:18 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:18 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:18 2025] plugin.info - Failed To Write Byte within 5 attempts! [Tue Jan 7 11:38:18 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:18 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:18 2025] plugin.info - Failed To Write Byte within 5 attempts! [Tue Jan 7 11:38:18 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:19 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:19 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:19 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:19 2025] plugin.info - Failed To Write Byte within 5 attempts! [Tue Jan 7 11:38:19 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:19 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:19 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:19 2025] plugin.info - Failed To Write Byte within 5 attempts! [Tue Jan 7 11:38:19 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:19 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:19 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:19 2025] plugin.info - Failed To Write Byte within 5 attempts! [Tue Jan 7 11:38:19 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:20 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:20 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:20 2025] plugin.info - Failed To Write Byte within 5 attempts! [Tue Jan 7 11:38:20 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:20 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:20 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:20 2025] plugin.info - Failed To Write Byte within 5 attempts! [Tue Jan 7 11:38:20 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:20 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:20 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:20 2025] plugin.info - Failed To Write Byte within 5 attempts! [Tue Jan 7 11:38:20 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:20 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:20 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:21 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:21 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:21 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:21 2025] plugin.info - Failed To Write Byte within 5 attempts! [Tue Jan 7 11:38:21 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:21 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:21 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:21 2025] plugin.info - Failed To Write Byte within 5 attempts! [Tue Jan 7 11:38:21 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:22 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:22 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:22 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:22 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:23 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:23 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:23 2025] plugin.info - Failed To Write Byte within 5 attempts! [Tue Jan 7 11:38:23 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:23 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:24 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:24 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:24 2025] plugin.info - Failed To Write Byte within 5 attempts! [Tue Jan 7 11:38:24 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:24 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:24 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:24 2025] plugin.info - Failed To Write Byte within 5 attempts! [Tue Jan 7 11:38:24 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:24 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:25 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:25 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:25 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:25 2025] plugin.info - Failed To Write Byte within 5 attempts! [Tue Jan 7 11:38:25 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:25 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:25 2025] plugin.info - Failed To Write Byte within 5 attempts! [Tue Jan 7 11:38:25 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:26 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:26 2025] bus.info - WriteByte(): Operation Failed. [Tue Jan 7 11:38:26 2025] plugin.info - Failed To Write Byte within 5 attempts! ---
**Author:** ![KMBak](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.signalrgb.com/kmbak/32/302_2.png) [@KMBak](https://forum.signalrgb.com/u/KMBak)\ **Post date:** [September 9, 2025, 6:01pm UTC](https://forum.signalrgb.com/t/my-kingston-fury-renegade-memory-sticks-are-not-recognised-as-rgb-devices/196/30 "2025-09-09T18:01:04Z")
Samne problem. Lot of errors and low FPS. MSI x870 Carbon Wifi. No other RGB software… ![Kingston Fury RGB problem](https://us1.discourse-cdn.com/flex015/uploads/signalrgb/original/2X/e/ec442428f7e4be6f6431a0cb010b365e958f69c8.png) ---
**Author:** ![SignalBadger](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.signalrgb.com/signalbadger/32/1654_2.png) [@SignalBadger](https://forum.signalrgb.com/u/SignalBadger)\ **Post date:** [September 10, 2025, 3:48pm UTC](https://forum.signalrgb.com/t/my-kingston-fury-renegade-memory-sticks-are-not-recognised-as-rgb-devices/196/31 "2025-09-10T15:48:57Z")
Low FPS on most devices is related to hardware limitations, the issue comes down to the manufacturer and their LEDs being unable to keep up with the data received. SignalRGB sends at about 30fps to devices (33fps to be more exact), but some devices can’t keep up and it resolves in some normal console errors. Hope this helps explain what’s going on! ---
**Author:** ![KMBak](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.signalrgb.com/kmbak/32/302_2.png) [@KMBak](https://forum.signalrgb.com/u/KMBak)\ **Post date:** [September 10, 2025, 8:20pm UTC](https://forum.signalrgb.com/t/my-kingston-fury-renegade-memory-sticks-are-not-recognised-as-rgb-devices/196/32 "2025-09-10T20:20:00Z")
But look for the errors on screenshots. ---
**Author:** ![SignalBadger](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.signalrgb.com/signalbadger/32/1654_2.png) [@SignalBadger](https://forum.signalrgb.com/u/SignalBadger)\ **Post date:** [September 11, 2025, 4:10pm UTC](https://forum.signalrgb.com/t/my-kingston-fury-renegade-memory-sticks-are-not-recognised-as-rgb-devices/196/33 "2025-09-11T16:10:54Z")
Those errors are typical for when the device cannot keep up, they aren’t indicative of an error with the program or per se. It’s just saying it failed to push the effect through, because the hardware can’t keep up. It’s reinforcing what I’m saying, rather than contradicting. The unfortunate solution here is “buy RAM with better LED performance”. 😕 ---
**Author:** ![KMBak](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.signalrgb.com/kmbak/32/302_2.png) [@KMBak](https://forum.signalrgb.com/u/KMBak)\ **Post date:** [September 11, 2025, 4:55pm UTC](https://forum.signalrgb.com/t/my-kingston-fury-renegade-memory-sticks-are-not-recognised-as-rgb-devices/196/34 "2025-09-11T16:55:47Z")
What RAMs have better leds? Will these work better? > **[F5-6000J3036F48GX2-RM5NRK - Overview - G.SKILL International Enterprise Co.,...](https://www.gskill.com/product/165/428/1731653822/F5-6000J3036F48GX2-RM5NRK)** > > Ripjaws M5 Neo RGB is a performance DDR5 DRAM memory series designed for AMD AM5 platforms. Featuring matte black or matte white aluminum heatspreaders and customizable RGB lighting, the Ripjaws M5 Neo RGB is the ideal memory kit for a wide variety... ---
**Author:** ![SignalBadger](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.signalrgb.com/signalbadger/32/1654_2.png) [@SignalBadger](https://forum.signalrgb.com/u/SignalBadger)\ **Post date:** [September 12, 2025, 5:16pm UTC](https://forum.signalrgb.com/t/my-kingston-fury-renegade-memory-sticks-are-not-recognised-as-rgb-devices/196/35 "2025-09-12T17:16:43Z")
Not sure to be honest, I’ve only personally used G.Skill Trident Z sticks and those are getting 22fps roughly. Another factor is the motherboard, as different motherboards will have different performance. We’ve a list of compatible devices [found here](https://signalrgb.com/devices/), and our [Discord](https://discord.gg/JryCvhcCvX) community might also have more insight. Hope this is useful! ---
**Author:** ![KMBak](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.signalrgb.com/kmbak/32/302_2.png) [@KMBak](https://forum.signalrgb.com/u/KMBak)\ **Post date:** [October 8, 2025, 6:41pm UTC](https://forum.signalrgb.com/t/my-kingston-fury-renegade-memory-sticks-are-not-recognised-as-rgb-devices/196/36 "2025-10-08T18:41:41Z")
I have G.Skill now. Refresh is better but I discover another problem. Sometimes after random amount of time the RGB freeze. I think there is some incompabilty between SignalRGB and my memory kit. F5-6000J3036F48GX2-RM5NRK is recognized as AURA compatible RAM and not GSkill it self. Any plan for support these specific modules? ---
**Author:** ![SignalBadger](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.signalrgb.com/signalbadger/32/1654_2.png) [@SignalBadger](https://forum.signalrgb.com/u/SignalBadger)\ **Post date:** [October 9, 2025, 3:59pm UTC](https://forum.signalrgb.com/t/my-kingston-fury-renegade-memory-sticks-are-not-recognised-as-rgb-devices/196/37 "2025-10-09T15:59:51Z")
You can [submit a device request here](https://signalrgb.com/devices/), but sounds like it’s working generally. You can also create a ticket through [our contact page](https://signalrgb.com/contact/) if you want us to take a closer look! ---
**Author:** ![KMBak](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.signalrgb.com/kmbak/32/302_2.png) [@KMBak](https://forum.signalrgb.com/u/KMBak)\ **Post date:** [October 18, 2025, 11:24pm UTC](https://forum.signalrgb.com/t/my-kingston-fury-renegade-memory-sticks-are-not-recognised-as-rgb-devices/196/38 "2025-10-18T23:24:44Z")
I had to go back to the Fury. Unfortunately, the G Skill doesn’t work well with the iCue. Even though iCue theoretically has no effect on memory (strange, plugins disabled), it can suspend the RAM stick RGB - a known problem. But regarding the Fury, the stock firmware has no problem with smooth backlight animations. So I think there’s significant room for improvement with SignalRGB. ---
**Author:** ![SignalBadger](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.signalrgb.com/signalbadger/32/1654_2.png) [@SignalBadger](https://forum.signalrgb.com/u/SignalBadger)\ **Post date:** [October 20, 2025, 5:21pm UTC](https://forum.signalrgb.com/t/my-kingston-fury-renegade-memory-sticks-are-not-recognised-as-rgb-devices/196/39 "2025-10-20T17:21:02Z")
The performance of the Fury RAM sticks is based on how Kingston designed and manufactured them, and not related to SignalRGB. Unfortunately there’s no more room for improvement from our end, Kingston would need to install an onboard RGB controller that handles real-time effects with more efficiency. [Previous page](https://forum.signalrgb.com/t/my-kingston-fury-renegade-memory-sticks-are-not-recognised-as-rgb-devices/196.md?page=1)