Jump to content
Corsair Community

iCue - Application error


Recommended Posts

Seen this a couple of times now. Here's from the WEV app log:

Log Name:      Application
Source:        Application Error
Date:          2022-09-27 17:57:18
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      TheNest
Description:
Faulting application name: iCUE.exe, version: 4.28.174.0, time stamp: 0x63076e07
Faulting module name: DeviceCommands.dll, version: 0.0.0.0, time stamp: 0x630763b4
Exception code: 0xc0000005
Fault offset: 0x000000000000b4ca
Faulting process id: 0x543c
Faulting application start time: 0x01d8d257ec44d092
Faulting application path: C:\Program Files\Corsair\CORSAIR iCUE 4 Software\iCUE.exe
Faulting module path: C:\Program Files\Corsair\CORSAIR iCUE 4 Software\DeviceCommands.dll
Report Id: 6afb105c-4404-4e29-8c6f-1acc908e4d57
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>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2022-09-27T15:57:18.9413625Z" />
    <EventRecordID>4617</EventRecordID>
    <Correlation />
    <Execution ProcessID="24724" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>TheNest</Computer>
    <Security />
  </System>
  <EventData>
    <Data>iCUE.exe</Data>
    <Data>4.28.174.0</Data>
    <Data>63076e07</Data>
    <Data>DeviceCommands.dll</Data>
    <Data>0.0.0.0</Data>
    <Data>630763b4</Data>
    <Data>c0000005</Data>
    <Data>000000000000b4ca</Data>
    <Data>543c</Data>
    <Data>01d8d257ec44d092</Data>
    <Data>C:\Program Files\Corsair\CORSAIR iCUE 4 Software\iCUE.exe</Data>
    <Data>C:\Program Files\Corsair\CORSAIR iCUE 4 Software\DeviceCommands.dll</Data>
    <Data>6afb105c-4404-4e29-8c6f-1acc908e4d57</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Link to comment
Share on other sites

  • 2 weeks later...

Same here, i did a uninstall, clean up and clean install.  It worked, then the next day, the icue icon disappeared  from hidden icons and when i launch it, its slow, it says "its not responding" then shortly after it comes up it crashes and leaves this in the application log

Faulting application name: iCUE.exe, version: 4.28.177.0, time stamp: 0x632822de
Faulting module name: DeviceCommands.dll, version: 0.0.0.0, time stamp: 0x63281889
Exception code: 0xc0000005
Fault offset: 0x0000000000015510
Faulting process id: 0x0xD28
Faulting application start time: 0x0x1D8D8F47A5790BD
Faulting application path: C:\Program Files\Corsair\CORSAIR iCUE 4 Software\iCUE.exe
Faulting module path: C:\Program Files\Corsair\CORSAIR iCUE 4 Software\DeviceCommands.dll
Report Id: 7b39b089-3912-4bc7-b912-d5ed692b8b84
Faulting package full name: 
 

Link to comment
Share on other sites

Yep, same thing here, iCUE keeps crashing left and right. I had my hopes up with the new version which was newly released but nope...here's my latest crash. This time said to be caused by ntdll.dll...seems to be different dlls every time

Log Name:      Application
Source:        Application Error
Date:          2022-10-06 09:04:33
Event ID:      1000
Task Category: Application Crashing Events
Level:         Error
Keywords:      
User:          THENEST\Richard
Computer:      TheNest
Description:
Faulting application name: iCUE.exe, version: 4.28.177.0, time stamp: 0x632822de
Faulting module name: ntdll.dll, version: 10.0.22621.608, time stamp: 0xf2e8a5ab
Exception code: 0xc0000374
Fault offset: 0x000000000010c1c9
Faulting process id: 0x0x2254
Faulting application start time: 0x0x1D8D95076E97214
Faulting application path: C:\Program Files\Corsair\CORSAIR iCUE 4 Software\iCUE.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 5facb188-b84f-4197-b432-dfae609120b7
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" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />
    <EventID>1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2022-10-06T07:04:33.7732823Z" />
    <EventRecordID>1734</EventRecordID>
    <Correlation />
    <Execution ProcessID="14280" ThreadID="9008" />
    <Channel>Application</Channel>
    <Computer>TheNest</Computer>
    <Security UserID="S-1-5-21-133767816-178543-123633953-1001" />
  </System>
  <EventData>
    <Data Name="AppName">iCUE.exe</Data>
    <Data Name="AppVersion">4.28.177.0</Data>
    <Data Name="AppTimeStamp">632822de</Data>
    <Data Name="ModuleName">ntdll.dll</Data>
    <Data Name="ModuleVersion">10.0.22621.608</Data>
    <Data Name="ModuleTimeStamp">f2e8a5ab</Data>
    <Data Name="ExceptionCode">c0000374</Data>
    <Data Name="FaultingOffset">000000000010c1c9</Data>
    <Data Name="ProcessId">0x2254</Data>
    <Data Name="ProcessCreationTime">0x1d8d95076e97214</Data>
    <Data Name="AppPath">C:\Program Files\Corsair\CORSAIR iCUE 4 Software\iCUE.exe</Data>
    <Data Name="ModulePath">C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
    <Data Name="IntegratorReportId">5facb188-b84f-4197-b432-dfae609120b7</Data>
    <Data Name="PackageFullName">
    </Data>
    <Data Name="PackageRelativeAppId">
    </Data>
  </EventData>
