Help with overclocking

Nic Miller

Nic Miller

Nic Miller

Associate
Joined
18 Mar 2007
Posts
161
Just a quick question, I have started to overclock my system - P5N32E-sli, 2Gb GeIL, E6600.

Have done the following:


Set everything to manual and disabled all the usual suspects eg spread, CE1
Have set the FSB:RAM to unlinked
Put FSB at 1,290
RAM to 800
Put RAM voltage up to 2.1v
Put timings as 4-4-4-12 2T - everything else to auto
Put 1.2V HT to 1.3
All other voltages except to auto

This gives me an overclock to 2,902 Mhz and Orthos priority 10 runs with no errors (did for 3 hours last night until I stopped it) - although the system slowed to a snails pace while it was doing it - normal?

My question concerns the Vcore voltage - it is set to auto and with the above settings the computer puts it on 1.38-1.41 (measured by AI probe) - am concerned that if I up the FSB any further the voltage will rise to high - should I set it manually and if so what to?

I only want 3Ghz clock so didn't expect the Vcore to even get as high as it has now!

Any other suggestions welcomed.

Thanks

Nic
 
I found my E6600 did 3GHz at around 1.36V as reported by Speedfan so that might be a good place to start.

Don't worry about giving it a high-ish voltage to start with, as once you have found your stable OC, you can just keep knocking the VCore back until it is as low as poss without being unstable.

EDIT: An FSB of 334 [or 1336 if that's how your board displays it] should give you bang on 3GHz so you're probably best starting there
 
You should be able to simple things like browse and maybe listen to music, but anything more will probably appear slow.

Also, in Orthos, what priority has been set?
 
Your system will be very slow with orthos set to priority 10 so dont worry about that.
With regards to the overclock you will be better off setting the vcore manually. A e6600 shouldnt need too many volts to get to 3Ghz. I would try setting the vcore at 1.35v and then test for stability. If unstable, up the vcore untill you get your system stable. If it is stable, it is worth reducing the vcore as much as you can whilst still maintaning stability to help reduce temps.
 
Just pushed to 3Ghz and set Vcore to 1.375 to start with. Seems stable and am happy with that - only prob is I still cannot get 3DMark to run - just crashes system. SO I don't know if my system is actually faster !

Just don't want it to lock up as last time I had to reformat the HDD ! - although that was using AI booster from within windows.

Cheers

Nic
 
3DMark is more for graphics so it wouldn't have shown a massive increase in pointage anyway I would have thought.

The fact that you have overclocked automatically means it is faster :D

Try reinstalling 3DMark and then see if it works.
 
Obviously its still GPU orientated but cpu's (especially dual core) are now utilised a lot more and are reflected in the overall and 'cpu' score.

A CPU overclock can stop intensive applications from working such as 3dmark even when it has been 'orthos stable'. I run my Orthos on 'blend' to test for overall system stability, is that what test you ran?

Small fft's - CPU
Large FFT's - CPU, cache, memory controller & a little ram
Blend - all of the above

Orthos is an 'indication' of system stability and by no means does it prove that it is 100% stable - it is however the best indicator of stability thats why so many use it ;)
 
Last edited:
I love Orthos - I wish I used it when overclocking my 4400+ last year. I also like the Gromacs testing as my computer usually folds 24/7.

I would suggest th OP reinstall 3DMark and see if it works. If not it could be a stability issue.
 
I couldn't get 3Dmark to run even before I overclocked. Tried 05 and 06 and reinstalled and downloaded a few times to discount those.

Their website mentions this as a possible problem and talks about running it with -nosysteminfo at the end of the target line - but didn't understand what they meant or how to do it.

System is stable in Orthos using priority 10 on small FFt and blend and oblivion for hours !

Bit concerned it doesn't want to play though as it is putting doubts into my mind about my hardware - although it all seems to run fine with no crashes, lockups etc.

Cheers

Nic
 
My opteron system suddenly decided to stop running 3dmark 06 last year. One day it just decided it wasn't going to run it. Reinstalling it didn't help. There was a way round it someone suggested on here. I'll try to find it...

[edit] here we go
 
Last edited:
Find or create a shortcut to the 3DMark .exe and right click on it and choose properties.

In the properties dialog you should see a text field marked "target". In the box will be something like:

"C:\Program Files\3DMark\3DMark.exe" [or similar]

At the end of this [AFTER the last " add the -nosysteminfo flag

ie:

"C:\Program Files\3DMark\3DMark.exe" -nosysteminfo

Click OK then run the shortcut.

From what I have read recently 3DMark reads system info during startup and on occassion it has a paddy and doesn't work. Using the nosysteminfo flag tells it to skip this step.

EDIT: Damn too slow! [as an aside, you dont need quotes around the flag :o]
 
You must log in or register to reply here.
Back
Top Bottom