I recently build a new rig, it all went well and everything. Until i checked the temperatures with Core Temp and NV Monitor. It Idles at 55c from what coreTemp shows and at load around 77c. Keeping in mind that the CPU is not the only thing that is water cooled. the loop includes CPU + 2x 8800 Ultras. The ultras are showing 50C idle both.
My question is my system running way to hot or is this temp okey with 2 GPUs and CPU?
*edit* the cooling kit is the Swiftech Apex Ultra with 2 GPU water blocks and the CPU is OC'd just by hitting the multiplier up once from 10 to 11 so its showing at 2.93GHz
We need to know more about what hardware you used to build your rig. Including how you have your loop setup (res->pump->rad->cpu->gpu1->gpu2->res). This way we can try to help you as much as we can.
We need to know more about what hardware you used to build your rig. Including how you have your loop setup (res->pump->rad->cpu->gpu1->gpu2->res). This way we can try to help you as much as we can.
-ouch1
The loop is exactly how u posted it res->pump->rad->cpu->gpu1->gpu2->res
Hmm it almost sounds like bad mounting. But I could be wrong. Try removing and reseating the waterblocks (after you clean off the TIM already installed). Also try turning up the fans to thier max to see ifthe temps drop more.
I*edit* the cooling kit is the Swiftech Apex Ultra with 2 GPU water blocks and the CPU is OC'd just by hitting the multiplier up once from 10 to 11 so its showing at 2.93GHz
If you have the MCR220 rad (2 x 120mm fans) then that's way too much heat for that rad to handle. You'll need at least a 3x120 rad with some high flow fans, and possibly consider two separate loops - one for the cpu and one for the GPUs. As someone suggested, reseating the water block might help, but that's still a lot of heat for three blocks.
Is it the Apogee GT or the original Apogee? Did you insert the larger O-ring to bow it? That would cut 2-5C.
------------------------------Intel Q6700 Quad/D-Tek Fuzion V1 with 2xPA120.3/ASUS Maximus II Formula/PCP&C
Silencer 750/Corsair Dominator 4Gb PC28500 memory/Corsair Dominator Fan
VisionTek Radeon HD 4870/Swiftech MCW60-R/Raptor 150GB HDD 1 X WD Caviar SE16 500GB HDD/Mountain Mods
Reply to TonyL222
On the other hand you get a hot resevoir, the idea behind cool water in res is that when it mixes it will further lose heat.
I'm not trying to cool the resevoir, but the blocks (smile). Either way, the temp dif would only be a degree or maybe two across the entire loop. I don't know if I'd re-route my whole setup just for that. Maybe on the next maintenance cycle.
If you look at the arrangement of your components in the loop you'll see that the GPUs suffer from having to deal with their own heat AND the heat generated by the CPU. The last GPU in the loop is especially having to deal with extreme heat. Ideally, two rads, one placed AFTER the CPU and one placed AFTER both GPUs would allow for your cooling loop to have a much more efficient function.
Reservoir - pump - CPU - Rad - GPU - GPU - Rad - back to reservoir
In this configuration, heat from each component is dealt with in some fashion before the next component in the cycle.
------------------------------Swiftech Mcres-Micro Reservoir, MCP655 Pump, D-tek Fuzion CPU Waterblock w/nozzle kit, Thermaltake Toughpower 1200, Swiftech Stealth GPU Waterblock, 2 external dual 120mm rads (each with four 120mm fans in "push-pull" )
Reply to phreejak
Haha! Three different people and three difference opinions on loop order. Here is Swiftech's opinion on loop order:
"From a performance standpoint there is very little performance to be gained from strictly controlling the component sequence: the maximum delta T (difference in temperature) between any two points of the liquid cooling circuit does not exceed 1ÂșC. Whenever possible, performance oriented users will typically want to route the radiator discharge(s) tube(s) to the inlet of the CPU cooler, since the fluid exiting the radiators is always the coolest." http://www.swiftech.com/products/i [...] a-rev2.pdf
I think there are a couple of areas of agreement:
1. The single Swiftech 220 radiator CAN'T handle the heat of an OC'd cpu and two GPUs.
2. The only MUST in loop order is that you go from res out to pump in no matter what the remaining order is - with the res being at the highest point in the loop.
You're going to need another rad regardless. That means you'll end up with two rads - the one you have and the one you need to purchase. The two rads in a single loop might work. In that case I'd get a 120 rad (if I could fit it in the case) or another 220 external. If you don't have room for two rads, then your next option would be a great 360 rad like the Thermochill PA120.3 and some high performance fans.
If that doesn't cool it down to your requirements, then I'd still consider two separate loops at that point (if you have the room for a 2nd pump and res (or T line) in your case).
Message edited by TonyL222 on 11-19-2007 at 04:43:45 PM
I think it makes a big difference when dealing with component heat output - especially if you o'clock. Having the heat output from an o'clocked Q6700 flow directly to an SLI setup - without the benefit of a rad between the two - will add to the heat that the GPU waterblocks are going to collect. It's not enough to cool the loop all at once. Rather, the loop should be cooled in such a way so that the major components do not have to suffer from - not only their own heat output but - the added heat from another major component.
For me, it's especially evident because I use a TEC waterblock for my CPU and the heat it puts out is tremendous.
------------------------------Swiftech Mcres-Micro Reservoir, MCP655 Pump, D-tek Fuzion CPU Waterblock w/nozzle kit, Thermaltake Toughpower 1200, Swiftech Stealth GPU Waterblock, 2 external dual 120mm rads (each with four 120mm fans in "push-pull" )
Reply to phreejak
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.