Jump to content
Corsair Community

Corsair Link & X399


Undermoose

Recommended Posts

Hello,

 

Corsair Tech Support just told me X399 isn't fully supported yet for Corsair Link. Is this true? When will it be supported?

 

I'm having lots of issues with Corsair Link detecting fans properly, video cards properly, etc. Additionally, Corsair Link is making my system LOCK UP / FREEZE / CRASH. Remove Corsair Link & system is 100 percent stable.

 

I own: Corsair AX1500i PSU, Corsair 110i GTX Cooler, & Corsair Vengeance RGB DDR4-3200 CL16 ram.

 

Would love Corsair Link to WORK.

 

This isn't specific to the current version of Corsair Link, rather Corsair Link general compatibility. That's why I posted here.

 

Thank you.

Link to comment
Share on other sites

  • Corsair Employees

X399 should be supported in Link, that was introduced a couple of versions ago.

 

Can you give me the system configuration so I can help troubleshoot the crashing? Please note that motherboard vendor specific software can conflict with Link and can result in these types of locks/crashes.

Link to comment
Share on other sites

Gigabyte X399 Aorus Gaming 7.

Full compliment of Gigabyte software loaded, including SIV.

I do use AIDA64, but it's not loading at boot, just when I want to review info.

 

Corsair Link isn't seeing all the fans connected to the motherboard, and it's seeing 3 video cards in a dual card system. Gigabyte AMD VEGA64 x2.

 

I've tried unloading SIV, then uninstalling Corsair Link and removing remnant folders in program files, etc, then reinstalling it without SIV. No help.

 

Pretty much straight up unstable system with CL installed, no lock ups or crashes after I removed it.

 

Other software includes Logitech G, Sophos anti-virus, Razer Mouse software.

 

 

 

Thanks for the reply.

Link to comment
Share on other sites

  • Corsair Employees

Okay, so we were able to do at least a little testing. Incidentally we're also seeing the AMD multiple GPU reporting bug (we plugged in a single Vega 64 and saw two), so that's logged and will get fixed.

 

We found the system would bluescreen almost immediately with the launch BIOS. On F3g, though, with an RMi and Vengeance RGB installed, the system stayed stable through some runs of Prime95.

 

We'll keep digging and see if we can't find where the incompatibility lies. Thank you for your patience.

Link to comment
Share on other sites

Was Corsair Link able to see all the fans connected to the motherboard?

 

I have:

System3 connected to a 3pin rear fan

System4 connected to a 4 pin bottom case fan

Pump/SysFan5&6 connected to 3 pin fans (front of case)

Motherboard set to Auto for PWM or Voltage

I don't have CL installed at the moment, but recall seeing only 2 of the 4 fans.

 

Corsair H110i GTX CPU fan isn't an issue (though it only seemed to see 1 of the 2 and believe that's normal?).

 

Progress, thank you!

Link to comment
Share on other sites

Hello,

 

I have same problem with corsair software,

 

my spec are:

gigabyte x370 gaming 5

corsair vengeance lpx ddr4 3200

 

for example in cpuz in the SPD window I do not read anything, but in the window I have all the information. This problem slows to open hwinfo64 (to open the window with the sensors it takes about 1 minute), and also problems with RGB applications (I have the Mobo gigabyte then the RGB fusion app).

 

So when I disable the problem it disappears and everything works fine.

 

I thinks this is software conflicts.

 

Can fix it?

Link to comment
Share on other sites

Hello,

 

I have same problem with corsair software,

 

my spec are:

gigabyte x370 gaming 5

corsair vengeance lpx ddr4 3200

 

for example in cpuz in the SPD window I do not read anything, but in the window I have all the information. This problem slows to open hwinfo64 (to open the window with the sensors it takes about 1 minute), and also problems with RGB applications (I have the Mobo gigabyte then the RGB fusion app).

 

So when I disable the problem it disappears and everything works fine.

 

I thinks this is software conflicts.

 

Can fix it?

Make sure that HWInfo is not monitoring the Corsair Link devices. This includes the Commander Pro, coolers, etc ... any Corsair device that it directly controlled from Corsair Link (not just monitored). In HWInfo, you can do this by right-clicking on the values and clicking "Disable Monitoring"

Link to comment
Share on other sites

I am having issues too with the most recent version and my Asrock X399 Gaming Professional.

 

