SpeedyV
-
Posts
549 -
Joined
-
Days Won
7
Content Type
Forums
Gallery
Release Notes
Corsair Blog
Store
Profiles
Posts posted by SpeedyV
-
-
I also was lucky enough to see this thread before I bought my last AIO. I went with another brand (can't say which because that is not allowed) specifically because of this thread . That was in the summer of 2021. It is both amazing and sad that I can come back here in February of 2022 and Corsair has still not done anything to fix this.
-
1
-
-
I don't think going through an RMA exchange is going to resolve anything. You are just going to go through the inconvenience of pulling out your AIO cooler (or video display pump head), send it back, and get another one with the exact same problem. If this is a firmware problem, a replacement with the same unit running the same firmware is not going to do anything other than waste your time. If it's a hardware problem (maybe excess current draw?), then Corsair would be in a bad situation, like they are with all the people complaining about pump noise. If they admit its a hardware problem, they would have to do a product recall. I don't think Corsair is going to do that unless they are forced to by either a ton of high profile bad press or a class action law suit.
A similar thing recently happened with the Asus Z690 Hero motherboards. They had a bad run of boards made in Viet Nam that have a capacitor installed backwards. This caused a bunch of brand new motherboards to catastrophically fail, in some cases actually catching on fire. Asus said nothing other than return for exchange until Buildzoid figured out the problem by comparing photos of failed boards to a reference photo. He spotted the capacitor that was installed backwards and he was 100% correct. Asus didn't own up to this until it started hitting Tom's Hardware, WCCFTech, etc. and even after all of that they are making it difficult to exchange the defective boards. If you go through and RMA exchange, you will end up with a scratched up refurbed board.
Sadly, I think the least objectionable course of action is to return the device, get a refund, and buy an AIO cooler from a reputable company that actually stands behind their products. That's what I did and I have no regrets.
-
On 2/3/2022 at 5:34 AM, Wesper686 said:
Helo there! Can smb help me? After installing the firmware in icue, my PC stopped seeing my mouse. What should I do?
Your mouse is probably on the list of products that Corsair suddenly decided to drop support for. There are a lot of people who updated to iCue v4.xx and updated firmware on some of their Corsair devices when prompted. Then they found out that some of their older Corsair products don't work with iCue v4.xx and their newer Corsair products with updated firmware now only work with iCue v4.xx. In these cases it is impossible to have everything working at once. Corsair has made a total mess and pissed off a lot of formerly happy customers.
If your old mouse is not supported by the current version of iCue, you may be able to go back to the old version but then your newer Corsair hardware won't work with the old version of iCue. There is no way to fix this that I am aware of.
My suggestion is to live and learn, and buy a mouse from a company that does not suddenly drop support for a whole bunch of their own products then push out software and firmware updates that cause people to end up with some products that only work with the old version of their software and other products that only work with the new version of their software.
Corsair could not have handled this any worse if they tried. It's sad and pathetic, and one of the many reasons that I have moved on from Corsair and the buggy mess that is iCue. Good luck with your mouse.
-
1
-
-
They probably put it out at trade shows...
-
2 hours ago, Tiger Ritch said:
Just an update - It's been 7 days, and the LCD is Still functioning properly after hooking it up to a stand-alone Commander unit.
Glad that what you did is still working, but you should not have to do it that way. This solution and the length of this thread reinforces my suspicion that there is something wrong with the USB communications to the display. I wonder if Corsair will ever actually fix it.
First, the very long thread full of people complaining about nasty, irritating pump noise and Corsair's refusal to allow a lower minimum speed. Now this. It's interesting (and sad) that most of the problems seem to be with the new Elite (or whatever) products. Pretty embarrassing.
-
On 12/24/2021 at 3:24 PM, djase said:
Hello,
Disabling the Corsair LLA service after doing the update, so far I haven't had any crashes or anything.
happy holidays 😀
Do you have any idea what the LLC service does (beside load down the CPU)? Have you noticed any all effects from disabling this service? Seems like iCue and Asus software in general start a bunch of services whose function is unknown. They must be doing something...
-
6 hours ago, Flardryn said:
Hi Everybody,
I just wanted to share my experince, I had the same exact issue and tried followings to fix it;
- change internal usb hub,
- directly connect it to mb without any hub,
- power drain my pc,
-reinstall the ICUE,
but nothing permanently worked until, I deleted device/driver from my system
- Corsair Virtual Input Device,
It has been a week and I still didnt get any red triangle.
Hope it also does the trick for you.
This is very interesting. Do you know what this Corsair virtual input device driver does? I am curious what led you to try deleting it and if it has had any affect on iCue or anything else Corsair related. I see posts from people who were able to get this thing working by doing a total power drain/reboot, installing a Windows update, and even by installing Armoury Crate. I suspect all of these solutions are not addressing the root problem and may not be permanent. If simply deleting this driver fixes it that is a huge step forward but I wonder if it will break something else.
-
On 1/11/2022 at 3:15 AM, Haensele said:
So in my case, the Disconnecting sound is propably caused by the Commander Core of the H150i Elite Capellix. When I hear the disconnecting sound and reconnecting sound, then my RGB of the AiO goes off, then goes on again and the AiO disappears and reappears in ICUE. If thats not whats happening in your case, then we propably dont have the exact same issue I guess.
But thank you anyway. I keep you guys updated, I just ordered a USB A to 9 Pin hub to replace instead of the USB 2.0 internal Hub from NZXT, because the NZXT Hub does not solve the issue.
When I start my PC i got no problems for like 10 min or so and then my Commander Core just goes crazy. Neither Corsair nor MSI itself could help me ^^.
Sorry to hear that. Putting an NZXT USB2.0 hub between any Corsair devices and the mobo USB2.0 header has worked for me in my last 2 builds.
-
4 hours ago, whocares said:
Apperantly I can't tell ppl the Truth about this AIO, my posts get deleted by MODs.
(which proves that they are reading what we write but don't care enough to do anything about the issues of their products btw)
Well, I RMA ed this AIO and got another cooler(Air), which works better and is silent.
(Hope this doesn't get deleted)
Yeah I got a "warning" for recommending other brands. Luckily for me, I saw this thread in October of last year. I posted and asked why they would not allow the pump RPM to be lowered, and how they made their noise measurements included in the specs (I am an audio engineer). The response back then was that the pump could not be slowed down because it could not overcome loop resistance, and it would be noisier at lower RPM. Both of these responses are obvious BS, which has been proven by the many irate customers who have hacked the config file to lower the pump speed. Apparently it still works fine and it does not get louder. As for how the measurements were done, the response from the Corsair rep was that he has one of these coolers running in a test machine and he can't hear it. I guess that is their noise measurement procedure - to see if this guy can hear it?
I ended up buying a different brand of AIO cooler that is not plagued by these problems. I won't say what brand because apparently that is not allowed on this forum. While I was at it, I changed my entire RGB control platform. When I read the iCue threads, I am very happy that that I changed brands but feel very sad for all of the people who are still dealing with this and other issues.
Corsair is not going to admit that this is a problem. The length of this thread is proof. If they did, they could be looking at a recall of thousands of AIO coolers. The sad thing is that their new Elite Capellix coolers with the fancy LCD screen have the same pump and mount and they are just as bad. I asked about that too and was ignored.
-
2
-
1
-
1
-
-
I feel sorry for the people that have not learned that Corsair iCue is a bloated, buggy mess. The certificate expiration oversite is just one more reason that I am sure that I made the right decision by removing iCue from all of my systems. I still have 2 rigs with Commander Pros and Lighting Node Pros, and my latest system has 2 Lighting Node Cores in it, but I don't use iCue to control any of them. I gave up on iCue long ago and since then it only seems to have gotten worse. More bloat, more bugs, expiring certificates, dropping support for a large list of their own fairly recent products, the list goes on.
-
On 12/7/2021 at 8:42 AM, Haensele said:
Basically i only want to use ICUE for the monitoring and want to have it on my second monitor. I disabled every other RGB program and forced the RGB through hardware lightning to stay in the color i want.
Using iCue to monitor your system sensors is probably the worst choice you could make. For years, Corsair has refused to use the proper mutex locks to safely poll system sensors without causing collisions with any other properly coded monitoring program like HWINO64, AIDA64, and SIV (not Gigabyte's SIV). That is why Corsair will tell you that iCue is incompatible with these other programs. What they don't tell you is that it's incompatible because they don't use the proper locks. All of these programs use the proper locks so they can safely poll system sensors. Corsair refuses to do this, so iCue will cause collisions when monitoring system sensors if any other monitoring program is running. HWINFO, AIDA64, and SIV all can do much more extensive sensor monitoring than iCue anyway. They also put much less load on your CPU since they are not full of extraneous bloat. If you want to monitor system sensors, do yourself a favor and use HWINFO64, AIDA64, or SIV.
-
Why would Aura running cause this? If the QL fans are plugged into a Corsair controller there should be no interaction with Aura. I don't understand how Aura running could affect this.
-
On 10/12/2021 at 6:28 AM, Theplum said:
Tried it already. Unfortunately it does not work...
Did you ever get it working?
-
Pretty sad that no one from Corsair will chime in here. All of their statements about the pump not being able to overcome loop resistance at lower speeds, and the pump being noisier at lower speeds were obvious total BS. I posted on the new H170i Elite Capellix thread asking them if their new H170i cooler uses the same pump with the same RPM restrictions. They won't respond.
-
A buddy of mine bought Corsair Vengeance DDR5 2x16GB @5200MHz kit. He checked the SPD for CRC errors and found errors on both DIMMs. He had some others check theirs and they also had SPD CRC errors. If you bought Corsair DDR5 Vengeance RAM I seriously suggest you check the SPD data for CRC errors. The fact that he had found others with the same problem suggests that this is not an isolated issue.
Corsair - You need to check your SPD data on these DDR5 DIMMs. There appears to be a problem.
-
-
If it was an Asus issue, HWINFO would have the same problem. I don't think it does. HWINFO reports Asus EC based values on my Crosshair VIII Dark Hero just fine. I don't use iCue so can't speak to that. I wonder why Corsair does not take advantage of Shared Memory Support and just import data from HWINFO, and abandon their direct polling of system hardware. It just seems to cause problems, especially with other monitoring programs. HWINFO, AIDA64, and SIV can all happily coexist and safely poll the same sensors, and provide accurate data. Why can't Corsair do that?
-
That is an interesting solution. I used to run Process Lasso but became concerned that it may interfere with Windows task to core scheduling optimizations that were implemented to improve Windows performance on Ryzen processors. I gave up on iCue long ago, not because it excessively loads the CPU, but because it is a bloated buggy mess. That said, it might be time to give Process Lasso another go.
-
Your response about the Capellix pump whine is a total cop out. The complaint thread about Capellix pump noise is now 11 pages long! How can you continue to pretend that pump noise is not an issue with the Capellix pumps when there are 11 pages of complaints about it?
Looks like someone figured out how to lower the pump speed by hacking a config file. Reports from those who tried this all say that it seems to work, and the pump noise problem is gone (no thanks to Corsair). So the statements made by Corsair that A-The pump speed cannot be lowered, B - at lower speeds the pump could not overcome loop resistance, and C (my favorite) - that the pump would make MORE noise at lower speeds, all seem to be 100% FALSE.
Finally, Corsair marketing pics of the new AIO pumps with LCD screen show the pump running at 600RPM. Is this speed supported in the new Corsair iCue Elite LCD AIO pumps or are these marketing pictures misleading? It has to be one or the other so which is it? What is the minimum pump speed supported for these new coolers?
Please don't respond with another BS statement that "Noisy pumps that emit any high frequency whine is not regular. Please open a ticket with our support if you are experiencing this." Maybe this time you could actually acknowledge the 11 pages of complaints, comment on the config file hack that a desperate customer found, and explain the ridiculous statements made by Corsair that the pump speed cannot be lowered, cannot overcome loop resistance at lower speeds, and would make MORE noise at lower speeds.
So what's it going to be this time? Another stock BS response, or actually acknowledging 11 pages of customer complaints, commenting on an end user's hack to get around the high minimum pump speed limitation imposed by Corsair, and apologizing for the obviously false excuses previously posted by Corsair?
-
1
-
-
Its pretty clear that Corsair is not going to do anything about this. I have no idea why they said the pump will not be able to overcome loop resistance at lower RPM. Its just an Asetek Gen-6 pump, which I believe is used on many other manufacturer's AIO coolers that can run at lower RPM than the Corsair Capellix products. The same Corsair guy also said that the pump would be louder at lower RPM, so I take both statements with a large grain of salt. If this work around allows the pump RPM to be lowered, I say give it a try while keeping a close eye on temps. If the coolant is not moving you will know it.
If lowering the pump speed this way works and does not cause problems, then Corsair has some explaining to do. It will be interesting to see if any of the Corsair reps bother to respond to this with anything more than stating that lowering pump RPM by "hacking" the config file will void the warranty.
-
7 hours ago, LeDoyen said:
the latest version adds support for H110i and H110i GT
That's great news. I suspect ThePlum will be very happy to see this. The H110i and H110i GT are both CoolIt pumps. There must be something different between these 2 models and the H80, H80i, and H100 which are also CoolIt pumps but were never placed on the dropped support list.
Squeaky hinge gets the oil I guess! Nice to see Corsair listening to their customers. Kudos for this!
-
1
-
-
On 10/2/2021 at 9:28 AM, Theplum said:
Hmm... so I have bought the GT and I feel I got played also... 😕
Any suggestion for 3rd party software to control the H110iGT?Yes. I use a program called SIV to control my Corsair H110i, a commander Pro and several lighting node pros. SIV can control your H100i GT, which has a CoolIt pump. I posted about SIV a few posts back in this thread. Here is a LINK. There are links to the SIV download site and the author's forum in my other post. Good luck!
-
1
-
-
This thread is almost a year old now, and 9 pages long. Corsair has barely responded to any of the posts in this thread. Corsair Travis stated that the pump must run at high speed to overcome loop resistance, and that he has a Capellix AIO running in open air and he can't hear it. I guess this is supposed to infer that this makes it OK? He also said they were Looking into it.. That was in April of 2021. Several Corsair people (most recently Corsair Albert) have said to open a ticket, which will solve nothing.
Now they have released the H170i Elite Capellix. I asked if this AIO uses the same pump with the same high minimum RPM. I got the same stock response from Corsair Albert - the pump should not be noisy and if yours is, open a ticket. He did not actually answer my question which was does the H170i Elite Capellix use the same Asetek Gen-6 pump as the other Capellix AIO coolers, with the same high minimum pump speed.
It is clear to me that Corsair is not going to admit to this problem, and they are not going to fix it. I assume that they actually can't fix it which means it is a design flaw that they cannot resolve with a firmware update. Considering the Capellix is Corsair's top of the line AIO cooler, it's pretty lame that they are ignoring the 9 pages of noise complaints in this thread. I don't know if the H170i Elite Capellix AIO uses the same Asetek Gen-6 pump with the same high minimum RPM limitation as the earlier models. If it does, and they still did not do anything about it, that is also pretty lame. Time to move on from Corsair AIO coolers.
-
On 9/24/2021 at 9:25 PM, Rubik2022 said:
I'm using iCUE for 2 years and no critical issues with it. iCUE is to control the RGB and related Corsair product functions, not the HW Monitoring software.
If you feel that iCUE is bugCUE, try to use other brand control software like ASUS, Gigabyte,.. and feel.
Agree that most software offered by Asus (Aura, Armoury Crate) and Gigabyte (and MSI) are even worse than iCue. Aquacomputer Aquasuite is considered to be by far the best by many serious custom loop builders. And programs like Open RGB and Signal RGB are becoming quite viable and popular replacements for iCue, Aura, Mystic Light, etc.
Request: iCUE ELITE CAPELLIX - Lower RPM (< 2000 RPM) for Quiet Profile via Firmware
in Build Hardware Troubleshooting
Posted
I think pretty much all AIO pumps that sit on the CPU block are made by Asetek these days. Some of the earlier Corsair AIO's (H80, H80i, H100, H100i, H110i, H110i GT) had CoolIt pumps which were better in many ways. Asetek pretty much ran CoolIt out of the market due to a patent they have on putting the pump on the CPU block, so now they all use Asetek pumps, at least in the US.
Because of this thread, I bought an AIO made by another company (forum rules do not allow me to say which one) that uses an Asetek pump and it's not noisy at all. I also have full control over the pump speed (not with iCue). It is generally known in the custom loop world that pump speed, within reason, does not really affect cooling efficiency, so there really is no reason to have these pumps running as fast as they do. Those who have hacked the config file to slow them down report no increase in temps. This pump speed limitation is an iCue thing. If you want full control of your pump speed, don't use iCue to control it. Unfortunately, Corsair makes it very hard to do that with their products.
All of this said, I think you may be onto something here when you talk about the cheap-o hollow plastic cover that Corsair sticks on acting as a resonant cavity, amplifying the pump noise. This makes sense because the same Asetek pump is used in many other brands of AIO, and they are not getting noise complaints. I tried to get Corsair to explain to me how they arrived at the published noise spec for these pumps and I never got a straight answer. The response I got was that the Corsair guy had one on an open test bench and he can't hear it. So I guess their spec is that this guy can't hear it so its ok. No info on how the noise level was measured - what calibrated measurement device was used, at what distance, and in what environment, with or without fans running, etc. TBH the impression I got was that they just made something up and never really did a proper noise level measurement. They have been dancing every since because if they admit it, they are looking at a product recall.
PS - Your pictures of how this "top of the line" product is assembled is disturbing, though sadly not surprising.