Home / Tech News / Featured Tech Reviews / Gigabyte X99M-Gaming 5 mATX Motherboard Review

Gigabyte X99M-Gaming 5 mATX Motherboard Review

We will be outlining the Gigabyte X99M-Gaming 5 motherboard's performance with the Core i7 5820K CPU at its stock frequency (3.6GHz due to forced turbo). Overclocked performance will be outlined later in the review.

stock-clocks

By default, the Gigabyte X99M-Gaming 5 motherboard applies multi-core turbo (MCT) and forces the 5820K to a constant 3.6GHz when XMP is enabled. This will be displayed as the ‘stock’ setting.

Gigabyte feeds the 5820K with 1.069V under load and at MCT speeds. That's a sensible voltage level that outputs low temperature values and can be cooled with relative ease.

X99 Motherboard Test System:

Compared X99 Motherboards:

Software:

  • Gigabyte X99M-Gaming 5 BIOS F2 (release and latest).
  • Catalyst 14.9 VGA drivers.

Tests:

  • 3DMark 1.3.708 – Fire Strike (System)
  • SiSoft Sandra 2014 SP2 – Processor arithmetic, memory bandwidth (System)
  • Cinebench R15 – All-core CPU benchmark (CPU)
  • WinRAR 5.10 – Built-in benchmark (CPU)
  • HandBrake 0.9.9 – Convert 4.36GB 720P MKV to MP4 (CPU)
  • ATTO – SATA 6Gbps, USB 3.0, M.2 transfer rates (Motherboard)
  • RightMark Audio Analyzer – General audio performance test (Motherboard)
  • Bioshock Infinite – 1920 x 1080, ultra quality (Gaming)
  • Metro: Last Light – 1920 x 1080, high quality (Gaming)
  • Tomb Raider – 1920 x 1080, ultimate quality (Gaming)

Become a Patron!

Check Also

Ducky One 3 Pro Nazca Line Keyboard Review

The One 3 Pro Nazca Line keyboard from Ducky feature the revamped Cherry MX2A switches

2 comments

  1. ASRock Fatal1ty X99M Killer seems like the Best bet with a 4x m.2

  2. Anthony Thurston

    I have been having that odd GPU load crashing issue, and I was beginning to think that I was going crazy. System is totally stable otherwise, Aida64 for 10+ hours with no issues, browse the web, watch movies, etc no problems. Game for more than a couple of minutes and crash, every time.

    At first I thought it was my XFX R9 270X, so I grabbed my other one (I pulled these out of a crossfire setup on my other system) and same issues occurred. I was just starting think about returning motherboard when I came across this post. I am going to try this fix when I get home and see if it resolves the issue for me.