New Corsairlink2 software is here 2.3.4816

[ts]

Make sure the Commander unit is on FW 2.0.6

This thread may help

http://forum.corsair.com/v3/showthread.php?t=113619

 

This solved my problems, and I can now see and control my Cooling Node. Thanks for the help! I've gone back to Link software 2.2, however, since it exerts better control over all of my fans than 2.3 seems to.

[robandcathy]

ok so I tried to downgrade to 2.1.7 to update firmware/verify I was on 2.0.6 sadly since Im on win8 I get a error that "to get cpu temps you need admin privileges" I am a admin and and it will not let me get past that. So its catch 22 canot update firmware with current version and cannot update with older version because it not compatible, this is like a mickey mouse circus. So let me guess I have to reinstall windows 7 to make 1.2.7 a outdated dashboard work then reinstall windows 8 and update again, this is ludricas at best! I tried compability mode on win8 as well with no luck. Seriously over a year in the making and its still so complicated! Not to mention if it were not for tosted providing the link to 2.0.6 I would have never found it since firmware guide by corsair does not provide links or current info!!! If tostaed got a nickel for every answer, he would make 3X what engineers at corsair make. Why does corsair not have someone giving official answers to problems? why are they taking the easy road and letting people use their free time to help others when the company has money to pay someone to do that, yes I know sometimes employees chime in but far and few between. I commend whyant and toasted for giving up their time to help others, which is a corsair obligation, that's not being met!.:evil:

[wytnyt]

when using this new software,what version should the cooling node be?

[Raven0215]

Just wanted to chime in.

 

I reinstalled my Link today finally with the new software update. I had to update my Commander to the latest firmware as nothing was showing up at first. I had just received a new commander after my previous unit was sent in for an RMA. I currently have an H100, 860I and 1 cooling node.

 

I have 3x akasa viper 140mm fans hooked up to the H100 and 5x Akasa Viper 120mm fans hooked up to the cooling node. Everything is working as it should so far so I am very happy with that. I previously had some corsair fans that I moved to another computer as they would not work properly when hooked up to the H100.

 

Also all my Hard Drives are showing up properly I have 1 corsair GT ssd and 3 Western Digital Hard drives 2 raided and 1 as a backup. I really hope the luck continues, fingers crossed.

[Raven0215]

Just a Quick Update. As Hawkeye posted above I am also getting strange Voltage fluctuation warnings from my Asus AI suite program, probably not a deal breaker but being as ASUS is one of the biggest Motherboard makers around probably something corsair should look into fixing the next go around.

[Hawkeye1]

Just a Quick Update. As Hawkeye posted above I am also getting strange Voltage fluctuation warnings from my Asus AI suite program, probably not a deal breaker but being as ASUS is one of the biggest Motherboard makers around probably something corsair should look into fixing the next go around.

Since I've removed Link from my system, the voltage fluctuations have stopped. All of the fans are adjustable to a much greater degree, including my generic 230mm fans, and every single one of them runs quieter (as in no clicking or whirring, lower speeds obtainable).

[grantyboy]

I would go with the update as sierra services was a huge issue for us all and they have removed it for something else. You have nothing to lose. Update it and let us know whats going on.

 

Removed the old software using Revo and then updated to 2.3.x.x. Everything seems to be ok although had to set up the LED manually. Updated the firmware to 1.05 as well which has reduced (but not removed) the low level humming noise that was coming from the pump.

 

So far so good but will be watching for the performance slow down issue.

 

Thank you for fixing the issues.

[Toasted]

Hi Toasted and thank you again for your reply. I had already tryed this but I tried it again to see and no they did not appear.

 

Another problem I am finding is that the background hardware monitor is often crashing on resume from Hibernate.

 

Cheers

 

R

 

Have you tried a different fan port?

What fan is it?

Is the Cooling Node on 1.2.5?

 

