schmak01 Posted March 19, 2020 Posted March 19, 2020 It seems to be daily if not more occurrence. Things worked fine on the previous version. Are others having this issue? Any patch/hotfix? Right now I am running a powershell script to see if it is closed and relaunch it as a band-aid. I get a ton of windows error reports like this: Fault bucket , type 0 Event Name: BEX Response: Not available Cab Id: 0 Problem signature: P1: iCUE.exe P2: 3.26.95.0 P3: 5e5d5bd0 P4: StackHash_2beb P5: 0.0.0.0 P6: 00000000 P7: PCH_74_FROM_ntdll+0x0007232C P8: c0000005 P9: 00000008 P10: All after an Error: Faulting application name: iCUE.exe, version: 3.26.95.0, time stamp: 0x5e5d5bd0 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0x5860 Faulting application start time: 0x01d5fd6e7e16bfcb Faulting application path: C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\iCUE.exe Faulting module path: unknown Report Id: 21c1a860-98b5-49c7-a771-e9760196b668 Faulting package full name: Faulting package-relative application ID:
WillerZ Posted March 19, 2020 Posted March 19, 2020 Yep happens to me also. I'm looking for where to download the previous version at this point.
schmak01 Posted March 19, 2020 Author Posted March 19, 2020 (edited) I made a PowerShell script that will re-launch it after it crashes, set to run every 5 minutes in task manager. If it was down, it will pop up in a window, otherwise stay minimized. I haven't figured out how to keep it minimized when launched manually. $path = "C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\iCUE.exe" get-process | where-object {$_.Path -eq $path } | measure-object | where-object { $_.Count -eq 0} | foreach-object {start-process -filepath $path } It pops up a PS window so I am trying to figure out how to stop that. Edited March 19, 2020 by schmak01
xMacias Posted March 19, 2020 Posted March 19, 2020 When iCUE crashes, could you export the log file from iCUE Settings and also create a dump file for the crash? That would help the devs get a head start on what's going on.
schmak01 Posted March 19, 2020 Author Posted March 19, 2020 When iCUE crashes, could you export the log file from iCUE Settings and also create a dump file for the crash? That would help the devs get a head start on what's going on. I already did that, is there a specific place to upload?
schmak01 Posted March 19, 2020 Author Posted March 19, 2020 Got a script working. Create a new PS1 file with the following: $CheckEverySeconds = 10 $path = "C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\iCUE.exe" while ($true){ get-process | where-object {$_.Path -eq "C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\iCUE.exe" } | measure-object | where-object { $_.Count -eq 0} | foreach-object {start-process -filepath $path } Start-Sleep -Seconds $CheckEverySeconds } Create a new scheduled task, name it what you want, as your user, don't need high privileges. Run at login, delay 15 minutes. Run program: powershell.exe Arguments: -windowstyle hidden -f "C:\Scripts\iCue.ps1" Of course, make the latter whatever your path is.
Sineira Posted March 19, 2020 Posted March 19, 2020 Thanks for doing the work on that script! Works great!
schmak01 Posted March 20, 2020 Author Posted March 20, 2020 I would suggest changing the timer to 5-15 minutes, I had it at 10 seconds to test. That's the first variable in the script.
mrkrgers Posted March 20, 2020 Posted March 20, 2020 I recommend going to an earlier version of iCue. http://downloads.corsair.com/Files/CUE/iCUESetup_x.xx.xx_release.msi Replace the x.xx.xx with the version of iCue you want. I am using 3.25.60 without issue.
Recommended Posts