Jump to content
Corsair Community

Corsair Dominator Platinum RGB 32GB Lights Unresponsive


BallsofSteel91

Recommended Posts

So I've had 4 of these running for a little over a month now, no issues. One morning when I turned the PC on and logged in, the LEDs were static and multicolor on all four of them (not my configured effect in iCUE). They are unresponsive in iCUE unless I manually force a firmware update. This fixes the problem until I shut down the PC, at which point the issue returns. A few notes:

 

I have a lightning node pro, H150i Capellix, and Asus motherboard all configured in iCUE with no issues.

 

The only new hardware installed was a Lian Li V2 Strimer Plus PSU extension cable about a week ago. The RAM issue has been going on for at least 3-4 days, but I'm not sure if it started the same day as the new cable was installed

 

When I first turn the PC on, before logging into windows, the lights are showing an old green "rain" effect I had set up. This is not the currently configured effect, but something from a while back. They've always done this, but I think it shows that the hardware itself is fine. Its only once I log into Windows and the lighting effects take place for the other hardware, that the RAM lights change and become unresponsive.

 

Anyone have any thoughts on what could be causing this?

Edited by BallsofSteel91
Link to comment
Share on other sites

Like other Corsair devices, the RAM has a software lighting mode (when CUE is running) and a Hardware Lighting Mode (when CUE is not running). What's not the same is how those modes are toggled back and forth. There is a switch in the RAM settings for "enable full software control". This turns on software mode. If it is off, then when you set a CUE lighting effect, the program writes it to the RAM storage. That is the effect you see when CUE is not running as well (green rain). One temporary workaround might be to revert to hardware mode (uncheck the slider).

 

Do you get the red triangle over the RAM when you open CUE on first load? It is a general warning and does not point to something specific. If this is happening every single time, it is a little more concerning. Most of the time it means there is some type of handshake error between software and device. You might try reloading your current chipset drivers. Some people get stuck in this after a Windows update. RAM and KBs seem to be the most often affected devices with the initialization issues.

 

More specific to this might be Aura or Armory Crate. Which MB series are you using and which software?

Link to comment
Share on other sites

If no red triangles, this might be something more basic. Try a repair install of CUE from Windows Settings -> Apps menu. Select modify and follow the prompts for a repair install.

 

If that does not clean it up, it's probably going to be related to Aura/Armory Crate.

Link to comment
Share on other sites

The repair install had the same effect that forcing a firmware update did. Fixed the problem, but once computer was restarted and I logged into Windows, the issue returned.

 

Anything specific I should be looking for in Armory Crate?

 

I also realized that my initial post is incorrect. I did add in a Lian Li V2 Strimer Plus PSU extension cable about a week ago. The RAM issue has been going on for at least 3-4 days, but I'm not sure if it started the same day as the new cable was installed

Link to comment
Share on other sites

Is Armory Crate the controller for the strimmer? If so, go to CUE and uncheck the "enable plugins" box in the general settings. That will release MB control from CUE back to AC/Aura. See if that makes any difference.

 

Aside from that, I am not sure what else to try aside from reinstalling Armory Crate, which is a major irritant since they don't use a savable installer. If the above did not help, I would start a support ticket with Corsair through official channels. Turn on 'debug logging' in the CUE settings so you can export the logs when asked. This is different than the usual RAM RGB issues that show up.

Edited by c-attack
Link to comment
Share on other sites

Looks like it was Armoury Crate/Aura Sync.

 

The way I have the strimer set up, it goes to the MB AURA Addressable Gen2 header, and I do see that in Armoury Crate (haven't had much time to play with the Strimer settings so this is my first time looking here since). I guess when I set up the strimer, Armoury Crate/Aura checked off "Memory" and that's where there was an issue with iCUE communicating with the RAM. Once unchecked in Aura Sync, it's back to working normally even after restarts.

 

Thanks for all of the help!

Link to comment
Share on other sites

×
×
  • Create New...