Alberello Posted February 11, 2017 Share Posted February 11, 2017 Subscribed, I have the same issue and I am waiting for a solution... Link to comment Share on other sites More sharing options...
Marmite_II Posted February 15, 2017 Share Posted February 15, 2017 Hi Corsair Fans Reply from Corsair: Created By: Technical Support Rep (2/14/2017 4:01 PM) Hello Jochen, Our developers are working on it still. For now I recommend using HW monitor by CPUID to check your CPU temp. Regards, Francois Link to comment Share on other sites More sharing options...
red-ray Posted February 15, 2017 Share Posted February 15, 2017 Reply from Corsair: Created By: Technical Support Rep (2/14/2017 4:01 PM) Hello Jochen, Our developers are working on it still. For now I recommend using HW monitor by CPUID to check your CPU temp. Regards, Francois I just can't see how Corsair can give replies like this when I have proved that all you need to do to fix this is use a later CPUID SDK (cpuidsdk.dll). I initially proved this for CL 4.3.0.154 (http://forum.corsair.com/forums/showthread.php?p=890593) and then again for CL 4.5.0.55 (http://forum.corsair.com/forums/showthread.php?p=891269). Going further back to around 05-Aug-2016 I intimated in http://forum.corsair.com/forums/showthread.php?p=864155 that I had also done this to address the issue with CL4 failing to report my DIMMs. I did not clearly spell it out at the time as I felt I should give the CL4 developers the benefit of the doubt, but now there is no reasonable doubt and they are not up to the job. OK I would not expect the support guys to know how CL4 works, but given I first specified this on 01-Feb-2017 (http://forum.corsair.com/forums/showthread.php?p=889526) by now the developers should have got their act together and done something given I proved this on 09-Feb-2017 (http://forum.corsair.com/forums/showthread.php?p=890593) for such as answer to be given is rather poor. I suggest all users that have this issue log a call via https://corsair.secure.force.com/home/home.jsp pointing them at this post and ask for a 1.1.5.5 or later cpuidsdk.dll. Failing to support Kaby Lake is outrageous :mad:. Looking at my earlier post all it takes to fix this is a later CPUIDSDK.dll so one should be attached to the first post in this thread. It's also totally failing to report the 2 x Corsair Vengeance LED modules, is this the intended fix? :rofl: Further given that Corsair knew that Kaby Lake was not supported before releasing CL 4.5.0.55 they should have fixed this and released CL 4.5.0.55 30 seconds later. OK, I know it would need to be retested, but given that my and others LED DIMMs don't work at all I have to wonder if Corsair do any rigorous testing :eek:. Link to comment Share on other sites More sharing options...
xxgbj Posted February 16, 2017 Share Posted February 16, 2017 I also have this problem, i7 7700k+Asus Rog M9H. So the only thing i can do is waiting? Link to comment Share on other sites More sharing options...
virdog Posted February 18, 2017 Share Posted February 18, 2017 I have also recently upgraded and will wait for a version with proper support before installing CL. Subscribed Link to comment Share on other sites More sharing options...
SGW_SinATrA Posted March 21, 2017 Share Posted March 21, 2017 I just can't see how Corsair can give replies like this when I have proved that all you need to do to fix this is use a later CPUID SDK (cpuidsdk.dll). I initially proved this for CL 4.3.0.154 (http://forum.corsair.com/forums/showthread.php?p=890593) and then again for CL 4.5.0.55 (http://forum.corsair.com/forums/showthread.php?p=891269). Going further back to around 05-Aug-2016 I intimated in http://forum.corsair.com/forums/showthread.php?p=864155 that I had also done this to address the issue with CL4 failing to report my DIMMs. I did not clearly spell it out at the time as I felt I should give the CL4 developers the benefit of the doubt, but now there is no reasonable doubt and they are not up to the job. OK I would not expect the support guys to know how CL4 works, but given I first specified this on 01-Feb-2017 (http://forum.corsair.com/forums/showthread.php?p=889526) by now the developers should have got their act together and done something given I proved this on 09-Feb-2017 (http://forum.corsair.com/forums/showthread.php?p=890593) for such as answer to be given is rather poor. I suggest all users that have this issue log a call via https://corsair.secure.force.com/home/home.jsp pointing them at this post and ask for a 1.1.5.5 or later cpuidsdk.dll. Further given that Corsair knew that Kaby Lake was not supported before releasing CL 4.5.0.55 they should have fixed this and released CL 4.5.0.55 30 seconds later. OK, I know it would need to be retested, but given that my and others LED DIMMs don't work at all I have to wonder if Corsair do any rigorous testing :eek:. I've tried to switch the cpuidsdk.dll and cpuidsdk64.dll in "C:\Program Files (x86)\CorsairLink4" with a newer version 1,1,5,8 and it's even worse. After doing this you can only see and change the LED color, change the fan and pump speed and see the liquid temperature. I switched it back now and I'm waiting for an update wich doesn't seem to come anytime soon. Link to comment Share on other sites More sharing options...
red-ray Posted March 21, 2017 Share Posted March 21, 2017 I've tried to switch the cpuidsdk.dll and cpuidsdk64.dll in "C:\Program Files (x86)\CorsairLink4" with a newer version 1,1,5,8 and it's even worse. After doing this you can only see and change the LED color, change the fan and pump speed and see the liquid temperature. I switched it back now and I'm waiting for an update wich doesn't seem to come anytime soon. Where did you get 1.1.5.8 from? Link to comment Share on other sites More sharing options...
SGW_SinATrA Posted March 21, 2017 Share Posted March 21, 2017 Where did you get 1.1.5.8 from? I've extracted the files from NZXT software... :D: Link to comment Share on other sites More sharing options...
red-ray Posted March 21, 2017 Share Posted March 21, 2017 I've extracted the files from NZXT software... :D: :rofl: That's not the Corsair cpuidsdk.dll so won't work. Had this not been the case I would have specified doing this a long time ago :laughcry:. I guess you also failed to notice CL 4.6.0.85 has been released and the Kaby Lake support is improved as it comes with the 1.1.5.4 .dll. Link to comment Share on other sites More sharing options...
SGW_SinATrA Posted March 21, 2017 Share Posted March 21, 2017 :rofl: That's not the Corsair cpuidsdk.dll so won't work. Had this not been the case I would have specified doing this a long time ago :laughcry:. I guess you also failed to notice CL 4.6.0.85 has been released and the Kaby Lake support is improved as it comes with the 1.1.5.4 .dll. For real? You are right, I've just checked for an update 30 minutes ago and there was no update, but now it is... Are you a god or something? lol Link to comment Share on other sites More sharing options...
red-ray Posted March 21, 2017 Share Posted March 21, 2017 For real? You are right, I've just checked for an update 30 minutes ago and there was no update, but now it is... Are you a god or something? lol It's been there since at least 20-Mar-2017 @ 22:54 I just noticed Corsair-LINK-Installer-v4.6.0.86.zip contains Corsair-LINK-Installer-v4.6.0.86.zip which contains Corsair LINK Installer v4.6.0.86.exe, this is silly :rofl:. Link to comment Share on other sites More sharing options...
SGW_SinATrA Posted March 21, 2017 Share Posted March 21, 2017 It's been there since at least 20-Mar-2017 @ 22:54 Interesting, I just got the update... But now it doesn't matter anymore because it's working! :biggrin: Link to comment Share on other sites More sharing options...
Reinvented Posted March 22, 2017 Share Posted March 22, 2017 I am glad that they finally got Kaby Lake supported...now it's time for Ryzen. One thing I am curious about is, how come there's no option to manually input fan speed rpm values for a custom fan curve? Or is it not supported anymore? I absolutely hate having to drag a dot/slider, because it doesn't go where exactly I want it. Link to comment Share on other sites More sharing options...
bounty44 Posted March 24, 2017 Share Posted March 24, 2017 How are you guys controlling fan speed with the latest version of Link? Once I finally got my h115i to be detected by the latest version after trouble shooting, now the fan noise is unbearable whenever a core spikes above room temperature. The h115i keeps rapid firing the fans every 15-30 seconds and it sounds like a leaf blower in my office. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.