Yeah, that's what I think. In order to get CPU speed, you should drop cache to 35, maybe, and maybe lower memory a little bit, run 1600 or 1333 if you aren't already.
Your chip is 1.070 V @ stock..to me, that's 4.3 GHz chip. 1.060 V is 4.4 ghz, 1.050 is 4.5 GHz, on down to 0.950 V.
But then, I see that PolRoger, who should have a 4.9/5.0 GHz chip, isn't getting that clock yet.
Of course, I came to this "bin by BIOS V" from having 15 chips only, maybe I haven't had enough chips yet. Seems we are missing something still, or pushing the Cache is the issue, since PolRoger is pushing cache higher than what I think it should run at.
If you run cache/CPU at 1:1, or like cache 3x multi down from CPU, my "rules" don't apply, since that changes the loading characteristics of the chip.
Overclocking while running reboots, rather than shut-down, will lead to false stables, IMHO. I ALWAYS fully shut down a stable clock, leave the rig for a couple of hours, then come back and boot it up to see if it works. Cold boots and reboots get slightly different results, has been that way for a few generations now. I have a video on my youtube channel back form 775 days, on the Foxconn BlackOps board, showing how timings can change in reboots when system warms up, and that was many many years ago. I still look for this behavior, and I see discussions with the extreme guys dealing with setting RTLs properly. These chips are easy to a point, then OC becomes MASSIVELY more complex.
