WebMaximus

That's brilliant, will do the same!

Sorry to hear about this since I'm waiting to receive an HP Reverb G2 myself. Due to all issues we've seen with later versions of iCUE, I'm still on 3.30.97 which is the latest stable version for me where all my Corsair hardware (plus all other hardware) still work with no issues. What version of iCUE are you guys on and have you tried older versions of iCUE such as the one I mention above? If you haven't and want to give it a try, you can download it directly by going to -> http://downloads.corsair.com/Files/CUE/iCUESetup_3.30.97_release.msi

As the topic suggests, how can I disable iCUE software update notifications? Due to the sad history of iCUE software updates for a very long time now where new versions brake more than they fix, I'm still on 3.30.97 which is the latest version where all my Corsair hardware still work as intended. For this reason I'm not interested in any updates and thus don't want the notifications. Maybe I'm just missing it, but surely there must be a way to configure iCUE to not look for updates in the same way you find that option in pretty much any other software?

My "solution" is to stay on 3.30.97 which seems rock solid on my system and always has vs the newer versions of iCUE which have been a disaster quite honestly.

For everyone in here asking what to do after they upgraded and things stopped working, I would suggest to simply go back to an earlier version of iCUE you know has been working without issues earlier on your particular system. What version that is seems to vary between different systems which makes sense I guess, since people will have different devices etc. "Solving" your issues this way has been suggested before and I think that is the best (only) way to get things working again at this time until/if Corsair properly addresses the mess they caused for their customers with these latest versions of iCUE. Do note I don't say version but versions. This since these kind of issues are not specific to only this latest version of iCUE but have existed many versions back. So unfortunately, this isn't a single version that for whatever reason was messed up by Corsair. Rather, this seems to be more of a sad trend I'm very sorry to say. And again, I do hope things will swing around for the better again since I always really liked Corsair. Come on Corsair, set this right again!

This have proven to be the most stable version for me http://downloads.corsair.com/Files/CUE/iCUESetup_3.30.97_release.msi I'm sure though you can put in another version in the URL to get whatever old version you like. At least that's what someone said earlier in this thread somewhere.

Judging by the posts so far, this "patch" seems to have introduced more bugs than it addressed. What I don't get is how there's still no input from Corsair in this thread. In response to all that has been said and reported up to this point. That is equally bad as the quality of this patch or even worse IMO. Almost like they don't care. Not about all of their customers having issues with their products, nor about their reputation going down the drain. Really odd! In a sad way since I've always been a big fan of Corsair.

The absence of Corsair staff contribution in here despite all issues reported by such a large number of members doesn't smell particularly good.

That's quite bad I'd say when this amount of people are having all kinds of issues. Plus, one of the issues reported way back still hasn't been fixed it seems (I haven't even dared trying this version out after all I've read so far...) Must say I'm a bit disappointed and equally surprised. As I recall it, the level we're seeing here right now from Corsair and their new versions which seem to implement more issues than they fix, that's new to me.

I've been using http://downloads.corsair.com/Files/CUE/iCUESetup_3.30.97_release.msi for a long time now and this version seems really stable. Commented about issues already over here -> https://forum.corsair.com/v3/showthread.php?t=198763 and after reading about all sorts of issues people are reporting in this thread, I have to wonder what the procedure is internally at Corsair when trey try out a new version before public release.

Just tried out 3.32.80 only to discover the issue is still there. Come on Corsair!

Here's another one having constant iCUE crashes after updating to 3.31.81. Good thing I have a system image just before the update I can restore!

I brought the Virtuoso headset back and I no longer have any issues. In all honesty though, I think I saw the same issue once or twice even after I brought the Virtuoso headset back. So...I'm not really sure what to think about all this. Anyway, I'm now on 3.28.70 and have also done some reconfiguration of my devices in iCUE in regards of lighting setup etc and as stated in the beginning of this message, I luckily don't see this issue anymore.

That's highly unlikely IMO

Thought this would be a fairly simple question. Aren't there any Corsair reps in here?

I'm sure I'm missing something obvious here. I'm trying to figure out how to set up the lighting effects for my system after I added a Virtuoso SE headset to the mix. Other than the Virtuoso headset, I have the following products: - ST100 RGB stand - H115i Platinum - Vengeance RGB PRO - Commander Pro with 4 LL RGB fans connected My goal is this: - have the ST100 RGB stand use the temp of my GPU for color - have the H115i Platinum use the water temp for color - have the Vengeance RGB PRO DIMMs use the water temp for color - have 3 of the LL RGB fans connected to the Commander Pro use the water temp for color and the 4'th fan the temp of the GPU I've created 2 lighting links, one for CPU water and one for the GPU. I then use these successfully for all products except for the Virtuoso headset. For some reason, I'm not able to see the 2 lighting links in the list. Instead, all I can do is pick temperature under the lighting links section. When I change what sensor should be used, it affects also the lighting links for the other products making a mess. Where the lighting link I previously configured to use the temp sensor for CPU water now instead switches over to use the sensor I configured for the Virtuoso headset...the GPU. Sorry for the confusing description. Quite hard to describe this in text. Here's a picture illustrating what I see when looking at the lighting effect for the Virtuoso headset. As you can see, I don't have a list of my created lighting effects and I'm not sure why? Since I do see my custom lighting links for all other products.

