Need some help with an overclock

[clevere1]

Hey guys, I have a problem. I can't seem to get my E6600 past 2.8 gigs without prime or Orthos failing with this type of error:

FATAL ERROR: Rounding was 0.46875, expected less than 0.4

The Setup is as follows:

EVGA i680 Motherboard
Corsair TWIN2X2048-6400 2GB Kit DDR2-800 XMS2-6400 Xtreme (2 gigs total) (5-5-5-12 2T))
Intel Core Duo 2 E6600:
Family 6, Model F Stepping 6 Revision B2

EVGA 7900GT (not over clocked)
Seagate SATA
Zalman 9500 Cooler

I've unlinked the memory, and FSB, and left the memory at stock, and even increased it to 850, but I get the same error no matter what. When the error occurs with both Prime95 and Orthos, it seems CPU 0 is the one biting the dust. CPU 1 keeps on running.. I've tried playing with voltages for the CPU and memory (within limits) and nothing makes a freaking difference. I'm at a loss, and would appreicate any help. I'm somewhat new to overclocking, but I've been reading, and many people have been able to bump up the speed, but I'm not able to.

I'ved:

Adjusted FSB only, and let the mainboard control the voltages. Same problem, anything over 2.8gigs fails or causes reboots.
Adjusted FSB, and CPU voltage, same as above
Adjusted FSB, CPU and CPU FSB voltage, same as above
Adjusted FSB, CPU, and memory voltage (to 2.2) same problem.

Heat doesn't seem to be the issue. Things get warmer, but not past 55-58C