With the most recent version, I am having the issue that I thought was resolved about the fans not running at the correct speed. In fact, they are not even detected at all in Link. The software controls them, but it displays 0 RPM. The pump speed and temp is correctly displayed.

 

Sometimes when I boot, the software seems to be fine, and the fans will hold the desired profile fan speed, and increase as necessary when the temp rises. However after the computer sleeps and then wakes back up the fans go in to oscillating mode where they speed up and down.. it's annoying as heck. I have to restart the computer at that point.

Link to comment
Share on other sites

Make sure that HWInfo is not monitoring the Corsair Link devices. This includes the Commander Pro, coolers, etc ... any Corsair device that it directly controlled from Corsair Link (not just monitored). In HWInfo, you can do this by right-clicking on the values and clicking "Disable Monitoring"

 

I tried to disable corsair ram, corsair h80i v2 in hwinfo, hwinfo always puts us open for about 1 minute

Link to comment
Share on other sites

  • Corsair Employees

This is a known bug with sleep mode. It's something we're working on but slow going.

 

I am having issues too with the most recent version and my Asrock X399 Gaming Professional.

 

With the most recent version, I am having the issue that I thought was resolved about the fans not running at the correct speed. In fact, they are not even detected at all in Link. The software controls them, but it displays 0 RPM. The pump speed and temp is correctly displayed.

 

Sometimes when I boot, the software seems to be fine, and the fans will hold the desired profile fan speed, and increase as necessary when the temp rises. However after the computer sleeps and then wakes back up the fans go in to oscillating mode where they speed up and down.. it's annoying as heck. I have to restart the computer at that point.

Link to comment
Share on other sites

This is a known bug with sleep mode. It's something we're working on but slow going.

 

I've found that going into Device Manager and disabling the device for the pump and then re-enabling it (after waking back up) gets things working again. But ... that's also on a z270, not an x399 so I don't know if it's directly applicable.

It smells like a driver issue to me ... at least on my system.

Link to comment
Share on other sites

Corsair 4.9.3.25 installed.

 

Still sees 3 Video cards in my Dual VEGA64 rig, however at least all three fans are running =P LOL.

 

It does see all 3 of my motherboard's connected case fans now :) (Gigabyte Aorus X399 Gaming 7)

There's a bit of a problem confirming this new CL version fixed its detection though. I moved fan headers connections around due to a new case, so it's possible the two fan headers at the bottom of the motherboard weren't being detected properly. The old case had 4 fans, and only saw 2, and 2 were connected to headers not being used now. Currently it detects all three case fans though.

Link to comment
Share on other sites

  • Corsair Employees

After the problems you've had, I'll take what I can get. We're aware of the extra AMD card problem and I don't know when that will be fixed, probably not for at least another month since it's cosmetic and we're focusing on product support and functionality bug fixes.

 

Corsair 4.9.3.25 installed.

 

Still sees 3 Video cards in my Dual VEGA64 rig, however at least all three fans are running =P LOL.

 

It does see all 3 of my motherboard's connected case fans now :) (Gigabyte Aorus X399 Gaming 7)

There's a bit of a problem confirming this new CL version fixed its detection though. I moved fan headers connections around due to a new case, so it's possible the two fan headers at the bottom of the motherboard weren't being detected properly. The old case had 4 fans, and only saw 2, and 2 were connected to headers not being used now. Currently it detects all three case fans though.

Link to comment
Share on other sites

Corsair Link 4.9.3.25

 

System has started locking up:

 

About 8 minutes prior the lock up I see this in the application events:

 

Log Name: Application

Source: Application Error

Date: 12/16/2017 5:15:13 PM

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: PC

Description:

Faulting application name: CorsairLink4.exe, version: 4.9.3.25, time stamp: 0x5a1837ff

Faulting module name: KERNELBASE.dll, version: 10.0.16299.15, time stamp: 0x2cd1ce3d

Exception code: 0xe0434352

Fault offset: 0x001008b2

Faulting process id: 0x3478

Faulting application start time: 0x01d376a2e84f807a

Faulting application path: C:\Program Files (x86)\CorsairLink4\CorsairLink4.exe

Faulting module path: C:\Windows\System32\KERNELBASE.dll

Report Id: 9f01abf8-0bb3-4b18-932c-f92d36eb8d05

Faulting package full name:

Faulting package-relative application ID:

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Application Error" />

<EventID Qualifiers="0">1000</EventID>

<Level>2</Level>