ok so I tried to downgrade to 2.1.7 to update firmware/verify I was on 2.0.6 sadly since Im on win8 I get a error that "to get cpu temps you need admin privileges" I am a admin and and it will not let me get past that. So its catch 22 canot update firmware with current version and cannot update with older version because it not compatible, this is like a mickey mouse circus. So let me guess I have to reinstall windows 7 to make 1.2.7 a outdated dashboard work then reinstall windows 8 and update again, this is ludricas at best! I tried compability mode on win8 as well with no luck. Seriously over a year in the making and its still so complicated! Not to mention if it were not for tosted providing the link to 2.0.6 I would have never found it since firmware guide by corsair does not provide links or current info!!! If tostaed got a nickel for every answer, he would make 3X what engineers at corsair make. Why does corsair not have someone giving official answers to problems? why are they taking the easy road and letting people use their free time to help others when the company has money to pay someone to do that, yes I know sometimes employees chime in but far and few between. I commend whyant and toasted for giving up their time to help others, which is a corsair obligation, that's not being met!.:evil:

 

Right Click>Run as admin should fix the privileges error on LINK 1.2.7.

[tyrannosaurus]

Please, can you guys take a look in your Event Viewer, if there are Link errors like mine?

 

Log Name: Application

Source: CorsairLINK2 Hardware Monitor

Date: 16-Mar-13 10:28:58 AM

Event ID: 0

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: MAXIMUS-PC

Description:

Unable to write/verify to register 231

Event Xml:

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

<System>

<Provider Name="CorsairLINK2 Hardware Monitor" />

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

<Level>2</Level>

<Task>0</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2013-03-16T09:28:58.000000000Z" />

<EventRecordID>17023</EventRecordID>

<Channel>Application</Channel>

<Computer>MAXIMUS-PC</Computer>

<Security />

</System>

<EventData>

<Data>Unable to write/verify to register 231</Data>

</EventData>

</Event>

 

 

 

Details

ID: 0

Source: CorsairLINK2 Hardware Monitor

 

We're sorry

There is no additional information about this issue in the Error and Event Log Messages or Knowledge Base databases at this time. You can use the links in the Support area to determine whether any additional information might be available elsewhere.

[robandcathy]

Right Click>Run as admin should fix the privileges error on LINK 1.2.7.

 

In windows 8 I don't have the option to run as admin for the link, either on short cut or in programs, even though all other programs allow me to do it.

[wytnyt]

Right Click>Run as admin should fix the privileges error on LINK 1.2.7.

 

In windows 8 I don't have the option to run as admin for the link, either on short cut or in programs, even though all other programs allow me to do it.

 

have you tryed removing every corsair and sierra reference from your registry beford install?

even after doing a software uninstall,theres a couple hundred references left in the reg file.

[ACP]

@hawkeye I can confirm the voltage fluctuation as well...I use intel desktop utilities and I got weird notifications saying the voltage was at 1.65 and my temps were at 95 when none of them happened...I uninstalled 2.3 and went back to 2.2 lets see what happens but I never had any problems with 2.2 on win7 64

[Zoubiey]

Late answer on your question Toasted but its CorsairLINK2 that shows up in my process list and sometimes the software just starts but isn't showing any devices like the first time I managed to start it.

[KappaRho]

Have you tried a different fan port?

What fan is it?

Is the Cooling Node on 1.2.5?

 

Hi Toasted. Sorry this is being a bother.

 

Most of the fans are the stock Corsair fans that came with the 800D case. They were working fine (most of the time but not always) with the older application but none of them seem to show up at all on the newer software. The Cooling Nodes (2 of them) are both running 1.2.5 and I have tried them on different ports. The thermal probes on the cooling nodes are working fine. Having used the new software for longer now I am seeing the Lighting node always being found but sometimes the LEDs do not work at all and sometimes they are fine. I think I need a can of SW-RAID ! Bugspray, not array :)

[Hawkeye1]

@hawkeye I can confirm the voltage fluctuation as well...I use intel desktop utilities and I got weird notifications saying the voltage was at 1.65 and my temps were at 95 when none of them happened...I uninstalled 2.3 and went back to 2.2 lets see what happens but I never had any problems with 2.2 on win7 64

