L33T5ON

Well now I feel a little dumb because I looked all over that screen and must have missed being able to click the actual DIMM and move it around. Thanks for helping me out Corsair Notepad :)

I have a 4x 8GB Kit of Dominator Platinum RGB (CMT32GX4M4C3200C16) RAM and while iCUE does show all 4 DIMMs no problem, the order of the sticks is incorrect. For example, when I change the LEDs on the ram directly to the right of the CPU in iCUE (what I will call the "1st" DIMM), it changes the 3rd physical DIMM. The 2nd DIMM in ICUE, is the 1st DIMM. The 3rd DIMM in iCUE is the 4th DIMM. And the 4th DIMM in iCUE is the 2nd DIMM. Motherboard is a ASUS Crosshair VIII Dark Hero currently running BIOS 3204, RAM is running firmware v1.03.26 and iCUE itself is v3.37.140. Any help or advice would be greatly appreciated.

As others have said, the problem isn't necessarily Corsair's fault/issue. In my case, ASUS released a new BIOS for the Dark Hero (version 3204) that included an LED Firmware update (it wasn't listed in the release notes but it said it applied a LED Firmware update during the BIOS update process). That update resolved my "red triangle" issue on my RAM so I can now have iCUE and ASUS Armoury Crate running/installed at the same time. I still can't get iCUE to control the Motherboard LEDs (it sees the motherboard and it's LED "areas" but won't actually change their colors) but that's not a huge problem now that I can open Armoury Crate and control them.

ASUS recently released a new update to their "HAL Central" (hardware abstraction layer) and I think that is what "broke" iCUE. In short, I think the new HAL update is basically trying to control the RAM before iCUE can "take control" of it so iCUE throws an error. As soon I ran the "Armory Crate Uninstall" tool from ASUS to completely remove that software and it's services (the services are actually the important part in this instance), iCUE was able to control my RAM again. The downside is I can no longer control the lighting on my motherboard but I'm sure a new update will get released from either ASUS or Corsair (or both) that will rectify the issue. The question is just what the update will be (BIOS, Software, HAL, etc) and when that will happen. Also, just to be clear, I had Armory Crate running alongside iCUE for a little over a month (just built this system a little over a month ago) with no issues. As soon as the HAL update got released from ASUS is when I started seeing these problems. I also have EVGA's Precision X1 installed and that causes no issues.

@Corsair James I can also confirmed disabling plugins within iCUE (ie: the new ASUS Motherboard Plugin) does not fix the issue. One thing I can say is that I saw some posts related to Easy Anti-Cheat for Halo MCC throwing this same error and people were saying it was related to having RGB RAM (for example, I have Dominator Platinum RGB RAM). Not sure if that's helpful or not but below is a link to one of those posts I found and a screenshot of the error (from both launching The Division 2 & Halo MCC). https://steamcommunity.com/app/976730/discussions/0/2666626567709303256/

TL;DR - The Division 2's code isn't calling the correct profile names and some of the profiles are missing lighting effects. Take a look at this post I found on Reddit a few days ago. I followed the instructions as was able to get the lighting effects working on my K70 and customized the profiles to enable lighting on my H115i Platinum RGB.