Jump to content
AIDA64 Discussion Forum
dna

Corsair iCUE program breaks after enabling sensors in AIDA64

Recommended Posts

Motherboard: ASUS Maximus XI Formula

OS: Win 10 Pro

Hello, I am having an issue with the option in Stability settings that allows you to enable Corsair Link sensors. This, it seems, is pulling sensor data from my Commander Pro, which is a hub that connects several water temp probes, 6 radiator fans, and lighting strips. When i enable that option, I can see where I'm able to add the water temp sensors into my OSD panel, however, enabling the option in Stability section does something where it's screwing up the Corsair iCUE software. Once enabled in AIDA64, the iCUE software gets really buggy, the stops reading the Commander Pro correctly, sensors start dropping out, etc.
Not sure if this is a problem with iCUE or a problem with AIDA64... both are currently updated using latest releases (AIDA64 on latest beta, iCUE on latest stable)

Share this post


Link to post
Share on other sites
On ‎9‎/‎21‎/‎2019 at 8:09 AM, dna said:

Motherboard: ASUS Maximus XI Formula

OS: Win 10 Pro

Hello, I am having an issue with the option in Stability settings that allows you to enable Corsair Link sensors. This, it seems, is pulling sensor data from my Commander Pro, which is a hub that connects several water temp probes, 6 radiator fans, and lighting strips. When i enable that option, I can see where I'm able to add the water temp sensors into my OSD panel, however, enabling the option in Stability section does something where it's screwing up the Corsair iCUE software. Once enabled in AIDA64, the iCUE software gets really buggy, the stops reading the Commander Pro correctly, sensors start dropping out, etc.
Not sure if this is a problem with iCUE or a problem with AIDA64... both are currently updated using latest releases (AIDA64 on latest beta, iCUE on latest stable)

This is a collision between AIDA64 and iCUE.  Please report this issue to Corsair.  We've been in contact with them for over a decade now, but this is the only issue where we cannot convince them to fix their software.  AIDA64 -- as well as many other 3rd party monitoring applications including CoreTemp, CPU-Z, GPU-Z, HWiNFO, HWMonitor, MSI Afterburner, Rivatuner, SIV, SpeedFan, etc -- use industry standard synchronization mutexes in order to prevent such collisions when multiple monitoring software is trying to interact with the same hardware.  This works great as long as you use two or more of the mentioned software concurrently.  We've got to the point of convincing Corsair to implement a synchronization mechanism in their previous generation software (Corsair Link Software), but then at a certain point they simply removed the mutex and never implemented in iCUE.  It means iCUE cannot be used concurrently with 3rd party monitoring applications which is simply unacceptable IMHO.  No matter how much pressure us and the developers of the previously mentioned 3rd party monitoring software put on Corsair, they stick to their stance on this matter.  Only you, the customers of Corsair and owners of Corsair hardware have a chance to convince Corsair to change their mind.

Share this post


Link to post
Share on other sites
On 9/22/2019 at 8:29 AM, Fiery said:

This is a collision between AIDA64 and iCUE.  Please report this issue to Corsair.  We've been in contact with them for over a decade now, but this is the only issue where we cannot convince them to fix their software.  AIDA64 -- as well as many other 3rd party monitoring applications including CoreTemp, CPU-Z, GPU-Z, HWiNFO, HWMonitor, MSI Afterburner, Rivatuner, SIV, SpeedFan, etc -- use industry standard synchronization mutexes in order to prevent such collisions when multiple monitoring software is trying to interact with the same hardware.  This works great as long as you use two or more of the mentioned software concurrently.  We've got to the point of convincing Corsair to implement a synchronization mechanism in their previous generation software (Corsair Link Software), but then at a certain point they simply removed the mutex and never implemented in iCUE.  It means iCUE cannot be used concurrently with 3rd party monitoring applications which is simply unacceptable IMHO.  No matter how much pressure us and the developers of the previously mentioned 3rd party monitoring software put on Corsair, they stick to their stance on this matter.  Only you, the customers of Corsair and owners of Corsair hardware have a chance to convince Corsair to change their mind.

