Recent content by madrooster

Thanks! Precisely what I wanted to see. Looks like considering they are the same price the 2133 @ 11-11-11-30 will be faster than the 1866 @ 9-10-9-28.

Hi All, What would be faster in benchmarks (Sandra/AIDA64 etc etc.)? 2133MHz @ 11-11-11-30 or 1866MHz @ 9-10-9-28 Eg. G.SKILL Ripjaws X Series 8GB (2 x 4GB) 240-Pin DDR... G.SKILL Ripjaws X Series 8GB (2 x 4GB) 240-Pin DDR...

This is because Supertalent has essentially put a SATA SSD onto a USB interface in a stick form factor. All of their USB 3.0 drives need to be treated with the same alignment rules that apply for SATA SSDs. If you use diskpart and type: list disk (look for the number next to the ST drive)...

Those prices quoted are what an e-tailer in Europe has set for preorder. The real price for the 120GB is $280.. click the vr-zone link.

It still hasn't been confirmed as to which chipsets are affected, it may not be all chipsets.

That card is definitely longer than 10.5 inches (that's the length of the reference card). Put http://gigabyte.com/fileupload/product/3/3615/3519.jpg and http://gigabyte.com/fileupload/product/3/3663/3658.jpg side by side and compare. It's even longer than their HD5870 super overclock...

Just an update on further fiddling I eventually got around to... I found the culprit to LinX erroring within the first run whilst running as 1600 CL7 on the D0 chip. Turns out the tRFC timing that is set in the XMP profile is not appropriate at all for the 128MB chips the dimms use. Even...

Well, I recently noticed that even the C0 cannot stay 100.0000000% stable running 1600MHz 7-7-7-24 2T. It errors around the 60th run of LinX. On the C0, 1600MHz 9-9-9-28 2T seems to pass 100 runs of LinX. On the D0, 1600MHz refuses to pass 5 runs even. However *both* the C0 and D0 pass...

@ SummerDays No this is a VERY bad idea on (at least) the Gigabyte X58 boards. When you just set the multi to 12 and leave everything on auto, the board uses 1.8V VDIMM which is well beyond Intel's recommended spec. Similarly setting it to 10 (for 1333MHz), it tries to use 1.6V VDIMM for...

The C states are enabled yes - though under LinX it should be in C0 state the entire time. I'm running the F8 bios, pretty sure the D0 microcode was introduced ~F5. I have now tried 1.2V Vcore, VQPI 1.34V, VDIMM 1.65V, CL7, 1600MHz. No go, it bombs after the 2nd run of LinX (it was bombing...

No, the BIOS remained the same the entire time. Everything else has stayed the same. Only the CPU changed.

@ mastrdrver I'm well aware of that, though generally D0's require less voltage compared to a C0 - not more! @ Binge I've only gone as far as "safe" voltages go, ie. 1.35V QPI/VTT, 1.65V VDIMM. Best I can do with those is 1333MHz CL7 on the D0. On the C0, no issues running 1600MHz...

I'll try 1.2V vcore first, as that's what the C0 maxes out on, at full load with EIST, C1 etc. turned on.

On the C0 stepping chip, I could leave the vcore on auto with the usual power saving features on (basically defaults, stock core freqs), but with the RAM running the sticks' rated 1600MHz CL7. There is no core overclock in this case, only the uncore (as a result of the 1600MHz RAM). On the...

I've got a 1600MHz CL7 kit here which works with the following on a C0/C1 i7 920 at stock CPU freq (for now) on a Gigabyte EX58-UD5: 10x RAM multi to get 1600 Vdimm 1.65V Vcore auto V-IOH auto V-QPI 1.34V All other voltages on auto. The kit works fine for 25 runs of LinX on max problem...