c-attack

C:Users/(name)/App Data (hidden)/Local/Corsair

You will never see a meaningful difference between the QX and RX on a multi-fan radiator setup. If you were running a 120mm radiator fan test you could create some differences at high watts and high fan speeds. On dual 360mm radiators (?) all of that yields to higher surface area and that’s the point of maximizing your radiator space. You can run whatever fans you like and speed becomes much less important. The RX cost less because it’s a lower tier model. Don’t get caught up the airflow and pressure spec game. Those are marginal differences. If you are running single sided fans on a 45-60mm radiator with a relatively high FPI (18+), then there could be a measurable difference (1-2C liquid temp), but if you’re using normal radiators or standard 30mm AIO rads it’s not going to matter.

It appears there may be an issue with CUE Link XD5 devices "resetting" their custom cooling curve at random intervals. This is a new system and brand new hubs and hardware with a clean CUE install. Each time I make a custom curve for the XD5 Elite, it resets back to the default custom cooling curve at a later interval. It does not seem to happen with fans on the same CUE Link circuit. Anyone running a custom curve with a CUE Link XD5 may need to pay attention. That default curve is 20% up to 45C. That's only 800 rpm on D5 pump and will lead to temperature problems when loaded.

There is going to be a lot of confusion with these changes. Device Memory Mode = Hardware Mode (Lighting and Cooling). They have changed the mechanic to work a bit more like the current keyboard lines with active saving required (at least you get a prompt), presumably as a way to tidy up or create more UI space. The functionality has not changed, but if you have older gear it's going to feel a bit strange. You go into DDM to set the behavior you want when CUE is not running. Toggle back out when you've finished your settings. Make sure you "leave" Device Memory Mode. Unlike the prior Hardware lighting/assignments etc where it goes back to software mode when you tab out, you must deactivate DMM when leaving or it stays on. So if you are running through your devices and don't toggle it off, you'll wind up with half your gear in hardware mode and half in software mode. I have to admit I liked the prior system better where the other devices previewed their own Hardware Lighting while you were changing one device. Everything went back on its own. Now in order to see that, you need to toggle all your devices into DMM and then all of them back out. At least all the CUE Link devices act in unison and perhaps that was the basis for the change.

You can’t roll back with CUE 5. It’s server based and always pulls down the current version, regardless of which installer you use. Not clear what those posters are referring to unless they went back to CUE 4.

You likely need to do a clean install. Vanishing from the OS menu strongly suggests registry corruption and this is one of the more common issues with CUE 5. Try the clean install directions below but export any valuable profiles first — if you can. This does erase everything. https://help.corsair.com/hc/en-us/articles/360025166712-iCUE-How-to-perform-a-clean-reinstallation-of-iCUE It’s also possible you won’t be able to install the program and it will be grayed out or the operation won’t succeed. If this happens, try one of the following: 1) Reboot to safe mode and uninstall + registry clean; 2) Use a professional software removal tool like Revo. The free version is sufficient and this also does the registry clean for you making it a better choice if you are not overly Windows savvy on getting into safe mode.

Case strip 28 -> LED strip (10) x 3 Leave the last two LEDs out of the selected effect. CPU block and GPU block -> As Hydro XC7 or XG7 if it will let you (16 LEDs each) or as LL fan (16 LEDs as 12+4 rings). The one led on the end will not be noticeable. Other option is led strip x 2 which can work better with some kits because of unique Corsair led numbering. I am pieces right now moving into a new build. Let me get it back together and connect in a Commander XT to see what it can do. I was playing with this idea as well but am loathe to give up 2 temp sensors and an extra usb passthrough. With a lot of CUE Link in this new one including pump/res and gpu block, it’s actually viable for me to use a XT now.

So theoretically you use an adapter like this to connect to the fan rgb ports on the Commander XT. Previously you would be forced to choose from fan led counts as described on that page. However, Corsair had added support through this device for some of their “non CUE” AIOs, so it’s possible there is a 16 led pump style option. A lot of it comes down to led counts. Otherwise you have 1 led port on the Com XT vs 2 on a Commander Pro.

I believe this is a known issue. I have seen this with my Darkstars as well, including a brand new replacement just hours after it came out of the box. I believe what happens is the mouse shuts off in accordance with its power saving timer. Then on wake it doesn’t some properly reconnect to the receiver and you get the three flashing LEDs on the side. What’s at fault? Mouse firmware? Receiver? Not clear to me. You can contact Corsair Support and see what they say. I’d be open to individual device fault, but I just had mine replaced for scroll wheel issues and the new one did this right out of the box.