Here are a couple of pictures of the bios settings (I'm not using the nvidia software to make bios adjustments, just using it for reference). This is at 2850mhz, and prime95 and orthos still error out. Any ideas?

Picture 1 of the bios
Picture 2 of Bios
Bios settings #3

I forgot to mention, I had this exact same problem with the Asus P5B board.

 

[lxskllr]

You may have a chip that doesn't want to be overclocked How are you measuring temps? The older utilities, and motherboard software under report temps by a large margin. Check out the Intel thermal analysis tool for accurate readings.

 

[redhawk56]

Take a screen shot of your cpuz main tab and memory tab and spd tab and post them please. I think this is a memory issue of some kind. I'm not sure I read your memory speed in the bios correctly so I want to see cpuz.

 

[redhawk56]

I think what you will find is that those latency numbers are the SPD for 533mhz. I was pretty shocked by that with my crucial ballistix.

According to the specs I found, those latencies are tested at 2.1v at 533mhz. So that may be part of your problem. Still do the screen shots and post them so I can take a look.

I think what I would recommend would be to put the memory at 1:1 with the FSB and start over at stock and go up again. But I want to see the cpuz tabs first. Thanks!!

 

[Noubourne]

My mobo has Memtest 86 that I can enable and it will boot into it instead of my OS for testing RAM stability at given settings. It really helps to narrow down what is causing instability for troubleshooting.

Looks like your motherboard has a similar feature. Enable it and see if your RAM is stable.

You might try starting from stock speeds too! If you're undervolting your RAM (and I agree it seems like you are undervolting them by at least .2v), then that would explain your stability issue.

 

[clevere1]

Ok, I will do that tonight when I get off work. Thanks in advance for the help.

 

[clevere1]

One thing I can answer now. The memory is indeed 1.9v:

Retail
2048 Megabytes of memory in a pair of 240-pin DDR2 DIMMs
Two matched CM2X1024-6400 modules
Implemented using 64M x 8 DDR2 SDRAMs
100% tested at 800MHz in high performance DDR2 motherboards
Legendary Corsair reliability and service
TEST SPECS
Each module pair is tested together in an Intel-based motherboard at 800MHz
Tested and packaged in pairs
Packaged together immediately following system test
Tested at 5-5-5-12-T1 latency settings at 1.9V
SPD programmed at 5-5-5-12-T1 values


Looks like the T value I have is a little low, I can set it to T1, but that wouldn't explain the problem I'm having

 

[genec57]

I have almost the same hardware as you except that my Corsair memory is DDR2- 5400C4 as opposed to your faster, better 800 ram. I am running at 3400 with no problems and have held 3600 with several hours torture under prime 95.
I do note that your screen shots are from Ntune.
NTune has never been the best. You might get better results making all your settings directly in bios.
I didn't see your Vcore. At 3400 my Vcore is 1.375
Also, you might try to further loosen your memory to 5,6,6,15,T2 at 2.0. If that results in stable prime 95 you can gradually tighten from there.
I really think that your biggest problem lies in using ntune.
Good luck

 

[clevere1]

Originally posted by: genec57
I have almost the same hardware as you except that my Corsair memory is DDR2- 5400C4 as opposed to your faster, better 800 ram. I am running at 3400 with no problems and have held 3600 with several hours torture under prime 95.
I do note that your screen shots are from Ntune.
NTune has never been the best. You might get better results making all your settings directly in bios.
I didn't see your Vcore. At 3400 my Vcore is 1.375
Also, you might try to further loosen your memory to 5,6,6,15,T2 at 2.0. If that results in stable prime 95 you can gradually tighten from there.
I really think that your biggest problem lies in using ntune.
Good luck

I'm actually not using Ntune, I used it to take shots of the "Bios" settings (since ntune reads the current settings) to make it easier to provide as much information as possible. I've been making all my adjustments directly in the bios. I'll have to see what the core voltage is when I get off work.

What stepping is your CPU?

 

[genec57]

It is Model F, Stepping 6, Rev B2 the same as yours.
I think the error you are getting is most often memory.
I just noticed that you had the same problem with the ASUS board. As an earlier poster said you just may have a chip that doesn't want to oc. Have you tried memtest to isolate a possible memory prombem?

 

[clevere1]

Originally posted by: genec57
It is Model F, Stepping 6, Rev B2 the same as yours.
I think the error you are getting is most often memory.
I just noticed that you had the same problem with the ASUS board. As an earlier poster said you just may have a chip that doesn't want to oc. Have you tried memtest to isolate a possible memory prombem?

Yup, I've tried memtest and a couple of other Dos based memory testing applications. None of which have turned up any memory errors. I've tried running single sticks, testing them one at a time, with the same results both times. I can borrow some known good memory if needed, but I'd like to try and nail it to the memory before I bother someone with borrowing thier stuff.

 

[myocardia]

Originally posted by: clevere1
I can borrow some known good memory if needed, but I'd like to try and nail it to the memory before I bother someone with borrowing thier stuff.

Then give your processor some voltage, and report back with the results.

 

[clevere1]

Originally posted by: redhawk56
Take a screen shot of your cpuz main tab and memory tab and spd tab and post them please. I think this is a memory issue of some kind. I'm not sure I read your memory speed in the bios correctly so I want to see cpuz.

Here we are!

Cpu-z 1
Cpu-z 2
Cpu-z 3


Ok these are taken with the system @ 2800mhz, for stable operation while I am at work, so nothing gets corrupted while my wife uses the computer.

Now I double checked, and according to the bios I am currently running the memory at 806mhz....

Thanks to all for the help, it is greatly appriecated.

 

[clevere1]

Originally posted by: myocardia

Originally posted by: clevere1
I can borrow some known good memory if needed, but I'd like to try and nail it to the memory before I bother someone with borrowing thier stuff.

Then give your processor some voltage, and report back with the results.

I've got the processor voltage set to auto as it is, because I'm not quite comfortable adjusting it myself...

 

[cmdrdredd]

Originally posted by: clevere1

Originally posted by: myocardia

Originally posted by: clevere1
I can borrow some known good memory if needed, but I'd like to try and nail it to the memory before I bother someone with borrowing thier stuff.

Then give your processor some voltage, and report back with the results.

I've got the processor voltage set to auto as it is, because I'm not quite comfortable adjusting it myself...

set it to 1.4v to start see if it works. Auto is always bad IMO

 

[redhawk56]

Put your memory at 1:1 with your FSB and put the memory timings on auto. But you will need to increase the vcore a little too. Put it up to 1.4v. They can handle that easily.

 

[clevere1]

OK, I've increased the cpu voltage to 1.4
Increading the memory voltage to 2.1 causes windows to restart.
Set memory back to 1.9
Set FSB to match 2.9 gigs, set memory fsb to 739
restarted
No failure with Prime, or Orthos
restarted, set cpu FSB to match 3.0 gigs, memory still at 739
restarted
Started Prime95, normally after the first 3 seconds, it would fail. It has not as of yet.
Hmm .. Indeed, my memory is crappy?

 

[cmdrdredd]

Originally posted by: clevere1
OK, I've increased the cpu voltage to 1.4
Increading the memory voltage to 2.1 causes windows to restart.
Set memory back to 1.9
Set FSB to match 2.9 gigs, set memory fsb to 739
restarted
No failure with Prime, or Orthos
restarted, set cpu FSB to match 3.0 gigs, memory still at 739
restarted
Started Prime95, normally after the first 3 seconds, it would fail. It has not as of yet.
Hmm .. Indeed, my memory is crappy?

your memory is the issue. Corsair is junk IMO unless you're buying extreme high end parts from them. Sorry.

 

[redhawk56]

Originally posted by: clevere1
OK, I've increased the cpu voltage to 1.4
Increading the memory voltage to 2.1 causes windows to restart.
Set memory back to 1.9
Set FSB to match 2.9 gigs, set memory fsb to 739
restarted
No failure with Prime, or Orthos
restarted, set cpu FSB to match 3.0 gigs, memory still at 739
restarted
Started Prime95, normally after the first 3 seconds, it would fail. It has not as of yet.
Hmm .. Indeed, my memory is crappy?

No....not really......these c2d processors like to be at 1:1 with the FSB. Keep them together and it will go higher. Watch the temps though. Sorry you probably know that.

If it were my machine, I'd run memtest86+ instead of prime. If it passes 15 minutes of that, go ahead and boot windows and run a super pi 1 mill and then a super pi 32 mill. If you get past that.......you are probably ok. No need to beat it to death in prime.

 

[clevere1]

The memory isn't 1:1. The machine wouldn't even boot it was. Right now the memory is 788, anything over or below that causes failure

 

[clevere1]

your memory is the issue. Corsair is junk IMO unless you're buying extreme high end parts from them. Sorry.

Better than the PNY I had

 

[clevere1]

So I downloaded the Intel Thermal Tool. It says the cores are runnin around 60-70c. Is this bad, good, indifferent?

 

[cmdrdredd]

Originally posted by: clevere1
So I downloaded the Intel Thermal Tool. It says the cores are runnin around 60-70c. Is this bad, good, indifferent?

at load that's normal for some people.

 

[redhawk56]

Originally posted by: clevere1
The memory isn't 1:1. The machine wouldn't even boot it was. Right now the memory is 788, anything over or below that causes failure

Your memory isn't stopping you from running at 1:1,

Put the FSB at 333 and I bet the memory will work at 1:1.

But watch those temps. The thermal spec for your cpu is somewhere in the low 60s. Dont let it go over that for long.

Also, try the vcore at 1.375 now that you are past your other problem. That will cool it off a little.

 

[lxskllr]

Originally posted by: clevere1
So I downloaded the Intel Thermal Tool. It says the cores are runnin around 60-70c. Is this bad, good, indifferent?

You want to be on the low side of that. I wouldn't be comfortable going over 62C. I forgot to turn my fans up while using Orthos one time and when I got to about 65C the test failed after about 2 minutes. I tried it again with my fans turned up and it went almost 3 hours before failure. I had to drop my speed a bit, but the real point is how temps can affect your overclock.