Updated iCue 4.22.203 but now it crashes after a few minutes

[Thicc Boi Brandon]

I updated iCue but now it is crashing every few minutes. I have checked drivers, done a fresh/clean reinstalled of iCue and reinstalled windows 10 just in case.

 

This is what I am getting in Event Viewer when it crashes, can anyone shed some light?

--------------------------------------------------------------------------------------------------------------

Faulting application name: iCUE.exe, version: 4.22.203.0, time stamp: 0x62331df7
Faulting module name: ntdll.dll, version: 10.0.19041.1566, time stamp: 0x1be73aa8
Exception code: 0xc0000005
Fault offset: 0x0000000000025bb6
Faulting process ID: 0x2fe0
Faulting application start time: 0x01d849b9949f08da
Faulting application path: C:\Program Files\Corsair\CORSAIR iCUE 4 Software\iCUE.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: 9e13ea1a-2790-49e1-91aa-9917d6901ebc
Faulting package full name: 
Faulting package-relative application ID: 

--------------------------------------------------------------------------------------------------------------

[Thicc Boi Brandon]

The only thing that actually comes to mind is that I have 2 Dark Core Pro SE Mouse's and the ones is running through my Virtuoso SE Dongle on Multipoint and the other is using the original Dongle but plugged into a a USB expansion card below my GPU and that the only thing I can think that has changed other then the update.

[Sidney_Smi]

While I can't offer any concrete help, I can say that my computer, updated to the same version, also crashes within minutes of this error. I also have a Dark Core RGB Pro mouse that is paired to the computer using the dongle of the Virtuoso SE. I also noticed that sometimes ICUE doesn't start synching after booting like it normally does.

[Corsair Notepad]

On 4/6/2022 at 6:42 AM, Thicc Boi Brandon said:

I updated iCue but now it is crashing every few minutes. I have checked drivers, done a fresh/clean reinstalled of iCue and reinstalled windows 10 just in case.

 

This is what I am getting in Event Viewer when it crashes, can anyone shed some light?

--------------------------------------------------------------------------------------------------------------

Faulting application name: iCUE.exe, version: 4.22.203.0, time stamp: 0x62331df7
Faulting module name: ntdll.dll, version: 10.0.19041.1566, time stamp: 0x1be73aa8
Exception code: 0xc0000005
Fault offset: 0x0000000000025bb6
Faulting process ID: 0x2fe0
Faulting application start time: 0x01d849b9949f08da
Faulting application path: C:\Program Files\Corsair\CORSAIR iCUE 4 Software\iCUE.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: 9e13ea1a-2790-49e1-91aa-9917d6901ebc
Faulting package full name: 
Faulting package-relative application ID: 

--------------------------------------------------------------------------------------------------------------

That error actually shows that iCUE itself is not the cause of the crash but rather something else you have installed. This specific error happens when you have extremely outdated third-party software installed and running causing a conflict leading to a crash. You will also most likely notice other Application Error events also showing system level DLLs as the faulting module for crashing applications. 

[Sanatorious]

@Corsair Notepad Your response doesn't clarify much. It is quite confusing.

First you say that the issue is extremely outdated third-party software... how did you come to that conclusion based on the evidence provided?

Second you say that the system level DLLs are to blame (in this case the evidence points to an issue with ntdll.dll).

So which is it? Outdated third-party software or ntdll.dll?

Let's examine system level DLLs as the faulting module...

So you are saying Windows ntdll.dll is the issue? What is ntdll.dll? It's a fundamental Windows library. Microsoft Windows library files - Wikipedia

Quote

NTDLL.DLL exports the Windows Native API. The Native API is the interface used by user-mode components of the operating system that must run without support from Win32 or other API subsystems. Most of this API is implemented in NTDLL.DLL and at the upper edge of ntoskrnl.exe (and its variants), and the majority of exported symbols within these libraries are prefixed Nt, for example NtDisplayString. Native APIs are also used to implement many of the "kernel APIs" or "base APIs" exported by KERNEL32.DLL.^[3][4][5] The large majority of Windows applications do not call NTDLL.DLL directly.^[6]

So what the error actually suggests is that iCUE is making use of ntdll - either directly or indirectly - to perform its functions. It also suggests that iCUE is doing so in a manner that creates the fault (e.g. a memory leak).

I'm not a coding expert, but I write and compile my own executables and dlls - all making calls to Windows DLLs to have a rudimentary understanding of the issue. I suggest Corsair stop blaming other software and examine their own code making calls that eventually reach ntdll (note that iCUE doesn't need to make a call to ntdll directly - other DLLs used may take a call from iCUE and pass that call to ntdll).

I'm having this issue and have read a number of other threads from other users who have the same issue. I have yet to find a solution.

[jetpuck73]

I get the same error.

[jetpuck73]

EventData

AppName

iCUE.exe

AppVersion

4.30.162.0

AppTimeStamp

636284f2

ModuleName

ntdll.dll

ModuleVersion

10.0.22621.755

ModuleTimeStamp

8a328c67

ExceptionCode

c0000374

FaultingOffset

000000000010c249

ProcessId

0xef0

ProcessCreationTime

0x1d8f7d2b8d0962b

AppPath

C:\Program Files\Corsair\CORSAIR iCUE 4 Software\iCUE.exe

ModulePath

C:\Windows\SYSTEM32\ntdll.dll

IntegratorReportId

bd41981a-76eb-4732-87fe-b008508e2098

PackageFullName

PackageRelativeAppId