Timings

Ok - I'll drop the tRD back to 7 which the mobo would select on Auto (latency changes by around +10% with tRD 6 to 7. If I can get a clean test at that setting then we are heading in the right direction.
After much research I think I've got all the correct timings although a few may be loose - Im waiting for an email from OCZ to list me the correct settings for my mem and mobo.

~Scotty
 
mem 2.1v 1065 (not sure of ratio)
cpu auto
NB auto
FSBv Auto

I'm gonna lower the mem ratio a bit and see what volts I need to get a post and boot - is that a good place to start?

~Scotty
 
If you tried to change the FSB from 333MHz to 355MHz while still using the [8:5] Memory-Multiplier then that would be trying to run the RAM @ 568MHz (DDR2-1136) which it probably didn't like!

If your sure that 333MHz-FSB is stable with DDR2-1066 then drop the Memory-Multiplier to [1:1] sync and slowly but surely bump the FSB up from 333MHz to 400MHz if you can. Your not testing the Memory at this point but your Motherboard and your Chip, you need them both stable @400MHz-FSB before you can continue really . . .

Not sure how your chip will cope at 3.6GHz so maybe worth while dropping the CPU-Multiplier from [x9] to [x8] and see how you get on! :cool:
 
The ratio was changed so mem was clocked at 1065

Ok no probs - I did try something similar with all the mem in but strangly it would'nt boot at x8 400FSB (with ram ratio dropped down to 800Mhz ish) but when I changed the multi to x9 it would boot but wasnt stable for gaming.

It's definately the cooling thats stops me getting a stable 3.6Ghz (Everest starts to throttle the cpu as the temp peaks around 85C, my H50 hopefully will cool it better;)

For now lets see if we can raise the bar a bit more like you suggested - even if it means under clocking the mem for now. Keeping the mem at 1:1 I'll see how far I can go and tweak the CPU volts. Might I need to volt the FSB more or not?

~Scotty
 
Last edited:
strangly it would'nt boot at x8 400FSB (with ram ratio dropped down to 800Mhz ish) but when I changed the multi to x9 it would boot but wasnt stable for gaming
Ok there is a reason for this happening but before I explain can you confirm if the Nortbridge volts (vNB) was on [Auto] or was it manually set?
 
I'm not too sure what it was on at the time, it may have been up a couple of notches or on auto.

That Crucial mem of yours is clocktasic, I got a matched pair of Crucial Ballistix 2x1GB (DDR2-666 3-3-3-) for £15 squid - Im interested to see how it performs, im sure i can get my money back if they arnt so good but it the love of tinkering that counts:D
 
Last edited:
I'm still here Wayne, just doing testing still, now I have the H50 in I'm hoping to get the FSB upto 400x9 so we can run 1:1 and work this clock out.

Ill post soon ;)

~Scotty
 
No probs, I wonder if your E2160 can reach 3.6GHz (9x400), if so you can then take the memory off [1:1] sync and switch it back to to DDR2-1066, that alongside a 3.6GHz Processor and 1600MHz System Bus should be sweet! :cool:
 
I got it running at 3.6 GHz with the temps just fine, it runs bench marks with no issues but I still got the problem of real world crashes at the moment (Gaming on Crysis) - I'm just tweaking to see if I can stablise it (with some success) until I'm 100% happy.

***EDIT***
I maxed out at 3.7Ghz but, as I had to raise the CPU volts, temps becaming a problem again while running benchmarks. So I'm still testing at 3.6Ghz - all benchmarks are solid but I'm getting just the odd glitch in games

~Scotty
 
Last edited:
I've never used Prime95 before - can you tell me how to set it for small FFTs and do I need 2 workers? one for each core?
 
Just download it, unzip it to your PC testing stash folder and run it, tell it your stress testing and then choose Small FFTs for CPU stress or Blend for Memory/Northbridge test . . .
 
AHHH! Prime95 just battered my PC into next week.:eek: LinX, Intel burn test,Everest all run for hours with no probs. Then Prime BSODed me in seconds. I tinkered but couldnt get past 3rd test so I dropped down to 3.5GHz ......then to 3.4GHz before I could run 13 tests without error. Going to have to rethink this situation!! Is the small FFT test only cpu intensive?

~Scotty
 
cpuconfig.jpg
dram.jpg


voltages.jpg
onel.jpg


pic1un.jpg
 
Last edited:
Not sure about the voltages
Chuck all the voltages back onto [Auto] *except* your RAM and CPU, only adjust the voltages one at a time then Save & Exit before going straight back into BIOS and adjusting the next one. If you can do that and keep getting back into BIOS then drop the CPU multi to x8 (Save & Exit) then straight back in and adjust the FSB up to 400MHz . . .

If that doesn't work then take the vNB voltage off [Auto] and bump it manually until it works

400MHz FSB
500MHz Mem (DDR2-1000)
3200MHz Processor (8x400)
 
Back
Top Bottom