I think I may have borked my windows installation already - diagnostic mode plays funny with restarting. When I open up msconfig and select diagnostic mode, it takes about 30 seconds to actually get there, and the "Msconfig: Not Responding" is displayed at the top in the meantime. After restarting my system, it powers down before POST then up again as if there has been a fault, but it keeps trundling along happily and when in windows it sometimes detects a really random amount of memory, like 3.7GB, and I must have inadvertently run the test with about 3GB, hence the low GFlops. I've since managed to get diagnostic mode working properly/seeing all memory, but it's very temperamental...
Regarding GFlops: my main problem is that GFlops are going up and down with no change to voltage whatsoever... it's really annoying. Today I did two runs (at different times, with several restarts in between) with the exact same voltages of 1.4125 vcore/1.35 QPI, but I mysteriously lost 4GFlops somewhere along the line. Every single setting in BIOS was unchanged.
Thanks for chipping in pilsy.

Bookmarks