DFI UT X58-T3EH8 continued - Part 2

[unclewebb]

Most users find it a lot easier to get 4GHz by using an odd multiplier like 19 or 21 compared to using an even multiplier like 20.
If you have trouble getting 20x200 stable then try 21x191 instead.

[batmang]

Most users find it a lot easier to get 4GHz by using an odd multiplier like 19 or 21 compared to using an even multiplier like 20.
If you have trouble getting 20x200 stable then try 21x191 instead.

I'll give it a shot today.

[JustCallMeFrank]

For me, 200 bclck gives me a nice round figure of 800mhz for my RAM (which is rated at 1600mhz).

Factotum: I'll try and play with the CPU VID special add to see if it makes a difference to my OC (I'm currently using CPU VID control).

Almost stable for 8 hours of prime at 210x21 for 4410mhz (with HT on). 1 thread decided to die at 1hr 40m. The other 7 made it.......... GRRRRRRRRRRRRR

[Peen]

For me, 200 bclck gives me a nice round figure of 800mhz for my RAM (which is rated at 1600mhz).

Factotum: I'll try and play with the CPU VID special add to see if it makes a difference to my OC (I'm currently using CPU VID control).

Almost stable for 8 hours of prime at 210x21 for 4410mhz (with HT on). 1 thread decided to die at 1hr 40m. The other 7 made it.......... GRRRRRRRRRRRRR

Might be ram, atleast my cpu never errors, it just bsods but my ram tends to error prime out

[Sam_oslo]

For me, 200 bclck gives me a nice round figure of 800mhz for my RAM (which is rated at 1600mhz).

Factotum: I'll try and play with the CPU VID special add to see if it makes a difference to my OC (I'm currently using CPU VID control).

Almost stable for 8 hours of prime at 210x21 for 4410mhz (with HT on). 1 thread decided to die at 1hr 40m. The other 7 made it.......... GRRRRRRRRRRRRR

800MHZ was the norm at the start av i7 C0, but i7 has evolved and most D0's will do @4.2-4.4GHZ 24/7, and this is the BCLK210 territory. 840MHZ has become the "not so nice an round" number that creates a big RAM-dilemma (many sticks can't run at this speed even with higher voltages). I guess many of these "strange" stability problems starts when people try to push the RAM over it's limits.

[v_parrello]

800MHZ was the norm at the start av i7 C0, but i7 has evolved and most D0's will do @4.2-4.4GHZ 24/7, and this is the BCLK210 territory. 840MHZ has become the "not so nice an round" number that creates a big RAM-dilemma (many sticks can't run at this speed even with higher voltages). I guess many of these "strange" stability problems starts when people try to push the RAM over it's limits.

imho is not only RAM issues, I think these problems are related to CPU Integrated Memory Controller and QPI bus frequency.

Not all the CPU are abe to run with uncore > 3.6 GHz and/or QPI bus strongly overclocked: BCLK>190 MHz and then QPI bus >190x18=3420 MHz.

[Sam_oslo]

imho is not only RAM issues, I think these problems are related to CPU Integrated Memory Controller and QPI bus frequency.

Not all the CPU are abe to run with uncore > 3.6 GHz and/or QPI bus strongly overclocked: BCLK>190 MHz and then QPI bus >190x18=3420 MHz.

I agree, depending of the CPU-batch, the QPI bus can be the problem too, but that's relatively easy to diagnose/fix. On the other hand, many RAM-sticks can limit a good CPU-batch to run at BCLK210 (1680MHZ RAM). This is not so easy to diagnose and people are reporting some "strange" instability problems (it can pass the Memtest, LinX and PrimeBlend, but fails in SuperPI, or other "strange and unheard" problems).

It is not easy to generalize, but I believe many of these "strange" instability problems are rather related to "too high BCLK for the RAM" than for CPU/QPI/Uncroe (but I agree that this problem exists too). After "the dead of the hyper", there not many sticks in the marked that can run stable @1680MHZ (even with unsafe Vdimm).

An easy way to diagnose the QPI-problem can be to run LinX/PrimeBlend with QPI fast mode, disabled.

[Razer(x)]

I agree, depending of the CPU-batch, the QPI bus can be the problem too, but that's relatively easy to diagnose/fix. On the other hand, many RAM-sticks can limit a good CPU-batch to run at BCLK210 (1680MHZ RAM). This is not so easy to diagnose and people are reporting some "strange" instability problems (it can pass the Memtest, LinX and PrimeBlend, but fails in SuperPI, or other "strange and unheard" problems).

It is not easy to generalize, but I believe many of these "strange" instability problems are rather related to "too high BCLK for the RAM" than for CPU/QPI/Uncroe (but I agree that this problem exists too). After "the dead of the hyper", there not many sticks in the marked that can run stable @1680MHZ (even with unsafe Vdimm).

An easy way to diagnose the QPI-problem can be to run LinX/PrimeBlend with QPI fast mode, disabled.

My problem is, for example, that i can't get the pc stable with uncore >3000

[v_parrello]

....
After "the dead of the hyper", there not many sticks in the marked that can run stable @1680MHZ (even with unsafe Vdimm).
...

What about this one?


I think the main problem to run high RAM frequency is strictly related to uncore frequency and quality of IMC of CPU. There are a lot of RAM in the market that are able to run at high frequencies with really low voltages (all the kits equipped with elpida BBSE).