The Corsair User Forums

The Corsair User Forums (https://forum.corsair.com/forums/index.php)
-   Corsair Link (https://forum.corsair.com/forums/forumdisplay.php?f=209)
-   -   Discuss Link v4.3.0.154 here (https://forum.corsair.com/forums/showthread.php?t=162184)

Technobeard 09-16-2016 06:51 PM

Discuss Link v4.3.0.154 here
 
This will be the official discussion thread for Link v4.3.0.154.

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.3.0.154, 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.

Quote:

09/14/2016 - Corsair Link Software Update Version 4.3.0.154

Changelog:
  • Added option copy settings between similar devices (One fan to another fan, LED Lighting, etc.)
  • Option for application now to update automatically added
  • Added custom curve option for PSU Fans
  • AXi Series PSU show more accurate power values at lower loads
  • Added BETA support for Vengeance LED memory modules. Z170 Platforms ONLY
    • Change from Default lighting (Pulsing) to static
    • When “static” is selected brightness can be configured
    • Brightness allows the dimming of the LED on the memory modules, including turning the LED off completely
  • Now graph window is able to remain open after minimizing main window
  • Add new skin without hex pattern background


drminer 09-16-2016 07:10 PM

I am running Windows 10 Pro (v1607, x64). I tried v4.3.0.154. It detected my Intel SSD, which the previous version did not. That was nice! Unfortunately, the Corsair Link 4 service crashes upon shutdown. It also crashes when the computer enters sleep mode. Also, most of my previous configuration settings did not carry over. I have reverted back to the previous version for now. The sleep mode issue worries me.

Astral85 09-16-2016 08:45 PM

I have a quick question on upgrading/installing v4.3.0.154. At what point am I able to do an update rather than doing a full install? CL4 4.2 notified me about the update but sent me off to download the file rather than offering an upgrade option...

Since I now have the 4.3 install package should I uninstall CL4 4.2 first or just run the new package over the top?

bwrin 09-16-2016 10:38 PM

New to the forum.

I installed the update and I'm not sure what's happening. Fan speeds are all over the place, not responding to changes in profiles. The fan are spin way faster than they ever have, very noisey. No overheating or anything. Also, the Corsair logo on the pump went from white to red.

Landerx74 09-16-2016 11:00 PM

I am having the same issue where it will crash when my PC goes into sleep mode (or coming back from sleep mode). It also crashes when I reboot my PC. I am reverting back to the previous build until this is fixed. Hate seeing all those errors.

Croxy 09-17-2016 12:34 AM

Hi folks... I tried running the upgrade several times and received the following error...
"Error 1923 (0x783: Service 'Corsair Link 4' (CLink4Service) could not be installed..."

I had to uninstall the previous version before installing the update in order to get this to work.

Previous version was v4.2.4.25

Let me know if I can help with any other info.

Cheers
Croxy

red-ray 09-17-2016 04:14 AM

The interlocking semantics are still incorrect
 
The interlocking semantics are still incorrect and given I reported this on 09-Aug-2016 why? I also e-mailed the product manager who did not even reply to my e-mail. I suspect it's a one line change and can be tested using SIV 5.12 which typically reports the issue in < 2 seconds.

The CPUID SDK that comes with CL 4.3.0.154 is ancient and as a result my DIMMs and NVMe Disks still don't get reported. Why was such an old CPUID SDK released?

No fix for http://forum.corsair.com/forums/showthread.php?p=854759 is pathetic and as I specified before to fix -ve X and fail to fix -ve Y is incompetent!

How do I download new firmware into my CL Minis + H100i + H110iGT?

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. http://forum.corsair.com/forums/showthread.php?t=134621 - Commander Mini will not control fans based on temp sensors
  2. http://forum.corsair.com/forums/showthread.php?p=757703 - Commander Mini + H100i + H80i fan mode register is not returned correctly.
  3. http://forum.corsair.com/forums/showthread.php?t=137364 - Commander Mini + RGB LEDs - Blinking Issue.
  4. http://forum.corsair.com/forums/showthread.php?p=754023 - 10,000 RPM Fans #1 - Corsair suspect it's a firmware bug of 16-Jan-2015.
  5. http://forum.corsair.com/forums/showthread.php?p=709734 - H100i + H80i incorrect colour if you use zero, use 255,1,1 rather than 255,0,0.
  6. http://forum.corsair.com/forums/showthread.php?p=855427 - H100i + H80i you can't use 1,1,1 rather than 0,0,0 as this is not black.
  7. http://forum.corsair.com/forums/showthread.php?p=837226 - CLCC support for 0% PWM or 0 RPM to stop the fans.
Some fixes appear to get promised, but then never seem to be released.
Quote:

Originally Posted by Corsair Dustin (Post 757679)
This is a known issue with a fix coming.

This was posted over 17 months ago on 02-Feb-2015 so I would have expected it to be fixed by now. On what date is the fix expected? On 03-Feb-2015 Corsair stated:

Quote:

Originally Posted by Corsair Dustin (Post 757857)
I believe it requires a firmware update to be corrected. It should be in the next Corsair Link drop, or the one after.

There have been at least 8 CL drops since then :(:.

Quote:

Originally Posted by Corsair Dustin (Post 739747)
So just so you guys know, we're aware of this bug, but because of the issues we've seen with H100i/H80i and the current version of C-Link, this has been backburnered to get more pressing problems fixed.

Posted on 03-Nov-2014, over 22 months ago.

Quote:

Originally Posted by Technobeard (Post 871629)
If you'd like to report a bug, please respond to this thread.

I have done this for all the CL4 releases and Corsair have not responded to most of these posts. Why is this and why should I bother to report issues?

Here is an itemised list of issues which Corsair failed to respond to or address in a timely manor.
  1. http://forum.corsair.com/forums/showthread.php?p=864149 - CL 4.2.4.25 issues
  2. http://forum.corsair.com/forums/showthread.php?p=851701 - CL 4.2.3.41 issues
  3. http://forum.corsair.com/forums/showthread.php?p=844974 - CL 4.2.2.27 issues - How do I change the TCP port
  4. http://forum.corsair.com/forums/showthread.php?p=841278 - CL 4.2.1.42 issues
  5. http://forum.corsair.com/forums/showthread.php?p=833499 - CL 4.2.0.162 issues
  6. http://forum.corsair.com/forums/showthread.php?p=833532 - CL asking for a reboot when it should not
  7. http://forum.corsair.com/forums/showthread.php?p=837724 - CL4 using a massive amount of TCP transfers
  8. http://forum.corsair.com/forums/showthread.php?p=833695 - Silly driver package name
  9. http://forum.corsair.com/forums/showthread.php?p=833699 - Issues with > 32 CPUs
  10. http://forum.corsair.com/forums/showthread.php?p=834459 - CL4 does not support CSMI RAID
  11. http://forum.corsair.com/forums/showthread.php?p=836506 - CL4 does not support EC Sensors
  12. http://forum.corsair.com/forums/showthread.php?p=836736 - NVMe Disks are not Reported
  13. http://forum.corsair.com/forums/showthread.php?p=837364 - No support for the original Commander.
  14. http://forum.corsair.com/forums/showthread.php?p=845182 - BSOD caused by Corsair supplied AXi PSU/Asetek Cooler kernel mode driver
  15. http://forum.corsair.com/forums/showthread.php?p=845092 - 10,000 RPM Fans #2 - no reply
  16. http://forum.corsair.com/forums/showthread.php?p=853869 - 10,000 RPM Fans #3 - no reply
  17. http://forum.corsair.com/forums/showthread.php?p=854759 - To fix -ve X and fail to fix -ve Y is incompetent
  18. http://forum.corsair.com/forums/showthread.php?p=839550 - H100iV2 and H100iGTX have different firmware
  19. http://forum.corsair.com/forums/showthread.php?p=850509 - CL4 causing high DPC latencies.
  20. http://forum.corsair.com/forums/showthread.php?p=864164 - CL4 causing high DPC latencies after Corsair claim to have fixed it.
  21. http://forum.corsair.com/forums/showthread.php?p=837228 - CLCC support for 0% PWM or 0 RPM to stop the fans.
Note that some of the entries itemise up to 52 issues and I expect I reported other issues I could add to the list.

CL 4.5.0.55 has addressed none of these issues, see http://forum.corsair.com/forums/showthread.php?p=890711

red-ray 09-17-2016 05:37 AM

How do I stop the fan when using a PSU Custom Curve?
 
1 Attachment(s)
Quote:

Originally Posted by Technobeard (Post 871629)
Added custom curve option for PSU Fans

When using CL how do I stop the fan when using a PSU Custom Curve? I have tried to do this and suspect it's impossible. I setup as below and as you can see the AX1500i temperature is 30.5°C and the fan is still spinning.

I feel the Configure Fan should specify the device (AX1500i) that the fan is associated with and that 25% rather than 40% PWM should be the low limit. At 25% PWM my AX1500i fan happily spins at about 600 RPM.


BixTix 09-17-2016 08:13 AM

1) v4.3.0.154
2) Windows 10 64bit V1607 build 14393.187
3) corsair link crashes on shutdown and sleep mode
4)this is from the aftermath in even viewer.

