• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

E2160 overclocking help....

jimbobaggies

jimbobaggies

jimbobaggies

Associate
Joined
16 Jun 2003
Posts
267
Location
Torbay, UK
System;

ASUS P5KC [0804 BIOS]
E2160
2GB OCZ PC6400 Platinum Rev 2 [4-4-4-15]
Corsair HX520
XFX 7800GT



System will run 2.4GHz without breaking sweat, 45C max on the CPU under load. I managed to get the system to boot at 3Ghz with memory at 400MHz (standard), but when I ran Intel Thermal Analysis Tool the system rebooted itself when I tried to open Everest. I then dropped the CPU to 2.7GHz, but it did exactly the same thing.....

Anyone with the same motherboard / CPU combo with any help on BIOS settings appreciated. Also, how do you work out the memory dividers? They seem to randomly change as I increase the CPU past 266MHz!

Thanks in advance!
 
Set the VCore to 1.4V
Turn off speedstep.
set the multi to 9
lock the PCI-E bus
|->raise the FSB by 5/10 MHz
| adjust the speed of the RAM so it is DDR2-800 or less.
| boot
| stability test with orthos for 30mins
|-repeat.
 
melbourne720 said:
Set the VCore to 1.4V
Turn off speedstep.
set the multi to 9
lock the PCI-E bus
|->raise the FSB by 5/10 MHz
| adjust the speed of the RAM so it is DDR2-800 or less.
| boot
| stability test with orthos for 30mins
|-repeat.
Click to expand...

Hi, and thanks for your reply. I understand this, just not sure of memory dividers on C2D boards.... for instance, if I set the fsb to 333 for 3GHz, and set the memory to DDR-800, is this actually setting the memory to 800, or will it be dependent on the CPU fsb.

ots3go said:
Might need to up the FSB voltage a little too.
Click to expand...

It is set to auto atm. What is the standard setting, and what do you suggest I change it to?

sarge78 said:
Have you got enough vcore? I need over 1.4v for a stable 3Ghz overclock!
Click to expand...

I changed it to 1.4v, and changed the damping setting to enabled, but it never reads above 1.35v.
 
When I was clocking with the P5k, and changed the FSB, the RAM changed dynamically. Like it would always offer options of ratios of 1:1, 1:1.25, 1:1.5, 1:2 relative to the FSB.
 
jimbobaggies said:
Hi, and thanks for your reply. I understand this, just not sure of memory dividers on C2D boards.... for instance, if I set the fsb to 333 for 3GHz, and set the memory to DDR-800, is this actually setting the memory to 800, or will it be dependent on the CPU fsb.

It is set to auto atm. What is the standard setting, and what do you suggest I change it to?

I changed it to 1.4v, and changed the damping setting to enabled, but it never reads above 1.35v.
Click to expand...

Yes, it means DDR-800, exactly as it says.

Make sure that you have the RAM voltage set correctly, for your RAM, and not on Auto. Set the timing manually too, to be sure that it's right.
 
wolvers69 said:
Yes, it means DDR-800, exactly as it says.

Make sure that you have the RAM voltage set correctly, for your RAM, and not on Auto. Set the timing manually too, to be sure that it's right.
Click to expand...

I tried it yesterday, and found that DDR-800 option disappeared at certain FSB settings, also, that to get them memory running at 400MHz at some FSB settings I had to set it to DDR-750 iirc.... however, at 266 and 333 DDR-800 setting gave 400MHz.

The RAM is on AUTO, so I will manually set it to 1.9V, although it is fine with the processor running at 1.8 and 2.4GHz, so probably not that which is the issue.

I have set the Vcore to 1.4v in the BIOS, but in CPU-Z it is 1.352, in Everest it is 1.325 on the overclock page and 1.34 on the sensor page, and in ASUS PC Probe it is 1.34. When running Intel Thermal Analysis Tool it rebooted again, so assuming I need to up the Vcore again.
 
jimbobaggies said:
I tried it yesterday, and found that DDR-800 option disappeared at certain FSB settings, also, that to get them memory running at 400MHz at some FSB settings I had to set it to DDR-750 iirc.... however, at 266 and 333 DDR-800 setting gave 400MHz.

The RAM is on AUTO, so I will manually set it to 1.9V, although it is fine with the processor running at 1.8 and 2.4GHz, so probably not that which is the issue.

I have set the Vcore to 1.4v in the BIOS, but in CPU-Z it is 1.352, in Everest it is 1.325 on the overclock page and 1.34 on the sensor page, and in ASUS PC Probe it is 1.34. When running Intel Thermal Analysis Tool it rebooted again, so assuming I need to up the Vcore again.
Click to expand...

Ah, your talking about the FSB strap which is the frequency between your cpu fsb and the Northbridge which controls the RAM. I leave mine on Auto as it gives me the RAM option that I want but some people say that the Asus boards are more stable at 333. A bit of trial and error may be required to get the best out of your set up.

Set the FSB that you want for your cpu overclock first (say 334 x 9 for 3.0ghz) then set the RAM to the closest to it's rated speed (yours is DDR2-800) that the mobo gives you. Begin under that to be sure that the RAM isn't overclocked and potentially making your system unstable. You can try overclocking your RAM later when you've got a stable cpu overclock.

The RAM voltage will have no effect on your cpu stability as long as it is correct.

Set the vcore that you want by the value in cpuz when it's under load using something like Orthos. It will always be lower than what you set in the bios. Mines 1.45v at 3.2ghz.
 
Right, failed Orthos after 2hr 56min 43sec, what is my next step?

The system has been running fine, no crashes at all, no unusual application activity, gaming for 1hr+ on TF2 and CoD 4, temperatures remain below 60C... Looking at the Intel Tech Spec, with CPUID = 06FDh the max temp should be 73.3C, so at the temps I am seeing it should be fine.

 
Last edited:
Up'd the vcore to the next setting up from 1.45, probably 1.475, and it has been running orthos overnight for 9+ hours without error, so left it running whilst I am at work also. :)
 
You must log in or register to reply here.
Back
Top Bottom