KnightArch

So your iCue crash problem is not related to the AurySync, it is about something else. Sorry for not being helpful.

I had some exp with this kind of issue, I have an asus motherboard with aurasync that doesn't work for more than a year since asus lacks to update the aurasync to support "newer" (already old) versions of Windows 10 and this caused the crashes for me. Just go to the installation folder ..\Corsair\CORSAIR iCUE Software\plugins\ASUS and DELETE the DLL file in this folder, problem solved for me. Probably for you too. If you does own another brand of motherboard, there are a few more folder aside the Asus one that may contain some DLLs causing the crash. Let me know if this solves the problem for you.

In this new version my mouse clicks macros are broken, I have some click macros that I used for years that will constantly repeat while the button is pressed but in this new version when I press and release any keyboard button, the macros are stopped. I'll go back to the previous version because this literally broke my gameplay. I suggest you to implement some way to revert to the previous version easier and remove the profiles version lock or converter back the profiles to the previous version, because of these constant broken versions that are being rolled out to everyone, this is very frustrating and I don't want to create all the insane macros scripts from scratch every time you break the iCue without testing before releasing to the public.

Thank you Johnny, I have tried this but I think I messed something in the URL LOL

Well, I have the same issue here with my H115i and my solution was disconnect the fans from the watercooler and plug them on the motherboard, tried several possible workaround but no one worked. I have currently no firmware update available to download and install so I think I'll be using this "solution" for the watercooler lifetime...

Just updated from v3.24.xx and now it crashes right after loading my hardwares. Any workaround or a link to the previous version??

Asus Prime x299 A, Prime x399 and ROG Rampage VI Extreme, none of them working/showing up on iCue and now my iCUE crashes right after it's opened. Aurasync application also doesn't work for more than a year, so...

After all this sheet of paper we went through here it's quite offensive read this...

Nope, didn't work here. But thank you.

Well, this update indeed "fix" the high cpu usage, but every hardware has now a problem besides the new software bugs and weird behavior, like the UI overlapping the taskbar when maximized. I have to rebuild all my profiles from scratch AGAIN to get my light FX working properly and fix some macros misbehavior. Let's start from keyboard following the iCUE hardware assortment. K95 RGB Platinum started to show some purplish/pinky light in some leds, like the top bar with ordered spaces, as if it were purposely programmed. I'll provide some photos as soon as my smartphone finish to update or my cameras get some charge on batteries. Glaive RGB randomly stops to be recognized by iCUE. Just vanishes but the functions continues to work, like macros and light effects but with stuttering or blinking behavior. Had to restart the iCUE proccess several times do get it being recognized again. At random times, DPI switch changes more than one state with one click, what don't happen in 3.2.87. At random times I notice the surface calibration is reseted and cursor movement get's "lazy" and "sticky", which seems to be connected with app or system restart. Void Surround changes the eq profile to "pure direct" independent of the eq profile selected or the priority order of them on the list, only being on other eq profile if I remove the others and let only the desired on list. Sometimes it changes the eq profile while in mid-game, waiting concentrated and focused on the sounds of my enemy foot steps and suddenly the audio goes crazy and low. ST100 RGB has the same behavior problem as the headset, but the changes in eq profile are in different times. After the first update/upgrade to 3.4.95 the colors became to a bluish intonation, with blurry color like if there is some layers of plastic film on it. This was noted by my subscribers when I was live and they started the flood the chat my ST100 was dying because the lights was decreasing the bright and turned out, which reconnecting the USB fixed but the colors never was the same. I tried rolling back to older iCUE versions, tried on another PC and tried to restore the previous firmware but the colors are still weird. MM800 RGB Polaris sometimes started the light FX the wrong way it's supposed to be, like in rainbow link clockwise, it actually is in anticlockwise but everything is in clockwise. At random launches, the app notifies me about an firmware update but there is none when checked. H115i is the worse to me. They removed almost all features that I usually use to monitor this extremely import component of my computer build. Now I can't set notifications anymore because the notification tab was removed and can't set a warning color to a little high temp and set the coolers to 100% when triggered by a even higher temp. I configured my notifications to stay white until the coolant temp reaches 40ºC, when they changes to orange and going on to red on 60ºC with max coolers speed and after shutting down my system with 75ºC. Now it only has a light FX to warn about one single temp. They also removed the graphs tab which is the more important and accurate than the panel ones. In panel, even with bigger size they are incredible tiny and I can't see anything in the graphs. Another bizarre behavior is that I'm not able to set the pump to the balanced profile anymore. It's only possible to select quiet or extreme. Instead of improve and let us set a custom speed, they just drops the possibility to barely set a average speed. Edit: I think I should clarify that when I said "panel" I meant "dashboard" with the kind of widgets. Sorry for this. And finally the Vengeance RGB RAM modules. It starts with light off on some modules and/or stuck in red light. Sometimes it's stucked in red light but it's trying to change to another color, but the process restarts to red light as soon as they started to change the color. I have to disable the lights and enable it again to fix this behavior and/or turn the lights on in the modules that was the lights turned off. Some times the sync between the modules is lost and they start to change colors in async mode. It's not the same behavior when in conflict with AuraSync by Asus, it's a different one. There are some minor unwanted behavior in light FX when mixing they together to get some nice FX and changes in triggers to get the things working together with macros. Also some profiles have changed from hardware to software mode when upgrading to the new version and all the icons were swapped to the iCUE default icon. But nothing triggering my anger and rage further than have to delete more of a three dozen "default" profiles one by one and confirming the action every single time I did it and what probably was created every time I installed or rolled back to other versions. Weird... Thank you that read all this essay I wrote. :toomuchin :owned: Obs: I am sure that has some wrong spelling here. Be nice with my english, I'm Brazillian :laughcry:

