Jump to content
Corsair Community

Newer versions of iCue crashing


robr
 Share

Recommended Posts

I recently did an auto update of iCue to 3.37.140 and now when I start the app, it loads for a split second then crashes (window vanishes). I'm not sure what version I was on previously (3.35.152 I think based on my downloads but that crashes after reinstall), so I tried installing older versions but the ones that worked weren't recognizing all my hardware.

 

Note I have been deleting profiles each time I uninstall and have also followed the instructions for removing registry entries and files/directories. I did see a note in another post about ASMedia USB drivers but far as I can tell this MB (ASUS Z-490E Gaming) doesn't use that chipset.

 

My results are below. Any ideas how to fix this? I need a tool to turn up my fans as my desktop is running hot since I'm now mining Ethereum.

 

Hardware that should be recognized is H115i Platinum, Vengeance RBG Pro, strix MB, RTX3070 Strix

 

3.37.140 - crashes

3.36.125 - crashes

3.35.152 - crashes

3.34.161 - crashes

3.33.246 - crashes

3.32.80 - crashes

3.30.89 - memory & motherboard

3.24.52 - only sees memory

3.20.80 - only sees memory

Edited by robr
Link to comment
Share on other sites

  • Corsair Employees

Perform the steps exactly as stated in the article linked below. Also close all other software running in the background, especially any other RGB controlling software, or hardware monitoring software.

 

https://help.corsair.com/hc/en-us/articles/360025166712-Perform-a-clean-reinstallation-of-the-Corsair-Utility-Engine-iCUE-

Link to comment
Share on other sites

are there any other tools that will let me adjust fan speeds? or are there any log files for icue that would help me to troubleshoot? it makes no sense the older versions load fine but the newer ones dont.
Link to comment
Share on other sites

FYI I solved the issue. For whatever reason, the problem is with the Corsair provided file below. I renamed it and now 3.34.161 (which is the last version I installed) loads fine and sees all 4 of my Corsair devices.

 

C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\plugins\LenovoY750s\y750splugin.dll

 

Faulting application name: iCUE.exe, version: 3.34.161.0, time stamp: 0x5f74743a

Faulting module name: y750splugin.dll, version: 0.0.1.0, time stamp: 0x5f2beab2

Exception code: 0xc0000005

Fault offset: 0x00008840

Faulting process id: 0x5f54

Faulting application start time: 0x01d70fe1f228106d

Faulting application path: C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\iCUE.exe

Faulting module path: C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\plugins\LenovoY750s\y750splugin.dll

Report Id: 13a6a7d6-f731-427f-9dbe-53fa9041015d

Faulting package full name:

Faulting package-relative application ID:

Edited by robr
Link to comment
Share on other sites

Further info. I upgraded to 3.37.140 and it crashed on startup again, this time I needed to rename both y750splugin.dll and Y760Plugin.dll

 

After doing that it works fine.

 

I'm having the same problem except I checked those folders and they are named as you've stated them here. Wondering if there are other solutions.

Link to comment
Share on other sites

I use windows event viewer to identify the problem files.

Check event viewer when yours crashes to help identify the cause.

 

Also I renamed the dll extension to old to fix it. If they are dll that will break things (at least for my scenario)

Link to comment
Share on other sites

I use windows event viewer to identify the problem files.

Check event viewer when yours crashes to help identify the cause.

 

Also I renamed the dll extension to old to fix it. If they are dll that will break things (at least for my scenario)

 

Faulting application name: iCUE.exe, version: 3.37.140.0, time stamp: 0x5feb82e4

Faulting module name: iCUE.dll, version: 3.37.140.0, time stamp: 0x5feb829f

Exception code: 0xc0000005

Fault offset: 0x026a05c2

Faulting process id: 0x4b48

Faulting application start time: 0x01d715b9f905acee

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: 12e11f5b-0712-4089-85f2-5e85150f8d83

Faulting package full name:

 

 

This is what my error is coming up as. So, in my instance, you're saying I would rename the 'iCUE.dll' file to 'iCUE.old'.

Link to comment
Share on other sites

I'm guessing that's a mandatory file. You could try renaming to icue.old but may get a different error. Can't hurt to try. It's also possible if you've been trying different versions of icue it could be a mismatched version of the dll so an uninstall followed by verification the icue directory is deleted followed by reinstall (and perhaps following the instructions in the 2nd post of this thread re cleaning up registry entries).
Link to comment
Share on other sites

  • Corsair Employees
Faulting application name: iCUE.exe, version: 3.37.140.0, time stamp: 0x5feb82e4

Faulting module name: iCUE.dll, version: 3.37.140.0, time stamp: 0x5feb829f

Exception code: 0xc0000005

Fault offset: 0x026a05c2

Faulting process id: 0x4b48

Faulting application start time: 0x01d715b9f905acee

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: 12e11f5b-0712-4089-85f2-5e85150f8d83

Faulting package full name:

 

 

This is what my error is coming up as. So, in my instance, you're saying I would rename the 'iCUE.dll' file to 'iCUE.old'.

 

Perform a system restart, close ALL OTHER third party software, and then test iCUE to see if the crash persists. You most likely have another program running causing a conflict which is leading to iCUE crashing.

Link to comment
Share on other sites

Perform a system restart, close ALL OTHER third party software, and then test iCUE to see if the crash persists. You most likely have another program running causing a conflict which is leading to iCUE crashing.

 

I tried this. I can't seem to identify what may be conflicting with the iCUE software. Is there perhaps a better way to identify potential conflicts?

Link to comment
Share on other sites

 Share

×
×
  • Create New...