Jump to content

asyvan

Members
  • Posts

    16
  • Joined

Reputation

10 Good
  1. I do think my problem with iCue "flatline" has been resolved. The last recommended action from Corsair on my support ticket was to: 1. Remove iCue and/or CLink 2. Remove the Corsair folders from %appdata%\local and \roaming 3. Install latest iCue 3.8.91 I have not had a freeze or "flatline" for several days now, before this it was "flatline" several times each day. I hold my breath, but looks good.
  2. That is my experience as well. I have not found anything that triggers this.
  3. I can confirm that renaming (basically removing) cpuidsdk.dll and cpuidsdk64.dll does NOT solve the problem. iCue monitoring still freeze and requires a service restart.
  4. I have renamed both cpuidsdk.dll and cpuidsdk64.dll to _old and will now monitor the system. Will report back in a day or so.
  5. I hope you didn't... because I can confirm my issues are still present with latest. Verified just today.
  6. If I can be of any assistance with my system, let me know. The issue is extremely repeatable (multiple times per day) although I do not know yet exactly what triggers it (or exactly when in time). You can have my business email in a PM if you so desire.
  7. I can confirm that quitting/exiting the iCue UI does not resolve the freeze. Only restarting the Service will. I will uninstall this software now and hope that Corsair solves this soon, because next option is to remove the Corsair products and move to other vendors.
  8. Any idea of what to expect in terms of fixing this? Just to make it clear, it happens all the time, every day, for many users as it seems. Can CORSAIR please push this a bit higher in development/support? I run Corsair H115i, Commander Pro, ML fans.
  9. Someone (all of us maybe) need to make a support ticket. Corsair does NOT seem to take this seriously and does not seem to pick this thread up.
  10. Have you picked up the latest in this thread and can you confirm you are working on a solution? Thanks
  11. This is a workaround. I hope this is picked up by Corsair so they can fix this issue in their software. I would be kinda embarrassed if I was Corsair, not having this fixed yet.
  12. Here is a ZIP of the logs showing the error that caused my iCue to freeze all actions, reporting as well as control of devices such as fan speeds. Restaring the service resumes the iCue operations and control of fans. The error I can see occurs at 10:05 in the log... see below. I restarted the Service at approx 12:45. Until then iCue flatlined and had no control over fans. 2018-08-01 10:05:28.7616 | 3 | WARN: DeviceControlExtentions | Exception of type CorsairLink4.Module.ProDevices.Common.Exceptions.ProDeviceException occured (try 1 of 5) CorsairLink4.Module.ProDevices.Common.Exceptions.ProDeviceException: No response ---> System.TimeoutException: Operation timed out. vid HidSharp.Platform.Windows.NativeMethods.OverlappedOperation(IntPtr ioHandle, IntPtr eventHandle, Int32 eventTimeout, IntPtr closeEventHandle, Boolean overlapResult, NativeOverlapped* overlapped, UInt32& bytesTransferred) vid HidSharp.Platform.Windows.WinHidStream.Write(Byte[] buffer, Int32 offset, Int32 count) vid HidSharp.HidStream.Write(Byte[] buffer) vid CorsairLink4.Module.ProDevices.Common.ProDeviceHidCommunicationHandler.WriteOutputBufferBuilderData(ProDeviceOutputBufferBuilder builder) --- **** på stackspårning för interna undantag --- vid CorsairLink4.Module.ProDevices.Common.ProDeviceHidCommunicationHandler.WriteOutputBufferBuilderData(ProDeviceOutputBufferBuilder builder) vid CorsairLink4.Module.ProDevices.Common.ProDeviceHidCommunicationHandler.WriteAndRead(ProDeviceOutputBufferBuilder builder) vid CorsairLink4.Module.ProDevices.Common.FanDevice.ProFanDeviceDataProcessor.ReadFanState() vid CorsairLink4.Module.ProDevices.Common.FanDevice.ProFanDevice.ProcessExternalTemperatureData(DeviceCommunicationData data) vid CorsairLink4.Module.ProDevices.Barbuda.BarbudaDeviceComponent.ProcessExternalTemperatureData(DeviceCommunicationData data) vid CorsairLink4.Module.ProDevices.ProDevicesComponent.<InternalProcessExternalTemperatureData>d__14.MoveNext() --- **** på stackspårningen från föregående plats där ett undantag utlöstes --- vid System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) vid System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) vid CorsairLink4.Module.Common.BaseControlledComponent.<ProcessControlData>d__0.MoveNext() --- **** på stackspårningen från föregående plats där ett undantag utlöstes --- vid System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) vid System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) vid CorsairLink4.Service.Common.Utils.DeviceControlExtentions.<ProcessDeviceRequest>d__0.MoveNext() 2018-08-01 10:05:29.2762 | 7 | ERROR: AsetekCoolerV2Device | Device can't be open. USBCommandHandler.SI_Open returns false 2018-08-01 10:05:29.2762 | 7 | ERROR: AsetekCoolerV2Device | Exception while writing and reading: Ett undantagsfel av typen SIUSBXpWrapper.USBDeviceReadException inträffade. 2018-08-01 10:05:30.2779 | 7 | ERROR: AsetekCoolerV2Device | Device can't be open. USBCommandHandler.SI_Open returns false 2018-08-01 10:05:30.2789 | 7 | ERROR: AsetekCoolerV2Device | Open was failed 3 time(s). Need to restart devices 2018-08-01 10:05:34.8723 | 7 | ERROR: AsetekCoolerV2Device | Try to open one more time after restart... 2018-08-01 10:05:34.8723 | 7 | ERROR: AsetekCoolerV2Device | Additional open: Success! 2018-08-01 10:05:34.9622 | 28 | INFO: DevicesMonitor | TIME = 1977(avg: 1012,26) ms 2018-08-01 10:05:34.9622 | 28 | INFO: DevicesMonitor | Devices: 8(51 sens.) Service logs.zip
  13. Hi I have the same issue with iCue. Will try to post the logs once I have something in them. H115i + Commander Pro
×
×
  • Create New...