E2160 Overclocking Help - on IP35-E Motherboard

[itakey]

So I am just getting started with my overclocking on my new Rig. Thanks to SerpentRoyal for helping along the way!

My System:
CPU: Intel E2160 dual core
Mobo: Abit IP35-E
RAM: 4X1GB HP PX976AT $9.99 after rebate ram
380W Antec Earthwatts Power Supply

Memory Overclocking
I did a ton of MemTest86 test #5 loops with the memory at the 1:1.00-DDR2-666 at 1.85V and it kept on testing well past 60 or 70 and never reported any errors.

___________________________________________
So I am started my first cpu/ram stress tests running Orthos for 10+ minutes and using Core Temp to watch my temps.


CPU Overclocking

First overclock test was:
SP2004 Orthos Blend - Stress CPU and RAM
300X9=2.7GHz at 1.345Vcore
1:1.00-DDR2-666 at 1.85V

The Result:
11+ minutes of Orthos went by and both of the 2 cores hovered around 58C and never went over 61C at 1.345Vcore.



Second overclock test was:
SP2004 Orthos Blend - Stress CPU and RAM
333X9=3.0GHz at 1.365Vcore
1:1.00-DDR2-666 at 1.85V

The Result:
11+ minutes of Orthos went by and both of the 2 cores hovered around 61C and never went over 63C at 1.345Vcore. In the 11th minute it went up to 65C.

Since my second overclock test passed 11+ minutes, I decided to leave the settings the same, but ran the different SP2004 Ortho's - Large test.




Third overclock test was:
SP2004 Orthos Blend - Large, in-place FFTs - stress some RAM
333X9=3.0GHz at 1.365Vcore
1:1.00-DDR2-666 at 1.85V

The Result:
11+ minutes of Orthos went by and both of the 2 cores hovered around 65C and never went over 66C at 1.345Vcore.

___________________________________________

I don't need to push it for every bit, I just wanted to get to 3.0GHz as stable as possible. Should I be doing anything different with the memory? Or is it good at the 1:1.00 DDR2-666?


Should I be happy with this overclock and leave it here as a very stable machine?

 

[SerpentRoyal]

Drop Vcore to 1.325 or 1.345 and see if PC is stable at 3.0GHz. You could also use 1:1.20 memory divider to overclock RAMs, but you may need to bump RAM voltage to 2.0V. Those RAMs should work fine at 1.8V/333MHz FSB.

I would use the lowest voltage and highest FSB that will get the CPU up to 68-70C range after one hour of Orthos Large mode.

 

[MarcVenice]

I wouldn't bother overclocking the ram, the speed increase will be negligible, if there will be any at all. It's only going to cause instability if you ask me. The ram will do just fine running at stock speeds.

 

[itakey]

So I put the side of the case on, since I didn't have it on before and ran the last test again and it failed after 14 minutes. Current settings are:
333X9=3.0GHz at 1.365Vcore
1:1.00-DDR2-666 at 1.85V

Guess i'll leave the ram where it is, but I want to get the CPU in a nice stable place around 3.0GHz. What are some other acceptable combinations I should be trying?

 

[SerpentRoyal]

Run Memtest86 again with the side on. Sounds like you may need to increase air flow across the case. If RAMs are good, then run Orthos large mode and watch coretemp. Limit peak temp to 75C. You may need to increase Vcore by one notch.

 

[itakey]

It is currently running around 37C to 40C with the side on, and at the 3.0GHz specs I have listed above. I have a nice heatsink with fan, a rear fan, and a front fan so it may be sufficient.

What MemTest86 test is best? The test #5?

 

[SerpentRoyal]

I like test #5...fast and will often spot RAM problem. I think your RAMs are okay. Still need to check CPU load with case on. 1.385 will probably do the job.

 

[itakey]

Thanks for the test #5 confirmation.

I am running ortho's large test again to see if it errors. It is at about 66C to 67C after 4 minutes. Will let this run for 1 hour, or till it fails and post back. I will then try to raise up the Vcore like you mentioned to 1.385 and see what's up if it fails on this current test.

 

[itakey]

Test finished over 1 hour of Orthos large and climbed to 70C once, and maintained around 68C.

 

[SerpentRoyal]

