Problem with Trident Z RGB post-BIOS update.
Problem with Trident Z RGB post-BIOS update.
I just reassembled my setup using an Asus Tuf X570 Plus Wi-Fi and R7-5800X3D. Right out of the box, my Trident Z RGB RAM was recognized by both G.Skill software and OpenRGB, making color adjustments straightforward. My motherboard ran an outdated BIOS without the latest AGESA microcode, so I decided to upgrade it. It looked safe at first. But after updating the BIOS, the RAM stopped responding to G.Skill Trident Z Lighting Control or OpenRGB—just a default rainbow effect. When I tried changing colors in either program, nothing happened. However, saving a color change to a device in OpenRGB restarted the rainbow cycle. So while it seems like the RAM is detecting something, it can't apply new colors post-update. I installed Armoury Crate hoping Aura would help, but it didn’t find anything beyond the motherboard and GPU. I removed it. I upgraded from BIOS version 4204 to 4403. If anyone has suggestions or experiences, please share. I might consider reinstalling Windows again next time.
I previously handled the CMOS reset by disconnecting the battery briefly, but nothing changed. While working on this device, I became more precise about the issue after the BIOS update. If OpenRGB attempts to fix memory issues first, it becomes unusable until the next boot and displays the behavior I described earlier. Allowing G.Skill’s software to run initially resolves the problem, letting me apply a color profile at startup to bypass the default rainbow cycle. I’m now using both programs for RGB to completely avoid this problem. It’s frustrating, but I finally understood what was happening. OpenRGB hasn’t been updated since December 2021, which makes me wonder if it conflicts with newer BIOS versions. It’s odd that G.Skill’s software seems to enable compatibility across Intel and AMD models, yet there are still Trident Z RGB differences.