c-attack

Coolant temp? Or cpu/gpu temp?

Short Version: 1 & 3 -> Anyone with a pre-existing CUE Link hub that was set up prior to CUE 5.14 and the FW expansion to 24 devices needs to do a clean install of CUE. This has been discussed at length elsewhere, but in effect the fan enumeration changed when it went from 1-7 and 8-14 to 1-12 and 13-24. Lots of things tied to that identification. Export all your valuable profiles, clean install, then import your profile exports. Things will not work right until you do. https://www.corsair.com/us/en/explorer/diy-builder/blogs/addressing-over-current-protection-issues-expanding-the-icue-link-system-hub-to-24-devices/ 2) You should be able to save basic custom patterns like static, wave, ripple, etc. to DDM mode and the CUE Link hub and half the point of DDM is make it work like the keyboards with an active save mechanic (whether you like that or not). I’ll try and test some combinations later today. What’s your hardware? CUE Link AIO and QX fans?

Yes, unfortunately this seems to be the only option right now. There is another thread where we worked through it along with some additional issues, but if you have new fans or need to configure a Commander Core or XT, you likely need to uninstall 5.14, download 4.33 from the website, run the lighting wizard to auto detect, then reinstall CUE 5.14 over the top. There should be a correction in the next release, but for the moment this is an issue.

Yeah, unfortunately I’ve seen and reported that one as well. My tests were for the XD5 Elite, but not too surprising the CUE Link AIO does the same. I believe the hub is using CPU temp as the DDM control variable even when the custom curve specifies a native liquid temp from the AIO or XD5 Elite. So for your original issue, you create a DDM mode curve based on coolant temp (20-45C range), but it substitutes CPU temp as the sensor causing you to run at the high end of the curve at idle. If you set the actual Quiet fan preset in DDM mode, it seems to behave itself. This is probably another opportunity to remind Corsair the invisible presets don’t benefit anyone. Even if they don’t want us to be able to modify them, show the graph data “greyed out” so users can understand the behavior.

I am trying to get a look at those CUE Link Temps (orange). The ones in the low 30s are normal. The 4th one is 41C? If that is liquid temp, then that is warm. Be aware there is often a default CUE alarm set to flash fans red at 40C liquid temp. You can deactivate it and nothing happens at 41C except the CPU is +1C warmer. Regardless of the above, other users have reported some random CUE Link pump stops in the past. I am not sure we know why it happens, but most often it is a one off event. I guess just keep an eye on things.

You probably needed to clean out the registry files as well. For some reason Corsair has removed that part from their posted clean install directions. Maybe too many people deleting the wrong thing. At this point I would use to Revo or some other free professional software removal tool to clean out any remaining files. It should give you elevated permissions so you don’t have to back into safe mode again.

Definitely a necessary step because of the file corruption. Anytime you see it grayed out in the Windows menus, things have gone wrong. That is not likely specific to v5.14 and we have seen a steady stream of these type of install/registry errors since CUE 5 debuted. So the flashing red is after doing the clean install? If before, I am not surprised and hopefully it’s now cleaned up. If after, keep an eye on things. One of the difficulties with the new Link Tech is the device is entirely dependent on the software to supply power and control. If it thinks there is no device there, it might not supply power. I haven’t seen any other loss of power issues reported this far. One thing I can confirm is there is an issue with custom curves on the XD5 Elite models resetting to a “quiet” preset that keeps the pump at 800 rpm — too slow for any load situation. However, the same behavior on the AIO could only drop the pump to its 2000 rpm minimum. You can’t overheat the AIO at 2000 rpm. The pump definitely needs to stop and that’s not something you can do in the software. I don’t think there is a connection.

This is an actual overheat warning. Flashing red fans, especially before Windows and CUE loads is a hardware temp detection feature. There's not enough information here to guess why. However, if you have a CUE Link AIO you need to do the clean install to make sure all devices are detected and in proper sequence. If you have an Elite Capellix Model, most of this discussion doesn't apply to you and we still need to figure out why the AIO alarm is going off.

It seems like the AIO is actually overheating. That’s not something g anyone else has reported, but possible if it sets pump and fan speed to absolute minimum. Definitely possible if it’s not making the pump run and that is no longer a guaranteed factor without its own SATA cable.

That’s where the CUE Link 4 way splitter or Y-Splitter come into play. You don’t need to set it up like a traditional series circuit. All paths need to come back to either side of the hub.

This part is specifically about the missing CPU Package Temp data in CUE 5.14. Not related to the corrupted files. Unfortunately, corrupted files seems to be the most prevalent user side error with CUE 5 and this does happen. If it happens on a regular basis, then something is interacting with CUE in a negative way, but that is not what most users report. Most of the time this is a one off event. I hate Windows safe mode and usually recommend most people use Revo. The free version will do the job. Don't buy anything. Uninstall it when done if you like. That will give you the option of the registry clean as well.

You can't go back to a prior 5.xx version. It's all server side, so no way to pull down the file. The workaround for mdwflyer was to uninstall CUE 5, then install CUE 4.33 and run the normal lighting wizard. Then proceed to install CUE 5 again over the top of CUE 4. The configurations files stay and the lighting config remains intact. Note this only works for solving a configuration issue. It did not resolve the end of the line physical lighting issue and we are still working on that.

OK, can confirm I am seeing this as well. Likely in place for most users. In general, Sleep mode tends to be problematic for CUE and I locked CUE up several times working different combinations of effects and sleep/wake cycles. However, if you need to use it what did work for turning off your lights in sleep mode is to set a black static layer in Device Memory Mode and then leave DDM toggled on when you put the PC to sleep. That worked multiple times for me and turns the lights off prior to entering S3.

Not sure how this slipped by and probably too late now. Nevertheless… Did you finish already? Hopefully two separate loops for dual GPUs and CPU?

Murals are not part of the profile back up system and not part the profiles at all. It used to be something called “instant lighting”. Just a quick drop down color for your entire system. Toggle on/off. It has since grown into something more but doesn’t really have a way to preserve the files and still exists as a toggle state. Good job tracking down the bad file. Hard to believe the DPI library is capable of preventing launch, but there it is. At least that’s an easy setting to recreate.