OpenRGB caused one of my RAM modules to stop working, any possible fix?
Posted by ThatRustyBust@reddit | buildapc | View on Reddit | 86 comments
My OS is Linux (Linux Mint Cinnamon 22.2, 6.17 kernel)
Alright, so I had no idea that OpenRGB could do this before it broke, I only did my research on OpenRGB/SPD after installing it. (also, my motherboard has no SPD Write Protection feature)
But anyways, one of my DDR5 sticks is now no longer being detected both by the motherboard BIOS and by Linux. So I'm down to 16GB of RAM.
I did uninstall OpenRGB though, to prevent further damage to devices.
I have tried reseating the RAM and swapping slots, but it seems to only confirm that the stick that is broken, not the slot.
And yes, I tried disabling EXPO to see if it helps. It didn't.
Then I discovered the Linux utility ddr5-spd-recovery that can help flash SPD data to the stick in case it goes bad.
Well, guess how that went?
$ i2cdetect -y 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- 4b -- -- -- --
50: -- -- -- 53 -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
I have the faulty RAM module in the slot that should correspond to a 51 here, and the good RAM stick is in the slot that should correspond to a 53. (I'm not sure what the 4b is, but I guess it's another device or something different, since RAM should only be using 50-57.)
So my understanding is that my computer is not even realizing there is a stick in the slot at all. Therefore, I can't even flash to it. I was successfully able to dump SPD from the good stick, but can't flash to the bad stick.
Anything I can do about this short of buying new RAM sticks?
My RAM is TEAMGROUP T-Force Vulcan 2x16 GB, DDR5-6000 with CL30. I'm going to edit in the exact model number after I post.
Mauro88@reddit
Even if OpenRGB has worked great for me, this scared me enough to delete it. So now its rainbow or nothing in linux. Meh. Anyone know if there is any other software that can work with asus boards that is safer then OpenRGB?
PERNlClOUS@reddit
Late, but SignalRGB. It has mutex, it realistically won't let you open it or work until you close icue, and other things that control RGB. So that you never run the risk in the first place.
Lil_Azzaro_Sung@reddit
none so far, unfortunately :/
JohnnyJacksonJnr@reddit
Well that is unexpected. Are you 100% certain that OpenRGB caused it?
Either way, you might end up having to RMA it.
aminy23@reddit
If you read the description of the recovery tool, that seems to be exact situation: https://github.com/ubihazard/ddr5-spd-recovery
pythonic_dude@reddit
Not to defend the absolute fucking morons who coded those parts of OpenRGB, but nowadays the app just crashes 99.99% of the time when it tries to read anything on SMBus, let alone try to write. Not surprised though.
ArkhamRobber@reddit
Funny enough it used to work for me and i stopped using it the other day. Now it doesnt work. Didnt change anything. So i just install. Need really use the rgb but hate having to use asus armoury crate. Wont be paying for signalrgb either
Woodcat64@reddit
I can't imagine paying for subscription to be able to control RGB lights.
Willing_and_Fable@reddit
And destroy RAM 🤖
PERNlClOUS@reddit
SignalRGB has Mutex and realistically, shouldn't. Unlike horrible OpenRGB.
TheHelplessTurtle@reddit
Signal is a different group. Tried both and OpenRGB never worked quite right, and it seems that was a blessing in disguise now. Signal is backed by several groups I trust, so I'm assuming it is fairly reliable compared.
TheHelplessTurtle@reddit
Signal has a free tier. Limits some things, but for basics it works pretty well.
Melodic_Arachnid8311@reddit
Asus still has their Aurora RGB software available for download on their site so you don’t have to use armory crate.
It’s kind of a pain to find so reply if you need a link. I don’t have a time to search at the moment, but I will later.
TheFotty@reddit
Pretty sure it's end of life though right?
Melodic_Arachnid8311@reddit
It seemed up-to-date when I downloaded it six months ago but admittedly I haven’t been paying attention since.
I tried armory crate, and that was such a piece of garbage I’ll just go without or look at open source options if for someone reason Aurora stops working or has critical vulnerabilities.
TheFotty@reddit
This page indicates it has been folded into armory crate and will soon stop receiving standalone updates.
https://www.asus.com/campaign/aura/us/download.php
ArkhamRobber@reddit
You can still download it for use. I download it and tested it when i was trying to see why OpenRgb wasnt working. It works just like the version within armoury crate. It just not longer receives any updates, so eventually it may stop working on some devices/future devices, id imagine microsoft might break compatibility first though
TheFotty@reddit
Who makes your ram? I have Corsair ram and Asus mobo and use icue for ram RGB control. Only issue is if you want true full color sync between the various RGB components but I prefer the options in icue anyway for the ram.
ArkhamRobber@reddit
Its not my ram its actually the fans the no longer work with open rgb. They used to work fine. Didnt touch the rgb for months. Tried to turn it on to see something and openrgb would only control my gpu's rgb. I uninstall it and just use the armory crate when i wanna turn it on. Which is like once or twice a year
alvarkresh@reddit
Stuff like this makes me happy that I normally just let my RAM happily rainbow-flow their way forever and ever.
The only time I've ever gone for a specific color was by using the specific G.Skill software for my G.Skill RAM, and the ASRock motherboard I have has BIOS-level control for all the ARGB connections so I don't even need to mess with OpenRGB.
screwdriverfan@reddit
Not so fun fact: I had to rma G.Skill TridentZ in 2018 due to SPD being bad after changing lighting. Granted, it was probably my fault cuz I used two seperate pieces of software to control rgb.
ratshack@reddit
Honestly, this is the first time hearing of separate control systems for RAM RGB.
I think I’ll stick to vanilla rainbow-flow. I mean when I happen to see it there is usually something wrong anyway.
pythonic_dude@reddit
G.skill uses an ancient rgb controller in their ram that hasn't changed for probably a decade.
I don't have much of a choice on linux, and will probably just buy some random heatsinks (with or without rgb) eventually to replace mine. Or maybe SignalRGB will launch earlier.
Symphonic7@reddit
Damn bullet dodged for me when I installed it and it didnt work. Awesome. Now I should probably just keep SignalRGB off unless I really feel like it.
tesfabpel@reddit
Wow, the GitHub's repo's author is incredibly obtuse here.
Imagine saying "imbeciles" to OpenRGB devs and not the HW manufacturer who allows anyone to brick their product just to control lighting (or even worse, if lighting and critical RAM info are in the same space!).
slackwaredragon@reddit
Both situations are pretty boneheaded, imo. Once openRGB realized the issue they should have pulled that feature until they can investigate. Additionally the hardware manufacturers should be held accountable for making it so easy to break. That being said I wouldn’t be surprised if it wasn’t intentional on the manufacturers side.
AsrielPlay52@reddit
It wasn't
How Ram R&D and advancement is often flows is from Data Centers and then only reach to consumers.
They research for Data Centers first, and then adapt to Consumers.
Consumer division assume users never touch it either (and to be fair, that's a good assumption) and didn't bother to write protect it
ThatRustyBust@reddit (OP)
Apart from normal system updates (which, on Linux, shouldn't affect much as I don't recall an update related to SPD occurring, unless a kernel update caused it), I don't recall doing anything recently. A few days ago I installed OpenRGB, then the next day I happened to notice while playing a game that RAM was out of 16 GB instead of 32 GB. I'd been using these sticks for about half a year without issue- I don't know if they can be RMA'd. If it comes to buying new RAM, I guess I'll just have to.
KlausKoe@reddit
youw saw https://old.reddit.com/r/buildapc/comments/1r3fwxc/openrgb_caused_one_of_my_ram_modules_to_stop/o543ygv/?
ThatRustyBust@reddit (OP)
Yep, I did. It didn't work though, which I explained in my post
WherePoetryGoesToDie@reddit
I'd be surprised if they weren't still under warranty. I can't think of the last stick I've bought that didn't come with a limited lifetime warranty.
The current situation being what it is, though, they may just refund you instead of repair/replacement.
Elias23Player@reddit
Yeah, used it once years ago on a perfectly good working set of ddr4. 2-3 changes all LEDs off and unresponsive. Worked fine with the Asus bloatware before using openRGB, had to RMA the kit.
AgileIllustrator8147@reddit
Here's how I solved this in my Elementary OS Linux install: ran OpenCode using its free model and asked it to clone and build a custom version of OpenRGB with RAM scanning disabled.
Took about 10 minutes and I had a clean version that runs without further issue. That was after many failed attempts attempting some of the suggested manual fixes.
brendan135@reddit
Okay, after reading all this and dang near having a panic attack and rushing to my PC to uninstall - does anyone know if signalRGB poses any risk on windows?
elmiondorad0@reddit
I'm late to the thread but SignalRGB and OpenRGB literally fried the led strip on my Sapphire Nitro+ 7900 XTX TWICE.
Then the case fans and the controller.
I thought it was a factory issue with the card but after I got the third card I've not touched the colors for over a year now everything has worked minty apart from some case fans/strips not turning on when powering the PC but it fixes on its own after shorting the header.
I tried matching the whole setup to a wallpaper today because i did some deep cleaning and organizing but i have such severe ptsd i just nuked the software (MSI Mystic light) and reverted to default. Not touching signal or OpenRGB. So I think I'll be stuck using MSI's software for my mobo and HyperX and Logitech for my KBM respectively.
Shit is ass, bro. It's 2026.
screwdriverfan@reddit
I had to rma G.Skill TridentZ in 2018 due to SPD being bad after changing lighting. Granted, it was probably my fault cuz I used two seperate (but official) pieces of software to control rgb.
SkellySkeletor@reddit
I just recently switched from Signal to OpenRGB because signal was the worst paid application I’ve ever used, full stop. Purchased themes would disappear from my library, devices would randomly fail to be detected and not work, and don’t even get me started with how terrible the user customization of effects is. All to say, it’s not going to brick your computer, but it’s a gamble if it’ll work at all.
brendan135@reddit
That does sound quite frustrating, sorry to hear you had all those difficulties with the platform. My personal use with signal has always been the free version, I haven’t desired any themes (or know the specific layout of all my LEDs well enough) to justify it.
Beyond issues as a paid service, what did you think of signal? I guess if my main concern is a universal led controller app and to not brick my ram during the crisis, sticking with signal is my best move.
SkellySkeletor@reddit
It works fine enough for putting static colors or simple rainbow wave effects & unifying all your LEDs, I'm just a toddler and like seeing cool patterns and such. The biggest issue in general with the app, though, was that it was 50/50 whether your lighting profiles would start with the computer at all, and manually going in to start them often led me to see that the app just forgot all configurations I had made. So, your results may vary, but it should work for what you want.
brendan135@reddit
Okay, now that startup issue is one that I frequently have with signal rgb. I’ve given it all necessary permissions and set it to launch on start up, but it feels like half the time I’m having to do it manually after booting up.
Vertrixz@reddit
I tried using signalrgb when I first built my PC and honestly, too many issues to even count. I've decided to not bother and just leave my RAM without lights, and honestly looks much better and less tacky.
Woodcat64@reddit
Or Windows Dynamic Lighting.
SwiftUnban@reddit
Maybe someone smarter than me can chime in, but is it possible to use one of those bios flash tools, or a tool similar to flash the bad module with the firmware from the good one?
ThatRustyBust@reddit (OP)
Well, the bad module doesn't seem to be detect no matter what I try, so...
ketsa3@reddit
1) Remove stick, reboot.
2) Reinstall stcik and reboot.
ThatRustyBust@reddit (OP)
Already tried reseating and changing slots, clearing CMOS didn't seem to help either
Successful-Day-3219@reddit
Yikes, similar specs on a Linux Mint and OpenRGB setup. Ditching OpenRGB immediately, which frankly, has been a piece of shit to deal with from the get go.
Rainmaker231@reddit
I agree, idk why everyone's been glazing it, I did not like the ui and settings at all and took a long time to fix it and configure it. And reading this post, I guess it just isn't worth it
Worldly-Ingenuity843@reddit
Well shit. Good thing I don't run OpenRGB regularly because my mobo seems to be capable of retaining the RGB settings even after turning off. I am going to get rid of it after I get home.
RZ_Selected@reddit
Which Mobo do you use ?
Worldly-Ingenuity843@reddit
Asrock B650 Pro RS. I am using simple RGB settings only though, aka constant or breathing. The more complicated ones require software to run constantly in the background and take up CPU cycles.
d0m1n4t0r@reddit
Same... scary shit.
Technical_Yam_1265@reddit
Use caution. OpenRGB soft bricked my mobo. Had to clear CMOS to post.
ketsa3@reddit
So it wasn't bricked...
Josie1234@reddit
same
TakingOnWater@reddit
Wow. Is there any chance this could affect DDR4 RAM that doesn't have RGB at all? Seems like a dumb question probably so please excuse me if so... just wonder if OpenRGB could still mess with the hardware even if you're not explicitly changing any RGB related stuff on it.
Booty_Bumping@reddit
The chance of this being a problem is quite low. Individual IDs for hardware are hard-coded in OpenRGB, it's not going to try to use the driver for RGB RAM on non-RGB RAM.
cool_slowbro@reddit
Unrelated but the state of PC RGB is an absolute fucking joke. There's no simple straightforward way to "just" control all your RGBs in a sane manner. You have to download random programs, some which don't even clean after themselves upon removal, and even then you get conflicts with other software (SignalRGB fucked with my wooting software's RGB settings and was a pain to completely remove, you have to basically Google for all the individual bits to manually take away).
The year is 2026 btw, I expected this kind of stuff to have been sorted a decade ago.
elaborateBlackjack@reddit
For as much hate Corsair's iCue gets... It's lit the only software that has worked for me 99% of the time... So yeah I've paid the Corsair tax, but I never have to fiddle around with multiple softwares to see who's fighting for control over the RGB on the keyboard, mouse, fans, AIO, RAM and light strip. And I can turn it all off with one button on my keyboard
Ezzy77@reddit
For me, it just randomly forgot my keyboard and its settings until it forgot the keeb completely.
Tee-hee64@reddit
No iCue on Linux so it’s openRGB or nothing.
Ezzy77@reddit
There is ckb-next, but I can't recall if it controls Corsair RBG. At least it does control mice.
Sinaaaa@reddit
It's crazy that anyone thought SPD write through external software like this is a good idea.
ThatRustyBust@reddit (OP)
Also that whoever designed my BIOS thought SPD write protection wasn't a necessary setting to include.
Sinaaaa@reddit
Tbh I feel it's a bit stupid the spd is not read only to begin with.
CruelMarmoset@reddit
Not ram related for me yet, but Open RGB does some funky stuff to my computer. If I run the program, it stops reading the smbus temp and it goes to zero and then it no longer updates CPU temp so do example if I let that go, it would freeze at my cpu temp reading like 46 degrees and then if I booted up cyberpunk it would continue to think it was 46 degrees and thus the fans don’t respond appropriately. I’m not smart enough in the PC world to understand why that happens, but it’s an issue I can’t find an answer too. If I used my pc more intensively than I do, I fear this would fry my cpu. It’s really frustrating. So far putting the pc to sleep and waking it back up fixes this, but I don’t think it should happen at all.
m4tic@reddit
But you can be, you're already there. Read some docs on specs and standards.
baggyzed@reddit
You can read all the docs and specs all you want. When it comes down to chosing to use a piece of software, it's still all about trust.
m4tic@reddit
I wasn't referring to trusting an app, my comment was touching on eliminating self-doubt realizing capability through acquiring knowledge.
baggyzed@reddit
To what end?
CruelMarmoset@reddit
I appreciate the confidence lol the weird thing is I cannot find anyone that seems to have the same issue. I’ve posted about this before with a video of it happening and I don’t think anyone even commented. Since I know about the issue it’s not a huge task to manage it. But I wish it could get fixed.
Destione@reddit
Have you tried to boot it with every memory setting in the BIOS set manually?
ThatRustyBust@reddit (OP)
I already disabled EXPO and tried to boot so I'm not sure what else I could do jn the BIOS that's RAM-related, but I'll see if it boots on a default bios.
Destione@reddit
Default is that the timings are read from the SPD. EXPO is just OC. There is a large list of timing settings and voltage settings for the RAM, if it reads only garbage data from the SPD, it will not initilize the module. You might look for something like advanced settings or so to make the options appear.
globadyne@reddit
It’s the only option in Linux as well I just use it to set my ram to white as the rainbow bugs me
But don’t want to effect my ram or go back to windowed
I have Kingston ram on Asus Board
theresleadinthewater@reddit
i used openrgb once to disable my gpu rgb and it persists between reinstalls even, hope this doesn’t affect me
Deadly_Fire_Trap@reddit
Why is all RGB software just such shit for one reason or another? I've used OpenRGB in the past but have since switched to iCue, which has its own slew of problems and issues. But its like every single one comes with some stupid caveat.
Tee-hee64@reddit
OpenRGB been working fine for me on Kubuntu. But I’ll be uninstalling it now to be on the safe side. Memory too expensive to risk losing it.
mycheese@reddit
Are SMBs STILL being corrupted? It's my understanding that all SMB writes are literally impossible. Ram is too expensive to be playing with this stuff
Tee-hee64@reddit
I’ve not had the problems listed by I’ll probably uninstall openRGB to be on the safe side. Indeed memory is too expensive to find out. I’ve got 32gb of DDR5.
BoludoConInternet@reddit
good thing i stopped using that shitty software.
it was handy to change all my rgb to a static color when i turned on my pc but it required so much workaround to do something as basic as running on start up that i gave up on it and went back to the classic manufacturer's software
ratshack@reddit
Ok that is actually a pretty good use case but yeah, naw.
Also, TIL software can literally kill RAM.
Mind blown like an SPD.
mcds99@reddit
At first I was, NO WAY, then I googled "can openrgb damage memory" that was and education.
battler624@reddit
RMA it and stop using OpenRGB.
I'd honestly drop all RGB completely but thats up to you.
Fredasa@reddit
Preach. Back in olden times when people still bought RAM, I was quite fond of saving an arbitrary $5-10 for a handful of LEDs which, if they were on my sticks, I would bend over backwards to disable regardless.
This thread is a nice TIL, though. Note to self: Research any app designed to probe DRAM.
alvarkresh@reddit
And note to self: find out how to turn off access to writable parts of the SMBus and SPD on DRAM.