Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
the bios will ALWAYS read higher than windows due to it wont run any of the energy saving features.
maybe this is your issue?
do gigabyte have an overclocking app that you can run in windows?
i find that using the ASRock tuneup util gives me the best info for mobo/cpu temps aswell as all the voltages. i dont use it for anything other than a reference with realtemp and cpu-z.
I'd be pretty concerned if the 12V rail dropped an entire volt :/
have you tried running at stock settings?
if that works then its probs not the MB is borked, just that some settings aint correct.
Yeah I have thought about going back to stock, but my argument against was that it has been stable in prime (running prime now & no issues) for 6hrs + and the BSOD is so random and has only happened whilst having the power saving features enabled, though will give it a try.
In relation to the freezing I was having the other day, I found a thread where A guy had set his Corsair ram @ 1.5v and was having the same issues as I was, So he upped his volts to 1.61v and all has been well since.
http://www.sevenforums.com/crashes-debugging/145396-w7-random-lockups.html
Just in case anyone is having the same issues, mine seems ok now on that front, just these BSOD`s.....Will try stock settings with the power features enabled and disabled.
I'd be pretty concerned if the 12V rail dropped an entire volt :/
prime really isnt proof its 100% stable. its good as a guide, but i have had mine pass over 24hours of prime testing and fail on a video encode or something.
EDIT : if it was me, then as its universally agreed that 1.35v is 'safe' then i would bump it up to that, and do the tasks that are causing the BSOD. if that then stops them, lower it a notch and try again, until you get to the point where the BSODs come back. once you have this sorted and have stopped them in normal use, then prime it.
One word: Linpack.
Get Intel Burn Test and use that. Prime 95 has been useless for at least 5 years IMO.
Using it properly? Correct number of threads and amount of memory? What GFLOPS was it averaging?