Five $160 To $240 990FX-Based Socket AM3+ Motherboards

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Status
Not open for further replies.
Depends...

Naturally, a few things willing improve. The 890/990 wasn't that bad to begin with. I wouldn't mind seeing it carry on for awhile personally. But none of it will matter much if the CPU won't perform worth anything on it's end.

Like with the Bulldozer, I knew from my first experience with Phenom, it's better to wait for the 2nd-3rd Gen chip to be on the safe side, thanks to teething issues. I doubt AMD saw the whole TLB Erratum saga approaching after release. After B2 and B3 stepping, things changed for the better. It may not have been a barn burner, but Phenom eventually became a real value and powerful chip for what it was. And during that time, they went from one chipset to the next, improving as they went along.

Vishera (Enhanced Bulldozer) should be out by Q3 next year. If they don't improve things by then, AMD will be in serious trouble. In fact, I'd go as far as to say, they should just sell their stock to Intel or ARM and close their doors if things haven't changed by then. I personally have my reservations about a 8 core chip, when they haven't shown that it's worth having anything more than a 6 cores at this point. But if they intend to increase performance, they better think about the here and now, and focus more attention to single thread performance. That's what biting them in the rear.
 
I went with the Sabertooth myself this past summer as I was building to last, and the five year warranty was particularly impressive. I had hoped Bulldozer would be good, but even if I never get one, the 970BE I'm running should meet my needs for the foreseeable future. I would like to have seen a comment about the MemOK feature of the Sabertooth though, as it is another useful feature that distinguishes this board from the others in the roundup.
 
Asus proclaims quad-GPU SLI support, referencing a pair of dual-GPU GeForce GTX 590s. In fact, that arrangement is supported by all SLI-capable motherboards. Our problem with the quad-GPU terminology is that it almost appears to be an attempt to confuse neophytes into believing this four-slot board will take four cards working cooperatively. Asus clearly indicates on Page 2-16 of its manual that this is a triple-card SLI design, though.

Quick question .. is it still possible to run 4 separat cards into quadfire/crossfire-x; quad-sli? I remember a long time ago in a SBM 4x4850 (or something similar). So ... are there still cards out there with that option?

Also ... if it's a motherboard round up .. how come there's no LAN, audio, esata, usb tests going on?
 
The Crosshair V has an expander board that can supposedly run four cards all at x8, but I don't think the Sabertooth has anything like it. It looks like the Gigabyte board in this roundup can do it though.
 
Wow, this article couldn't be more well timed since I just posted something yesterday about wanting to get a motherboard suitable for my 1055T that I'm not using right now. Now I'm having a hard time deciding between the Sabertooth and the UD7.
 
[citation][nom]g00ey[/nom]According to your review you have the rev 1.1 of this motherboard and yet LLC features are missing in the BIOS[/citation]Please try reading the entire page instead of the first three paragraphs, it says the LLC setting missing from one menu is found in another.[citation][nom]dkraptor[/nom]Hmmm. So where is the most important of them all? Asus Crosshair V Formula?[/citation]Asus had to make a choice since, at 2-3 days per board, there wasn't enough time to give everyone the option to include two boards.[citation][nom]jtt283[/nom]The Crosshair V has an expander board that can supposedly run four cards all at x8, but I don't think the Sabertooth has anything like it. It looks like the Gigabyte board in this roundup can do it though.[/citation]You do understand that expander boards are used for bench testing only, right? I mean, it's no like you're going to put cards that stick out too far in a case :)[citation][nom]jtt283[/nom]I would like to have seen a comment about the MemOK feature of the Sabertooth though, as it is another useful feature that distinguishes this board from the others in the roundup.[/citation]I tried it to recover from a bad O/C, believing it would temporarily lower the actual settings without changing the programmed settings. I was wrong, using it deleted my programed settings. So rather than fuss about how it sort of works but not as well as expected, I ignored it.
 
But the UD5 I've chosen was $10 cheaper than the Sabertooth, and has all the features of the UD7 except for quad SLI. It really was the ideal board for me, and the superior overclocking makes it a win in my book.

Anyway thank you very much for this article. Seems everyone has written off BD a a fail, but there are reasons to be hopeful for the future. Even without a Bulldozer CPU, I like my Gigabyte board very much and find that I really don't care about a lack of UEFI.
 
[citation][nom]g-unit1111[/nom]Wow, this article couldn't be more well timed since I just posted something yesterday about wanting to get a motherboard suitable for my 1055T that I'm not using right now. Now I'm having a hard time deciding between the Sabertooth and the UD7.[/citation]

Take a look at the UD5
 



