The Corsair User Forums  

Go Back   The Corsair User Forums > Corsair Product Discussion > Corsair Link


Closed Thread
Thread Tools Search this Thread Rate Thread Display Modes
Old 05-16-2017, 05:10 PM
Technobeard's Avatar
Technobeard Technobeard is offline
Bearded Corsair Employee
Join Date: Oct 2012
Posts: 4,292
POST ID # = 903464
Technobeard Reputation: 68
Default Discuss Link v4.7.0.77 here

This will be the official discussion thread for Link v4.7.0.77.

If you'd like to report a bug, please respond to this thread in this format:
  1. Version of your Link software. NOTE: If you're not using v4.7.0.77, please install it and see if the bug has been fixed.
  2. What version of Windows you're using.
  3. Summary - One line / sentence explaining the issue
  4. Detailed description of the issue - This part can be as long as you want. It should be detailed enough so that we can clearly identify the issue and attempt to replicate it.
  5. Attach photos of the issue to the post that help #4.

05/16/2017 - Corsair Link Software Update Version v4.7.0.77

  • New CPUID SDK backend update for AMD Ryzen support
    • Ryzen support for CPU/MB information
    • Ryzen support for LED DRAM control (Both RGB and Single Color)
  • Added additional HD fan effects to Lighting Node PRO (Sequential, Marquee, Strobing/Blink, Visor)
    • Included in Firmware update for Lighting Node PRO
  • Added Rainbow effect for SP fans on Lighting Node PRO
    • Included in Firmware update for Lighting Node PRO
  • Addressed LED DRAM lighting control for 4-slot X99 systems
  • Addressed a specific instance with Lighting Node PRO and some HD Series fans being unresponsive after firmware update
    • Included in Firmware update for Lighting Node PRO

Last edited by Technobeard; 05-17-2017 at 01:11 AM.

Old 05-16-2017, 05:28 PM
red-ray red-ray is offline
red-ray's PC Specs
Join Date: May 2014
Location: England (GMT+1)
Posts: 7,152
POST ID # = 903472
red-ray Reputation: 81
Thumbs down PCH/ICH SMBus locking totally broken, no X79 MB + CPUs and LNP firmware update fails

  1. With CL the PCH/ICH SMBus interlocking is totally broken .
    1. Below you can see only five of the six DIMMs were reported and one of the names was misread.
    2. SIV also detected the ICH10 SMBus controller registers had been changed when it was holding the Global\Access_SMBUS.HTP.Method named mutex so needed to do retries.
    3. The issue is far more likely to happen on systems with have DIMMs with MTS as other utilities (AIDA64+HWiNFO+SIV) are likely to be reading the SMBus of a regular basis.
    4. I am at a loss as to why Corsair failed to find this issue before CL was released .
    5. As I found the same issues with CPUZ + HWM I contacted the CPUID SDK developers and worked with them to fix the bugs .
    6. Corsair, you need to ask for the fixed CPUID SDK and should make it available as a download .
    7. I also just noticed there two DIMMs called Temp #1 which is somewhat inappropriate.
    8. After working with the CPUID SDK developers on Tue 20-Jun-2017 I tested a cpuidsdk.dll and using this CL finally reported my system as it should, well almost, staring from Core #2 is rather poor and shows the Corsair testing is .
    9. Corsair would be wise to ensure the next CL4 release uses the cpuidsdk.dll or later and I have made them aware of my view.
  2. CL no longer lists my Motherboard and CPUs. Below are the [Home] tabs from CL + CL that clearly show this regression.
  3. The LNP 0.3.72 firmware update got stuck at 35%, see for how I recovered from this.
  4. CL also failed to display the CPUs and Disks on my Dell 490 when CL did, see
  5. The memory title still also flashes between Hyundai Electronics and Qimonda.
  6. On my HP DL580 G5 CL also failed to report the motherboard and CPUs, further none of the 32 x FB-DIMMs were reported when they used to be, yet another regression . HWM reports them, so it can't be down to the CPUID SDK.
  7. No fix for is rather poor and as I specified before to fix -ve X and fail to fix -ve Y is a major oversight! When I move the CL window to screen 3 as soon as I release the mouse it jumps back to screen two .
  8. Again rather the DRAM CL4 should display the RAM type, DDR4/DDR3/etc. and it's also silly to display 16.0 as the latency and the .0 should not be there except for DDR1. The number of channels and operating mode should also be displayed, Single/Dual/Triple/Quad and Dual Xeon system has 8 Memory Buffers/Channels.
  9. Yet again CL4 should display it's version number as I find many members fail to specify this or state "latest version" when posting.
  10. Yet again I further feel CL4 should use meaningful names rather than the Temp #1 form it currently uses, same for the fan names.
  11. Yet again reporting the same disk temperature twice is silly and causes confusion for some, see the 2nd #2 in
  12. Yet again can control the H110i + H110iGT pump speed using a Custom Curve be added to CL4?
