My new rig. [PICS] Started to overclock as well.

Soldato
Joined
12 Sep 2003
Posts
11,333
Location
Newcastle, UK
How do! I wasn't too sure where to post this, I just wanted to share some pictures of my new rig with people. Thought I'd put it in here as I have some "mild" overclock results as well to share.

So I hope you enjoy the pictures. This is my first Intel rig. I have upgraded from an X2 3800+ @2.85Ghz on a DFI LanParty SLI-D to this new setup (in Sig).

The Old Setup

Old_Setup.jpg



Q6600 CPU (Nice and clean, cheers Easyrider).

CPU.jpg



G.Skill RAM (Don't worry, I did peal the plastic covers off the logo's before installing them).

Ram.jpg



DFI LanParty P35-T2R

DFI_P35_1.jpg
 
New CPU and Watercooling bracket installed

CPU_Installed_1.jpg



Watercooling in place

Water_Complete_1.jpg



All done (I did eventually clean the soundcard. lol)

Complete_1.jpg



Outside Pic (Installed a 120mm fan to blow over the CPU and heatsinks)

Complete_2.jpg
 
Last edited:
And finally... my first overclock results. Compared to my old setup I had a score of 31.031s for 1M SuperPI. With the new rig at 2.6Ghz I score 19.438s! Nice improvement there. Although I think the cache helps with SuperPi.

And with 3DMark06 I had a score of just under 9.5k but now with the new rig I score just under 11k. So far I'm very pleased for an upgrade that's cost me just around £300. :D

3DMark_Result_1.jpg



Anyways, cheers for reading. I still have far to go with regards to overclocking. The GTS is still at stock as well, so that should also help when I get round to overclocking that. But... back to the CPU for now!

Cheers.
 
Last edited:
Got to give that 6600 some mucho needed FSB

Indeed. :) Just rebooted at 2.8Ghz so far. So that's 311x9. So far so good. It's weird, I don't know if all Intel setup's do this or just the DFI mobo. But after changing anything in the BIOS to do with like the CPU or Memory, as soon as you say "Y" to save it powers the PC off and then switches back on after say 2-3 seconds with the applied changes.

At first I thought I'd killed the PC.... my old setup never did this. Would just beep as if I had restarted the PC. :)
 
How come your GFX is in the lower PCI-E slot?

Nice rig tho

That's actually the middle PCI-E slot. :)

But I've re-shuffled it back around in to the top one since the photo. Basically the manual for the mobo says that each slot is x16 with one card. But I couldn't get it to work. It goes x16/x4/x1. So I've had to put it in the first slot, then set in the BIOS the other two to x1/x1 and then I've put my Wirless PCI-X adapter into that slot.

Works fine now. :)
 
Wirless PCI-X adapter..

Sorry to be pedantic, but PCI-E is very different to PCI-X :p

On a more constructive note, my Asus P5E does the powering off then on again thing whenever you change a memory ratio related option in the BIOS. If I just change CPU multi, FSB or up voltages it doesn't do it. I always put it down to being an Asus quirk but clearly it's not if other boards do it too.
 
Yeah shoot for 8x400 or 9x400 instead of faffing around with the lower clock speeds :) It's pretty much a given that it'll do 3.2GHz with ease.
 
Sorry to be pedantic, but PCI-E is very different to PCI-X :p

On a more constructive note, my Asus P5E does the powering off then on again thing whenever you change a memory ratio related option in the BIOS. If I just change CPU multi, FSB or up voltages it doesn't do it. I always put it down to being an Asus quirk but clearly it's not if other boards do it too.

You're right, just checked in the manual and that small slot is just called PCI Express x1 slot... for some reason I always thought it was PCI-X. Just looked on wikipedia and yeah, PCI-X is completely different. lol. ;)

Cheers for letting me know that it's not just my board. :)

dive in the deep end 9 * 400 :)

:D Well I'm at 3.0Ghz at the moment running nicely. Just had to do a System Restore as Windows decided to go **** up after I ran spybot in safe-mode. :confused: So all is well again!

