Core 2 Duo Overclocking Thread

Status
Not open for further replies.
3.4 probably was a ram related error.

Take the ram out of the equasion and try again.

I trust you know how to do that...
 
The General said:
Who said anything about Prime95? I hate it, it fails at stock speeds on all my computers. Prime95 is BS. I did SuperPI 32M at 3.4ghz and it was 52c.

When I get better cooling, I'll shoot for sub 13s, Lord AnthraX. :)

EDIT: Actually I forgot, I ran Prime95 from 3AM to 11AM and it didn't fail, that was at 3.2ghz, 3.4 failed instantly at 1.48v, but stood out for like hour at 1.5. This was like really late last night, I totally forgot about that. :p

Speka la anglais?...im lost, somewhere near Pluto right now...
 
NosBoost300 said:
i don't!!! so tell me!!

or are you just speaking of having a super low multiplier?


Im not as familiar with DDR2 ram but it basically means putting it to like a 2:1 Divider and as slow as it can go so it dosen't create problems in prime.
 
Pluto blew up? Since when?

And Prime95 is the standard for measuring stablility. SuperPi doesnt mean shat other than for benchmarking.

24hr Prime95 is the undisputed king of stability.
16hr Prime95 is my personal undisputed king of stability.
8hr Prime95 is stable enough to brag about.
 
Yeah it seems that the ram has these choices: Auto, 1:1, 2:3, and other higher ones. I can adjust the timings I guess, but like I said I need better cooling before I go any further than 3.4Ghz. :confused:

Here, I made a graph for what I have so far:

graphrm1.png
 
Status
Not open for further replies.
Back
Top Bottom