How do I download new firmware into my CL Minis + H100i + H110iGT?
  1. - I suspect the CL-9011110-WW will replace the CL Mini, does this mean the CL Mini firmware bugs will never be fixed?
Have any of the following firmware bugs been addressed some of which have now been outstanding since 20-Nov-2014? If not on what date are they scheduled to be addressed please?
  1. - Commander Mini will not control fans based on temp sensors
  2. - Commander Mini + H100i + H80i fan mode register is not returned correctly.
  3. - Commander Mini + RGB LEDs - Blinking Issue.
  4. - 10,000 RPM Fans #1 - Corsair suspect it's a firmware bug of 16-Jan-2015.
  5. - H100i + H80i incorrect colour if you use zero, use 255,1,1 rather than 255,0,0.
  6. - H100i + H80i you can't use 1,1,1 rather than 0,0,0 as this is not black.
  7. - CLCC support for 0% PWM or 0 RPM to stop the fans.
  8. - H110i + H110iGT Custom mode does not work for the pump.
Here is an itemised list of issues which Corsair failed to respond to or address in a timely manor.
  1. - CL issues.
  2. - CL issues
  3. - CL issues
  4. - CL issues
  5. - CL issues
  6. - CL issues - How do I change the TCP port
  7. - CL issues
  8. - CL issues
  9. - CL asking for a reboot when it should not
  10. - CL4 using a massive amount of TCP transfers
  11. - Silly driver package name
  12. - Issues with > 32 CPUs
  13. - CL4 does not support CSMI RAID
  14. - CL4 does not support EC Sensors
  15. - No support for the original Commander.
  16. - BSOD #1 caused by Corsair supplied AXi PSU/Asetek Cooler kernel mode driver
  17. - BSOD #2 caused by Corsair supplied AXi PSU/Asetek Cooler kernel mode driver
  18. - BSOD #3 caused by CL (CPUID SDK) on W10 RS2 Build 15063.
  19. - 10,000 RPM Fans #2 - no reply
  20. - 10,000 RPM Fans #3 - no reply
  21. - To fix -ve X and fail to fix -ve Y is silly
  22. - H100iV2 and H100iGTX have different firmware
  23. - CL4 causing high DPC latencies.
  24. - CL4 causing high DPC latencies after Corsair claim to have fixed it.
  25. - CLCC support for 0% PWM or 0 RPM to stop the fans.
  26. - AMD GPU fan speed and temperature information not reported.
  27. - previous releases can't be downloaded .
Note that some of the entries itemise up to 52 issues and I expect I reported other issues I could add to the list.

I feel Corsair should be posting the following as only the latest release is available via the support downloads and some members wish to revert to old versions

Attached Images
File Type: png LNP 0.3.72 Firmware Update stuck @ 35%.png (8.7 KB, 6610 views)
File Type: png REX.png (177.7 KB, 6536 views)
File Type: png RXD.png (222.2 KB, 6278 views)
File Type: png REG.png (205.7 KB, 6082 views)

