- 261,035 Members
- 1,226,391 Posts
- 357 Online Now
Featured Posts
See all featured-
- 0
- 8
System Build InspirationStart Building with CORSAIR BUILD KITS
-
- 0
- 23
New Product ReleasesA Great Day for DIY – Introducing a Multitude of New Components
-
- 2
- 17
New Product ReleasesIntroducing the CORSAIR RMx SHIFT Series™ 80 PLUS Gold Fully Modular ATX Power Supplies
-
- 1
- 7
New Product ReleasesIntroducing the CORSAIR TC100 RELAXED Gaming Chair
-
- 0
- 1
New Product ReleasesLaunching the CORSAIR XENEON FLEX 45WQHD240 45-Inch OLED (3440x1440), 240Hz, Bendable UltraWide Gaming Display
Trending
Go to the forums-
iCUE v5.14.93 Release Notes
erebuswarrior replied:
Forgot to add that I'm also using a corsair k100 keyboard. The 5.13 installer I had from August of 2023 ended up just downloading the latest version instead, but good news, I was able to get the lighting, fan, and pump control to work again, and it's using my custom lighting and fan profiles so luckily I didn't have to spend forever setting up everything again.
By Technobeard
Started50 -
Question about H115i RGB PRO XT fan sensors in iCUE
c-attack replied:
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.
By AMLime
Started11 -
Where is iCue Crash reports located?
c-attack replied:
C:Users/(name)/App Data (hidden)/Local/Corsair
By coldviper
Started2 -
iCUE Link Fans QX-RX
Clicky4ever replied:
I just installed 11 of the RX fans and love them. Like c-attack stated though, the performance gain compared to your QX setup is probably negligible. I have a 54mm and 30mm thick radiators, so I need as much static pressure as I can get.
By Bluestake
Started2 -
ICUE LINK XG3 RGB HYBRID and iCUE LINK H150i LCD
Dyne Reardon replied:
Thank you!
By Dyne Reardon
Started2 -
12VHPWR PSU Cable is this one safe and authentic ?
Technobeard replied:
It says: Ships from: Amazon.com Sold by: Amazon.com So yeah, it'll be an authentic part. Here's the part page for the cable: https://www.corsair.com/us/en/p/pc-components-accessories/cp-8920334/premium-individually-sleeved-12-4pin-pcie-gen-5-12vhpwr-600w-cable-type-4-red-black-cp-8920334 That cable's listed as an accessory on the PSU's part page (under More To Consider), so you're good to go: https://www.corsair.com/us/en/p/psu/cp-9020201-na/rmx-series-rm1000x-1000-watt-80-plus-gold-fully-modular-atx-psu-cp-9020201-na Under Tech Specs the PSU shows that the Cable Type is Type 4. The cable product page states it's a Type 4 cable. So you're doubly good to go 🙂 There's also the PSU Cable Compatibility chart to check out.
By Petergh
Started1