Whether they're real voltage/temp fluctuations or errors caused by Link messing with the sensors, they're dangerous. That was the last straw before I uninstalled Link entirely. Used Revo Uninstaller to remove any leftover registry files and leftover files. It really has been a rollercoaster ride with this thing to get mediocre to dangerous/annoying results.

[Raven0215]

Whether they're real voltage/temp fluctuations or errors caused by Link messing with the sensors, they're dangerous. That was the last straw before I uninstalled Link entirely. Used Revo Uninstaller to remove any leftover registry files and leftover files. It really has been a rollercoaster ride with this thing to get mediocre to dangerous/annoying results.

 

Agreed,

 

I am pretty confident the errors are just being caused by some software conflict somewhere but obviously it is taking a risk if you aren't 100 percent sure. Hopefully this is something that would be a quick fix and after the weekend once corsair has a chance to see the reports of this they will get on it.

 

I am kind of surprised they haven't taken more of a proactive approach on working with some of the people on the forums with having them beta test some of the software.

[batcrave]

Please, can you guys take a look in your Event Viewer, if there are Link errors like mine?

 

Unable to write/verify to register 231

 

I've seen the register 231 event a couple times (and once I saw it complain about register 0), but I regularly get reports that it can't write/verify register 234. I've found that it (reg. 234) appears in conjunction with the OCP sliders counting down (although I'm still not sure quite why)... Unfortunately though (or maybe fortunately), I haven't seen the 231 version often enough to even guess at the cause.

 

I'll hazard a guess that it relates to something in the AX*i hardware (as the ax1200i is the only piece of Link hardware I'm running), but beyond that I'm afraid I can't be much help.

 

 

-Bats

[Hawkeye1]

Agreed,

 

I am pretty confident the errors are just being caused by some software conflict somewhere but obviously it is taking a risk if you aren't 100 percent sure. Hopefully this is something that would be a quick fix and after the weekend once corsair has a chance to see the reports of this they will get on it.

 

I am kind of surprised they haven't taken more of a proactive approach on working with some of the people on the forums with having them beta test some of the software.

Well I never signed up to be a beta tester and never was informed how just how incomplete and unrefined Link is. I didn't sign up to use my PC as a guinea pig, so Link is out until they shape up.

 

I doubt Corsair will do much about the sensor/voltage issue, at least for awhile. From what I've experienced so far with Link, they're pretty unresponsive to actual important issues.

[wytnyt]

i thought id post my finding after having installed my new h110I

the installation of the software was much smoother than any other ive used ,everything went nice and smooth.it detected 6 out of 7 hard drives and so much for wondering which hard drive is which [kudos to corsair for that]

i especially like how fast the fans spin up and down,much better than before.theres much more in depth information about hardware than before

overall for me corsair did a good job on this software update.

 

update

ok,since my last post the software has been very favorable.i especially like the emergency shutdown if a reading over heats.the email notification didnt work but im still working on that

over all a much better software for me.

[tyrannosaurus]

I've seen the register 231 event a couple times (and once I saw it complain about register 0), but I regularly get reports that it can't write/verify register 234. I've found that it (reg. 234) appears in conjunction with the OCP sliders counting down (although I'm still not sure quite why)... Unfortunately though (or maybe fortunately), I haven't seen the 231 version often enough to even guess at the cause.

 

I'll hazard a guess that it relates to something in the AX*i hardware (as the ax1200i is the only piece of Link hardware I'm running), but beyond that I'm afraid I can't be much help.

-Bats

 

Thank you, batcrave. So we're in the same boat, as my only Corsair Hardware is AX1200i as well. My H80 is disconnected, as the fans ran wild.

Maybe it's just a random error with no further consequences.

If the error is restricted to AX1200i-owners we've to be patient as this product seems to be not in the focus of Corsairs support.

I love if everything is running fine and my rig is free for gaming. This stuff makes no fun, but that for I've built my system. :sigh!:

[batcrave]

Thank you, batcrave. So we're in the same boat, as my only Corsair Hardware is AX1200i as well. My H80 is disconnected, as the fans ran wild.