Last edited by red-ray; 07-01-2017 at 09:15 AM. Reason: More issues + PCH/ICH SMBus locking broken !!!!! CPUID SDK fixed things

Old 05-16-2017, 06:11 PM
kaygib kaygib is offline
Registered User
Join Date: May 2017
Posts: 2
POST ID # = 903477
kaygib Reputation: 10

can somebody please post the new lighting node pro firmware 0.3.72 so that we can install it manually

Old 05-16-2017, 06:34 PM
Dicehunter's Avatar
Dicehunter Dicehunter is offline
I Fight For The Users
Dicehunter's PC Specs
Join Date: Aug 2014
Location: EU
Posts: 444
POST ID # = 903480
Dicehunter Reputation: 16

Just curious but by chance would this enable lighting control over the Vengeance LED non RGB memory or is it permanently stuck to slow flashing ?


Nevermind, I may be slightly blind

Ryzen support for LED DRAM control (Both RGB and Single Color)

Last edited by Dicehunter; 05-17-2017 at 07:54 AM.

Old 05-16-2017, 06:51 PM
baskura baskura is offline
Registered User
Join Date: May 2017
Posts: 2
POST ID # = 903488
baskura Reputation: 10

Still can't update my Lighting Node Pro without having to open my case, reset it and doing it manually.

It just forver gets stuck on:
Bootloader mode
Firmware flash: 0%

Really needs sorting.

Old 05-16-2017, 07:09 PM
red-ray red-ray is offline
red-ray's PC Specs
Join Date: May 2014
Location: England (GMT+1)
Posts: 7,152
POST ID # = 903491
red-ray Reputation: 81
Thumbs up LNP 0.3.72 firmware recovery

Originally Posted by kaygib View Post
can somebody please post the new lighting node pro firmware 0.3.72 so that we can install it manually
I have updated to include the 0.3.72 firmware.

Old 05-16-2017, 07:48 PM
kaygib kaygib is offline
Registered User
Join Date: May 2017
Posts: 2
POST ID # = 903506
kaygib Reputation: 10

Thanks for that. If they know there is a problem installing lnp firmware, why not just put the firmware in the download section with instructions for those who don't know how to use it? Seems odd to have to ask a forum member for this file rather than just download it using the corsair website.

Old 05-16-2017, 09:35 PM
Veliladon Veliladon is offline
Registered User
Join Date: May 2017
Posts: 3
POST ID # = 903517
Veliladon Reputation: 10

Thanks for the update. The new modes are really cool. Can't wait to see what you guys have coming next.

Old 05-17-2017, 01:56 AM
specialkone specialkone is offline
Registered User
specialkone's PC Specs
Join Date: Mar 2017
Posts: 19
POST ID # = 903542
specialkone Reputation: 10

Fans 1,3,4 are my Corsair 750D case fans. Fan 2 is my CPU fan. Corsair still can't figure out their own hardware with their software. What does that tell you?

Ever since version 4.6.086 and this version I have Link showing duplicate fans 5,6,7,8. If Corsair is unwilling or unable to fix this, could they please include the fix for the H110i pump running at lower RPM until startup in the 4.5.055 version. Then I will have no pump worries and four fans reported as it should be.

Old 05-17-2017, 04:35 AM
Zotty's Avatar
Zotty Zotty is offline
Zotty's PC Specs
Join Date: Apr 2017
Location: South Staffordshire, England, UK
Posts: 3,249
POST ID # = 903547
Zotty Reputation: 52

PERFECT!!!!! Thank you Corsair!!. just what the doctor ordered :).

1. All updated with out a hitch
2. All items present and correct in link
4.Corsair Link FOR THE WIN!!!!!! well done guys

Old 05-17-2017, 08:06 AM
unilythe unilythe is offline
Registered User
unilythe's PC Specs
Join Date: Mar 2017
Posts: 28
POST ID # = 903562
unilythe Reputation: 22

