Overclock.net banner
1 - 8 of 8 Posts

224 Posts
Discussion Starter · #1 ·
I got rid of a ton of heat at 3.4 by raising the vcore. It was stable, just hot. Now it's much cooler but one or two hours into orthos, orthos goes down. My settings are:

FSB: 377.8 Mhz
multiplier: 9X
vcore: 1.425
vdimm: auto
PCIE: 101
PCI: 33.3
ratio: 1:1
memory frequency: 775 Mhz
timings: 4-4-4-12
auto for everything else

Is my vcore too high? Anything else?

6,696 Posts
I should not think there will be a problem with your memory configuration given your current circumstances.
Your memory is rated to operate at 800MHz, with acceptable latency periods, therefore there should not be a problem with that particular part of your computer system (2.1005v rated voltage).

Unfortunately, after a given clock frequency, the Core 2 Duo Architecture has to have a massive increase in system voltage to compensate for these clock frequencies.

Here is an example chart I have created.

You can see that voltage will drastically increase after a certain point.

I therefore suggest that you do indeed increase the CPU Voltage to compensate for the clock frequency. All CPU's are different, you may require a higher voltage than others to ascertain your desired clock frequency.

Also, I really doubt that the memory is to blame as Orthos does not stress the memory a huge amount, unless it's repeatedly paged. Orthos mostly just does 32 bit random allocation locations, which are not particularly stressful.
You can of course increase the voltage of the memory if you wish to ascertain tighter timings, or just increase overall stability beyond what is required.

36 Posts

Originally Posted by The Argosy View Post
Excellent artwork, my man!
I did indeed bump up the vcore; I just passed the two hour mark on orthos--that's where I left off on my last attempt at 3.4--and everything looks good. Thank you much.
What kind of Temps are you seeing using TAT to stress it at 3.4?
1 - 8 of 8 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.