@TJ H
that is my main problem. they ran it with "stock" settings, which in almost all cases means auto settings, which will allow for higher clocks than "normal" for asus/msi/asrock boards (didnt use/build any other brands last few years).
http://www.intel.com/content/www/us/en/support/processors/000006652.html
as you can see, not one cpu boosts to full turbo clock, once all cores are running, and unless intel has completely redesigned its 6xxx cpu (vs 5xxx) or turbo boost, this is still valid.
dont remember when exactly i first read about the "auto" settings ocing the system, but i know its happening since ivy bridge.
might just be on boards that allow for ocing (like Z series), but i know it now appears to happen with smaller chipsets too (a couple of MHz more on BCLK/chipset)
AFAIK it started with bench results varying too much, and after looking into it, they found the cpu was clocking beyond boost freq,
and i know i read about it on more than 1 site.
best example is a good friend of mine that couldn't play a game without crashing a driver (sensitive to ocing), and asked if he was ocing his 4790k, and he said "no, everything on auto".
after changing everything in bios to fixed/normal (intel's limits for that cpu), it wouldn't oc anymore beyond the boost clock, nor would it run boost freq on all cores when at 100% load (prime95).
but that changed again after he swapped the air cooler for a H100i, and now runs boost on all cores again.
and so far, any i5/7k (non-extreme tho) rig i worked on or helped with problems, were clocking higher than max boost freq under full load, and then didnt, once i set everything to normal/reg/man.