blackweb Posted November 22, 2019 Share Posted November 22, 2019 iCUE 3.22.74 Product: CORSAIR iCUE Software -- Error 1719. The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance. Faulting application name: Corsair.Service.CpuIdRemote64.exe, version: 3.22.0.7, time stamp: 0x5da719a2 Faulting module name: cpuidsdk64.dll, version: 1.2.1.6, time stamp: 0x5c2e4d8a Exception code: 0xc0000005 Fault offset: 0x000000000009d68f Faulting process id: 0x8468 Faulting application start time: 0x01d5a0cbf496f09a Faulting application path: C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\Corsair.Service.CpuIdRemote64.exe Faulting module path: C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\cpuidsdk64.dll Report Id: 26db753e-ad65-4ab6-a2ef-f8cee0019218 Faulting package full name: Application: Corsair.Service.CpuIdRemote64.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException at CpuIdWrapper.Sdk.CpuIdSdk.RefreshInformation() at CorsairLink4.Service.CpuIdRemote.CpuIdRemoteService.RefreshInformation() at DynamicClass.SyncInvokeRefreshInformation(System.Object, System.Object[], System.Object[]) at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(System.Object, System.Object[], System.Object[] ByRef) at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(System.ServiceModel.Dispatcher.MessageRpc ByRef) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(System.ServiceModel.Dispatcher.MessageRpc ByRef) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(System.ServiceModel.Dispatcher.MessageRpc ByRef) at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean) at System.ServiceModel.Dispatcher.ChannelHandler.DispatchAndReleasePump(System.ServiceModel.Channels.RequestContext, Boolean, System.ServiceModel.OperationContext) at System.ServiceModel.Dispatcher.ChannelHandler.HandleRequest(System.ServiceModel.Channels.RequestContext, System.ServiceModel.OperationContext) at System.ServiceModel.Dispatcher.ChannelHandler.AsyncMessagePump(System.IAsyncResult) at System.ServiceModel.Dispatcher.ChannelHandler.OnAsyncReceiveComplete(System.IAsyncResult) at System.Runtime.Fx+AsyncThunk.UnhandledExceptionFrame(System.IAsyncResult) at System.Runtime.AsyncResult.Complete(Boolean) at System.ServiceModel.Channels.TransportDuplexSessionChannel+TryReceiveAsyncResult.OnReceive(System.IAsyncResult) at System.Runtime.Fx+AsyncThunk.UnhandledExceptionFrame(System.IAsyncResult) at System.Runtime.AsyncResult.Complete(Boolean) at System.ServiceModel.Channels.SynchronizedMessageSource+ReceiveAsyncResult.OnReceiveComplete(System.Object) at System.ServiceModel.Channels.SessionConnectionReader.OnAsyncReadComplete(System.Object) at System.Runtime.Fx+AsyncThunk.UnhandledExceptionFrame(System.IAsyncResult) at System.Net.LazyAsyncResult.Complete(IntPtr) at System.Net.LazyAsyncResult.ProtectedInvokeCallback(System.Object, IntPtr) at System.Net.Security.NegotiateStream.ProcessFrameBody(Int32, Byte[], Int32, Int32, System.Net.AsyncProtocolRequest) at System.Net.Security.NegotiateStream.ReadCallback(System.Net.AsyncProtocolRequest) at System.Net.AsyncProtocolRequest.CompleteRequest(Int32) at System.Net.FixedSizeReader.CheckCompletionBeforeNextRead(Int32) at System.Net.FixedSizeReader.ReadCallback(System.IAsyncResult) at System.Runtime.AsyncResult.Complete(Boolean) at System.ServiceModel.Channels.ConnectionStream+IOAsyncResult.OnAsyncIOComplete(System.Object) at System.ServiceModel.Channels.PipeConnection.OnAsyncReadComplete(Boolean, Int32, Int32) at System.ServiceModel.Channels.OverlappedContext.CompleteCallback(UInt32, UInt32, System.Threading.NativeOverlapped*) at System.Runtime.Fx+IOCompletionThunk.UnhandledExceptionFrame(UInt32, UInt32, System.Threading.NativeOverlapped*) at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32, UInt32, System.Threading.NativeOverlapped*) Link to comment Share on other sites More sharing options...
DevBiker Posted November 22, 2019 Share Posted November 22, 2019 Were you uninstalling at the time? Link to comment Share on other sites More sharing options...
blackweb Posted November 22, 2019 Author Share Posted November 22, 2019 Not just installing or uninstalling. Using the software. Link to comment Share on other sites More sharing options...
blackweb Posted November 23, 2019 Author Share Posted November 23, 2019 I have not had any issues since i turned on logging for the 2 Dominator Platinum RGB 3200 DIMMS. Vefore the logging was on, the dim module kept erroring out, leaving a red splat on the icon in iCUE and was not accessible. I would click oin the DIMM module and it would not respond. Link to comment Share on other sites More sharing options...
Recommended Posts