View Single Post
  #13  
Old 06-21-2018, 01:57 PM
JourneyOver JourneyOver is offline
Registered User
JourneyOver's PC Specs
 
Join Date: May 2017
Posts: 10
POST ID # = 960191
JourneyOver Reputation: 10
Default

Quote:
Originally Posted by DevBiker View Post
While I understand your frustration, it's apparently not that common. It may also be one of those things that's related to a very specific set of hardware conditions that you are unlucky enough to have.

However, what you can do is rename the cpuidsdk.dll to cpuidsdk.bak. You will lose any monitoring of these values and any fan curves that may be based on these values will need to be reset, so it's not an ideal fix. But iCue will still operate properly. I'm not sure what Corsair devices you have that you need iCue for ... they aren't in your profile ... so I don't know how big of an issue this would be.
so, so far this seems to have at least done the trick to allow me to update and run icue at the latest version instead of running the extremely out of date cue 2.24.35 without having any blue screens, though I did have to change the "cpuidsdk64.dll" one as well it seemed, not completely ideal as I'll probably have to change these every update to iCue until they finally fix this issue but it'll at least do for now.