</Event>

Link to comment
Share on other sites

Same issue here as well and was hoping the update today would resolve it, but it seems worse than before updating.

Log Name:      Application
Source:        Application Error
Date:          10/7/2022 8:50:13 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP
Description:
Faulting application name: iCUE.exe, version: 4.28.177.0, time stamp: 0x632822de
Faulting module name: DeviceCommands.dll, version: 0.0.0.0, time stamp: 0x63281889
Exception code: 0xc0000005
Fault offset: 0x0000000000015510
Faulting process id: 0x3a8
Faulting application start time: 0x01d8da53625575f1
Faulting application path: C:\Program Files\Corsair\CORSAIR iCUE 4 Software\iCUE.exe
Faulting module path: C:\Program Files\Corsair\CORSAIR iCUE 4 Software\DeviceCommands.dll
Report Id: 5e97b2b1-1191-4483-a5da-310ef9bb6a9b
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>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2022-10-07T13:50:13.1916605Z" />
    <EventRecordID>41623</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-CJQ3050</Computer>
    <Security />
  </System>
  <EventData>
    <Data>iCUE.exe</Data>
    <Data>4.28.177.0</Data>
    <Data>632822de</Data>
    <Data>DeviceCommands.dll</Data>
    <Data>0.0.0.0</Data>
    <Data>63281889</Data>
    <Data>c0000005</Data>
    <Data>0000000000015510</Data>
    <Data>3a8</Data>
    <Data>01d8da53625575f1</Data>
    <Data>C:\Program Files\Corsair\CORSAIR iCUE 4 Software\iCUE.exe</Data>
    <Data>C:\Program Files\Corsair\CORSAIR iCUE 4 Software\DeviceCommands.dll</Data>
    <Data>5e97b2b1-1191-4483-a5da-310ef9bb6a9b</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Link to comment
Share on other sites

  • 1 month later...
  • 1 month later...

Hey, I am currently running iCUE Software v.4.31.168 and get the same error. Did you find any solution or stable version for this?

 

EventData
    AppName iCUE.exe
    AppVersion 4.31.168.0
    AppTimeStamp 637256b4
    ModuleName DeviceCommands.dll
    ModuleVersion 0.0.0.0
    ModuleTimeStamp 63724c9f
    ExceptionCode c0000005
    FaultingOffset 0000000000014a60
    ProcessId 0x2b14
    ProcessCreationTime 0x1d911abd3b33872
    AppPath C:\Program Files\Corsair\CORSAIR iCUE 4 Software\iCUE.exe
    ModulePath C:\Program Files\Corsair\CORSAIR iCUE 4 Software\DeviceCommands.dll
    IntegratorReportId 8e7fcf6b-0d7c-4b2c-8aaf-86b906a42602
    PackageFullName  
    PackageRelativeAppId  
Link to comment
Share on other sites

Same Here.......

  • Like 1
Link to comment
Share on other sites

If you're using a Corsair AIO and have it plugged in to one of the motherboard fan/pump headers make sure to go into the BIOS and set the fan/pump speed to max.  My new board was set to auto and I'd forgotten to change it when setting it up.  I was getting the Windows sound for disconnected hardware every so often and iCUE would crash right after, once I set the motherboard pump header to max it stopped disconnecting and crashing.

Might not be the same issue for everyone but since I made the changes a few days ago it hasn't crashed once.

  • Like 1
Link to comment
Share on other sites

On 12/21/2022 at 8:23 PM, RandomDesign said:

If you're using a Corsair AIO and have it plugged in to one of the motherboard fan/pump headers make sure to go into the BIOS and set the fan/pump speed to max.  My new board was set to auto and I'd forgotten to change it when setting it up.  I was getting the Windows sound for disconnected hardware every so often and iCUE would crash right after, once I set the motherboard pump header to max it stopped disconnecting and crashing.