You can create a custom pump curve in CUE if you have it connected to a Commander Pro/XT. Go to Cooling for the Commander and click on the yellow + bar. That will reveal a graph below. GPU temp should be there as NVIDIA xxx Temp or AMD xxx temp. However, that’s a poor control variable. You don’t want or need the pump to drop speed when you open a map in game or spike back up when you resume. Coolant temp is the proper control variable but don’t get too caught up in the minutia. You either are fine with a fixed speed and can leave it alone or a small speed shift to differentiate between idle and sustained load coolant temps.

Font size and spacing changed with this release. The new fonts and spacing are larger and thus tiles and dashboard widgets take up more space. It's going to push everything down the app window a bit. People with a decent number of devices will need to scroll down or increase the app window. This would have been a really good time to finally allow the app windows to retain it's user specified size and position on launch, like nearly every other program in existence.

That is what I was expecting and 800 rpm is a typical baseline speed with a minimal PWM signal. That's too slow for almost any loop and will come with a temp penalty. You have a one block, one radiator loop and the GPU block is much less restrictive than a CPU block. You likely won't see any improvements past a specific middle pump speed. 2300 rpm seem likely, but obviously you can test by running something with a steady GPU load and then moving the pump speed around in 500 rpm increments. Th Hydro X profile is a preset like any other. No special sensing technology and it's a list of data points. It might be perfect in one loop or inappropriate in another. Don't feel tied to it and you can create your own curve or use a fixed speed that is a good blend of performance and noise.

This is normal for Asus boards. You get a lot of junk values at the ends of the possible range (0C, 127C) as well as duplicates. The CPUID program CUE uses to fetch this data has a hard time with the Asus Embedded Controller and other programs like HWinfo will note this as well. This should not be possible because AC has no way to interact with CUE or the AIO fans. That lead from the AIO to CPU fan is just a tachometer wire. It reports a RPM to the motherboard to satisfy the built in 'boot safety' feature. There is no power or control wire and that was the "3 pin"/1 wire connector you mentioned earlier. The fans connect to the AIO fan splitter directly. No motherboard control there. The only way Armory Crate can interact with CUE is on the software level as both fight for access to the motherboard bus or other common access points. This is possible, but it doesn't come up much. I would continue with the support ticket. In your CUE settings gear, turn on "debug logging". The next time the fans give the bad readings, go back and export the logs. You must do this manually. Send it in with the ticket. There may be some clue about the error. What's bugging me a little is these software interaction issues typically affect a wide range of sensors. Coolant temp, pump rpm, and anything else in CUE. For it to specifically target the AIO fans each time while not affecting the pump or coolant temp value on the same device is not typical, so I still wonder if there is a hardware issue.

If you have a CUE Link Hub, there are several threads discussing this inevitable issue with the expansion to 24 devices. There is Corsair Explorer link below. https://www.corsair.com/us/en/explorer/diy-builder/blogs/addressing-over-current-protection-issues-expanding-the-icue-link-system-hub-to-24-devices/ You don't necessarily have to use Revo or other professional software removal tools and the registry clean can be done manually. See the directions below. Some users have done a simple "uninstall and reinstall" and it partially works, but the trick is you need to delete the fan configuration as the numbers have changed from the old 1-7, 8-14 numbering to 1-12, 13-24 and that is why fans are missing and/or out of order. https://help.corsair.com/hc/en-us/articles/360025166712-iCUE-How-to-perform-a-clean-reinstallation-of-iCUE

Is this problem now consistent from boot to boot? Software interactions are somewhat random and different fans or values may turn into impossible numbers. If it’s only the two fans on the AIO and they do the same thing every time (fan 1 too high, fan 2 zero), then I wonder about the AIOs fan controller and it’s time to start a support ticket. Be aware at some point in the troubleshooting process Corsair will ask you to clean install CUE. It’s up to you if you want to get ahead of them and save 4-5 days of waiting for the next response. It is possible the cooling config file is corrupted. The directions are below and make you export (backup) all your valuable profiles before doing this. It erases everything. https://help.corsair.com/hc/en-us/articles/360025166712-iCUE-How-to-perform-a-clean-reinstallation-of-iCUE