Good enough for use. It's normal for CPU temp to go up 3 to 5C inside the case (especially if you don't have a down-draft CPU cooler with a side vent).

 

[itakey]

Currently it is cruising at 39C to 40C which seems reasonable I ran a few real world tests playing with some graphical programs and the CPU temps didn't go over 45C so everything seems to be good for now.

SPEED Overclock from stock to 3.0 GHz with minimal efforts!

 

[SerpentRoyal]

Don't forget to put the CPU fan under automatic control. System will be whisper quiet when idling.

 

[itakey]

CPU Auto control in the bios right?
What should I put my target temps too? I think it is set at 50C maybe? Currently the machine is at around 38C to 40C and is running nicely

How about the System fan control. Do you use that too?

 

[SerpentRoyal]

Originally posted by: itakey
CPU Auto control in the bios right?
What should I put my target temps too? I think it is set at 50C maybe? Currently the machine is at around 38C to 40C and is running nicely

How about the System fan control. Do you use that too?

On page 2-18. Enable CPU FanEQ control. Use 3 pin for CPU FAN TYPE. 45 to 50C target is good. You can also control another fan via SYSTEM FAN header. I use CPU as the reference temp.

 

[itakey]

Already swapped it up to 3 pin and have it at 50C. Maybe i'll drop it down to 45C to see if it actually does anything.

By the way, how many RPM's do your fans run? Mine are currently quiet and is showing in abitEQ as:
CPU: 1175
System: 850
Case - Front Fan: 1650

 

[SerpentRoyal]

That's about right. Use the lowest possible limit for the fan (50%).

 

[itakey]

So I decided to run another Orthos Large Test, and it failed after 1 hour and 12 minutes at these settings:
333X9=3.0GHz at 1.365Vcore
1:1.00-DDR2-666 at 1.85V

Should I be changing it up?

 

[SerpentRoyal]

Bump Vcore to 1.385 if your RAMs passed Memtest86. I personally would use as is since build-up heat can cause instability. Test the true stability with your software.

 

[itakey]

Ok, am going to do that. So when I change the VCore does that effect the ram too?

My software is the latest Windows XP Pro which should be at least stable enough to run

 

[2dee]

How's max FSB you could achieve ( prime stable ) with IP35-E board and E2160?
Mine only do 350 MHz stable, anything higher than 375 will result in board unwilling to post.
Yesterday i've tried to increase the GTLRef to 67%, and the system boot until 390 MHz and
it's prime stable ( passed 12 hrs of orthos blend test ).

But with 390 MHz the system sometimes won't boot ( blank like it's too high OC ). This is weird because it's prime stable.
My RAM is not the limitation, i'm testing with Corsair CMX6400 C4 ( rated at 400 MHz, 2.1V, 4-4-4-12 )

Here's my config for testing:
Multi : 6x ( set to 6 so CPU clock is low )
C1E and EIST : Disabled
Mem Ratio: set to 1:1
VCore: Default
VMEM: 2.1V
VTT: Default
Northbridge: 1.29V
Southbridge: 1.55V
GTLRef: 67%

Is this limitation because of my CPU FSB is only 200 MHz. Because I've seen other ppl can do up to
480 to 500 MHz FSB in this board using CPUs with 266 or 333 MHz FSB.
Any advice for achieving 400+ FSB with IP35-E and E2160?

Thx.

 

[Tweakin]

Originally posted by: itakey
Ok, am going to do that. So when I change the VCore does that effect the ram too?

My software is the latest Windows XP Pro which should be at least stable enough to run

If this machine is not your primary puter...I'd say it's all good, but if it was I would say running 1 hr of Prime or Orthos is not enough to call it stable by any stretch. I have had many systems fail around 10-12 hours...Just my 2 cents.

 

[myocardia]

Originally posted by: itakey
So when I change the VCore does that effect the ram too?

RAM voltage and CPU voltage are two completely different things, hence the different names.

Originally posted by: Tweakin
If this machine is not your primary puter...I'd say it's all good, but if it was I would say running 1 hr of Prime or Orthos is not enough to call it stable by any stretch. I have had many systems fail around 10-12 hours.

Agreed, 10-12 hours is the minimum, and just because you can go that long doesn't mean your system is completely stable. It just means that you're Prime or Orthos stable. If you start having programs crash, or BSOD's, you still have some tweaking to do.