Faulting application name: CorsairLink4.Service.exe, version: 4.3.0.154, time stamp: 0x57c697f6
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process ID: 0x3204
Faulting application start time: 0x01d210d9f7809319
Faulting application path: C:\Program Files (x86)\CorsairLink4\CorsairLink4.Service.exe
Faulting module path: unknown
Report ID: dc805699-f2c5-45a6-9eb2-a2b07874f446
Faulting package full name:
Faulting package-relative application ID: Faulting application name: CorsairLink4.Service.exe, version: 4.3.0.154, time stamp: 0x57c697f6
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process ID: 0x3204
Faulting application start time: 0x01d210d9f7809319
Faulting application path: C:\Program Files (x86)\CorsairLink4\CorsairLink4.Service.exe
Faulting module path: unknown
Report ID: dc805699-f2c5-45a6-9eb2-a2b07874f446
Faulting package full name:
Faulting package-relative application ID:

also .net framework error

Application: CorsairLink4.Service.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
at CPUIDSDK.Close()
at CorsairLink4.Module.Dram.DramComponent.Dispose()
at CorsairLink4.Service.Service.DevicesMonitor.Dispose()
at CorsairLink4.Service.WindowsService.Dispose(Boolean)
at System.ComponentModel.Component.Dispose()
at System.ServiceProcess.ServiceBase.Run(System.ServiceProcess.ServiceBase[])
at System.ServiceProcess.ServiceBase.Run(System.ServiceProcess.ServiceBase)
at CorsairLink4.Service.Program.Main(System.String[])

