Jump to content

wacdag

Members
  • Posts

    4
  • Joined

Reputation

10 Good

Converted

  • Occupation
    Mechanical Design Engineer
  1. Yes you would need to rename cupidsdk.dll and cpuidsdk64.dll every time you update the software. However, if your system is stable and doesn't black screen or lock up then why not consider leaving the software alone.
  2. They will just ignore everyone that complains and brush it under the carpet as only a minority of their customers are affected. I've had CPUID on my computer for years before iCue and never had a problem with black screening and it sounds like they have palmed you off to someone else and not claiming responsibility of iCue's problems on certain systems. Glad you got something out of Corsair though but can understand why you are no so frustrated by Corsair's attitude.
  3. Yes I'm British. The issue is that the problem with iCue has been around for more than a year (15 months since your original post I see ) . It depends if people with certain types of system like x79 know that iCue is causing problems, it took me a while to work it out. However, the peak of people having problems has probably already passed and gone. Many may have moved on and built new/upgraded computers and now not suffering these issues with iCue.
  4. Joining this discussion to tell my story of iCue and Corsair. Having completed my first computer build some five and a half years ago I purchased a number of Corsair products including case, PSU, CPU cooler etc. It wasn't until December 2017 when I purchased a Corsair Strafe RGB keyboard that I started to have problems. With the arrival of my new keyboard meant that I needed to install new software. I soon as I noticed that this corrupted the colour settings of my H100iv1 cooler which, to my annoyance would only display red rather than the custom colour CPU temperature (white-yellow-red). After much head scratching and endless installing/uninstalling of my corsair link software for the H100iv1 I worked out that my cooler and this newer software could not exist together and work exactly as they should. I liked my keyboard so decided that I would invest money into a new H100i Pro cooler hoping that I could finally return to the "colour change with temperature" setting I desired. I installed the new cooler and soon was experiencing random complete lockups and no output to my monitor. Was it the monitor? Was it the graphics card or the drivers? After many more complete lockups and experimenting I discovered the problems with iCUE and x79 based computers and this thread. I renamed CPUIDSDK.dll and CPUIDSDK64.dll and it was better straight away although for a while it would still make my graphic card not to output for a about a second every once in a while but it would recover okay. At present I still have iCe installed but with reduced functionality but a usually stable computer. However, Corsair's apparent unwilling or unable attitude to fixing iCue for affected users has made me decide not to purchase another Corsair product after spending £££ and having to use this iCue software which handicaps my computer (and many others) so much. I would love to see a fix appear one day but after all this time I'm not holding my breath. Sorry for my rant but I wanted to share my experience.
×
×
  • Create New...