aGeoM: I'll try higher volts. AOD is working quite flawlessly with P0F and P0H, so far.

Sapphire HD3870, yeah two in CF would block access to the buttons unfortunately.

Oldguy932: Thanks for the pics, pity about the CB. Don't you think that base needs some lapping and cleaning?
Keep going as high as you can on that stability testing.

Manicdan: Fingers crossed, I don't want it to happen now, again. About to reboot in a few...

jonspd: Doubt it yet, although they can add this BIOS option. Only way I've tried to disable a core is by using the Boot.ini (easily can disable any amounts of core before bootup).
Yep, disabling fix will work on all the MSI BIOSes, because the fix is the same one.

I discovered a bug earlier, it's an application bug affecting all monitoring applications but AOD when AOD is used to oc - it's temporary for CPU-Z, fixes itself after a while but most of the time it won't load the driver hence it reads wrong values. Check this out and the values it gives:




Bug remains in all other software but in CPU-Z/AOD after 15 minutes:




I believe this happens due the reason I've mentioned earlier-> opening more than on monitoring tool at the same time. I knew that was still 2550 because I had ran wPrime 32M and compared with 2530 and 2486 pics.