hope this is of some help
cheers
Mark

huppra 09-17-2016 10:25 AM

edit: thanks

red-ray 09-17-2016 10:55 AM

CPUZ is reporting VCORE and CL4 is VCCIN.
 
Quote:

Originally Posted by huppra (Post 871720)
1. 4.3.0.154
2. Windows 10 Pro
3. The version of Corsair link is reading my CPU Input Voltage as my CPU VCore Voltage and it gave me quite the scare. The correct voltage of 1.38 is showing in Asus Suite and in Bios.
4. CPU: Intel I7-6850k

They are different voltages and CL4 reports an incorrect name.

CPUZ is reporting VCORE and CL4 is VCCIN.

Weedbreather 09-17-2016 11:20 AM

1. 4.3.0.154
2. Windows 10 Pro
3.Custom profile based on cpu temp still only works while link is running on my h80i, this is an ongoing issue with the risk of frying something!!!
Please fix this issue ASAP!

huppra 09-17-2016 12:59 PM

Quote:

Originally Posted by red-ray (Post 871725)
They are different voltages and CL4 reports an incorrect name.

CPUZ is reporting VCORE and CL4 is VCCIN.

Thanks. Yeah the naming of VCPU had confused me, then when the it matched the rough value of my cpu input voltage it made more sense.

Qqu 09-17-2016 01:44 PM

Are there plans to support controlling Vengeance LED on x99 platforms?

doudar 09-18-2016 01:34 AM

does this version prevent your HDD from spinning down during idle times like the previous one?

is yes is there a way around it or i have to stick to v4.2.2.27 ?


All times are GMT -4. The time now is 11:43 PM.

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