Thanks for the input and let's hope someone from Corsair sees this and can help us figure out what is going on. And edited to add, I'm quite confident it's the Virtuoso headphones causing the issue since that is the only change on my side as far as iCue and Corsair products go. And as mentioned above, I've been using iCue for well over a year without any issues until I bought the Virtuoso headset.

Am I the only one seeing this issue? If so, maybe I should create a support ticket instead. Just checked my application log in Windows and counted this crash happened 11 times so far.

I recently bought a pair of Virtuoso SE headphones and an ST100 stand and would like to know if it makes any difference connecting these devices via USB 3.0 or USB 3.1?

Been using iCUE for a long time now for the below components: - H115i Platinum - Vengeance RGB PRO - HX1000i - Commander Pro Yesterday I bought a Virtuoso SE headset and after adding that one to the mix, I've noticed how iCUE keeps crashing (quitting by itself) every now and then. When this happens, I can simply restart it but would still know of course why this happens and what to do to fix it. iCUE 3.26.95 Windows 10 1909 18363.693 Looking in the Windows Event Viewer Application log, this is what it looks like after iCUE crashes: Log Name: Application Source: Application Error Date: 2020-03-08 11:38:40 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: TheNest Description: Faulting application name: iCUE.exe, version: 3.26.95.0, time stamp: 0x5e5d5bd0 Faulting module name: iCUE.dll, version: 0.0.0.0, time stamp: 0x5e5d5b87 Exception code: 0xc0000005 Fault offset: 0x006bb98f Faulting process id: 0x3ab0 Faulting application start time: 0x01d5f52ceffbb07c Faulting application path: C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\iCUE.exe Faulting module path: C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\iCUE.dll Report Id: b54c55ca-8caf-42fc-901b-01078d4c7bcb Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2020-03-08T10:38:40.686700400Z" /> <EventRecordID>40671</EventRecordID> <Channel>Application</Channel> <Computer>TheNest</Computer> <Security /> </System> <EventData> <Data>iCUE.exe</Data> <Data>3.26.95.0</Data> <Data>5e5d5bd0</Data> <Data>iCUE.dll</Data> <Data>0.0.0.0</Data> <Data>5e5d5b87</Data> <Data>c0000005</Data> <Data>006bb98f</Data> <Data>3ab0</Data> <Data>01d5f52ceffbb07c</Data> <Data>C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\iCUE.exe</Data> <Data>C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\iCUE.dll</Data> <Data>b54c55ca-8caf-42fc-901b-01078d4c7bcb</Data> <Data> </Data> <Data> </Data> </EventData> </Event>

I keep getting the below error message when I try to update. I'm currently on 3.22.74 which seems to work just fine. So no big deal for me but feels weird since I never had any issues updating before.

That's a great tip, will do the same! Feels quite weird indeed why a service is installed by Corsair for hardware that isn't installed but maybe someone from Corsair can shed some light on this? I also love the description of said service...simply the letter 'C' and that's it. I guess it stands for Corsair?! :D:

I have this in my Windows Event Viewer System log. Any ideas what is wrong and how to fix it? Clearly, it's about a file? that can't be found. No clue though where the file is supposed to be found nor why it isn't there. Log Name: System Source: Service Control Manager Date: 2019-11-27 17:29:42 Event ID: 7000 Task Category: None Level: Error Keywords: Classic User: N/A Computer: TheNest Description: The CorsairGamingAudioConfig service failed to start due to the following error: The system cannot find the file specified. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" /> <EventID Qualifiers="49152">7000</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8080000000000000</Keywords> <TimeCreated SystemTime="2019-11-27T16:29:42.460760100Z" /> <EventRecordID>40294</EventRecordID> <Correlation /> <Execution ProcessID="884" ThreadID="5080" /> <Channel>System</Channel> <Computer>TheNest</Computer> <Security /> </System> <EventData> <Data Name="param1">CorsairGamingAudioConfig</Data> <Data Name="param2">%%2</Data> <Binary>43006F0072007300610069007200470061006D0069006E00670041007500640069006F0043006F006E006600690067000000</Binary> </EventData> </Event>

After another test I realized I'm now using a very simple static color for my RAM which works just fine without full software control enabled. So...problem solved :) Many thanks for the quick and spot on support and help!

Wow, spot on! When disabling full software mode for my RAM, the CPU util dropped and the System Idle Process showed the normal 99% or so. I think I'll still keep it enabled though since I do like the effect. Any chance this could be addressed somehow in an upcoming version of iCUE? Or maybe it's unavoidable? Just feels a bit weird why this feature would need a constant 10% CPU time or so. Sorry, forgot to mention I do have HT enabled.