This makes sense. So my question to you would be this: given the nature of the issue and its complex history, what would be the best thing that I can do, as a Corsair consumer, to help motivate their development team to act on this. Contacting support is not likely to help, as this issue goes well beyond the scope of first-layer tech support. This appears to be a problem that senior technicians and developers need to be presented with, and I'm afraid that spending an hour explaining the problem to general tech support will be a waste of my free time. Maybe I'm wrong. I really don't know, which is why I ask for your opinion on the most effective way for a customer/consumer to bring this to the attention of middle-management or senior employees, done in such a way that it doesn't fall on deaf ears, so to speak

Share this post


Link to post
Share on other sites
2 hours ago, dna said:

This makes sense. So my question to you would be this: given the nature of the issue and its complex history, what would be the best thing that I can do, as a Corsair consumer, to help motivate their development team to act on this. Contacting support is not likely to help, as this issue goes well beyond the scope of first-layer tech support. This appears to be a problem that senior technicians and developers need to be presented with, and I'm afraid that spending an hour explaining the problem to general tech support will be a waste of my free time. Maybe I'm wrong. I really don't know, which is why I ask for your opinion on the most effective way for a customer/consumer to bring this to the attention of middle-management or senior employees, done in such a way that it doesn't fall on deaf ears, so to speak

I really don't know... Because we have done everything we could: talked to both the management and the right technical professionals at Corsair who understands the issue in depth.  And when I say "we", it's not only us here at FinalWire, but also the other folks behind CPU-Z, HWiNFO, HWMonitor and SIV.

I think the only way that may work is when multiple (10+, maybe 100+) inquiries to be submitted to Corsair customer support.  That should trigger someone from middle management to dig deeper and think about the issue thoroughly.

Share this post


Link to post
Share on other sites
On 9/25/2019 at 2:54 AM, Fiery said:

I really don't know... Because we have done everything we could: talked to both the management and the right technical professionals at Corsair who understands the issue in depth.  And when I say "we", it's not only us here at FinalWire, but also the other folks behind CPU-Z, HWiNFO, HWMonitor and SIV.

I think the only way that may work is when multiple (10+, maybe 100+) inquiries to be submitted to Corsair customer support.  That should trigger someone from middle management to dig deeper and think about the issue thoroughly.

ok so you think i should just approach the normal support team.. i can do that. it would be cool if we could get a group of people together to do this. if you have any contact info for someone i may be able to reach out to, please DM me and we can discuss that. We seem to be in agreement on one thing.. that a single user report to customer service will do very little to help. Of course I will do it anyways. I would absolutely love to have this data appear on my OSD panel.. opening iCUE to view my water temps (i have water temp probes positioned after the radiators, after the CPU and after the Pump/Res) is far from ideal, I hardly ever check them because it takes so much time.. its just not a very user-friendly solution for active monitoring..but, I digress

Share this post


Link to post
Share on other sites

Hi guys!

Count me in! I am also going to contact Corsair support for this. Hope we can get more people to contact them.

As we speak i am getting the Corsair commander pro out of my pc case to put the fans directly into my mb so i can see them on my external display.

Please keep us updated on any changes regarding this matter.

Share this post


Link to post
Share on other sites
On ‎9‎/‎28‎/‎2019 at 7:24 AM, dna said:

ok so you think i should just approach the normal support team.. i can do that. it would be cool if we could get a group of people together to do this. if you have any contact info for someone i may be able to reach out to, please DM me and we can discuss that. We seem to be in agreement on one thing.. that a single user report to customer service will do very little to help. Of course I will do it anyways. I would absolutely love to have this data appear on my OSD panel.. opening iCUE to view my water temps (i have water temp probes positioned after the radiators, after the CPU and after the Pump/Res) is far from ideal, I hardly ever check them because it takes so much time.. its just not a very user-friendly solution for active monitoring..but, I digress

I'm not entitled to publish any of the Corsair contact emails I've got.  Especially since they're proven to be great folks -- except for this single issue.  So I don't want to unleash a s* storm of angry emails flying into their individual mailboxes :) 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...