Jump to content
Corsair Community

Potential Source of Error For H1x0i Elite LCD AIOs and some Feedback/Suggestions for the Support Team


Recommended Posts

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 😛

iCUELogsHL.thumb.png.2f187934c2c71a4fac553f8fb1e62a27.png

CORELogs.thumb.png.078faab542d637ef62805e411a1daca4.png

Edited by rvzuwn
Link to comment
Share on other sites

  • Corsair Employees

Thank you for taking the time to provide your feedback @rvzuwn, and we'll take these points into consideration.  As you mentioned, the LCD and the Commander Core do communicate with eachother, however the issues are not necessarily directly related to firmware.  During the initialization and start up of iCUE, there is a step where screen Serial Number is resolved.  Working with the community, we've identified this as an area where we can improve the user experience, and will be removing this step tentatively in iCUE 4.25.x.  There are more details throughout the thread below about common experiences users are seeing, and steps to resolve them.  We are updating the OP with more information as we release it.

Let us know if you have any other questions.

  • Like 1
Link to comment
Share on other sites

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

 

iCUE4Modules.png

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...