Core i7/X58 Overclocking Thread

[SteveRo]

Anyone to advice me how to run my memory at 1333 without changing the bclk??
is it the qpi voltage that would make a difference?

p6t dlx and 920

sorry for posting again..

good morning, qpi v up to 1.35 and/or mem v up to 1.65 to stay within the intel max. mem multi x bclock to get to mem speed.

and this is important - you need to set you uncore multi to twice your mem multi, actually twice your mem multi plus 1 click up is even better.
However - careful - max uncore speed is 4000 may be just a bit higher. Hope this helps.

[Rammsteiner]

good morning, qpi v up to 1.35 and/or mem v up to 1.65 to stay within the intel max. mem multi x bclock to get to mem speed.

and this is important - you need to set you uncore muti to twice your mem multi, actually twice your mem multi plus 1 click up is even better.
However - careful - max uncore speed is 4000 may be just a bit higher. Hope this helps.

Im so glad I didnt go with those OCZ Blade's. The specs look awesome but yeah, if you Uncore cant run it you'll have to downclock the RAM anyway (right?). Although this might allow for tighter timings but well

Instead I got a nice Mushkin kit which had a 100 Euro discount

Anyway, I dont have the parts yet, but to be sure, VTT/QPI or how you want to name it, is best to stay within 1.35V according to Intel, leaving your Vdimm to be max 1.85V (to be sagfe maybe a notch slower), right?

[mojooh]

thanks for the quick reply

What i have tried so far is 3.2ghz QPI (24x) , 2.66ghz uncore (20x) and 1333mhz memory (10x). Bclk always 133mhz.

I did try up to 1.25 qpi v but still had problems passing linx!

So is it just the qpi voltage i should try to raise to get it stable?

[SteveRo]

thanks for the quick reply

What i have tried so far is 3.2ghz QPI (24x) , 2.66ghz uncore (20x) and 1333mhz memory (10x). Bclk always 133mhz.

I did try up to 1.25 qpi v but still had problems passing linx!

So is it just the qpi voltage i should try to raise to get it stable?

At what voltage are you running your memory?
Memory v might need a little boost also.

[mojooh]

At what voltage are you running your memory?
Memory v might need a little boost also.

I am running mem at 1.64 .... never tried 1.35 qpi though.... maybe i will give it a try when i am at the pc ...

So far i only played with vcore which didn't make a lot of difference ...

However i can see reading through the forum that not many people are running so high qpi clock and uncore even when overclocking...

[rge]

I am running mem at 1.64 .... never tried 1.35 qpi though.... maybe i will give it a try when i am at the pc ...

So far i only played with vcore which didn't make a lot of difference ...

However i can see reading through the forum that not many people are running so high qpi clock and uncore even when overclocking...

uncore speed = base clock x uncore multi.
qpi speed = base clock x qpi multi.

Most others are actually using higher qpi and uncore speed, but getting their by raising the base clock (bclk) as opposed to raising the multi as you are doing (since you dont want to OC the cpu).

Like Steve said, I would bump the qpi volts to 1.35, and if that works, then slowly decrease it until find stable point. Also what are your mem timings like 8,8,8 24, etc?

On the other hand, you might find it just as easy to increase bclk to get (if you change your mind about OCing cpu, then you will see increased speed, you wont see a difference by just running memory at 1333 vs 1066). Could raise bclk to 167, qpi decrease to 18, mem multi 8x, uncore to 17x, qpi to 1.35, vcore to ~1.3-1.35. That would likely be stable, then could decrease vcore (probably quite a bit) and qpi using linpack with max memory (all) as guide for stability.

[mojooh]

thanks for the help! ....

At the moment i don't want to overclock as i enjoy all the power saving features.... when i may start rendering i would almost definetly overclock.. actually it is the first time i use a pc without overclock!

My memory is 1600mhz 7-7-7-24 @ 1.9v (now 1066 6-6-6-18 @ 1.64)
memtest at 1333mhz 7-7-7-20 @ 1.6v without problems...

I did some benchmarks with 1333mhz and 1600mhz (they don't fail .. only linpack fails...) and it does have a major impact in memory performance ...

I will try 1.35 qpi later and tell you the results ... it is possible that it could be that!

[SteveRo]

Im so glad I didnt go with those OCZ Blade's. The specs look awesome but yeah, if you Uncore cant run it you'll have to downclock the RAM anyway (right?). Although this might allow for tighter timings but well

Instead I got a nice Mushkin kit which had a 100 Euro discount

Anyway, I dont have the parts yet, but to be sure, VTT/QPI or how you want to name it, is best to stay within 1.35V according to Intel, leaving your Vdimm to be max 1.85V (to be sagfe maybe a notch slower), right?

The jury is till out on the max mem voltage controversy.
INTEL officially told all the memory makers to keep the max v's to 1.65.
That said, there are quotes from INTEL engineers (well one anyway) that says that you can increase mem v as long as you do not exceed .5v over qpi.
So for example, if you run qpi at 1.35 you should be able to safely run mem v at 1.85v.
From what I can tell though - long term effects of any of this high voltage stuff is unknown.

[Rammsteiner]

The jury is till out on the max mem voltage controversy.
INTEL officially told all the memory makers to keep the max v's to 1.65.
That said, there are quotes from INTEL engineers (well one anyway) that says that you can increase mem v as long as you do not exceed .5v over qpi.
So for example, if you run qpi at 1.35 you should be able to safely run mem v at 1.85v.
From what I can tell though - long term effects of any of this high voltage stuff is unknown.

That counts for a lot of things, in the end those max values are questionable too. Not like Ill go and try stuff

But yeah, in the end it's defined by Intel, the same compagny who isnt really happy with people OC'ing.

For example, I guess 1.4V QPI for 24/7 might be less harmfull then an i7 at stock running 95C 24/7, although IIRC that's safe. Oh well, I got the information I needed thus far, now I only have to wait for the parts

[ewitte]

Heat is my problem (stock HSF) at the moment so don't have hard numbers but

19*211 with HT on will boot and do single threaded apps at 1.2v, 1.225v for untested stable (tested 1 minute because of heat)

Lowest stable vcore I've tried so far is 0.95v. 2.67Ghz. Runs 8 threads in prime, didn't crash.

[chance]

4GHZ 1.22v - PRIME95 64BITS 11H

[SteveRo]

chance

Excellent! What are you using for a cooler?