View Single Post
  #2 (permalink)  
Old October 14, 2007, 03:11 PM
Lithotech's Avatar
Lithotech Lithotech is offline
Join Date: Apr 2007
Location: North Vancouver Rain Belt
Posts: 409

Preliminary results are in for the Abit NF-M2 motherboard and the X2-5000 Black Brisbane. It'll be a couple days before I get time to upload the benches, for now here's what you really want to see... how much multi can she take Captain?

Summary - Abit NF-M2 nView

With 1.35 VCore (lowest available)
13X Multi @ 2.6ghz - no problemo
14X Multi @ 2.8ghz - no problemo
15X Multi @ 3.0ghz - no problemo
16X Multi @ 3.2ghz - boots Memtest, boots to desktop, very unstable

With 1.40 VCore (plenty more available)
16X Multi @ 3.2ghz - fails Super-Pi 32M about half way, fails Orthos, completed remaining benchmarks without incident

  • Even though the tests with this mobo were nearly effortless, it was not problem free. Difficulties with the Mushkin ram using 1T timings when set to auto, and then refusing to POST as soon as it's taken off auto, had me using different ram for this one in an effort to just get through it rather than fuss with the Mushkin. After trying several adjustments to get them running 2T, I briefly considered maybe running them 1T in auto. Then I'd really want to re-bench the ASRock with 1T as well. Turns out the Mushkin weren't stable at 1T anyway, so I pulled them and put in a 2gig kit of OCZ Reaper 6400 HPC. I went with these because I know they'll do 1T at DDR800. As it turns out, the OCZ auto'd to 2T, and ran fine when taken off auto. For this portion of experiments, I ran all the benches with the ram on auto. I did run some benches with the ram on 1T, how could I resist? I'll revisit this later I am sure!
  • The latest BIOS version for this motherboard is quite dated (04-27-2007), and the temperature readings for the X2-5000 Black are a off kilter. I had the same problem with an early stepping X2-3600 Brisbane EE. Except for the main CPU reading which has been reasonably on the mark, the diode and core temps will be disregarded.
  • The clock settings on the Abit are very accurate, speeds reported by various software show exact round numbers for 2600mhz, 2800mhz, 3000mhz and 3200mhz. Conversely, the ASRock always put the CPU a few mhz more than the setting. Hence, some of the scores for the ASRock are higher than the Abit, and would certainly be very very close if they were actually running the CPU the same speed.
  • The Abit CPU Vcore reads a bit higher in the BIOS sensor page as well as in the OS, than what it is actually set to. The lowest it will go, and auto's to, is 1.35V. This in turn reads 1.35v - 1.37v in the BIOS and 1.38v in the OS. This is reflected by the fact the Abit was able to better run the CPU with a 16x multi and limited to a 1.4v setting like the ASRock's maximum. One more tick worth of volts, and I am sure it'll pass Super-Pi and Orthos. I'll revisit the Abit with this chip later, as it'll most likely be it's final home.

More to come, once I have the screens uploaded.

eVGA 680i SLI (A1) P31
Intel Q6700 Kentsfield | Scythe Ninja-B | Antec Tri-Cool 80cfm
4GB (4x1024MB) Corsair Dominator 8500
boot: 4x WD Caviar SE16 250gb SATA2 Raid-0
backup: Seagate 500gb 32mb SATA2
eye: eVGA 9800GTX+ SC 512mb 770/2.25ghz
candy: Samsung 940B-HAS | X-Fi XMusic | Pioneer DVR-212D SATA
juice: PC Power & Cooling 750Quad | Cooler Master HAF932
steering: Logitech G15 & G5 | E3D Pro/Momo Wheel | X-530's

Last edited by Lithotech; October 23, 2007 at 01:52 AM.
Reply With Quote