Need some help 1st OC....E6600/Striker

Joined
Nov 16, 2006
Messages
50
Well finally got my temps in line and ready to start OC'ing! :)

Running a water cooled E6600 with 2 gig Crucial Anniversary 5300 DDR2

Not having much luck keeping a stable OC with Orthos with the best I have tested out (10 mins...haven't decided to really give it a go yet) was 365 FSB (3.285) at stock voltage mem at 730 (365) also stock voltage.

I can get orthos to go for about 30 seconds wtih the following settings:

400 FSB (3.600) at 1.65V (in bios) and memory at 800 (400) at 2.1V.

Looking for some advice where to go next. Thanks for helpin the new guy!
 
1.65v is too much to start with, especially for a E6600 will easy achieve 3.5ghz with 1.5v.
 
What is the best way to determine actual voltage? I understand the bios (I am using the newest 7.x) is not accurate. So the voltage you enter in Bios is actually lower on the chip. I used the higher number to try and achieve an actual around 1.55. If the idea is to use a 1.55 in the bios please let me know.

As for that thread...I have actually used a copy of that to begin. The settings I am using now are based from his initial stable 3.6 for his chip. Realizing my chip will not behave the same I began much lower. I actually hit a point where I couldn't boot into windows at all around 375-385 FSB and skipped up and was able to get in at 400 FSB.

I used Sandra to test the system and everything went fine. One caveat is that my idle temps in Windows (around 49-51) go to 59-60 at 100% CPU load. I was having heat issues previously and installed two 120 fans pulling in cool air over the radiator running around 2200 RPM. This brought my temps at stock idle to around 37C.

Thanks for the input...keep it coming!
 
Man, is that 1.65V CPU Voltage?

STOP RIGHT NOW!

If you have a good chip it might just do 3.6ghz with 1.5 or under and if it requires more than 1.55 it really isn't worth it.

The only way to find out how good your E6600 is to go ahead and try it yourself.

Set the CPU voltage to 1.4V and see what happends. If no go, then set it to 1.45.

Small steps, and please try and stay below 1.5!

Set the FSB to 401 and the RAM to 802

Disalbe C1E, speedstep, Thermal Control, and anythink Throttle or Spectrum related.

Set the FSB Voltage to 1.4
 
Hah..Thanks for the reality check.

I decided to start fresh from stock.

So far I am here....

Best Orthos Stable
FSB: 355 Mhz: 3195 CPUv: 1.33 Mem: 332.8 16:15 Temps(idle/load): 40/51

Not Orthos Stable
FSB: 365 Mhz: 3285 CPUv: 1.33 Mem: 331.8 11:10 Temps: 40/51

Gonna bump the CPUv to 1.34375 and give it another run. Best thing to do from here is bump voltage or are there other adjustments I should be making at this stage?

Thanks!
 
Under Voltages you need to set the correct RAM Voltage and set the FSB Voltage to 1.3 or 1.4V

Other Voltages leave as AUTO.

CPU Voltage needs to be set @ 1.4V or so. There is something called Vdrop which means that your Voltage in Windows is way lower than what you set it in the Bios.
Check it out yourself......

If you want to go any higher, up the CPU Voltage,

And, did you disable all the Spectrum, Throttle, C1E, Speedstep, TM Control...Options?
 
Yah...everything is disabled that should be.

I have been creeping the voltage up....to 1.38125 with no luck in Orthos. I will try 1.4.
How about the RAM. I noticed a nice OC by Evo which used a RAM voltage of 2.1 but I really have no idea where to go wth that one. I noticed the .02 drop in voltage when the system is loaded. I know the actual is below the bios setting too although SpeedFan which I have been using to get a more accurate read hasn't budged from 1.33 despite my moving up the voltage.

I am also using the new 701 bios....which I know keeps the AI Booster from installing. Gotta love a company that bios's out their own utilities. :rolleyes:
 
I believe your RAM needs 2.1V, ( Find the RAM specifications @ newegg.com)

Go into Chipset settings or so and under RAM select manual or expert timings and set the Advertised timings.

The voltage setting might be together with the CPU and FSB, MCH voltages. Look for Vdimm or RAM Voltage.

Bring the CPU voltage to 1.45 Volts and if it turns out stable, continue to lower it until you experience problems all over again.

Also, up the VMCH and VFSB voltages a bit (midway I guess)
 
Ok...

No better with increased voltage. Fails Orthos within seconds up to 1.4 and rebooted upon failing Orthos at 1.425.

No clue where to go now.....advice?
 
I have that printed and read some time ago and I believe Dan said he got better results not following it but I am open to trying whatever.....

Getting ready to call it a night so here was my last:

FSB: 360
Mhz: 3240
CPUv: Auto (CPUZ reads 1.248)
Mem: 332.3 13:12
Temps: 52 load

Ended up with the previous being Orthos stable for 10 mins (when I stopped it) using the CPU or RAM only testing. When using blend it twice stopped on me at exactly 4 minutes.

The error is
"Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
Torture Test ran 3 minutes 59 seconds - 1 errors, 0 warnings.
Execution halted."

Someone once posted:
"what type of error..is it the usual rounding .5 or...something with a lot of decimals i.e. .4890456894...cause usually (for me that is) when the rounding error has a lot of decimals it's ram..and if it's .5 it's lack of vcore..."

So I will give that theory a shot tomorrow by bumping my vcore again but that hasn't been much help previously and I am thinking I might need to pay a bit of attention to the RAM.

Looking forward to more expert insight!
 
To avoid having RAM issues you should use a 1:1 divider.

If you set your FSB to 360, use 720mhz for the RAM.


Also, MOST BOARDS are know for not liking working between 350 and 400 FSB and many times jumping all the way to a 401 FSB helps avoid problems.

Just set the RAM to 802mhz and the FSB to 401. CPU Vcore to 1.45V and report back!
 
To avoid having RAM issues you should use a 1:1 divider.

If you set your FSB to 360, use 720mhz for the RAM.


Also, MOST BOARDS are know for not liking working between 350 and 400 FSB and many times jumping all the way to a 401 FSB helps avoid problems.

Just set the RAM to 802mhz and the FSB to 401. CPU Vcore to 1.45V and report back!

Could not have said it better myself. It seems like a RAM/divider problem to me.

In that PM I replied to, just follow my steps and keep that 1:1 ratio - that is the one thing I forgot to tell you.
 
Here's the latest....

Seems like I can get into windows up to around 410 FSB using 1.52v however stability is the question. I haven't been able to get Orthos to run anywhere over 360FSB. I started playing with other tests just for kicks. I am able to complete Sandra "burn in" tests or individual tests no problem at higher settings. I can also complete 2 instances of Super pi @ 32M no problem. Aquamark runs fine but I have only completed a 3DMark once at 405 FSB. The results were great but I have been unable to repeat the feat after further tweaking...even when returning to those settings. Finally I ran some DOOM3 at full settings. It crashed at 410 and 405 but ran for a good 30 mins of gaming at 401.

Orthos though....just shuts down immediately not matter what.

Here are my current settings:

FSB: 401
Core V: 1.52 (Ntune and SpeedFan) and 1.60625 (BIOS setting)
*I can't get into Windows at all from FSB 401 or greater with less than a BIOS CPUv setting of 1.600. This consistently puts me reading around 1.49-1.52v in my monitoring programs.
MEM: 802
MEMv: 2.1
Timing: 1:1 5:4:4:19 25 2T

I can get these settings to boot at high FSB but I dropped it to try and achieve stability in Orthos (no go), 3DMark (been flaky) and DOOM3 (works at 401)

Get back with more (and some screenies!) soon.

BIG THANKS again....and for the record...I am having fun with this...so no (well minimal) frustrations on my part
 
Why are you using those timings?

1: Set the as advertised, at least the 4 fist values, the rest leave them as AUTO

2: You could also try leaving them under SPD while you test your system


Using too much voltage can also cause stability issues. See if you can do the same speed with a lower voltage.

And what voltages are you using for the FSB Voltage and SPP Voltage?

Those are the most important voltges other than the CPU Voltage.


I can overclock my CPU to 4ghz but I cannot get it to be Orthos stable no matter what.

However, it runs 24/7, lots of video encoding, music playing (40.000+ library), Gaming and other multitasking functions.

It's never crashed.....
 
Those are just the timings it auto sets when I plug in the mem speed.

Those are the minimum voltages for the CPU I have found allow me into windows at 401 FSB or above. Like I said though....the actuals are coming no where near the set.

FSB and SPP voltage I have left on Auto.

I will adjust some of the setting per your post although I am still not exactly sure where the mem timings should be.
 
you just got to see what works for you, for your specific set up, cuz someone with similar specs as yours gets a nice overclocked doesn't mean you are going to get the same, I got mine running at 4.05 33/40 ran prime for 2 hours stable, memory running at 4-4-4-4 and 1000. and it's stupid fast. but that's with the coolit Freezone, and crucial ballistix memory. good luck. and be careful as someone said small steps.
 
Those are just the timings it auto sets when I plug in the mem speed.

Those are the minimum voltages for the CPU I have found allow me into windows at 401 FSB or above. Like I said though....the actuals are coming no where near the set.

FSB and SPP voltage I have left on Auto.

I will adjust some of the setting per your post although I am still not exactly sure where the mem timings should be.

Set your FSB Voltage to 1.4V
And SPP to 1.45 or 1.5V
 
Tried to get a photo of my settings but put the file in a text document instead :rolleyes:

I will either link the file or list the settings I ended up with later tonight. So far the current settings at 3.55 seem stable. Memtest 86+ runs clean, as do super pi x2. Aquamark is good and 3DMark06 has completed successfully although honestly I should run it a few more times to confirm. Honestly I expect a few lockups when I run some games and will need some help troubleshooting at that time but haven't had the free time to play around.

I will update my settings here tonight.
 
Back
Top