c-attack

No. Even with fans off it would take you 20 min of max load to bring the coolant temp to 60C. That is the upper limit of the device and system and you should never be that close. It means the pump stopped flowing and the water trapped into CPU block cooling fins heated up to 60C. That can happen with a light load and no liquid flow. There seems to be a truckload of wonky issues on the new CUE 5.14. There is no reason the Elite Capellix model pump should ever stop. It's wired for power to the Commander Core and then to the SATA/PSU. In theory, the Commander Core could glitch and stop passing power on to the pump. However, we have seen this reported as a one off event since the beginning so it is more likely this is more of the old, rather than some new bug. Most users previously reported the pump failed to start with Windows at the power on moment. A restart or shutdown and start cures the issue. That is some type of hardware power on error rather than software. I think you simply note whether the pump is working at power on each time right now. It should become apparent within 30 seconds if it's not, both from the rush of fan noise, flashing lights, or in the case of a power delivery failure the LCD will be off too.

This is normal and those are very small differences in score for those two benchmarks. The cpu-z bench is very sensitive to any other processes in action and even with CUE closed you may see day to day variation. Cinebench (any version) usually causes you to hit the power limit and subsequently downclock. This makes your score dependent on your CPU’s ability to as fast a possible just under the power limit. In both situations you are running a max cpu usage test. Anything else running decreases your score. Open up a browser window and you drop points. Start killing of Windows services and you go up. Neither is important unless you are trying to register a competitive score for posting.

You can’t transfer a profile from software to hardware mode (now DM mode) or vice versa. Each mode has its own specific rules with hardware profile rules being both model and operationally specific. You always will have lower capabilities in hardware mode. Presumably the lighting isn’t that complicated. For hardware assignments, you just have dig in and do them again. There are some restrictions since you need the software to execute some actions. Once you’ve done one HW profile, those assignments can be copied to the Hardware Library and pasted to other HW profiles. If you have complex macros, you might be able to Windows cut and paste them over. KBs always required an active save, but now all devices do as well. The little SD card below the toggle switch is the save button. The new Device Memory Mode has a toggle state switch. Once you put it into DMM mode, you must toggle it back out to return normal functionality unlike the old system where leaving the tab auto-saved and returned you to a normal state. This is going to cause some issues as people learn to adjust to the new system.

A picture might help. Serial number likely will not, although a part number “WW____” is searchable.

So there have been quite a few of these false pump failure issues on the Capellix AIO series since it originally came out. We have theorized the problem is a failure off the internal tach sensor or circuit on that 3 pin connector, which is somewhat unfortunate since it’s not required for the AIO to work at all and that tach wire is there to satisfy the motherboard cpu boot protection feature. However, this is the first time I think any one actually has a concrete moment to link it back. Most users simply power on one day and bam… everything starts flashing red. More unfortunate is there isn’t a user side fix for this. As you’ve seen, nothing works to reset it and you can’t control anything on the Commander Core while it’s in this state. You have to contact Corsair Support for a hardware replacement. You don’t have to explain too much. You turned it on, it was flashing red, the pump clearly works and the CPU does not overheat, but you can’t use the controls. They have seen enough of these now to know there isn’t a solution. If you can, ask for the Advance RMA where they ship you a new AIO first on a credit card hold, then you ship the old back and they cancel it. That will cut the down time. Also, when you submit your ticket, make sure you include the purchase invoice for the AIO, a picture of its serial number, and your full name, address, phone number even though those things are on file. It will save you 2-3 days of back and forth later.

The usual cadence is every 4 weeks, so likely another 3 weeks away.

There appears to be a Lighting Wizard or lighting configuration problem in 5.14 for the Commander Core and XT. Multiple users have reported this and the wizard fails to properly detect and manual setup does not work either. The only workaround we found was to uninstall 5.14, download the old CUE 4.33 from the main website, and run the Wizard while on 4.33. Then install 5.14 back over the top of 4.33 without uninstalling. The lighting config file is preserved and this allowed several users to set up their fans and then continue on normally. This is a known error and there should be a fix in 5.15 if you prefer not to jump through hoops.

This is an XD5 Elite LCD for the CUE Link system? I have no seen anyone else post about a screen failure. Can you add in more detail? Just stays black one day at power on?

Hardware Lighting/Assignments/etc. is now "Device Memory Mode" or DMM. However, you are not the first to report this and it is a confirmed bug in this release. The RAM does not drop out of CUE in DMM/Hardware mode when the PC enters S3 sleep. The only workaround I found was to create your static black layer in DMM mode, then manually toggle the RAM into DMM mode prior to entering sleep. It will stay in DMM mode until you toggle it back off at a later time.

