Corsair H110i GTX Performance Testing and Review - page 2
This test confirms what martin tested with the H110i (0.11 gpm) tho in both cases, it's not experiencing the full resistance of the system as when the test is done, it's no longer closed and pumping thru block + rad.nukemaster said:For video cards it makes a surprising difference(much lower temperatures, but you still need to cool the VRM are) with even a slim 120mm rad.
But that's kinda like child proofing your house and extending your shelves from 4 feet off the ground to 6 feet off the ground. What does the extra 2 feet do your you witha 2 year old ?
With today's efficient GPUs, no one with a decent case / cooling arrangement id having performance curtailed by temperatures. The MSI 980 Ti for example starts to throttle at 85C and tops out at 75C at max overclock / max voltage according to TPU.
Using a CLC type GPU cooler might lower that to say 55C, but what does that for for ya ? Let's say that the stock cooler takes it down from 95 to 75 and the liquid cooler from 95 to 55. That means the single rad fan has to move twice as much heat via the air / metal contact as the stock cooler does w/ 2 fans. In order to do that, the air velocity thru the rad must be far greater than thru the air cooler and that means more noise... noise that carries outside the case as compared with the muffling that occurs on a stock cooler from reflections. And you are still left with a hot VRM which is the culprit that is going to limit your OC far before than GPU does.
This is why these new alternative OLCs from EK and Swiftech have so much promise. First off, you don't have to worry about 3 cooling systems (CPU, GPU, GPU VRM / Memory), you have just one. The pumps are powerful enough to handle all your components. You can cover a CPU and a hi load GPU with just one radiator, mounting it on top of the case, with the fans properly installed as intakes for greater cooling performance, creating positive pressure keeping dust out as well as hot exhaust air from PSU and the noise is funneled into the case where it's muted somewhat.
I can't wait for the Predator review, tho it's gonna have to really impress to justify a $60 performance premium over the H220-X.
H110 GTX @ $140 versus Swiftech H220-X @ $140 = "no brainer"
Either of those @ $140 versus $200 for the Predator ? Gotta be a lot more pluses (QD Fittings + ability to do 1 more fan in push pull) than minuses (no reservoir) to account for that price premium.
Quote:This test confirms what martin tested with the H110i (0.11 gpm) tho in both cases, it's not experiencing the full resistance of the system as when the test is done, it's no longer closed and pumping thru block + rad.
It's pretty dismal, that's for sure.
As for the Predator, I am overly impressed with it just from unboxing and doing some initial photos. It is exceptionally well put together. It looks professionally made. The radiator is hefty and relatively thick. And...the entire unit holds just around 300mL - almost twice the total liquid volume what the Corsair H110i GTX held - which should tell you how much thermal volume the radiators are able to cool at any one time, by comparison.
The radiator has 2x G 1/4 ports with chrome caps, sealed with o-rings. The pump is 'listed' as a DDC 3.1 on the label. There is a very nifty power distribution block for fans+pump, and both can be PWM controlled, depending on how you wish to set it up.
I haven't started on thermal tests yet, but based on what is contained in the box, it looks to be incredibly promising.
Thermal mass does wonders to even out load peaks.
Five things I remember not liking ..... just from looking at it.
a) Physical design allows push / pull but they don't provide enough fan ports.
b) No reservoir
c) No 140mm design, I'm done with 120mm
d) Not sure I can support $200 price tag.
e) Hey I'm 60... I forgot the 5th one
I started a radiator volume thread over on OCN but I admit to not keeping it updated. Thot the community would have provided more input....some users were very helpful / enthusiastic but how many rads can each person buy
I did read that the pump is only 6 watts, same as the Swiftech ... when i think "DDC", I think 18 - 24 watts.
I do see that they have the fans installed upside down (exhaust) and the TPU review says it's a PITA to change.
Reviews (EK 240):
So far I am liking the Swiftech better but there's still a lot I don't know.... both have wins on the various sites which is understandable but that $60 is a 43% price increase and the Swiftech warranty is 50% longer .... the performance per dollar difference can be used in the graphic from top to bottom as it doesn't address water vs air vs expandability. But given the similarities, the difference really hits ya in the graph here.
So I am anxious to see what ya come up with when letting these two go head to head .... like can ya go G-1/4 on the EK ?
The 1st one to come up with a 420 rad will get some attention as that will cover a hi end GFX card .... in fact... a combo discount $20 off w/ purchase of the company's GPU water block would do a lot to create market share.
a) Yes, you could run push/pull, but you're short 1 fan port (3 PWM fan total) but you could run a pigtail or something
b) True. We will see how this impacts 'reassembly' when I'm done (will include in the write-up)
c) True, only 120mm, but it is still most common for cases with dual fan setup; newer cases are more flexible with larger fans
d) $200 seems steep, but when you compare a custom loop for CPU-only, it's not bad, especially considering it's designed to be a gateway watercooling loop - start out with this, gain knowledge, expand.
e) I'm 36 and I have those days all the time.
I've always wondered how I could do something similar, then it kind of struck me that this would be very difficult to ensure everything is tested in the same way, unless they wanted to ship me radiators to test, and ship back. Tedious. I'd even be willing to do this kind of testing and data collection with an agreement to return to a vendor upon completion with my time and shipping reimbursed.
a) which kills an advantage it cuda had over the Swiftech which also allows only 3 fans because of a physical limitation ... but the PWM controller does 8 fans which is a big +
b) "Being a worry wart" ... I like the visual indicator. They got the idea here, maybe we see one in Predator 2
c) I think 120mm is more popular, yes, but only because of installed base ... 140mm gives way more bang for the buck and i think more new builds go this route ... 480 costs way more for rad than a 420 but have same cooling performance and yes save on one fan to boot.
d) I am speaking only in reference to the competition at $140.... Swiftech costs ya 46.67 per year of guaranteed usage (3 year warranty) ... EK costs $100 per year w/ 2 year warranty.
And yes, identical setups is required for testing but volume ? I kinda figured everyone had the same one of these
Was surprised about the variances I saw from users, sometimes 100 ml or more..
Yeah, it would have been nice to get 1 more fan header, but my guess is that distro block was engineer for both the 240 and the 360 - and assuming push/pull wouldn't be a highly chosen option. Plus, the rad itself is 40mm wide, plus 25mm fans, you're looking at a 65mm wide footprint out of the box...you'd be sitting at almost 10cm thick (95mm) with push/pull fans.
Funny you say that about the EK spin res - they actually have some pages in the manual on alternative loop setups, and that res (along with a cylinder res) are show as suggestions. Also shows the steps to add a GPU into the mix.
As for the performance comparison between the EK and the Swiftech - I'm expecting both to perform about the same at lower thermal loads and the EK to pull away at higher thermal loads. Either way, I would take either over any Corsair unit.
Once I get done with this EK Predator, I'll give any recommendations like I did with the Corsair.
That was the surprise c... Swiftech took 7 outta 8 performance tests in the TPU review. Then again, EK won in one of the other reviews.
-OC w/ Prime = Swiftech by 2C*
-OC w/ AIDA 64 = EK by 1C
-OC w/ AIDA 64 FPU = Tie
* Interesting enough, installed as push (intake) it picked up 1C. Given the difficulty of flipping the fans, ya wud think later editions will put the the normal way as intakes since it has better performance. As I recall martin showed fans work better in push up to 1650 rm and better in pull at 1850 rpm and up. So despite being less efficient at 2200 rpm in push, using them as intakes improved performance.
The EK tho was a rather significant 6 dbA louder which is expected with fans spinning 400 rpm faster. I think if you push the CPU up to 4.6 Ghz or more, the EK would therefore do better thermally, but I think a key data point will be both at 1800 rpm and, if nit equal, both at the same dbA.
I think a good move would be to put Tees on the inlet and outlet of the rad and install thermal sensors on the branch
|---- Thermal sensor
to pump / block
Might even do the same on inlet / outlet to block for sheetz and giggles ... no useful purpose really in single block loop as temps won't chnage after 8" of tubing but the reeven 6 eyes has 6 temp displays and with 2 at the rad, 1 ambient, 1 case interior temp, I can't think of how to use the other two
I have 7 waterproof Dallas one wire sensors that I have connected to a CrystalFontz 633 (I have 10 total). I currently have 2 in a tee exactly like you have diagrammed (fixed with epoxy and not interfering with flow) and then I drop at least one into the reservoir. The others are used and averaged for ambient air temps. Data logs out every second to a CSV file which I convert over to Excel to do calculations on each thermal load for both push and pull.
Pressure loss thru a T is minimal. Friction coeffiecient is 0.54 (x V^2 / 2G)
If I can remember my notes from days as a fluids instructor at 1.0 gpm, we have a flow of about 2.9 feet per second or about 0.07 feet of water or 0.03 psi. I wouldn't bother but I admire your attention to detail.
I like detail, especially when it comes to scientific methods. I know that given my setup and cost of equipment, my several hundred dollars worth of gear is nothing when it comes to several thousands or tens of thousands of dollars worth of equipment. But, if I can replicate my testing methods and identify potential areas where environmental variables can be eliminated, I should be able to collect data in a way that allows repeatable test scenarios for anything I put on the test bench (hopefully).
This detail oriented method is also the same reason I enjoy brewing beer on weekends - it requires repeatable methods and exacting times, temperatures and volumes.
Without repeatability, scientific investigation is meaningless. And I agree, if ya not in a position to quantify the impact of a decision, then it's best to go to the extreme to make sure a decision has 0 impact. If I kno that a rock weighs 375 pounds, I'll use a 500 pound hoist to lift it.... if I don't know how much it weighs, then i'll use the biggest mutha I can lay my hands on .
As for the beer, repeatability is important tho improvements sometimes come by way of mistakes. My niece's hubby just took home some awards at a recent brew competition and the one they served at their wedding was one of those. he told me what it was tho as I had sampled a few before he told me, I can't tell ya what it was. I have some samples in my fridge I gonna drink on their anniversary.
Sometimes you can get too scientific, and totally miss something very important, like, how well the individual water blocks perform actually mounted to a CPU?
The thermal load testing is OK, but we aren't cooling aquariums!
It all seems completely moot, and IMO a half completed review, if you never even mounted the CPU water block on any CPU at all?
The AIOs do cool CPUs and are designed to mount on CPUs so where is that data?
Secondly this is the Overclocking Section of Toms Hardware, so Overclocking data is missing as well?
CPU temperatures totally MIA.
You're missing the entire point. I don't need to mount to a CPU. I don't need to overclock a CPU. I can test exacting thermal loads to compare what ANY CPU could possibly load into the cooler. The testing methods that I am using allows me to account for any possible heat load these coolers could potentially see. For 'overclocking results' - this is about coolers, not specific CPUs or specific CPU overclocks. Thermal load in watts in various, increasing amounts accounts for overclocking; that's made clear in my testing methods. Otherwise, I would need 5-6 CPUs to try and replicate my load tests, and even then, it isn't as accurate because I'm still limited to testing and reporting based on MY exact CPU setups; not something that can be applied to everyone.
Every single one of these cooler reviews goes the route of "mount cooler, test cooler with CPU load test, overclock CPU, test cooler with CPU load test, give X-number of stars". Great, but this is not what I wanted to do. These tests and reviews are limited in knowing exactly what loads are being tested and dissipated by the coolers based on the 1 or maybe 2 setups they have available. This is where I am trying to draw the line of testing difference - I am removing the variables of any specific CPU speed or voltage, motherboard stability, RAM stability, wondering if 100% actual load is applied, etc. I have the tools to measure exact thermal load for each test.
You and I both know that the biggest problem with cooler reviews is that Joe User doesn't understand the difference in how thermal load and ambient temperatures account for cooling a specific CPU at a specific speed or thermal load. If I say that a i7 4790k running at 4.8 GHz at load reports temperatures of 55C, for example, someone is then going to say, "Great, but what about my i5 3570k running at 4.0GHz? What if I live in a hot climate? What if I use the +25% overclock in my BIOS?" ... you've now created a testing and overclocking review for only a cooler on a specific CPU because you cannot tell Joe User what to expect on his CPU. If you can TEACH Joe User how to account for his own CPU loads and provide him with a graph of data that represents a thermal curve, he can simply connect X,Y axis and find his expected cooling capability.
Of course, you're always welcome to do this overclocking testing and result reporting if you'd like to supplement. For someone who has been supportive of this testing to this point, I find it strange that you'd suddenly do a 180 and respond with this, and while I understand your point, my response is the entire reason why I did not go this route. The web is full of these kinds of reviews, why would Tom's want to add yet another when we could be the first to try and teach our members the how's and why's of cooling and show them how to determine what to expect in their own specific systems?
I'd invite 'everyone who is seeing the issue' to include their opinion on the subject. What exactly would you like to see in these write-ups?
Compromised the integrity of the remaining coolers, how? The remaining coolers for this group are intended to be expanded.
Maybe I am not following you, here. There are literally dozens of write ups on the web about what you are talking about; so you are suggesting I just do the same as everyone else?
rubix_1011 said:For someone who has been supportive of this testing to this point, I find it strange that you'd suddenly do a 180 and respond with this, and while I understand your point, my response is the entire reason why I did not go this route. The web is full of these kinds of reviews, why would Tom's want to add yet another when we could be the first to try and teach our members the how's and why's of cooling and show them how to determine what to expect in their own specific systems?
I am saying you should not exclude that direct mount CPU data but provide it as well, along with exact ambient room temperature the direct mount CPU test is conducted in.
Because you are really not even testing the water blocks, only the radiator cooling capability.
I understand your point, and I realize what you are saying. But this is exactly what is done on all other reviews, so I would just be providing the same information that exists so many other places on the web. Playing devil's advocate with myself, I can see the argument of 'we should provide that data here, as well' but at the same time, at the end of the day I'm only just providing data of that cooler based on my own, specific system that just represents what happened to me, but might not happen for someone else - I am then introducing not-repeatable results that would essentially have an asterisk that says:
(*Results seen may not be results or experience seen by anyone else. This is a generic application; installation and temperature results are not indicative of all systems)
In doing this, I have contradicted my own testing and results by introducing dozens of variables into a result for people to read and depend upon. They will overlook the load test results and skip right to "My CPU saw load temps of 55C using Prime95" and therefore undoing the teaching opportunity and understanding that each system is unique and different. I would also debate that far too many assumptions are made from reading reviews that return result data in this manner.
rubix_1011 said:So, here is my question to you, then; what should the ideal system be that I use to do this CPU testing?
I think your thermal load testing is great for overclock estimation but IMO you should have done your own direct CPU mount tests before that, even before taking any cooler apart, so your test not only covers the CPU direct mount load testing basics but goes way beyond other reviews including your thermal load tests.
IMO since the H110i GTX was not expandable it should have been isolated in it's own test group, and not disassembled.
But that's water under the bridge now, the expandable lines to be tested should IMO be thoroughly tested before disassembling with direct CPU mount testing.
Once you take it apart you have compromised the initial factory shipped state!
It would be interesting to see how the expandable line fares running the competitions water block, but Oh My, that would require mounting it to a CPU.
rubix_1011 said:Compromised the integrity of the remaining coolers, how? The remaining coolers for this group are intended to be expanded.
I believe I said something like compromised the shipped factory integrity, you know the sealed integrity that is shipped out of the factory door, that anyone buying the cooler you review could expect to receive when they buy one.
It would also be interesting to see how the AIO fares against your custom water cooling setup?
Because you are not just an AIO CPU cooler tester, you are a custom water cooler, you bring so much more to the table than some of the other testers do.
That could bring some illumination to some Toms users that are trying to decide going high end AIO or a custom build.
Quote:It would be interesting to see how the expandable line fares running the competitions water block, but Oh My, that would require mounting it to a CPU.
I have decided to not do any cross-vendor testing on the units. If it was "a bad idea" as you mentioned with the H110i and using, say, a DDC pump just to see what happens, doing something like this is also a bad idea - you're testing a scenario that doesn't offer value, so to speak. I have since accepted your advice in this regard.
If you would prefer to supplement the data yourself, please feel free to do so on your own accord. I also don't appreciate the mockery and sarcasm; it does nothing for the debate overall, but that is your choice.Quote:It would also be interesting to see how the AIO fares against your custom water cooling setup?
Because you are not just an AIO CPU cooler tester, you are a custom water cooler, you bring so much more to the table than some of the other testers do.
Considering I have a full cover GPU block in my loop, the only way to compare load results is to simply add the TDP load totals from my system and run it against the expandable loops. This is why I choose to test how I do - I don't have to build or buy components just to test with. I can use the engineering specs of components and load the loop based on this value total.
This was something I had planned to do with the XLC coolers - simply because that is what they are marketed as.
rubix_1011 said:If you would prefer to supplement the data yourself, please feel free to do so on your own accord. I also don't appreciate the mockery and sarcasm; it does nothing for the debate overall, but that is your choice.
So actually you ask for input to give reasons to disregard it.
Why should I do the testing, when you have the hardware?
My Bad on the mockery and sarcasm, it is good for you I actually like you!
We have a completely different point of view, and my mockery and sarcasm comes from testing AIO CPU coolers that are not actually mounted to a CPU?
To me that's preposterous, it's like buying a vehicle on stats alone and never test driving it?
That is absolutely not going to happen in my home!
You are incorrect with your assumptions about me being open for input - it is just that I disagree with the methodology you've mentioned and choose to continue as I have.
I have the right to disagree and defend my own system without having to concede to all outside ideas. Asking for input does not automatically mean that I am also required to do what is suggested, so please remember this when someone mentions they are open to input. I have elected to take some of your advice but I have also respectfully declined some, as well. The issue here is understanding that both are done with the same level of professionalism, but it is interpreted differently based on the decision.
Like I have stated, I chose to test in the way that I have so that I can repeat all tests in the same manner.
as a noob looking to get into watercooling as either an AIO or possibly custom down the road, i liked the data but also see the some of what ryan is saying. in a perfect world if this testing was done just for me (by me for my own use even) i'd run it on a cpu at stock settings to start with to get a baseline. then all the sweet testing you did after for the wonderful thermal load graphs.
as someone trying to educate users (like me) this baseline readings of the cooler and what it does on a specific cpu in a specific setting is part of the knowledge. knowing the rough tdp the cpu brings in, paired with the then exact delta numbers you are able to measure once it is broken down and controlled better helps paint the whole picture. some ending analysis of what you were able to read on a cpu and then helping me see how the delta graph you made relates to and can be extended to any cpu is the final exam of the overall lesson.
does this make sense? as thorough as all you did is, it is partially missing the connection to an actual result on a cpu. i know in your mind the connection is there, but as a student, the aha moment of comparing the graph to what we measured on the cpu and seeing how some of the variables effect that delta graph is the icing on the cake. i love the graph and feel i understand it's purpose, but the other variables that i now know mean a lot to actual real world performance could be explained a lot with a real world test and some insight on what is happening. you are the master and sometimes you have to do some initial hand holding and spoon feeding to get the lesson to stick. in science class, most theory is taught with a specific single experiment and then expanded from there to include the theory and effects represented by that single experiment.
either way i love it but i think ryan has a point, though he may not have explained it as well as he may have. remember i am actually an experienced teacher and it took me years to figure out how to take all the vast deep math knowledge i have and present it to a total novice in a useful digestible way. so i offer some insight from that perspective to you
I am going to agree and disagree with both sides of this argument. On one hand this is an AIO, one of the things peeps will want from a review is how it compares "as a package" with others that come "as a package". In addition, as has been shown in detail @ benchhmarkreviews.com, the "frostytech approach" of testing CPUs coolers on a "synthetic heat block" is pretty much useless as the heat signature of a particular CPU, will present different conditions to the block that is on a CPU. What rocks on one platform may be so so on another. This is show never more clearly than in xtremesystems CPU block reviews where there is a different "best" for almost every platform:
Here we see ...
- the top 3 water blocks for 3930k being the Koolance 380i, AC cuplex kyros pro and Koolance 370
- the top 3 water blocks for 4770k being the EK Supremacy J2, EX Supreme HF and EK Supremacy J1
- the top 3 water blocks for 4930k being the EK Supremacy J1, EX Supreme HF and EK Supremacy J2
So the different heat signatures of each CPU do in fact affect cooling performance.
On the other hand, these AIOs are a package and just as important as accounting for the above, is accounting for variables in the individual components, so here I agree with Rubix as to providing the data on each component. For example, let's say I want to pick the best cooler available "for me" on a 4790k w/ an anticipated 135 watt load. I want the best performance possible at no more than 40 dbA. We have the following:
Predator 240 under 150 watt load gives me 70.5C
Swiftech H220-X under 150 watt load gives me 70C
At the surface, the Swiftech seems like the better choice....
... but wait, the Swiftech has an advantage because it's using the fans as intakes, if I get the special tool from EK and flip the fans, I pick up 1C and now the Predator is better....
... but wait, the fans on the Predator are spinning at 2200 rpm and the Swiftech's at 1800 rpm and therefore are much quieter. If I make them the same speed, the Swiftech is now better....
... but wait, given the price difference, I could add different fans ... you see where this is going.
As this is an "expandable system" ... we can not only add blocks but also radiators, what radiator to I choose for my 2nd Rad ? How will each pump handle it ?
So from my PoV, I agree with Rubix in that creating repeatable scenarios allows one to weigh the relative strength of the individual parts so that I can perhaps consider modifications or better plan my expansion .... but I agree with Ryan in that in that many folks will just want to know about "what they bought" as a whole.
The other factor to consider is how much effort should be put into a $140-$200 component ? But, from a user perspective, the relative performance if the two blocks could effect which one you buy. Is it really realistic to do tests on 5930k, 4930k, 3930k, 6700k, 4790k, 3770k, 2700k and add in a few more for AMD...?
Picking one may be misleading because of heat signature variation or simply because one does better at 230 watts than it does at 88 watts. But I think if I had a choice, one or the other, I'd rather see results at say 90, 130, 180, 230 watts, then just 1 test on a particular CPU.
Ideally, I'd like to see both .... use a heat block to create the wattage and test the ability of the cooling system, and then test on a 6700k and 5830k to evaluate the effectiveness on the two major platforms. You'd wind up with an evaluation that addressed the relative strength of each component as well as the entire system.
For a little distraction from the philosophical approach... thot I'd try and list a perfunctory spec list, well a start anyway:
Manufacturer: Joe's Badarse Coolers
Model Name: JBC 2-120-1800
Included in Box: Whole Bunch of Good Stuff
Warranty: 10 years
Model No.: JBC 45-120-2-12
Configuration: 2 x 120
Material: Brass tubes, louvered copper fins
Dimensions: 250mm x 125mm x 45mm
Connection Type: G-1/4 Barb Type
Fittings: Swivel 90° elbows, 3/8" (10mm) OD
Removeable (tubes / fittings): Yes
Hardware: Standard: (8) coarse thread fans screws Alternate: (8) 6-32 x 1 3/16 (30mm) Philips screws
Design: Split Fin
Screw Protectors: No
Connection Ports: 2
Bleed Ports: 1
Model No.: JBC-1.5-6
Flow Rate: 0.50 - 1.25 gpm
Pressure Head: 4.2 psi max
Speed Control: PWM
Speed Range: 1200 ~ 4500 RPM
Voltage: 12 VDC
Nominal Power: 12W
Redundant Fail Safe Calls you on smartphone if there's a problem and shuts down system
Bearing Type: Ceramic shaft, Unobtainium bearing
Power connector: SATA
RPM & PWM connector: Mini 4-pin
MTBF: 100,000 hours
ROHS Compliant: Yes
Model No.: JBC-120-SP
Mounting Direction: Intake
Dimensions: 120mm x 120mm x 25mm
Speed Control: PWM
Speed Range: 600 - 2400 RPM
Airflow rRange: 20 ~ 80 CFM
Static Pressure Range: 0.50 ~ 2.50 mmH20
Noise Level Range: 15 - 35 dbA
Nominal Voltage: 12 v
Nominal Current: 0.2 - 1.0 A
Bearing Type: Z-axis Modified Rifle Bearing
Connector: Mini 4-pin
MTBF: 60,000 hours
ROHS Compliant: Yes
Model No.: JBC-I-1151
Base Plate Material: C110 copper
Cooling Engine: 0.25mm x 0.25mm micro-channel
Connection Type: G-1/4 Barb Type
Fittings: Swivel 90° elbows, 3/8" (10mm) OD
Removeable (tubes / fittings): Yes
Default Hardware: For Intel LGA 1150, 1155, 1156 (pre-installed by default) Back-plate (4) Spring loaded screws & washers
Alternate WorkStation Hardware: For Intel LGA 2011 (4) Spring loaded screws & washers
Alternate AMD Hardware: For AMD AM2, AM3, FM1,FM2, 939 (2) Pre-assembled brackets & spring loaded screws, Bracket installation screws
Optional Hardware: Optional back-plate available for Intel legacy socket 775 and 1366
Tubing & Coolant
Dimensions: 5/8" x 3/8" (16/10mm)
Coolant: Pre-filled with Tequila
No. of Clamps: 4
Clamp Material Black anodized aluminum
PWM Splitters: 1
PWM Ports 4
RPM Signal Port: Channel 1
Power Connector: SATA
PWM / RPM connector Mini 4-pin
Installation Hardware Peel-off sticker, w/ my picure on it, mounting screws & nuts
ROHS Comliant: Yes
TIM Provided: 1.5g
Material: Acrilic w/ clear window
Level Indicator: Yes, Visual
Flow Indicator: Yes, Paddlewheel
Critters: (2) Seahorses
T-Shirts (1) "Liquid Control Phreak"
Door Hanger: (1) "Shhh ... it's quiet in here, were water cooled"
Extras: Real girl's phone number
For what it's worth I realize this is an old thread, however I thought I'd add an observation that may be helpful to some.
I am running three of these H110i GTX coolers all cooling Xeon X5680 CPU's (yes I know they are older but they work).
These computers run a distributed computing project thus are on 24/7/365 under full load.
After running these for about a year I have noted that the cooling efficiency of these things has dramatically degraded.
The CPU's that were initially cooled to around 60°C while under full load with ambient room temp in the mid 20's, are all now showing 65-70°C and that with the CPU load reduced to 50% from the full 100% before.
I have read in several places other uses complaining of similar, and or overheating issues.
Corsair says these are closed systems that do not require maintenance but I'm a bit suspicious of this claim.
I know the pumps are all running fine, and good quality thermal paste is in play, so the only thing that leaves is a loss of coolant being the culprit.
I have to rebuild one of the computers in the near future and will be attempting to do what someone else did which is remove the copper bottom plate and fill the system up again, which apparently for him returned the performance to the great cooling capabilities seen when the unit was new.
Just out of curiosity has anyone else opened one of these up to top up the fluid?
You should never have to fill these, but I know that there are many people who have encountered the same thing. My recommendation would be disconnect tubing from the radiator to fill, but please realize this will void your product warranty if you choose to do so. Actually, 'opening' the unit at all voids it, but it sounds like you're OK with that.