I'm done with Corsair Link products. It takes me hours every time I want to update because something always breaks

I can't update my Lighting Node Pro. The new firmware got stuck on 73% for half an hour after which I decided to cancel it.
Now it won't update at all unless I completely restart my PC, after which it gets stucks before even reaching 50%.

This means every single time I want to update the Lighting Node Pro, I need to completely open my PC case, get my Lighting Node Pro from under my PSU shroud,
which requires me to remove my watercooling reservoir, which requires me to completely drain my waterloop.

So, in order to fix Corsair's software every time it updates I need to put in hours of work just to update it.
When I put together this build I did not expect that I had to be able to reach the Lighting Node Pro physically in order to update it, because why the hell would I?. Why is a simple firmware update so damn difficult?

I'm done with this. Next time this happens, I'm not just draining my waterloop but removing all Corsair Link hardware, taking it back to the store, and replacing it.

Edit: also no matter how annoying red-ray's posts may be to Corsair (and I know they are very annoying), from the perspective of users on this sub forum it seems he's putting in more work on Crosair's products than Corsair is, yet you're completely ignoring everything he says even though he makes very good points

Last edited by unilythe; 05-17-2017 at 08:12 AM.

2 members found this post helpful.
Old 05-17-2017, 03:08 PM
flicks09 flicks09 is offline
Registered User
flicks09's PC Specs
Join Date: Mar 2017
Posts: 2
POST ID # = 903606
flicks09 Reputation: 10

Apparently I now have 10 fans. Last update it was 8 so I've miraculously gained 2 more. Thanks Corsair. /s

Old 05-17-2017, 05:07 PM
Alberello Alberello is offline
Registered User
Alberello's PC Specs
Join Date: Feb 2017
Posts: 7
POST ID # = 903631
Alberello Reputation: 10
Thumbs down All fans lost

After the upgrade to this version no fans are detected from the device "Corsair Commander Mini"!

Old 05-17-2017, 05:27 PM
Schar07 Schar07 is offline
Registered User
Schar07's PC Specs
Join Date: May 2017
Posts: 5
POST ID # = 903638
Schar07 Reputation: 10

v4.7.0.77: mobo fans are OK, i see my DDR sticks, but i do not see AX860i (connected to H80i)
v4.6.0.86, v4.5.0.55, v4.3.0.154: mobo fans give wrong readings, DDR sticks are not detected, however AX860i is seen.

Why detecting DRAM masks power supply?

To do the testing between each test i cleaned Link files, reg and devices manually.


Last edited by Schar07; 05-17-2017 at 07:38 PM.

Old 05-17-2017, 10:34 PM
Tech_guy_76 Tech_guy_76 is offline
Registered User
Tech_guy_76's PC Specs
Join Date: May 2017
Posts: 1
POST ID # = 903687
Tech_guy_76 Reputation: 10

Came across this thread and registered to throw out my feedback.

CL has been a good experience, certainly better than some competing software I have used.

I have a custom water cooled set up with much of the hardware controlled by the Corsair Commander Mini.

The bad:
1. Have had a couple of system crashes during Windows startup after adding devices to the CCM.
2. PWM pump was not getting a proper PWM signal from #1 fan header on CCM. I could control it up to approximately 70% speed but it would not run any faster, even when set to maximum speed. A fan connected to this fan header has full speed control.

The good:
1. Custom fan speed curves on all of my connected fans.
2. Properly controls fans that are connected to an 8-way PWM hub.
3. Fan speed control based on temp sensors connected to CCM works perfectly.
4. LED lighting control works perfectly with none of the blinking that I have seen reported here.

Something I would like to see is the ability to type in the desired fan speeds and temperatures. It would ease the process of creating a custom fan curve.

Closed Thread

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

All times are GMT -4. The time now is 10:13 AM.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2019, vBulletin Solutions, Inc.