I had to update IBT manually by adding the new Linpack files that enabled AVX. This made a huge difference in the amount of GFLOPS that the program reported ~57 - ~110, and a significant change in the temps too. Of course, my CPU doesn't make use of hyperthreading, so that might be the difference. IIRC, hyperthreading actually slows down performance in IBT, so you might try disabling it for maximum CPU torture.
EDIT: A bit of Googling reveals that IBT 2.51 has the new Linpack libraries, but 2.5 did not. I think you might need SP1 to make it work properly. The general consensus is that for SB, AVX Linpack is the ultimate heat producer, so something seems to be fishy if you're getting higher temps with Prime95.
This thread for more info:
http://www.overclock.net/intel-cpus/1007442-gflops-question.html
Back to this. . . . First, I still need to review the link you gave, but there are some distractions at the moment -- so a little later today . . .
Second, I disabled HT in BIOS, and ran PRIME for at least 10 or 20 minutes, followed by a minimal 5 iterations of IBT. Now with four threads, Prime reaches 65C only here and there on the hottest core. IntelBurnTest reaches about 68C at maximum as recorded in the Min/Max lines of the dialog.
You would agree that we are talking about a very real set of mathematical relationships between voltage, temperature and loaded speed. For Extreme OC'ing, there are some exponential curves where one is trying to find a point that is already on the part the curve after turning sharply upward -- these things were explained with graphs in a 2007(?) ('08?) Fall article here at Anandtech on what was then the just-released high-end Yorkie.
While we want to push it to a comfortable chosen limit, these things are equally important to someone who does not include "extreme" in the priority list. We all want to know where those curves take sharp bends at various levels of VCORE, temperature and speed.
I'm wondering if there is really lacking any linear correspondence with how PRIME and IBT load the cores across the scenarios of HT Enabled or Disabled. But a three degree difference with high-load VCORE at 1.288V or so, bCLCK 103, Turbo Multi of 42 and speeds shy of 4.4, such a difference doesn't seem too significant.
That may all change if I increase the multplier another notch or two, try to sqeeze between 104 and 107 out of the bCLCK, and either SET VCORE higher or let "Auto" take it there.
But the inconsistencies with the shareware monitoring SW just-recognized this week, I'll have to go back and retry the settings in that range -- all over again. And be mindful that I use the ASUS monitor . . . .