Might not be the same issue for everyone but since I made the changes a few days ago it hasn't crashed once.

Thanks for sharing your experience. In my case the only hardware from Corsair is a mouse and keyboard.

Link to comment
Share on other sites

On 12/21/2022 at 2:23 PM, RandomDesign said:

If you're using a Corsair AIO and have it plugged in to one of the motherboard fan/pump headers make sure to go into the BIOS and set the fan/pump speed to max.  My new board was set to auto and I'd forgotten to change it when setting it up.  I was getting the Windows sound for disconnected hardware every so often and iCUE would crash right after, once I set the motherboard pump header to max it stopped disconnecting and crashing.

Might not be the same issue for everyone but since I made the changes a few days ago it hasn't crashed once.

Didn't work for me.

Link to comment
Share on other sites

  • 2 weeks later...

Happening to me too.  Not sure when it started tho.

Faulting application name: iCUE.exe, version: 4.31.168.0, time stamp: 0x637256b4
Faulting module name: DeviceCommands.dll, version: 0.0.0.0, time stamp: 0x63724c9f
Exception code: 0xc0000005
Fault offset: 0x00000000000159a0
Faulting process id: 0x0x6D80
Faulting application start time: 0x0x1D92107BB40BE96
Faulting application path: C:\Program Files\Corsair\CORSAIR iCUE 4 Software\iCUE.exe
Faulting module path: C:\Program Files\Corsair\CORSAIR iCUE 4 Software\DeviceCommands.dll
Report Id: 4a9317f1-f35b-4a37-a046-345c964416d6
Faulting package full name: 
Faulting package-relative application ID: 

Edited by BT843
Link to comment
Share on other sites

On 12/21/2022 at 2:23 PM, RandomDesign said:

If you're using a Corsair AIO and have it plugged in to one of the motherboard fan/pump headers make sure to go into the BIOS and set the fan/pump speed to max.  My new board was set to auto and I'd forgotten to change it when setting it up.  I was getting the Windows sound for disconnected hardware every so often and iCUE would crash right after, once I set the motherboard pump header to max it stopped disconnecting and crashing.

Might not be the same issue for everyone but since I made the changes a few days ago it hasn't crashed once.

I don't think this should make a difference since the cable going to the motherboard is only a dummy cable to avoid the no CPU fan error from your BIOS. Changing any fan curves will have no impact.

Link to comment
Share on other sites

On 1/11/2023 at 4:15 AM, Corsair Raven said:

If the faulting module points to iCUE, it might be worth repairing and clean installing iCUE. If you continue to have issues after that, go ahead and contact our support team by opening a ticket at https://help.corsair.com/hc/en-us/requests/new so our support team can look into this further for you.

I did this. Followed support's instructions to the letter, including all the registry removals and tracking down of every instance of iCue all over the place.

It's like a 10 step process. You guys should really make a removal tool for this 😉

Then I rebooted and resintalled from a fresh download. At first I thought the problem might have gone away, but nope, it just didn't crash for awhile but then went right back to its old ways.

On about my 12th crash today and it's only 5:30 pm. I submitted my logs to your support team for analysis 6+ weeks ago, after having complained about the problem for 6+ weeks prior to that. Yet no one from your side is providing anything better than, "did you reboot?", "did you repair/uninstall/reinstall?", or "open a support ticket?".

Yes, to all of the above, multiple times over. My latest support ticket # is 2005734863. If would be so inclined to see what's happening with that, it would be greatly appreciated!

Sorry for my tone, but I am well beyond frustrated with this whole situation. I've been a satified customer of Corsair's for years and I did not expect this.

Link to comment
Share on other sites

23 minutes ago, Fatbat said:

I did this. Followed support's instructions to the letter, including all the registry removals and tracking down of every instance of iCue all over the place.

It's like a 10 step process. You guys should really make a removal tool for this 😉

Then I rebooted and resintalled from a fresh download. At first I thought the problem might have gone away, but nope, it just didn't crash for awhile but then went right back to its old ways.

On about my 12th crash today and it's only 5:30 pm. I submitted my logs to your support team for analysis 6+ weeks ago, after having complained about the problem for 6+ weeks prior to that. Yet no one from your side is providing anything better than, "did you reboot?", "did you repair/uninstall/reinstall?", or "open a support ticket?".

Yes, to all of the above, multiple times over. My latest support ticket # is 2005734863. If would be so inclined to see what's happening with that, it would be greatly appreciated!

Sorry for my tone, but I am well beyond frustrated with this whole situation. I've been a satified customer of Corsair's for years and I did not expect this.