Maybe it's just a random error with no further consequences.

I'm really hoping this is the case... There are quite enough issues to deal with already, without another one sneaking around.

 

In any case, I'm fairly sure the 'unable to write/verify register x' messages are all coming from Corsair's core code (rather than the new Open Hardware Monitor routines), as I'd caught them on 2.2.0 as well. So at least there's a decent chance that it originates in something one of Corsair's coders wrote, rather than something carried over from another lib, where they'd have to wait for outside help.

 

If the error is restricted to AX1200i-owners we've to be patient as this product seems to be not in the focus of Corsairs support.

I love if everything is running fine and my rig is free for gaming. This stuff makes no fun, but that for I've built my system. :sigh!:

I'm with you on that. I've had nothing but headaches with this latest build - the Corsair software is just the latest in a string of problems stretching back to New Year's, so I'm definitely ready for everything to finally work. As for where Corsair's focus is, I think I'm going to have to refrain from comment and just hope for the best... or find the time to sit down and rip apart the software, in search of some way to work around it. Any chance anyone else has spent much time poking at the guts?

 

 

-Bats

[DevilSun]

Since I've removed Link from my system, the voltage fluctuations have stopped.

My new machine at work, running Windows 8 x64 has had these ASUS voltage fluctuations from DAY ONE and have never had Corsair Link installed on that system, as it's not running Corsair cooling product. The AI suite temperature and voltage fluctuates and reads incorrectly all day, even reporting sub-zero temperatures and zero voltage at times.

[Hawkeye1]

My new machine at work, running Windows 8 x64 has had these ASUS voltage fluctuations from DAY ONE and have never had Corsair Link installed on that system, as it's not running Corsair cooling product. The AI suite temperature and voltage fluctuates and reads incorrectly all day, even reporting sub-zero temperatures and zero voltage at times.

That may be a windows 8 issue. If you check my specs, I am (as many others who seem to have this issue) running windows 7 64-bit. Before Link, I had maybe one or two Vcore fluctuations over a 12-month period since I built the PC. I chalk that up to either issues with my Corsair power supply or possibly because I have my 3930K overclocked. Asus AI suite has also been updated a number of times since my PC was built and there's been no issues update to update.

 

Once Link 2.3 was installed, I would get an alert for voltage drops on the 3.3, 5, and 12 rails and Vcore fluctuations as well as errant temperature readings that were literally impossible unless I was a mad scientist (-61C, 100C, etc from board and CPU). I also checked Speccy when AI suite told me that the board was at 100C; Speccy also said it was at 100C, so it's not an issue with AI Suite, Link is f-ing with the sensors. Ever since I uninstalled Link (I gave it about 3 days), ALL voltage and temp issues have ceased and my fans no longer buzz (mainly my Corsair AF120s). My H100 fans (SP120s) no longer run max all the time and the H100 seems to be keeping the CPU cooler as the temps have dropped a few degrees Celsius at idle.

 

These weren't issues with 2.2 for me and weren't issues before Corsair Link. I've never had an issue with the Asus AI suite; I've had non-stop issues with Link. If it's not one thing, it's another. I'm done with Link and I'm done with Corsair. Between the Link software (be honest, this is a beta at best), cracking issues of my V2000 and the vaporware 1.8 drivers, and the V1300's being absolute trash, among other smaller things, I'm done with Corsair.

 

It's one thing to try to deduce if this is a problem with something else rather than Link, it's another for all these hopeful owners (I was one as well) to be in such ridiculous denial about Link. It's crap. It's bloated, buggy, unfinished, unpolished garbage. I only wish I could get my money back.

[batcrave]

My new machine at work, running Windows 8 x64 has had these ASUS voltage fluctuations from DAY ONE and have never had Corsair Link installed on that system, as it's not running Corsair cooling product. The AI suite temperature and voltage fluctuates and reads incorrectly all day, even reporting sub-zero temperatures and zero voltage at times.

 

