Accidentally fried my h100i (or not?). Need tech advice. Full story in comments.

[archa]

Hello there, folks.

First of all, long time big fan. Thanks for your positive impact to a community.

Great and quality products all the way. Good job, guys.

 

 

Sorry for my unstable English, not a native speaker.

 

 

Ok, here comes the story.

In a fall of 2013 I build my rig:

 

i5-4670K

z87x-ud4h

SLI'ed 770

16gb ddr3

AX860i

ssd's

win7

and a h100i.

 

All works like a charm all these 2,5 years.

Until I broke the golden rule of IT: "if it's not broken, don't fix it."

Corsair Link version used, was v2.4.5110 and I got a great idea, hey, let's update this stuff!

v4.2.0.162 was installed and minor troubles began.

 

So, here I need to tell you my fans setup.

I have two Noctua NF-P12 PWM 120mm directly on a h100i radiator, and to the 2 remaining fan-ports, I hooked two Y-splitters and connect four

Noctua NF-A14 PWM 140mm and installed them in a case.

I did this, so I can control all of my fans via Link software.

 

All of them spinning on a minimal rpms when I'm not gaming, 120mm on a ~450 and a 140mm on a ~700

 

So, after I upgraded to v4.2.0.162, one of the pairs of 140mm went insane, doing minimum of 1300rpms and does not slow down.

 

My reaction was, meh, I going back to v2.4.5110, but nothing changes.

 

Then I proceeded to open the case and hooked up noctua's low-noise adapter in front of the the Y-splitter and a noisy pair of fans.

 

All works great, problem fans speed dropped to 450rpm at idle and I was happy.

 

After ~1,5 days I was woken up during the night, my PC howling like a insane. All fans spinning like crazy.

Shut it down, goes back to sleep.

 

In the morning I start to investigate.

Link showed me two fan counters blinking red with 0 rpm. Two another, also 0 rpm but without blinking.

But, judging by the noise, they all spinning.

Pump was working as usual and shows ~2200rpm, but LED light was changed to White. Temps was okay.

 

I opened the case and saw that two 140mm fans hooked via low-noise adapter not working.

After shutting pc down, I disconnect that adapter and smell it... Very gentle smell of burnt electronics was felt.

I made some tests, turns out, one of 4 fan-ports coming from h100i was dead.

All fans was okay.

 

So, after that, I tried to regain control over remaining fans in link.

Installed and uninstalled different versions, after some time the h100i completely disappears from link.

I changed USB ports on MOBO, clean register, nothing...

When PC is booting, LED is blinking allright, but when windows starts, it's turns off.

 

Pump is working, all remaining fans spins on a very-high rpm, but there is now control over it.

 

Is my h100i dead? Can I run some more tests, or upgrade firmware? Maybe I screw up in a register?

 

tl;dr:

1.Upgraded corsair link

2.Two of the fans starts spinning like crazy

3.Fixed by low-noise adapter

4.All fans gone mad, adapter smells burned.

5.h100i completely lost from link, pump works and fans spinning fast and loud. Need to regain control over it.

 

Thanks for any feedback guys.

[red-ray]

What firmware version does the H100i have? If it's not 1.1.3 I suspect you will need to install CL 3.2.5742 to update the firmware as CL 4.2.0.162 does not seem to be able to do this.

[archa]

What firmware version does the H100i have? If it's not 1.1.3 I suspect you will need to install CL 3.2.5742 to update the firmware as CL 4.2.0.162 does not seem to be able to do this.

Hello.

I don't really know with what firmware version I stuck now...

Okay, I'll try to install CL 3.2.5742 and see how it goes. Will post results later.

Thanks!

[archa]

Okay, so after I installed v3.2.5742 and rebooted, I got these error on a startup:

 

http://i.imgur.com/o5erMjY.png

 

Full error msg:

 

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

 

************** Exception Text **************

System.NullReferenceException: Object reference not set to an instance of an object.

at CorsairLink.SingleInstanceController.this_StartupNextInstance(Object sender, StartupNextInstanceEventArgs e)

at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnStartupNextInstance(StartupNextInstanceEventArgs eventArgs)

at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnStartupNextInstanceMarshallingAdaptor(Object args)

 

 

************** Loaded Assemblies **************

mscorlib

Assembly Version: 4.0.0.0

Win32 Version: 4.6.1055.0 built by: NETFXREL2

CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll

----------------------------------------

CorsairLink

Assembly Version: 3.2.5742.27109

Win32 Version: 3.2.5742.27109

CodeBase: file:///C:/Program%20Files%20(x86)/Corsair/Corsair%20Link/CorsairLINK.exe

----------------------------------------

System

Assembly Version: 4.0.0.0

Win32 Version: 4.6.1055.0 built by: NETFXREL2

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

----------------------------------------

CorsairLink.Common

Assembly Version: 2.7.0.0

Win32 Version: 2.7.0.0

CodeBase: file:///C:/Program%20Files%20(x86)/Corsair/Corsair%20Link/CorsairLink.Common.DLL

----------------------------------------

System.Windows.Forms

Assembly Version: 4.0.0.0

Win32 Version: 4.6.1055.0 built by: NETFXREL2

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

----------------------------------------

System.Drawing

Assembly Version: 4.0.0.0

Win32 Version: 4.6.1068.2 built by: NETFXREL3STAGE

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

----------------------------------------

Microsoft.VisualBasic

Assembly Version: 10.0.0.0