Yeah shoot for 8x400 or 9x400 instead of faffing around with the lower clock speeds :) It's pretty much a given that it'll do 3.2GHz with ease.

I wasn't really aware what these chips will do with ease, like I say, this is my first Intel setup. :) Easy steps first. lol. :D
 
The board powering on, then off is a feature. The board sets chipset parameters then powers down then boots up at the settings it was programmed for.

You should be safe to get 400*9 with GTL's disabled.
 
The board powering on, then off is a feature. The board sets chipset parameters then powers down then boots up at the settings it was programmed for.

You should be safe to get 400*9 with GTL's disabled.

Cheers for the info. What are GTL's...? I saw them in the BIOS but obviously haven't got round to finding out what they do?

:)
 
It's a setting to do with VTT voltage, and usually runs around 67% of VTT but going off the 67% mark can help in times when the system isn't that stable. Fine tuning them will let you run lower volts than leaving them disabled and pumping volts into everything.

Courtesy of Praz of XS:
GTL 1/3 corresponds to the first two threads of Prime95. GTL 0/2 matches up with threads 3 and 4. If either thread for one core consistently fails adjust the CPU GTL for that core. If the failures are random between cores adjust NB GTL. You need to use Prime95 v25.6d.

http://www.mersenneforum.org/attachm...6&d=1199113967

Good article, explaining GTL and also a table of values per VTT settings (but don't take them as concrete - GTL for NB will change per board, and Core GTL's will changer per CPU but they're very good starting points).
 
It's a setting to do with VTT voltage, and usually runs around 67% of VTT but going off the 67% mark can help in times when the system isn't that stable. Fine tuning them will let you run lower volts than leaving them disabled and pumping volts into everything.

Courtesy of Praz of XS:
GTL 1/3 corresponds to the first two threads of Prime95. GTL 0/2 matches up with threads 3 and 4. If either thread for one core consistently fails adjust the CPU GTL for that core. If the failures are random between cores adjust NB GTL. You need to use Prime95 v25.6d.

http://www.mersenneforum.org/attachm...6&d=1199113967

Good article, explaining GTL and also a table of values per VTT settings (but don't take them as concrete - GTL for NB will change per board, and Core GTL's will changer per CPU but they're very good starting points).

Excellent. Cheers for that. So basically they're a way of fine tuning without the need for just shoving more voltage through everything. :) Sounds good, will have to take a look later on.

Currently at 3.2Ghz. Tightened up some Memory options to "Fast" and "More Aggressive" and gained some more bandwidth. Going well so far.

Cheers.
 
CMon push it more ! 3.2 is for girls!

Got mine running at 3.9ghz under water so I'm sure you can get 3.6+ !

Haha but I only have a Reserator v2. Currently it idles between 37 - 42ºC depending on the core. Under load (3DMark06) it rises to 54 - 58ºC.

I'm waiting on my order of special wet n' dry to arrive. Goes all the way to 8000 grit. lol. Super smooth! So hopefully when I lap the CPU it'll run cooler as well. :)

But yeah, will get back to pushing some more.... :p
 
Excellent. Cheers for that. So basically they're a way of fine tuning without the need for just shoving more voltage through everything. :) Sounds good, will have to take a look later on.

Currently at 3.2Ghz. Tightened up some Memory options to "Fast" and "More Aggressive" and gained some more bandwidth. Going well so far.

Cheers.

with a 1/2 decent Q6600 you should be good to atleast 3.8ghz till you need to start fiddling with reference voltages :)
 
3.4Ghz. :) Had to bump RAM from 2.0v to 2.1v in order to become stable @947Mhz (info in screenshot). May try and reduce this slightly later on as it has lots of small increments inbetween and I just jumped from 2.0v to 2.1v.

CPU I had to bump from 1.24v to 1.25v in BIOS also. CPU-Z and CoreTemp reporting slightly higher than what is set.

3_4GHz_OC.jpg


...getting there like lads! lol.
 
Back
Top Bottom