We would like to thank the following companies for supplying and supporting us with our test system hardware and equipment: Intel, ASUS, MSI, Western Digital, MemoRight and Corsair.
As we've started to test a good bunch of Z87 motherboards, we've really got the chance to expand the lineup of boards in our graphs. Alongside the ASUS MAXIMUS IV HERO which we'll be running at stock and overclocked speeds which we'll cover in more detail in just a few moments, we've also got a number of other Z87 motherboards featured.
We've got the MSI MPOWER MAX, ASRock Z87 OC FORMULA and GIGABYTE Z87X-OC. All Z87 boards that have impressed us so far catering for different people and at different price points. Along with the Z87 offerings, though, we've also got the MSI Z77A-GD65 Gaming and GIGABYTE X79S-UP5-Wi-Fi to round things off.
Heading into the BIOS we started to adjust all the voltages to the appropriate level and move our CPU multiplier up to 50x for an even 5GHz. Like we've seen on other boards using this CPU, getting into Windows isn't an issue at this speed. As soon as we start our MediaEspresso encode, though, we run into problems and get a BSOD. We headed back into the BIOS and saw if bumping up the voltages a little more would help, but in the end, 5GHz stable wasn't going to be an option.
Heading back in we moved to the 49x multiplier and went into Windows. We ran our MediaEspresso encode with no problems. With somewhere between 4.9GHz and 5GHz being the number we expect to land on with this CPU, we headed back into the BIOS and started to mess around with the BCLK.
After a whole bunch of reboots, a whole bunch of voltage and BCLK adjustments, we just couldn't get the CPU stable above 4900MHz flat or 4.9GHz as shown in our graphs today. It didn't seem to matter what we did, even moving to a 100.5 BCLK would result in a BSOD during our MediaEspresso encode. It's worth noting that at 100.5 - 101 BCLK our encode would go into the 80% completion mark before the BSOD. It didn't matter what we did with voltages, though, we just couldn't get it 100% stable, which is always the most important thing for us.