Overclock Limit?

M

Mad_CatMk2

Gawd
Joined
Sep 21, 2007
Messages
712
Hey guys, I'm running a E6750 at 3.4GHz running at 1.35vcore (default 1.3375). It seems that going higher than the 3.4 is a very 'hard' thing to do. I increased vcore by a coupla notches, touching 1.4V and orthos fails within 10-20 minutes.

Any ideas? Would I need to up my other voltages (DDR2, MCH, FSB?)

Specs are in sig, but I'll post specifics here:

GA-P35C-DS3R F4 Bios (Default MCH and FSB voltages)
Mushkin XP2-6400 at 5-5-5-15 2.1V
Memory multiplier at 2.40 (425x2.4 = 1020MHz DDR)
E6750 @ 3.4GHz 1.35vcore
FSB @ 425, 8 multiplier

Cheers
 
Raising your MCH voltage would probably help, since your FSB is already quite high. Your RAM voltage looks okay, but you might try putting on a divider to make sure the RAM speed isn't limiting your overclock.
 
I can lower the ram divider to the lowest of 2.00 (well, DDR is double? hehe). I tried that and it seemed to not do well too.

I probably should raise the MCH voltage, but by how much?
+0.1V or more?

Damn I am confused :p
 
Raise the MCH voltage one increment at a time and keep testing for stability. Most boards don't let you set it at a dangerous level.
 
heh running 3.44GHz now, only bumped MCH voltage +0.1V
i'll try more testing tonight, raising fsb another 5mhz
 
Alright I'm now at 3.52GHz (440x8) with vCore at 1.3625V and MCH +0.2V

I tried 445x8 earlier but the computer bluescreened during an Orthos stress test.
Should I continue and raise the MCH voltage to +0.3V(max) and try again? Or should I work with cpu voltage and increase it up another 0.0125V (or double of that)?
 
That ram isn't known for overclocking very well, if you're too high on the ram that could possibly/probably be an issue.
 
Hmm,
I've read it can hit 1100+ or so DDR just fine...with 2.2V (im at 2.1V)
Here is the product page.
Reviews are there on the right. But I also read that my mobo can be picky...since its the dual-ram type version.
 
You should try putting on a RAM divider anyways just to rule out the possibility of it limiting you. RAM speeds don't really affect C2D performance much anyways.
 
Alright I'll try that next time maybe, I'm hitting a little wall at 3.52GHz.

Orthos fails at around 2hr mark...autorestarts system instantly :|
At 3.56(445x8), i set it to 1.375vcore, +0.3MCH and it still crashes, so maybe the ram is being pushed a little too hard. What if I set the ram voltage another +0.1V to 2.2V? Would it give a chance to stabilize more?
 
I wouldn't go over 2.2v. Raising it to that level will probably help a bit, but like I said in my last post RAM speed is not significant for C2D systems, so if the RAM is the limiting factor, keeping it on a divider and raising your CPU speed will give you the greatest benefits.
 
Hmm...I tried dropping to 2.0 multiplier and it still auto-restarted at 3.56(445x8). I even increased FSB voltage by +0.1V (cpu voltage at 1.3625), MCH voltage at +0.2V and ram voltage at +0.4V(2.2V).

Would my vcore be too low (after vdroop, that is)? Should I bump it up to 1.375V or even 1.3875V?
 
Mad_CatMk2 said:
Hmm...I tried dropping to 2.0 multiplier and it still auto-restarted at 3.56(445x8). I even increased FSB voltage by +0.1V (cpu voltage at 1.3625), MCH voltage at +0.2V and ram voltage at +0.4V(2.2V).

Would my vcore be too low (after vdroop, that is)? Should I bump it up to 1.375V or even 1.3875V?
Click to expand...

Vdroop can definitely be a problem. I'm not sure what your vdroop is like on that board but on my P35-DS3R and a Q6600 the vdroop is terrible. I have the voltage in BIOS set to 1.52 or close to that but after vdroop it's doing 1.41-1.42. As long as the voltage stays above 1.4 my overclock is good and I'm at 3.6Ghz, 9x400. I would love to go higher and I think the CPU will do it, but my temps are already reaching 60C with the vcore as high as it is. With better cooling I might raise the voltage up some more, but not with what I have right now.

 
Yeah I'm stable at 3.56GHz now at all the above settings...except Vcore is set to 1.4V in bios.

Now trying to hit 3.6 :p, patiently, of course.

edit: Strange, Orthos was stable well over 8 hours, but CS:S crashed on me earlier. Freak accident? Or not enough vcore?
 
It could probably do with a bit more VCore. Try upping it by a notch or two and see how that goes.
 
You must log in or register to reply here.
Back
Top