Jump to content

1ntel

Members
  • Posts

    21
  • Joined

Reputation

10 Good
  1. The latest iCUE update now has support for GPU and for me works a lot better. Seeing no issues with MB or GPU integration!
  2. I had to disable plugins as there is no way to disable motherboard integration. I have to use Aura because iCUE does not support my GPU or memory so the both conflict horribly.
  3. Ah okay. If I do open it then what do I do?
  4. Hi, I have today installed iCUE 3.26.95 and started using Motherboard integration. I can't seem to get it to control RGB and it is also missing the ASUS Aura GPU from the options. RGB is stuck on the last static color since I opened Aura. Is GPU control not yet supported? Regards.
  5. I am a software engineer myself although not .NET. I did some digging and found Corsair.Service has a handy output when you run it. I got it to throw the error after shutting down the service by pressing "Enter" to stop in the console. Ignore the red part about USB, that appears to be handled and doesn't throw errors in Windows. The key part in System.Management.ManagementException. It looks like they are trying to access an external process and I can only guess it is "Corsair.Service.CpuIdRemote64.exe" that iCUE uses. I can also guess what happens is Windows closes the process on shutdown before iCUE is shutdown which causes iCUE to search for the process and it throws the error "Not found." So there we go, now to get that to the development team..
  6. It's consistent for me on every reboot it will log the same error. I think that is just bad development and something wrong with the software.
  7. This error actually still happens for me. There was one version of Corsair Link where it didn't happen. Does this not happen for you @DevBiker?
  8. It does this on 3.9.93 too.
  9. Just to update, the issue still happens in v3.8.91.
  10. Apologies. I have attached the full logs. CorsairLogs.zip
  11. Sure, is it just the Service_Trace.log file? Attached is the Service_Trace. The reliability manager issue is: Description Faulting Application Path: C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\Corsair.Service.exe Problem signature Problem Event Name: CLR20r3 Problem Signature 01: Corsair.Service.exe Problem Signature 02: 3.7.0.22 Problem Signature 03: 5b86786d Problem Signature 04: System.Management Problem Signature 05: 4.7.3056.0 Problem Signature 06: 5a8e5a11 Problem Signature 07: 8a Problem Signature 08: 51 Problem Signature 09: PSZQOADHX1U5ZAHBHOHGHLDGIY4QIXHX OS Version: 10.0.17134.2.0.0.256.48 Locale ID: 2057 Additional Information 1: 2beb Additional Information 2: 2beba6fb4680d73a8c78ca7c24ccdb46 Additional Information 3: 9cbb Additional Information 4: 9cbb96fd98ad2db237e9e850ca5d0351 Extra information about the problem Bucket ID: e49489ab0e5b3b8b848aed265e00bcdb (1480256176586276059) I have also noticed it doesn't do it on Corsair Link 4.9.4.28, but it does it on Corsair Link 4.9.6.19, 4.9.7.35 and any Corsair iCUE versions. I assume Link and iCue share the same code for the service. Service_Trace.zip
  12. Using iCUE 3.7.99 does anyone elses Reliability Manager report that the Corsair.Service has stopped working? Mine seems to happen everytime I shutdown or reboot my machine. Not that it is a major issue as everything seems to work fine, it just fills up Reliability Manager with these reports.
×
×
  • Create New...