Looking good , what are your temps and volts?
thanks shaftyboyire yep think your right like i said earlier got into 3500 easy but temps put me off big time after orthos had been running 5min.You'll easily do 3.4g, infact i had it running at 3.375, under full load playing BF2142 for 10 hrs with avg temp of 48degrees.
Have left orthos running while i've been out & clocked 15hrs @3300 so that's a 24/7 setting will try 3400 think like u say that may be doable on air. & is about spot on where i was thinking of I love it when a plan Finally comes togetherAm looking at a 24/7 oc to around 3500 dual coreis the intel equivalent of amdtweaker, enabling the manipulation of memory timing parameters from within windows. The options can be saved & run to change timings every time xp starts. Or you can simply use it to investigate what the bios is setting those auto timings 2, As far as memory goes it's a bit more informative than the memory page on cpu-z.Down load MemSet memory tweakerMem Set 3.1: I've never used this tool before, what does it do? Is it of good use?
luck
Some one suggested the following volts:
MCH (VMCH = 1.55v
FSB Voltage = 1.4v
CPU (VCORE) = 1.4v
Memory = 2.1v
Memory Timings = 5 5 5 12
Temps: were 43 degress idle and 49 degrees fully loaded durning tests.
I used these as a starting point for oc'ing. When I started going for the 400 FSB i had to mess around with the voltages on the NB and SB. After many attempts it was too unstable over 400. How ever setting the memory timings did help it at 3.6gig.
I was able to hit 380mhz FSB with all volatages etc on Auto.
Last edited by shaftyboyire; 16-02-2007 at 04:27 PM.
Those cpu temps would worry me, they're at idle right ??. Have you checked temp using TAT which is supposed to be the most accurate. what vcore are u at couln't see it on your pic?
Last edited by Supershanks; 16-02-2007 at 05:14 PM.
v core is 1.072v NB 1.58v, the first pic is under full load and the second is idel. I find it very strange cus at 2.5ghz my temps are the same as stock.
Last edited by No.72; 16-02-2007 at 05:23 PM.
hmmmm
I just installed TAT as suggested. Should I be worried that the temps displayed are 10 degrees higher in TAT? Or is that some kind of error?
Idle its showing as 55-57 degrees??
Motherboard: Asus Commando
CPU: Intel E6600 2.4g @ 3375mhz
Memory: Corsair XMS2 Pro 6400 (800mhz)
Graphics: X900 + X1900XTX Crossfire
RAID 1: x250g (x2 250g SATA2 7.5k)
Storage: 500g + 300g SATA 2 7.5k
Sound: XFI Platinum
Montior: Samsung LCD 913n
Mouse: Razor Copperhead
Keyboard: Saiteck Illuminated
Bench Mark: 3d Mark 06 = 10747
Yep that is too high imo, if it is idel it's hotter than mine
My first commando that I RMA'ed had temp issues too.
well i've just reset the bios and i am getting a reading of 37 degrees in the bios. Yet once i load TAT its at 44 degrees.
mmm not good at all grrrrr damn you Asus! lol
but that would mean while I was oc'ing i was getting temps towards 80 degrees ffs.
Isn't it strange how the system was stable at such high temps? Im thinking TAT isn't 100% either
Motherboard: Asus Commando
CPU: Intel E6600 2.4g @ 3375mhz
Memory: Corsair XMS2 Pro 6400 (800mhz)
Graphics: X900 + X1900XTX Crossfire
RAID 1: x250g (x2 250g SATA2 7.5k)
Storage: 500g + 300g SATA 2 7.5k
Sound: XFI Platinum
Montior: Samsung LCD 913n
Mouse: Razor Copperhead
Keyboard: Saiteck Illuminated
Bench Mark: 3d Mark 06 = 10747
it's strange the way these temp utilities vary. Tat is supposed to read temps direct from cpu, whilst asus use an indirect measure. are u running the latest pcprobe.
Many find that probe understates temps. In my case probe seems to understate when initially loaded or on idle but when under load both utilities are +/1C only between them.
i'm an 1.5hr into orthos run on 3400 & tat is at 58/57C 57C pcprobe.
Yay I have hit 500 fsb and got it to boot.
again the temps are really bad . this board keeps on For some reason now the system does not seem to hang, it boots into windows after every change made.
that is going to the limit for me on that cpu atm unless asus sort out the tamp issues.
oh and btw this is idel :0
What does it hit under load?
This wont boot at 500fsb at all.
humm it go's up to high 70's! before I have to stop. I know I can get it to boot higher than 500, but I don't want to try it due to the temp issues. It is ether; your board is a dodge one (it is looking that way sry), or the commando with it's current BIOS does not like your other components. Cus looking at your cooling and RAM it should be easy.
or 'photobucket'
Think i've found my 24/7 clock
sorry about your board clunk.
Edit:
Ran this
Then remembered seeing this Asus P5B-Deluxe: Overclocking and Tweaking Guideso went from 205 to 210selecting 120 or so can add a healthy boost to PCIE bandwidth if the cards you have can run this frequency. This option needs to be tested thoroughly to see how much the video cards can stand.110 is usually very safe, 120 is starting to push it a little
xtra 7 points. .
Dropped my cpu volts from auto to 1.4625 on auto think i was running at 1.4875~1.475 bios. Should save a few degrees. will re-run orthos tonight to verify it.
feel guilty seeing clunks results but am now enjoying this rig
Last edited by Supershanks; 17-02-2007 at 03:37 PM.
There are currently 1 users browsing this thread. (0 members and 1 guests)