Originally Posted by
StellaNor
Bashing this nice piece of hardware - who did? Tell me and I will slap em :D
So back to topic, if this is the right place for.
I got most recent Beta G27 today. Compared to G25/G26 I can see a little improvement of memory stability, but that counts only for the working dividers. I still run into trouble while using Auto, 1:3, 1:3,2, 1:4 (strap 200, 266 and 400). Divider of 1:2, 1:2.4, 1:2.665 and 1:4 strap 333 performing quite well.
So here is what I experienced after a full set of settings with 4 different memory kits. Memory using was Corsair XMS2-1600 CL7 2x2.048 (only kit can run at 1T), Mushkin XP3-14400 2x.1024 (with XMP-Profile), CSX Diablo-2000 2x1.024 and CSXO-CEC3-1333 2x1.024. FSB is set to 500 and thats stable of course (@Auto and 1:4 memory should run at 1.000 MHz). CPU E8500. All memory-modules have been tested to run at 1.000 MHz on a 790i (yes I know and I will not compare to it). VDimm is set to 2.044 and measured with DMM at 2.014.
So here is the first test with Diablo-2000 CL8-24-75 2T:
Divider Auto no boot, error E1
Divider 1:2 fine
Divider 1:2.4 fine
Divider 1:2.665 fine
Divider 1:3 BIOS-Boot shows only 1 Core out of 2
Divider 1:3.2 no boot, error E1
Divider 1:4 strap 200 no boot, error C1
Divider 1:4 strap 266 no boot, error E1
Divider 1:4 strap 333 fine and primestable for 45 minutes b4 I skipped testing
Divider 1:4 strap 400 no boot, error C5
Next Test Mushkin XP3-14400 CL8-24-75 2T (XMP-Profile):
Divider Auto no boot, error E1
Divider 1:2 fine
Divider 1:2.4 fine
Divider 1:2.665 fine
Divider 1:3 BIOS-Boot shows only 1 Core out of 2
Divider 1:3.2 no boot, error E1
Divider 1:4 strap 200 no boot, error C1
Divider 1:4 strap 266 no boot, error E1
Divider 1:4 strap 333 fine and primestable for 45 minutes b4 I skipped testing
Divider 1:4 strap 400 BIOS-Boot shows only 1 Core out of 2
Next Test CSXO-CEC3-1333 CL8-24-75 2T:
Divider Auto no boot, error E1
Divider 1:2 fine
Divider 1:2.4 fine
Divider 1:2.665 fine
Divider 1:3 BIOS-Boot shows only 1 Core out of 2
Divider 1:3.2 no boot, error E1
Divider 1:4 strap 200 no boot, error C1
Divider 1:4 strap 266 no boot, error E1
Divider 1:4 strap 333 fine, but not even benchstable- the memory simply sux ;)
Divider 1:4 strap 400 no boot, error C5
Last Test Corsair XMS3-1600 CL8-24-75 2T:
Divider Auto boot fine
Divider 1:2 fine
Divider 1:2.4 fine
Divider 1:2.665 fine
Divider 1:3 BIOS-Boot shows only 1 Core out of 2
Divider 1:3.2 no boot, error E1
Divider 1:4 strap 200 no boot, error C1
Divider 1:4 strap 266 no boot, error E1
Divider 1:4 strap 333 fine and primestable for 45 minutes b4 I skipped testing
Divider 1:4 strap 400 boot fine
same Corsair at CL8-24-75 1T:
Divider Auto boot fine
Divider 1:2 fine
Divider 1:2.4 fine
Divider 1:2.665 fine
Divider 1:3 BIOS-Boot shows only 1 Core out of 2
Divider 1:3.2 no boot, error E1
Divider 1:4 strap 200 no boot, error C1
Divider 1:4 strap 266 no boot, error E1
Divider 1:4 strap 333 fine, just not stable (you guessed ;)
Divider 1:4 strap 400 boot fine
So what I am asking is if you guys can confirm that especially the 1:3x dividers not working as they should. I think they are pretty important to close the gap between 1:2x and 1:4. Im neither pissed nor upset, the blackops is just great (which other x48 except the evo delivers such big fsb) and even the memory-performance increased alot. But I am unhappy with the dividers. As you can see, there is a difference between memory running at 2T (cannot boot at Auto and strap 400) and the Corsair-Kit, which is able to run at 1T (boots at Auto and strap 400), also. And no, I did not tweak any memory settings in the test (I usually do, when pushing the memory clock beyond 1.000 and thats working well, but divider-problem remains. The blackops here is a media sample with factory testreport included ;)
Any help is much appreciated.
Kind regards,
Steffi