I've had similar trouble with AI Suite warnings on both 7 and 8, and they've been fairly consistent (well, consistently erratic) from day one - before I even upgraded from my old hec PSU (which did have voltage fluctuations, although nothing like AIS reports). It also regularly alerts me in a panic that my PCU fans have stopped, and everything's about to explode in a fiery ball if I don't do something right now. I've never been able to spot any similar readings with any other monitoring software, however - and the fans, very audibly, have not been stopping.

 

That said, Hawkeye1 may also be right in blaming Link - although, if I'm right, it's not exactly a bug like some of the other problems it's having. A lot of monitoring packages (MSI Afterburner, and maybe HWiNFO or AIDA spring to mind) have warnings about potential clashes with other software trying to access the same sensors. Usually they talk about the risk of potential lockups, but it can also result in unexpected (and meaningless) values being returned.

 

I don't know what (if anything) else you might be running to cause conflicts on your Asus machine, DevilSun (although I suppose that's a question for troubleshooting AI Suite rather than Link), but Hawkeye1 has - at the least - Link and AIS probing his hardware sensors (which sounds dirtier than it should) and possibly fighting for control of some of the fans as well. One package or another getting the occasional nonsense value wouldn't be at all surprising, and AIS seems to have something of a hair trigger for its warnings.

 

Mind you, this is something that only occurred to me today, I haven't done much of any testing or research on it (I've still got a list of other headaches to troubleshoot before I worry too much about getting rid of some spurious warning popups) - but, after seeing a few other people's symptoms, it seems to fit.

 

 

-Bats

[batcrave]

Once Link 2.3 was installed, I would get an alert for voltage drops on the 3.3, 5, and 12 rails and Vcore fluctuations as well as errant temperature readings that were literally impossible unless I was a mad scientist (-61C, 100C, etc from board and CPU). I also checked Speccy when AI suite told me that the board was at 100C; Speccy also said it was at 100C, so it's not an issue with AI Suite, Link is f-ing with the sensors.

 

I just posted my best theory (read: guess) on the issue, so I'm not going to go into that again, but this bit is interesting (read: worrying). I've seen plenty of erratic results when one monitoring suite trips over another on the same sensor - and running three separate monitoring packages could definitely increase the chances of that - but I don't recall seeing matching blips like this across multiple packages when it happens.

 

Wherever the cause actually is, it'd really be nice (read: absolutely essential) for the Link software to allow for disabling of unneeded sensors. For those of us running only AXi PSUs, that could well mean everything outside of the unit itself. Being able to use advertised control features on a PSU shouldn't preclude (or, really, have any impact at all on) the use of other monitors for unrelated hardware.

 

These weren't issues with 2.2 for me and weren't issues before Corsair Link.

 

One of the more obvious changes between 2.2 and 2.3.x is that it's now using libraries from Open Hardware Monitor. I'm not yet sure to what extent they're being used, but I suspect it was a drop-in to handle (at least) the stock non-Link sensors. It might be worthwhile (read: a great way to waste time) to see if any of the problems can be replicated by running Open Hardware Monitor instead of CorsairLink. Any problems that can be narrowed down to that lib can be fixed or worked around without waiting for Corsair to do something about Link.

 

It's crap. It's bloated, buggy, unfinished, unpolished garbage. I only wish I could get my money back.

 

I won't argue with most of these - Link has a remarkably impressive assortment of issues - but, especially in the same breath as AI Suite, I wouldn't include 'bloated' as one of them, beyond the usual .NET tendency in that direction (and maybe the sheer size and amount of wasted space in the UI). That's one area (along with 'mostly working right', of course) where AI Suite definitely has it beat. That particular package isn't one I'd ever hold up as a paragon of clean, streamlined, or focused design, and - up until I encountered Link - it actually seemed to me like a great example of what happens when hardware companies try to do software (outsourcing, guys! it's not always a bad thing)... And then, of course, there's AI Suite's truly awful interface design - Link doesn't exactly shine in that department either, but it lacks the feel of a UI lifted from a mid-90s adventure game. Still, it does manage to usually do what it's meant to do, which is something Link is still aspiring to.