I'm in the same boat as you. iCUE is just a mess and it has been for the last couple of months. I followed the same uninstall process and did a clean install, heck i did a clean Windows install and it's still crashing. The only fix is to change all the hardware lighting/fan settings and then quit and iCUE and all its processes. Corsairs support has been really bad. I opened a ticket in November because my AIO was failing and it took them like 4 weeks to even respond to it. Tbh I'm so fed up with Corsair and their terrible software that I'll most likely ditch it and go for a different brand. That new EK AIO looks very appealing ,,,

Link to comment
Share on other sites

10 hours ago, foldpages said:

I'm in the same boat as you. iCUE is just a mess and it has been for the last couple of months. I followed the same uninstall process and did a clean install, heck i did a clean Windows install and it's still crashing. The only fix is to change all the hardware lighting/fan settings and then quit and iCUE and all its processes. Corsairs support has been really bad. I opened a ticket in November because my AIO was failing and it took them like 4 weeks to even respond to it. Tbh I'm so fed up with Corsair and their terrible software that I'll most likely ditch it and go for a different brand. That new EK AIO looks very appealing ,,,

This pains me, because based on the responses like yours, and based on what I have experienced, it doesn't look like any of us that are suffering from these problems are going to get any resolve. I have spent about €5000 on this build, and obvioulsy the vast majority of this falls under mobo, CPU and GPU. However, the rest is all Corsair. RAM, PSU, AIO, fans, case, and all the accessories. And it doesn't work properly. I have threatened RMAing the lot, but I make my living on my PC, so I can't just unplug it all and ship the **** that doesn't work.

It's completely disheartening. I am quite saddend by how this has turned out. Being an "enthusiast" doesn't mean that you should have to troubleshoot your new rig for three months to make it work properly.

Link to comment
Share on other sites

  • 2 weeks later...
On 1/12/2023 at 5:46 PM, Fatbat said:

I did this. Followed support's instructions to the letter, including all the registry removals and tracking down of every instance of iCue all over the place.

It's like a 10 step process. You guys should really make a removal tool for this 😉

Then I rebooted and resintalled from a fresh download. At first I thought the problem might have gone away, but nope, it just didn't crash for awhile but then went right back to its old ways.

On about my 12th crash today and it's only 5:30 pm. I submitted my logs to your support team for analysis 6+ weeks ago, after having complained about the problem for 6+ weeks prior to that. Yet no one from your side is providing anything better than, "did you reboot?", "did you repair/uninstall/reinstall?", or "open a support ticket?".

Yes, to all of the above, multiple times over. My latest support ticket # is 2005734863. If would be so inclined to see what's happening with that, it would be greatly appreciated!

Sorry for my tone, but I am well beyond frustrated with this whole situation. I've been a satified customer of Corsair's for years and I did not expect this.

I'm also very much identified to your situation. It's so silly to have a response after almost a month asking the same questions over and over. I've followed the same recommendations as you did, even fresh restart, but nothing helps. I'm trying to claim a replacement, because when we bought these components, we built 2 computers and my brother had 0 issues so far with everything exactly same (hardware settings, software settings, Windows configuration, etc.). This is so frustrating.

Link to comment
Share on other sites

The beauty of all this is that these post are starting to rank when you search for, "why doesn't iCue XYZ?". So Corsair ignoring these problems is eventually going to hit them in the wallet.

Maybe then they will pay attention.

One can only hope.

Link to comment
Share on other sites

I am having the same problem. The error actually points to the corsair program itself. It crashes on fresh reboot, on fresh install, on repair, on clean reinstall, on clean windows 11 reinstall. I tuirned off the firewall. I deleted the program folders. I deleted the registry keys. I deleted the temporary and app folders. I tried the high DPI setting, I tried setting my CPU/AIO fans to 100%. Considering how much I spent on my new pc with corsair components I am very frustrated. Nothing makes a difference.

Faulting application name: iCUE.exe, version: 4.32.129.0, time stamp: 0x63933ce2
Faulting module name: iCUE.dll, version: 4.32.129.0, time stamp: 0x63933c01
Exception code: 0xc0000005
Fault offset: 0x00000000006b8e90
Faulting process id: 0x0x3700
Faulting application start time: 0x0x1D93464D83DD1F7
Faulting application path: C:\Program Files\Corsair\CORSAIR iCUE 4 Software\iCUE.exe
Faulting module path: C:\Program Files\Corsair\CORSAIR iCUE 4 Software\iCUE.dll
Report Id: c6010a42-990e-423e-8702-4bd1ff8a7d75
Faulting package full name: 
Faulting package-relative application ID: 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...