1st ever water cooling

mark.d.

New member
hi all,just finished my 1st ever water cooling project.

i just started off with the cpu and im very happy with the result's and temp's.

DSCF0710.jpg


DSCF0711.jpg


DSCF0714.jpg


my system now comprises of the folling after a upgrade of many parts

asus maximus special edition mobo

asus 4850 g/c

2.4ghz conroe

8gb corsair ram

xspc water cooling kit with double radiator

1200 antec power supply's

1tb samsung h/d

500gb samsung h/d

250 maxtor h/d

p190 case
 
im actually thinking of getting a q6600 very soon so i might start there.

any idea on how much a 2.4ghz conroe goes for ?
 
Depends how high your willing to take the volts. :P

4ghz.jpg


Realistically though, you've got an incredibly low VID (compare it to mine above) so I wouldn't be surprised if you could get 3.6Ghz (400x9) with less than 1.3v.:)
 
thats a nice clock m8.

any tips on how you got it that high ?

and what you pressed in the bios to overclock it ?
 
His VID is with speedstep enabled I think as it is only using a 6x multi??

So it might not actually be that low. Worth turning speedstep off so you can get a good idea of whereabouts to start.

Isn't 1.6v enough to like, fry your cpu :/
 
Ah, I just realized why temps in the screenshot in post #3 are so low; you haven't set the Conroe temperature offset in CoreTemp settings (Options -> Settings -> "Tjunction Max offset:"). The offset is supposed to be set at 15 for Conroes in order for correct temp to be displayed.

So, once the offset is applied the 17/19°C CPU temp in your shot is 32/34°C in reality.
 
whats that all about then ?

dont have a clue what t junction is and what it does.

i have turned it on and it's gone up to neally 70c !

whats happening there ?
 
tjunction is a component in the method how Intel CPUs report temps.

The CPU doesn't actually report a temperature, it reports the difference between temperature and tjunction (DTS_reading). So correct tjunction is a necessity for a correct temp reading:

Temperature of the chip in °C = tjunction - DTS_reading

At default, CoreTemp assumes 85 is correct for all Conroes, this is because some Conroes actually have 85 tjunction. Not all. Some have 70 (rare), but most have 100. The problem is, software cannot read the actual value of tjunction from Conroe chips.

For example, I had a cache-crippled Conroe E6400 (not Allendale, like most E6400s are) that had tjunction of 70, and two very early E6600 chips that had 85. But almost all retail E6600s have 100.

Anyways, user has to deduct the tjunction value based on temps the software reports. Basically, one has to find what tjunction would make sense. 70 and 85 don't make sense for your chip cause tjunction of 70 would mean CoreTemp gives 15°C too high temperatures, and it can't be 85 either cause the chip can't be cooler than it's surroundings without using chilled cooling - 100 is the only option left.

edit:

I'd say D-Cyph3r's 4GHz E6600 (in post #8) too has tjunction 100 and as such his CoreTemp reading is 15°C too low.
 
What ever happens Clocking isnt a 5minute job.

So meny people seem to think you whack the settings in and you are garantied a clock.

Over clocking is about spending time with your system to see what works best for that set up. Im currently running an e5200 while I build my new rig, but it doesnt like high fsb, so I have got it at stock stable running at just 1v!

Read the guides and understand your bios before you go whacking the volts up on everything!
 
Back
Top