Unfortunately I don't have any clue of a possible solution. I backed them up exporting from 3.3.103 anyway and make some screenshots from my most frequently used profile (and the most complex one) to make it again from scratch and rolled back to 3.2.87. At some point they have to release a fix for this issue and hopefully I don't have to concern myself about making them again, but if it's the case, I have the backup AND the installer from 3.3.103 to do the update and upgrade of my profiles the way it supposed to be made. I prefer to not do this search for some workaround as I don't have the time to spend on it. I have to work to pay Corsair's expensive hardware. :laughing:

My hardwares has the same problems and I make the same mods. The answer? Laziness...

I don't think it's installation problem. My guess is bad coding, like some mistaken loop or some thread stuck waiting for some action to trigger it out of the loop, which is not the intended and uses a lot of cpu resources for some obscure reason, it happens. As a dev, I saw a lot of these problems in my career and sometimes it's not easy to find the source of the problem, but I'm speculating here. I have experience with app development but what I said is purely speculation since I did't see the code, so I'm not 100% sure, of course. Here I have problems with my Dell Inspiron 15 7560 using only my void surround and my desktop that I built myself. Both has cpu consumption of one core at 95%+ even that there is no devices connected, which leads me to think there is something else besides the lighting effects causing this behavior as my notebook doesn't have any profile with lights and still has high cpu usage. In my desktop, jesus, I have a lot of things from Corsair connected to it and the problem are basically the same. I said a few post before that I even tried to remove all the profiles and removed the lighting for all my devices, but no changes. I hope now that Corsair released the "full version" of iCUE they will work faster to release new builds to us. Just to coop with you, based on your own pattern: Desktop PC Asus ROG RAMPAGE VI EXTREME/7900X Chipset Southbridge X299 Chipset Northbridge Skylake-X Vengeance RGB H115i K95 RGB Platinum Glaive RGB MM800 mouse pad ST100 Stand Void Surround Win 10 PRO 1803 (17134.81) Notebook PC Dell Inspiron 7560/7500U Chipset Southbridge Kaby Lake-Y PCH Chipset Northbridge Kaby Lake Void Surround Win 10 PRO 1803 (17134.81)

Multiple systems, good point. I have this scenario too. Forgive me to not think about this. Sorry.

There is no sense to list system setup in comments since it's listed in system specs and is "against the rules" of this forum, as said in system specs editing panel. It lacks some useful fields but is good enough to show our system specs.

@solarity - I'm aware of this method C-attack uses to "migrate" the data between iCUE versions. But I was unable to migrate from 3.3.103 to 3.2.87, I missed something that broke the entire process. I was very sleepy and tired working on workarounds since 8pm and was to sleep almost 6am. Yes, I have many devices affected by this flaw, but it's not really entirely related to devices. Even on my notebook with absolutely no devices connected iCUE devours my CPU, so i moved on to CUE 2 because I actually only use the headset on it. But in my desktop PC I decided to downgrade to 3.2.87 and make the hard way backing up my profiles because, you know, I was a fool and didn't make one single backup in this version LOL Regarding what you said, I agree that there might be something else. The 1 is absolutely not the case, but 2 and 3 it's possible hahaha even I don't think so, but you know, I was working on it for a very long time and this might have affected me in some way that I started to mess up with the things without notice at some point. I tried to contribute to help the community as much possible as I can, but I work streaming games, making videos and developing apps, so I can't spend much time trying to solve a problem that is beyond my hands, talking about the code lines itself. I think we as a community did our part in this "job" very well and it's done, now it's Corsair time to do something definitely final. I do agree with you it's better have one software to control everything. I dream with iCUE being able to handle Asus AuraSync using its API because the native Asus app sucks and devours some CPU resources too, but... And finally, I did not get from where you found this "66%" of whatever I have hahaha I'm a dumb! LMAO