<Task>100</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2017-12-16T22:15:13.165689100Z" />

<EventRecordID>99005</EventRecordID>

<Channel>Application</Channel>

<Computer>PC</Computer>

<Security />

</System>

<EventData>

<Data>CorsairLink4.exe</Data>

<Data>4.9.3.25</Data>

<Data>5a1837ff</Data>

<Data>KERNELBASE.dll</Data>

<Data>10.0.16299.15</Data>

<Data>2cd1ce3d</Data>

<Data>e0434352</Data>

<Data>001008b2</Data>

<Data>3478</Data>

<Data>01d376a2e84f807a</Data>

<Data>C:\Program Files (x86)\CorsairLink4\CorsairLink4.exe</Data>

<Data>C:\Windows\System32\KERNELBASE.dll</Data>

<Data>9f01abf8-0bb3-4b18-932c-f92d36eb8d05</Data>

<Data>

</Data>

<Data>

</Data>

</EventData>

</Event>

 

Log Name: Application

Source: .NET Runtime

Date: 12/16/2017 5:15:12 PM

Event ID: 1026

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: PC

Description:

Application: CorsairLink4.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.OutOfMemoryException

at CorsairLink4.Common.Shared.Logger.LoggerAdapter.Error[[system.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.__Canon)

at CorsairLink4.Win7.App.OnTaskSchedulerUnobservedTaskException(System.Object, System.Threading.Tasks.UnobservedTaskExceptionEventArgs)

at System.Threading.Tasks.TaskScheduler.PublishUnobservedTaskException(System.Object, System.Threading.Tasks.UnobservedTaskExceptionEventArgs)

at System.Threading.Tasks.TaskExceptionHolder.Finalize()

 

 

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name=".NET Runtime" />

<EventID Qualifiers="0">1026</EventID>

<Level>2</Level>

<Task>0</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2017-12-16T22:15:12.753622400Z" />

<EventRecordID>99004</EventRecordID>

<Channel>Application</Channel>

<Computer>PC</Computer>

<Security />

</System>

<EventData>

<Data>Application: CorsairLink4.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.OutOfMemoryException

at CorsairLink4.Common.Shared.Logger.LoggerAdapter.Error[[system.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.__Canon)

at CorsairLink4.Win7.App.OnTaskSchedulerUnobservedTaskException(System.Object, System.Threading.Tasks.UnobservedTaskExceptionEventArgs)

at System.Threading.Tasks.TaskScheduler.PublishUnobservedTaskException(System.Object, System.Threading.Tasks.UnobservedTaskExceptionEventArgs)

at System.Threading.Tasks.TaskExceptionHolder.Finalize()

 

</Data>

</EventData>

</Event>

 

 

About 1.5 hours prior I this in the system events

 

Log Name: System

Source: Service Control Manager

Date: 12/16/2017 3:51:31 PM

Event ID: 7032

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: PC

Description:

The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the Corsair LINK 4 service, but this action failed with the following error:

An instance of the service is already running.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />

<EventID Qualifiers="49152">7032</EventID>

<Version>0</Version>

<Level>2</Level>

<Task>0</Task>

<Opcode>0</Opcode>

<Keywords>0x8080000000000000</Keywords>

<TimeCreated SystemTime="2017-12-16T20:51:31.653447800Z" />

<EventRecordID>19587</EventRecordID>

<Correlation />

<Execution ProcessID="220" ThreadID="1768" />

<Channel>System</Channel>

<Computer>PC</Computer>

<Security />

</System>

<EventData>

<Data Name="param1">1</Data>

<Data Name="param2">Restart the service</Data>

<Data Name="param3">Corsair LINK 4</Data>

<Data Name="param4">%%1056</Data>

</EventData>

</Event>

 

Log Name: System

Source: Service Control Manager

Date: 12/16/2017 3:50:31 PM

Event ID: 7031

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: PC

Description:

The Corsair LINK 4 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />

<EventID Qualifiers="49152">7031</EventID>

<Version>0</Version>

<Level>2</Level>

<Task>0</Task>

<Opcode>0</Opcode>

<Keywords>0x8080000000000000</Keywords>

<TimeCreated SystemTime="2017-12-16T20:50:31.652954800Z" />

<EventRecordID>19586</EventRecordID>

<Correlation />

<Execution ProcessID="220" ThreadID="1768" />

<Channel>System</Channel>

<Computer>PC</Computer>

<Security />

</System>

<EventData>

<Data Name="param1">Corsair LINK 4</Data>

<Data Name="param2">1</Data>

<Data Name="param3">60000</Data>

<Data Name="param4">1</Data>

<Data Name="param5">Restart the service</Data>

<Binary>43004C0069006E006B00340053006500720076006900630065000000</Binary>

</EventData>

</Event>

 

 

The lock ups have been happening regularly and require either power or reset button.

 

I've removed Corsair Link to see if they're directly related to the lock ups. If I don't experience continued lock ups I'll have to assume CL is part of the root cause.

 

I'll report back.

Link to comment
Share on other sites

For the first, it's an exception in the exception handler; it looks like it's happening when it's trying to log.

Can you look on C:\ProgramData\CLink4 for the log files, zip them and post? Also, if they are big, go ahead and delete them.

For the second one (with the service crash), can you look to see if there is an event in the Application Log from the .NET Runtime around the same time? This should have a stack trace.

Link to comment
Share on other sites

I turned off logging. The last logs I have are dated 11/19.

 

I don't see anything else for .NET Runtime in the Application Event viewer, but right after the crash I see an info:

 

Log Name: Application

Source: Windows Error Reporting

Date: 12/16/2017 5:15:15 PM

Event ID: 1001

Task Category: None

Level: Information

Keywords: Classic

User: N/A

Computer: PC

Description:

Fault bucket 1572228982622385932, type 1

Event Name: APPCRASH

Response: Not available

Cab Id: 0

 

Problem signature:

P1: CorsairLink4.exe

P2: 4.9.3.25

P3: 5a1837ff

P4: KERNELBASE.dll

P5: 10.0.16299.15

P6: 2cd1ce3d

P7: e0434352

P8: 001008b2

P9:

P10:

 

Attached files:

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREF68.tmp.mdmp

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF332.tmp.WERInternalMetadata.xml

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF32F.tmp.csv

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF35F.tmp.txt

 

These files may be available here:

C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_CorsairLink4.exe_71dd3137d412a625ae94d8fca312892db58ad5d_76857c7b_3fecf802

 

Analysis symbol:

Rechecking for solution: 0

Report Id: 9f01abf8-0bb3-4b18-932c-f92d36eb8d05

Report Status: 268435456

Hashed bucket: 4a68062b7f2eb55685d1adedfec7f70c

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Windows Error Reporting" />

<EventID Qualifiers="0">1001</EventID>

<Level>4</Level>

<Task>0</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2017-12-16T22:15:15.613012500Z" />

<EventRecordID>99006</EventRecordID>

<Channel>Application</Channel>

<Computer>PC</Computer>

<Security />

</System>

<EventData>

<Data>1572228982622385932</Data>

<Data>1</Data>

<Data>APPCRASH</Data>

<Data>Not available</Data>

<Data>0</Data>

<Data>CorsairLink4.exe</Data>

<Data>4.9.3.25</Data>

<Data>5a1837ff</Data>

<Data>KERNELBASE.dll</Data>

<Data>10.0.16299.15</Data>

<Data>2cd1ce3d</Data>

<Data>e0434352</Data>

<Data>001008b2</Data>

<Data>

</Data>

<Data>

</Data>

<Data>

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREF68.tmp.mdmp

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF332.tmp.WERInternalMetadata.xml

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF32F.tmp.csv

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF35F.tmp.txt</Data>

<Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_CorsairLink4.exe_71dd3137d412a625ae94d8fca312892db58ad5d_76857c7b_3fecf802</Data>

<Data>

</Data>

<Data>0</Data>

<Data>9f01abf8-0bb3-4b18-932c-f92d36eb8d05</Data>

<Data>268435456</Data>

<Data>4a68062b7f2eb55685d1adedfec7f70c</Data>

</EventData>

</Event>

Link to comment
Share on other sites

Even with logging turned off, there should still be error logs. And they should have some indication of what what wrong here.

Unfortunately, I don't think we'll be able to fix this here ... although we might be able to diagnose it to get a fix. A support ticket might also provide more insight. :(:

Link to comment
Share on other sites

  • Corsair Employees

Okay, I've put in a formal bug request with our team. We'll see what we can do.

 

The bad news is we're right on the edge of the company's annual holiday shutdown. So the last day we're open is Friday. I don't have high hopes of seeing this addressed before the new year. :(

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...