A few other people have reported the loss of package temp on this release, but all of them were AMD and that has been on ongoing issue for a while on some of those models. You're the first I have seen on Intel and my XD5 LCD pump will show CPU package temp for my 13900K and it is present in CUE as a data point and source. Normally I would say do a clean install, but you've already done that. Not sure why package temp is missing for you.

No, it will not damage the hardware. The RAM red triangle in CUE is a communications error. You can pull up HWinfo or something similar and you'll notice it can't read the RAM temp data either in this state.

Try reinstalling your chipset drivers and make sure you quit CUE before you do it. Usually this (red triangle) happens when CUE gets tied up on the SMBus and can’t communicate with the RAM. I don’t know why it happens. Program conflict is one, but it certainly happens without that and I’ve seen short stretches of it as well. As annoying as it is to do, a clean install of CUE may help as well if the problem is with the Corsair LLA service.

Did you recently update to CUE 5.14? This version has the new UI changes but critically for CUE Link users expands the device capacity from 14->24. This caused the fans to be renumbered and it's not going to match your previous configuration. Anyone with CUE Link gear needs to do a clean install to clean out any old config data. Make sure you export your profiles first so you can import them back later. Might need to reapply some lighting effects to specific fans or devices. https://www.corsair.com/us/en/explorer/diy-builder/blogs/addressing-over-current-protection-issues-expanding-the-icue-link-system-hub-to-24-devices/

Yeah, don't get too worked up over the CUE CPU temp reading or it's % load either. If you want detailed CPU temp info, use HWinfo. While we are talking about it, CUE's core temp numbering is incorrect for Raptor Lake and has been for a long time. I don't even leave my cores up on the dashboard anymore. You've already figured out it provides a different reading for package temp than HWinfo. Use HWinfo when trying to accurately asses core behavior, both for the temp and the frequency/VID/Voltage values you need to make sense of it. This is normal behavior these days for Intel. One core spiking is some minor task being executed and the CPU is doing what it's supposed to do -- respond rapidly. A slightly more complex issue is when all the cores respond to these minor tasks and this can sometimes happen with some manual overclocks. The CPU behavior has become very sophisticated and the brute force manual OC is not a great option. However, the temps are still fairly simple. When a core sparks up, it will warm up. No amount of pump speed, fan speed, or radiator real estate that prevent it from heating up as voltage is applied. The CPU IHS transfers the heat to the cold plate on the block, which in turn transfers to the water. The water transports heat to the radiator for dissipation. The cooling system is a waste heat removal service. It's fun to set up a massive case with yards of radiator length, but when your CPU is sitting at idle and only punching 17-23W, it doesn't make a difference whether you are running a 3x3m square external cooling system or a little 120mm radiator. The cooling system only has 20W to get rid off and all CPU temp results are voltage and conductivity alone. If we pair your motherboard and CPU with any cooling method or brand, the idle temps will be effectively the same aside from minor differences in thermal conductivity on the cold plate. It's when you load up your 600W GPU and 300W CPU that you can start showing off and blowing that heat all over the room while maintaining excellent hardware temps. If you get the mount wrong, you will see CPU temps 15-20C higher than expected. They will instantly hit that 95-100C mark when they should not. If you get the mount just a little imperfect, you might see a large disparity between core temps when at full load. However, this is no longer a reliable metric as these 8+16 CPUs all have a health 5-9C core differential between best and worst cores. Too many cores, too close together. There is some heat sharing and some of them will be better/worse for it. So a slightly imperfect mount might run just a touch higher than expected. Don't use idle temp to measure that. Use a full stress test with a linear load. I usually recommend CPU-Z "bench test" because it is under the 253W Intel power limit so you won't bang off the ceiling and downclock while providing an even load. This is a good way to test multiple things, like pump speed vs CPU temp or your heat transfer.

There is definitely something going on with fan/pump curves and the "new" Device Memory Mode as well as some glitches when running from normal software mode. There seem to be a lot of shades of this and new reports are coming in frequently for different gear. At this point I am just trying to categorize into controller type -> Does X, when I do Y. I am a little short on workarounds right now. Older devices still show a static color option under custom in DDM. My CUE Link stuff has no custom options. Presets only. I believe this to be an error as the CUE Link hub has higher hardware capabilities than most other devices and at a minimum there needs to be a static color option so you can do 0,0,0 (off).