GIGABYTE G1.Sniper Z87 Review
by Ian Cutress on February 24, 2014 2:00 PM EST- Posted in
- Motherboards
- Intel
- Gigabyte
Many thanks to...
We must thank the following companies for kindly providing hardware for our test bed:
Thank you to OCZ for providing us with 1250W Gold Power Supplies and SSDs.
Thank you to G.Skill and ADATA for providing us with memory kits.
Thank you to Corsair for providing us with an AX1200i PSU, Corsair H80i CLC and 16GB 2400C10 memory.
Thank you to ASUS for providing us with the AMD HD7970 GPUs and some IO Testing kit.
Thank you to MSI for providing us with the NVIDIA GTX 770 Lightning GPUs.
Thank you to Rosewill for providing us with the 500W Platinum Power Supply for mITX testing, BlackHawk Ultra, and 1600W Hercules PSU for extreme dual CPU + quad GPU testing, and RK-9100 keyboards.
Thank you to ASRock for providing us with the 802.11ac wireless router for testing.
Test Setup
| Test Setup | |
| Processor |
Intel Core i7-4770K ES 4 Cores, 8 Threads, 3.5 GHz (3.9 GHz Turbo) |
| Motherboards | GIGABYTE G1.Sniper Z87 |
| Cooling |
Corsair H80i Thermalright TRUE Copper |
| Power Supply |
OCZ 1250W Gold ZX Series Corsair AX1200i Platinum PSU |
| Memory |
G.Skill RipjawsZ 4x4 GB DDR3-1866 8-9-9 Kit ADATA XPG 2x8 GB DDR3L-1600 9-11-9 Kit |
| Memory Settings | XMP |
| Video Cards |
MSI GTX 770 Lightning 2GB (1150/1202 Boost) ASUS HD7970 3GB (Reference) |
| Video Drivers |
Catalyst 13.12 NVIDIA Drivers 332.21 |
| Hard Drive | OCZ Vertex 3 256GB |
| Optical Drive | LG GH22NS50 |
| Case | Open Test Bed |
| Operating System | Windows 7 64-bit SP1 |
| USB 2/3 Testing | OCZ Vertex 3 240GB with SATA->USB Adaptor |
| WiFi Testing | D-Link DIR-865L 802.11ac Dual Band Router |
Power Consumption
Power consumption was tested on the system as a whole with a wall meter connected to the OCZ 1250W power supply, while in a single MSI GTX 770 Lightning GPU configuration. This power supply is Gold rated, and as I am in the UK on a 230-240 V supply, leads to ~75% efficiency > 50W, and 90%+ efficiency at 250W, which is suitable for both idle and multi-GPU loading. This method of power reading allows us to compare the power management of the UEFI and the board to supply components with power under load, and includes typical PSU losses due to efficiency. These are the real world values that consumers may expect from a typical system (minus the monitor) using this motherboard.
While this method for power measurement may not be ideal, and you feel these numbers are not representative due to the high wattage power supply being used (we use the same PSU to remain consistent over a series of reviews, and the fact that some boards on our test bed get tested with three or four high powered GPUs), the important point to take away is the relationship between the numbers. These boards are all under the same conditions, and thus the differences between them should be easy to spot.
Windows 7 POST Time
Different motherboards have different POST sequences before an operating system is initialized. A lot of this is dependent on the board itself, and POST boot time is determined by the controllers on board (and the sequence of how those extras are organized). As part of our testing, we are now going to look at the POST Boot Time - this is the time from pressing the ON button on the computer to when Windows 7 starts loading. (We discount Windows loading as it is highly variable given Windows specific features.) These results are subject to human error, so please allow +/- 1 second in these results.
Hitting sub-10 seconds at stock is rather good, as well as sub-8 seconds when features are disabled.
Facebook
Twitter
RSS
36 Comments
View All Comments
Flunk - Monday, February 24, 2014 - link
Really? I didn't know that discrete GPUs used exactly the same chipsets as onboard GPUs and sometimes even inferior DACs. Oh wait they don't, making your comparison ridiculous and nonsensical.apoe - Monday, February 24, 2014 - link
I have used exclusively sound cards for almost a decade. The first time I went from onboard to discrete, I was using a 5.1 system and the difference was massive. Recently I plugged my Beyer DT770s into the onboard (ALC1150) just to see how bad it was... and surprisingly, the audio quality was exactly the same. In fact it was better, since the sound card (HTO Striker) would pick up EM interference resulting in a buzzing noise whenever the frame rate went >140 fps in any game, yet this didn’t happen with the onboard audio. This buzzing under load is apparently still a common problem with discrete cards, which I guess is why some of them have shielding now.Kaihekoa - Monday, February 24, 2014 - link
Have you tested this theory recently? The tech has made good progress. In my experience, the biggest difference in sound quality comes from the speakers/headphones these days.Samus - Monday, February 24, 2014 - link
Totally, it takes a hell of a pair of phones or speakers to actually measure the SNR difference from one audio codec to another. Most of it comes down to capacitor quality these days since many caps aren't even designed for audio. I've replaced caps with Panasonic FM's and still couldn't tell the difference on my Beats (j/k I wear Grado's)lever_age - Monday, February 24, 2014 - link
How are you getting the SNR figure from the graph under the RMAA section? Integrating and A-weighting in your head? Calculating with what?For what it's worth, RMAA is supposedly giving you A-weighted noise and dynamic range figures, which should deemphasize ultrasonics. So the figure for the motherboard as-is should be fine... as fine as RMAA is in general (frequently strange, high on bugs, and low on documentation). Though I believe the weightings are not defined above 20 kHz, so I don't know if they just carry through the equations / curves, notch them out for the actual calculation, or just use the weighting for the 20 kHz and extend it out to the ultrasonics.
popej - Monday, February 24, 2014 - link
RMAA can be configured to compute noise and distortion only in range 20-20kHz. And probably this is default setting, so problem simply doesn't exist. Please check your settings.And of course an attempt to estimate noise floor from the graph is plain wrong.
DanNeely - Monday, February 24, 2014 - link
Have Creative's audio drivers gotten any better in the last 7 years? Their being bad enough in the first part of the prior decade that MS ripped the entire audio sub-system into userland to stop Creative's buggy drivers from BSODing the system is still fresh in my memory; and of more potential concern again now because to improve power management on tablets Win8 has moved the audio sub-system back into the kernel where boggy drivers can crash the system.ViRGE - Monday, February 24, 2014 - link
For what it's worth I've been running an X-Fi Titanium for years without any issues. So I'd say their drivers are fine.As for Vista, my understanding is that it was Realtek that was BSODing everywhere and was the biggest motivation for the audio stack change, not Creative.
Nfarce - Monday, February 24, 2014 - link
Exactly, ViRGE. I've been usinggg an X-Fi Titanium for nearly 5 years now, bought originally and put into a C2D Duo/Vista gaming build, now being used in a near 3 year old i5/Win7 gaming build. No problems. And the sound blows away Realtek. Sounds like user error to me for this guy.angrypatm - Monday, February 24, 2014 - link
I had an X-Fi Titanium and the drivers sucked, and the "critical updates" which would remove the entire program and require full reinstall took longer than loading an O/S -and you had to baby sit through the whole process to click yes or proceed. Afterward, no difference, still clunky and slow, and unreliable. Critical update for a sound card? Never fixed anything. I moved away from Creative to the CMedia based HT Omega Claro Plus, quick uncluttered app, sounds better, and rock solid, NO problems. And creative's crystalizer is btw artificial nonsense.