My RAM Stopped Working After Using OpenRGB - Any Fixes?
Asked by
TechWhizKid87
Hey everyone, I recently encountered a problem with my RAM after installing OpenRGB on my Linux Mint Cinnamon setup (22.2, kernel 6.17). I didn't realize the potential risks before installing it, and now one of my DDR5 RAM sticks is not being detected by either the motherboard BIOS or my operating system. That leaves me with only 16GB instead of the 32GB I should have.
I've already uninstalled OpenRGB to avoid further issues, and I've tried reseating the RAM and swapping slots without any luck. I even disabled EXPO settings, but that didn't help either.
I found a utility called ddr5-spd-recovery that claims it can restore SPD data if it becomes corrupted. However, when I ran the command to check for detection, it showed that my faulty stick wasn't detected at all. The good RAM stick showed up fine, but it seems like I can't flash the bad one because it's not recognized.
Has anyone experienced something similar or have any recommendations before I consider buying new RAM? My RAM model is TEAMGROUP T-Force Vulcan 2x16 GB, DDR5-6000 with CL30. Thanks in advance!
Answers
Honestly, I’d suggest just RMAing the defective stick and phase out using OpenRGB entirely. RGB effects can be appealing but can cause issues like this one. You could play it safe and go for a non-RGB setup if you’re done with headaches.
Reply to this answer
Wow, that sounds frustrating! Are you completely sure that OpenRGB is the culprit? Sometimes hardware failures can happen out of the blue. But if you’re looking to have it repaired, you might need to consider RMAing it back to the manufacturer.
Reply to this answer
Add your answer
Answers are reviewed before publication.
FixItFreddie42: I think you're spot on. The recovery tool you mentioned actually addresses situations where poorly designed software messes with the SPD data, and it seems that's exactly what might have happened with OpenRGB. If it’s corrupt, your RAM might not be recognized at all, leading to the issues you’re seeing.
LinuxGuru78: It’s strange that it just suddenly happened after using a new program. It might be worth checking if the RAM can be RMA'd before buying new sticks.