rvzuwn

Also know someone else who got a brand new H170i LCD, in a different province as me, with the exact same issues as mine. However, I get that Corsair has to keep insisting on RMAs because it makes it look like an issue a few defective units have and not something fundamentally broken about their product for a material number of system configurations.

Worst part of this is that its not even an aesthetic thing, with iCUE the pump runs at 2000RPM, without it 2400RPM, so you can't even get all the performance out of the cooler. On my system the pump doesn't even start unless I power cycle.

Same old with 4.26 . No pump control.

Identical situation for me as rdh, iCUE 4.25 on clean install, H170i Elite LCD. LCD is overlaid over Commander Core just as in the picture. If I change the LCD background in iCUE the LCD will update to the selected background and read out the coolant current temps for a second and then will go back to the exclamation mark.

Not sure if this is meaningful but for the latest version of iCUE4, under ProgramFiles\Corsair\CORSAIR iCUE 4 Software\modules , there is no .dll for the H170i Elite, only goes up to 150i. Initially I assumed this is because they share components other than the rad so the H170i just uses the same firmware as the H150i but I don't know if thats the case. If you guys have had an unusual amount of H170i LCD tickets lately maybe thats something to look into

For AIOs showing only the Commander Core in iCUE4, where iCUE4 can detect the Coolant Temp, I think a large number of the failures are caused simply by a failed firmware update the to LCD Cap. I've attached images of the relevant logfiles to explain why I think this is the case. We can see that "LCD PUMP GP PLUS" is detected but the "fw obj" is empty, I've highlighted this line. Further inspecting the Commander CORE log we see that it shows a "Cooler component IDs read error". We know that there exists a relevant fix for this, as mentioned by other users who have reported successfully fixing their AIOs this way, it's shown in this link: https://www.youtube.com/watch?v=jjGa1D6Xx7E I think it would helpful for Corsair to simply just makes these .hex files available on their site, with some disclaimer to warn users about the risks of manual firmware flashing etc. This would take a lot of burden off their support staff to attend to other issues, as well as avoiding unnecessary RMAs which hurt the company's bottom line and frustrate customers. Many users may have reinstalled/restored their OS and now are without the .hex file in AppData, and this would be a solution that costs Corsair nothing and resolve many issues quickly. Although this topic has been discussed before, I just wanted to substantiate it a little more, and perhaps Corsair could take this into consideration to improve the troubleshooting resources available to customers. TLDR: It seems possible that in many cases the LCD Cap and Commander Core are detectable and Commander is attempting to communicate with the Cap. The issue is that the Cap's firmware has been corrupted and has no information in the "combined-image" fw obj. In these cases its doubtful that an iCUE4 update can help these customers, since iCUE can't see the device in the first place. Some customers can't have more than a days downtime since they use their system for work and a fix that solves this issue is making a manual firmware upgrade available. For now I guess I'll just hang around checking my email like an insane person for a support ticket response 😛