Need help choosing a motherboard for 9800x3d gaming PC

Associate
Joined
19 Jan 2005
Posts
1,172
Location
Cambridge
I was able to place an order for the 9800x3d before it sold out but I'm having trouble deciding on an ATX motherboard. My budget is around £200-£300 max, with my main focus being something reliable with good build quality that is going to last 5-7 years.

Must have:
  • PCIE-5 slot for graphics card with no lane sharing.
  • At least 3 NVME slots with at least one of them being PCIE-5.
  • At least one additional PCIE 4x slot with no lane sharing.
  • 2.5GB LAN or better.
  • Good enough VRMs for possible future overclocking.
  • Black or dark grey with minimal RGB and logos.
Nice to have:
  • Debug post code.
  • Clear CMOS button.
  • Support for 9000 series without BIOS update.
Currently I'm looking at the MSI X870 Tomahawk, MSI x670E Tomahawk, Asus B650E-F, and Asus B650E-E. I’ve had bad experience with Gigabyte in the past but I might be willing to consider them. ASRock I’ve always seen as a budget brand and their boards are a bit overdone with RGB and logos for what I’m going for. They seem to be popular though.
 
The X870 Tomahawk has USB4, if you care about that, but they share bandwidth with the second M.2 slot.

The B650E-E knocks the GPU down to 8 lanes if you use M.2 slot 3.
 
The B650E-E knocks the GPU down to 8 lanes if you use M.2 slot 3.

I knew there was a reason I ruled this one out before but I couldn't remember what it was. Thanks !

I'm leaning towards the X870 Tomahawk currently, it has some lane sharing but not with the GPU and nothing that will bother me. I'm keeping a close eye on the recent report of a 9800x3d burning out in one of those though.
 
I knew there was a reason I ruled this one out before but I couldn't remember what it was. Thanks !

I'm leaning towards the X870 Tomahawk currently, it has some lane sharing but not with the GPU and nothing that will bother me. I'm keeping a close eye on the recent report of a 9800x3d burning out in one of those though.
Theyre saying possible socket defect, or user error. Bound to be a few that fail I guess
 
Back
Top Bottom