Fail is a little to harsh, more like underwhelming. It's an increase from Phenom II X4 era but not enough of one to justify it's costs. It's barely faster then the X6 and even slower in some areas. It does provide you with a very wide set of processing resources, but unless your coding your software specifically for it then those don't really matter. And it seems to have some severe L2 Cache issues, so severe that it's crippling the chips performance.

Recommendation now is to just wait it out for revision 2 or 3.
 
MemOK! - you're using it wrong. Save your settings to a testing profile before you reboot. If it fails, press MemOK! and it'll boot with defaults. Reload your OC profile and figure out where you went wrong. It's awesome.
 
[citation][nom]asusmemok4872[/nom]MemOK! - you're using it wrong. Save your settings to a testing profile before you reboot. If it fails, press MemOK! and it'll boot with defaults. Reload your OC profile and figure out where you went wrong. It's awesome.[/citation]But I could do that with CLR_CMOS. So, what's "awesome" about MemOK?
 


MemOK is just a press button for testing the upper limits of memory, it's an extension of the built in overclocking system. Generally it's only useful for testing how high your base memory clock can go before memory becomes unstable (204/210 ect..).

Interesting note on the Sabertooth board. The original BIOS was set to do stability testing ~every time~ the system powered on, meaning its BIOS POST time was a good 30+ seconds. If the board detects a CPU / Memory failure then it will auto-revert to base known-good defaults and alert you that there was a overclocking failure. The second BIOS for it fixed it so that it only does this test the first time you change settings then skips it afterwards.

Also the board is a little -too- smart for it's own good. I put in a set of four 4GB Corsair Vengeance DDR3 1600 memory sticks. The SPD settings are DDR3-1333 but the XMP settings are DDR3-1600. The sticks are rated at 1.5v and are quite sensitive to voltage. Took me forever to figure out how to get them to run at 1600 speed. I had to manually set the voltage to 1.5 rather then leave it at auto. What was happening was when I put in the manual timings are set it to DDR3-1600 speed, the BIOS would try to auto-set the voltage to 1.6 and the sticks would stop working and never POST. Setting the voltage manually prevented this from happening.

Next is during my OC on the Phenom II x4 970BE on water. Stock speed is 3.5Ghz. I can get a stable POST at 4.5 but windows bombs out trying to boot. I can get a successful boot at 4.4Ghz but windows randomly reboots / shuts down. 4.3Ghz it lasts longer but eventually will crash / reboot, Prime95 has it crashing in minutes. 4.2Ghz has been running fine for awhile now, Prime95 goes for 6+ hours no issues. Something I noticed during this time is that you don't have to set the voltage on the CPU, it will automatically adjust it for you. With the CPU voltage set to auto and 4.2Ghz clock I would run CPU-Z and CPUspeed program. You can see the voltage starting at 1.45~1.47 with the CPU at 4.2ghz. Start up prime95 and it starts running, you immediately see the voltage spike to 1.5. I don't allow the board to set it higher as I'm not sure what the highest "safe" setting could be before damaging my CPU.

Overall the Sabertooth is a great overclockers board if a bit too smart for it's own good.
 
Sabertooth is an AWESOME overclocking board but I wish there was a way to force it to boot at default settings while storing previous settings (boot failed, press F1 to load defualts or DEL to enter BIOS) etc.
 



Actually there is kinda. Under tools there is a place to save your current settings to a profile. I made profile #1 be my default profile (it is by default) and made profile 2 my OC settings. You can store up to 7 or 8 separate OC settings.

If the systems detects a OC failure it will revert to default "safe" settings and prompt you to go to setup "F1". It will appear that your settings were wiped but they aren't. If you reboot (don't save) then it'll try to boot with what you had previously and fail again. Instead go to where you had your profile saved and tell it to load whatever profile you were testing. *POOF* everything is back again. Now go find your failed setting and test again. I did ALOT of this when I was trying to find right OC settings for my rig.
 
Yes, I've done this with CLR_CMOS a bunch of times too.
 


CLR_CMOS is only for when the system won't even get to POST which would indicate a basic failure of the CPU / memory subsystem. A hotkey to "default" BIOS wouldn't work then anyway, the keyboard controller wouldn't of had time to be initialized by the failed CPU. Maybe 10 years ago when things were pretty much hardwired on startup but nowadays everything is soft loaded by the CPU during system POST. The best you can hope for is a rear mounted CLR_CMOS button so you don't have to open the case, but honestly I'd be afraid of having something like that near the back of my box.
 
200$ for a BD motherboard??? Isn't this like buying a toilet seat? I mean, what you will drop there will be shit, anyway...

PS: I am a huge AMD fan, I really am.
 
"990FXA-UD7 includes a lighted CLR_CMOS button" shouldn't "lighted" be "lit" or "backlit" or something? Other than that cheers for a great article Thomas!
 
Status
Not open for further replies.