Quote Originally Posted by justapost View Post
Bro your chipset voltages are too high. My board ran stable with those at the lowest possible values. Four hours of prime95 do not mean that much, I ran prime96 for nine hours at 2.9GHZ/2.2GHz before it failed , 2.8GHZ/2.4GHz failed prime95 after ~13hrs. At 2.9GHz however i had the freezing issues, the setup i primed for hours froze after a few minutes just surfing the web, repeatable.
You plan to go above 2.8GHz?

During my first testings i first had freezing issues at 2.9GHz with NB speeds below 2.4GHz. I thought i could fix the freezings with an 2.4GHz nb but this turned out to be impossible due to the high voltage the nb would have required.

Looking at my testings with nb at 2.4GHz i think >1.4V for ~30hrs was too much even at a cpu temperature around 60°C. I used the bottom-up-lowest voltage method here and started at 1.3V.

After that test I started to realize I get those idle freezings even at 2.8GHz in winxp 32bit. So I think i'd better tested the nb speed via ref HT increasement with an 11x multi.
What do you mean chipset voltage is to high? Which setting? If you mean CPU-NB Voltage I set it the same as CPU Vid as suggested by DFI Engineers and have yet to have a issue. Also I find since doig that I was able to kick it down 1 notch with CPU Core

I will OC more when my cat is better and I have time right now it has to wait!