Quote Originally Posted by drunkenmaster View Post
still can't work out what aod is changing that i haven't done in bios myself that can cause a drop in performance. meh, will track it down eventually.
The AOD button? Or a half enabled patch?
Quote Originally Posted by AlabamaCajun View Post
What I suspect it a stored value from learned settings eventually comes back to bite your tail when you progressively OC. From these experiences, you have to pull the RAM and drop one stick of different timing RAM to get the number(s) to correct settings.
Anyone want to back up or prove this wrong, go for it. I would just like to see my board work.
This is exactly what happened with my Phenoms on both a DFI and an MSI. Esp. if you use AOD to get a failed oc, when it reboots, the BIOS doesn't clear the settings, so you fail bootup until you clear CMOS, but the problem is, *some* BIOS settings don't get cleared even with the battery out unless you leave the system off without power for over 8-9 hours. Then you can attempt to boot with minimal components installed and just one DIMM and it should work fine... until you repeat such a procedure. Many times that'll kill your Windows install totally, I mean you won't be able to recover your HD docs which makes me think, it's actually the PCIe gettin stuck at highr than 100MHz which causes these problems in the first place

I am still working on it with the devs to see if its a BIOS issue but I have tried clocking using AOD at time, closed it and restarted it to see the PCIe at plus 120MHz, sometimes reading 150-190MHz and then crashing.