For me, when I tried this earlier, it doesn't worked. CPU consumption was the same extremely high as before removing the XML profiles. Maybe it's a good idea to put the warning about what I said when you downgrade to the previous version. I was unable to convert my profiles back to the old format used by iCUE 3.2.87. I tried that but even if I delete all my profiles and delete all color or lights in the last profile, the CPU still gets burned by iCUE. Thank you for this, CJ. Corsair's dev team should speed up coding and releasing a build to fix this issue. They are too slow even for a small size company. I'm a developer and I'm sure they can be faster to solve a problem that they should tested before releasing a faulty version. There is no way that a team can be slower than me coding an app alone. I am sure Corsair dev team can be more efficient and do things faster and testing it better. What happen to that history of Corsair be the best manufacturer of hardware because the other ones in the market isn't good enough for a "fair" price if this doesn't apply to software too? Maybe things has changed to worse sneaky in front of our eyes and we didn't see it.

I have a HUGE problem with this. Spend all day trying the solutions given here by you, Solarity, trying another other things and nothing worked for me. I have a bunch of corsair things. K95 RGB Platinum, Glaive RGB, Void Surround, MM800 RGB Polaris, ST100 RGB, H115i AIO watercooler and Vengeance RGB RAM modules on my desktop based on a intel core i9 7900x. The iCUE proccess is consuming ~5% of my computing resources, but this is like a margin for all resources available, being different for each CPU used by you. Looking deeply, it's consuming almost 100% of one core of my i9 with 350mb+ of RAM and on my notebook with one intel core i7 7500U, it destroys the entire performance and makes the PC useless. I tried all the solutions presented here and not even one makes any less consumption of my CPU. I'll try now rolling back for the previous build or change back to CUE+Link until this ridiculous code is fixed. If anyone else has another idea, please let me know. Thank you solarity for your help by making this post with all this info. Edit 1: Thank you again for the previously build of iCUE in another thread, solarity. You rocks! \m/ I'm rolling back to iCUE 3.2.87 on my desktop PC and backing to CUE 2.24.50 on my notebook. It's impossible to use iCUE on a i7. I'm wondering what is happening with the people using i3 or even older CPUs. Worried... a lot! Hope they find this topic with a little effort. Edit 2: I found in this another thread (thanks guys!) one post with some helpful hint, minimizing the iCUE rather than closing it to system tray helps a lot. With this now it's consuming like 40% of one core and drops the overall use to 1~2% instead of 100% of one core and 5~7% of overall CPU resources. BUT this only works in the standard profile. If I switch to another profile rather than the default one, the CPU use increases again. Tried to understand what's causing this in other profiles but I can't find anything that is causing this, nothing related to lighting effects on my KB, mouse pad, mouse, headset stand or memories. I really have no idea what is different in my profiles that is triggering the CPU extreme use. Edit 3: Ok now I figured out what is going on with my profiles. Seems that the linked lighting FX and only a few others makes this weird workaround useful and ONLY AFTER moving the XML of the demo profiles to another folder or temporary removing them. And the things becomes even more bizarre. The CPU use is only reduced when at least one light is on. If I use the "visor" FX, I got spikes in the CPU use and the spike is in the moment which the lights if off, backing to drop when lights becomes on. The graph changes accordingly the speed of the "visor" FX. Instant light mess with everything although of the state/color of it, so don't use it if you want to use this workaround. I am tired of testing this things, so I removed all the 9 XML demo profiles. Edit 4: This workaround worked only until I restarted my desktop PC. So I'm giving up for this sheet of A4 paper and rolling back to 3.2.87. Edit 5: After some more and more and more and infinite more time spent on this state of art Corsair's code, I have to let you know that they changed the things in profile database, converted when updated to the new iCUE build. So, guess what?! If you want to roll back to the previous version, your profiles wouldn't be compatible with it and no tool to convert them to the previous format is provided, if you are wondering yourself... So, for precaution, always get your profiles backed up anyway even if you are reverting to the previous build in case of the new ones isn't restored to the profile library when update again, when they should be showed up again. Although they are not in the profile lib if you roll back to 3.2.87, they still are in the profile folder: %appdata%\Corsair\CUE\profiles. So when you update again to 3.3.103+ they should be back again into the lib.