Win32 Version: 14.6.1055.0 built by: NETFXREL2

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll

----------------------------------------

System.Core

Assembly Version: 4.0.0.0

Win32 Version: 4.6.1055.0 built by: NETFXREL2

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll

----------------------------------------

Microsoft.Win32.TaskScheduler

Assembly Version: 2.2.0.18504

Win32 Version: 3.2.5742.27109

CodeBase: file:///C:/Program%20Files%20(x86)/Corsair/Corsair%20Link/CorsairLINK.exe

----------------------------------------

Telerik.WinControls

Assembly Version: 2013.3.1127.40

Win32 Version: 3.2.5742.27109

CodeBase: file:///C:/Program%20Files%20(x86)/Corsair/Corsair%20Link/CorsairLINK.exe

----------------------------------------

Telerik.WinControls.Themes.VisualStudio2012Dark

Assembly Version: 2013.3.1127.40

Win32 Version: 3.2.5742.27109

CodeBase: file:///C:/Program%20Files%20(x86)/Corsair/Corsair%20Link/CorsairLINK.exe

----------------------------------------

Telerik.WinControls.UI

Assembly Version: 2013.3.1127.40

Win32 Version: 3.2.5742.27109

CodeBase: file:///C:/Program%20Files%20(x86)/Corsair/Corsair%20Link/CorsairLINK.exe

----------------------------------------

TelerikCommon

Assembly Version: 2013.3.1127.40

Win32 Version: 3.2.5742.27109

CodeBase: file:///C:/Program%20Files%20(x86)/Corsair/Corsair%20Link/CorsairLINK.exe

----------------------------------------

System.Runtime.Remoting

Assembly Version: 4.0.0.0

Win32 Version: 4.6.1055.0 built by: NETFXREL2

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll

----------------------------------------

System.Configuration

Assembly Version: 4.0.0.0

Win32 Version: 4.6.1055.0 built by: NETFXREL2

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

----------------------------------------

System.Xml

Assembly Version: 4.0.0.0

Win32 Version: 4.6.1067.0 built by: NETFXREL3STAGE

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

----------------------------------------

 

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

 

For example:

 

<configuration>

<system.windows.forms jitDebugging="true" />

</configuration>

 

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.

 

I have no idea what all these means :)

 

Funny thing, when PC is booting, LED was glowing purple! As it intended to be by my setup. So, we are getting somewhere.

 

That's my CL window right now: http://i.imgur.com/LJs3g2z.jpg

h100i is still missing, with all fan controls.

Here's devices menu: http://i.imgur.com/lXxvZFi.png

 

All help and ideas appreciated, thanks!

[c-attack]

Ray may be right about the firmware and you should try to continue troubleshooting, but the burnt smell is definitely concerning and this does seem familiar. I doubt you will appreciate the irony. It appears to be a blown fan controller or some other component in that chain of circuitry. The F12's are about 0,05A per fan and the A14s at 0,13A x 4 (less if using L.N.A.). That doesn't even add up to 1A, let alone 4A. I would start a support ticket. The unit should still be under warranty, however depending where you are in the world shipping it back to Corsair may or may not be the best option for you going forward.

[archa]

Guys, are you magicians or something?!

Two advises, and both helps me! Problem solved! Thank's a LOT.

 

you will need to install CL 3.2.5742

 

It appears to be a blown fan controller or some other component in that chain of circuitry. The F12's are about 0,05A per fan and the A14s at 0,13A x 4 (less if using L.N.A.). That doesn't even add up to 1A, let alone 4A.

 

So, what did I do.

After installing v3.2.5742 I noticed purple LED was briefly revived.

After that, I read c-attack's comment about circuitry.

So I proceed to boot up only with two fans hooked to h100i.

And it booted perfectly and popped in CL!

http://i.imgur.com/nCF1QHd.png

http://i.imgur.com/bc7koDh.jpg

After that, I shut it off and hook 4 NF-A14's to one fan-port on h100i via 2 Y-splitters.

http://i.imgur.com/UICFMAP.jpg

 

So far it working as it should.

It's even offers me to upgrade firmware, but no way I'm doing it :D

 

Thanks everyone one more time!

[c-attack]

OK, but is this the same configuration you were running before? Just with the 4 x A14 on a different fan channel?

 

"Gigabyte Motherboard Fan" is any other fan or device connected to the motherboard. It could be a standard case fan, memory fan, Northbridge fan, etc. You used to be able to rename it in C-LINK.

[archa]

OK, but is this the same configuration you were running before? Just with the 4 x A14 on a different fan channel?

Previously it was:

1st channel - one P12

2nd channel - one P12

3rd channel - two A14

4th channel - two A14

 

And now, 4th is burnt and all A14 is on 3rd :)

[red-ray]

After installing v3.2.5742 I noticed purple LED was briefly revived.

 

Do you now have CL 3.2.5742 installed and working? Assuming so then my advice is to update the firmware from 1.0.5 to 1.1.3. After doing this I expect CL4 will work. If it fails and bricks the H100i then RMA it while it's still in warranty.

[archa]

Do you now have CL 3.2.5742 installed and working? Assuming so then my advice is to update the firmware from 1.0.5 to 1.1.3. After doing this I expect CL4 will work. If it fails and bricks the H100i then RMA it while it's still in warranty.

Yes, it's working with CL 3.2.5742.

And I don't have any temptation to change something again. :)

 

You guys saved me 12000 rubles, 2,5 years ago this unit costs only 4500!

Damn, our economy is screwed.