GSkill RipjawsX 2133C7 2x2GB @ 2260Mhz 7-10-10-27-1T - stock VCCSA


2133Mhz 6-10-6-27-1T

Populated DIMM slots...

GSkill RipjawsX 2133C7 4x2GB @ 1600Mhz 7-7-7-20-1T, 1.65v VTT 1.2v
- 1600C6 no post


1866Mhz 8-9-8-24-1T, 1.775v vdimm, VTT 1.35v
- 8-8-8-24 no post


2133Mhz 9-10-10-27-1T, 1.8v vdimm, VTT 1.4v
- 2133C8 no post

PLL doesnt hurt my GFolps, turning off AI suite helps me in getting 84Glops on HT and 132GFlops HT off. Meanwhile i just need to enable internal PLL overvolt 51x onwards.

Actually was refering to LinX 4threads instead of 8.
Core2 max at 90C. Will upload both 84 and 132Gflops ss tomoro once get back to penang.
Saw an XS forumer hit 58x dice with my batch L042B243

5.0GHz LinX 8 Threads @ 84GFlops


5.0GHz LinX 4 Threads @ 132GFlops

Nice one.. Asus hasnt release any new bios this month..
BSOD error codes added in post #1.

Still cant solve intel SATA3 raid0 issue on port0,1...
now i'm still using raid0 on SATA2 ports

Intel Core i7 2600K @ 5.0GHz HT ON (4C/8T)
Asus Maximus IV Extreme 0951
2x2GB GSkill RipjawsX 2200C7 @ 2133Mhz 7-10-7-27-1T
2x MSI GTX580 SLI, 930/4100Mhz
Corsair AX1200
LinX:

Vantage:

Pi 32M:


5.1 GHz HT ON
LinX:

wPrime:

Pi 32M:


This post has been edited by owikh84: Feb 19 2011, 04:29 PM

I hv problem with my raid0 X25-M on M4E, can't build raid0 on the Intel SATA3 ports. The raid manager cant recognize my SSD on port0.
Marvell SATA3 is the option but I need to re-create raid and hence lost the data.
So to avoid data lost, create a GHOST image of the raid0 (and save the image on other drive/partition) before switching to SATA3 using Norton GHOST or Acronis Backup & Restore. Swap to SATA3, create raid0 then restore the image.

This post has been edited by owikh84: Feb 15 2011, 08:43 AM

It should do fine for 5.0, but again depends on CPU as well. Some are too stubborn playing with high voltages.
Check out THIS thread

Could be bios issue as old bios on specific drive in which raid manager could detect my raided SSDs. But im not alone with this problem.

This post has been edited by owikh84: Feb 16 2011, 02:56 PM

Dont get confused with the SATA3 flaw issue recently.
Mobo is the problematic part, not the Sandy Bridge proc.
But if u think newer batch of proc is better than the old batch, u r wrong as there's no such a thing. No one can really tell u which batch is good n evil etc..

whenever a manufacturer revised a mobo, they will print a revision number on the mobo. can identify thru CPU-Z and mobo box label as well.

More infos HERE

ASROCK

most cases CPU PLL doesnt affect and wont help OC.
VTT aka VCCIO yes, some chip needs higher VTT ie. 1.25v to boot, some are able to do at stock 1.05v.
Not sure abt this aircooler but supposed can do up to 4.6GHz HT.

PLL 1.8v stock is good enuf. Sometimes I need to adjust PLL sometimes dont. Increasing it will produce more heat and vise versa. Stability wise is still a myth.
VCCSA is mem controller, like NB aka IOH, let it auto but some said increasing it might help BCLK OC.
VCCIO stabalizes RTL, is actually the VTT, faster dram needs higher VTT. A proc with very good IMC doesnt need to increase VTT.
Out my knowledge, go google.

Every chip has its own frequency wall.
Let's say if my chip could do 100X53 = 5300 should be able to do 106X50 = 5300. For sure BCLK oc is harder as it is tied with mem frequency.

re-run on BIOS 1090...

i7 2600K @ 5.1 GHz HT ON

next time I will do LinX at least 50 runs to conclude stability.