Very interesting find

[xPliziT]

Hi guys.

did some testing on vista64 bit.

With bios only adjustments my maximum stable clock speed was 3.1Ghz vs. 3.3Ghz on Win Xp32 Bit.

As expected.

I still run the DFI M2RS with SB600.

Somehow i discovered that the CPU VDDC setting in AOD does improve my oc significantly !!!!
My system would normally crash immediately with CPU VID at max (1.45V) at 3.2Ghz.


I was able to hit 3.3Ghz almost stable and as it seems 3.248Ghz stable with slightly reference clock oc with NB at 2.2Ghz.

This is really almost unbelievable because its impossible to get this oc with bios only settings.
So CPU VDDC does MUCH to your oc stability !!!

I wish AOD would not show so many bugs because otherwise it would be usefull everyday

Here is a screenshot of AOD and Cinebench results

[Particle]

Yeah. On my K9A2 the only adjustment I ever make is vDDC. The VID setting never even seemed to do anything (ie, non-functional) on it.

[soundood]

mmmm

i personaly hate AOD, i think because whenever i use it on my current rig it fails, or corupts my bios.

funny thing the other day, i was showing a mate the software (new release) and he was messing about with it,(but hadnt made any changes)

he moved the HT ref clock to 203 and hit apply...the rig went into this high pitched squeel and locked up, the speakers where way up, and he S**T himself.

funny

[xPliziT]

Its not VDDC alone !!!

You have to increase both VID and VDDC in a certain ratio.
Currently have mine VDDC little higher or same as VID but had to go safe running at 3.2GHz on vista 64bit.

[MrMojoZ]

mmmm

i personaly hate AOD, i think because whenever i use it on my current rig it fails, or corupts my bios.

But you don't hate your board which is causing the issue? Funny.

[xPliziT]

Yes i hate it but have no other choice until the asus comes out....

[nanohead]

But you don't hate your board which is causing the issue? Funny.

Nope, I hate AOD also, and not my board. It just sucks. I've had LOTS of boards that work with AOD (Asus M3A32-MVP, MSI K9A2 Platinum, DFI 790FX-M2R, Gigabyte MA780G-S2H, Gigabyte MA780-DS3H) and it sucks on ALL of them. I stopped using it on everything except the DFI, as it causes the LEAST damage there. The 780G boards get totally mutilated by it.

It reminds me of the severely brain damaged Nvidia control panel in the early days, when it would destroy the BIOS of the mainboard and you had to either RMA or reload BIOS.

There are TERRIBLE mismatches between AOD and mainboard terminology, as well as massive inaccuracies between things like voltage, memory settings, CPU settings, North Bridge and PCIe settings.

I can set up my DFI 790FX board to be 100% reliable at say, 3Ghz in BIOS, then load AOD after boot, and voila', the stability is completely gone, without touching anything. My favorite is how it SETS VCORE by itself. I can set it to 1.3V in BIOS, and when I startup AOD after boot, it LOWERS it to 1.25.

It sucks and needs a TON more work, especially coordination between the mainboard company BIOS developers and the AOD developers. It is PATHETIC. I can tell that AMD writes it, and just THROWS it over the wall the mainboard guys, who are all used to doing their own thing anyway.

Nasty nasty nasty software

[charged3800z24]

I am having no issues with AOD on my new board (in sig) nor on the K9A2 Plat. On the Plat i could get better over clocks using AOD, then using the bios.

[soundood]

But you don't hate your board which is causing the issue? Funny.

personaly i dont see anything funny about it, i love my AX78, and rate it up there with a few cracking boards i have had, including the ECS K7S5A.

this board has not let me down once, even though AOD has wrecked it a few times.

personaly i have been trying this kind of app for years, whether it be speedfan/crystal cpu and so on.

only time i found any to work, was on my forementioned ECS board, the northbridge would not go above 140 mhz, but with speedfan in windows i could hit 166 mhz.

last time i used AOD (new version) i dropped the ht multi to 8 phenom multi to 10 and upped the FSB, and resulted in lock up.

now i know how to flash a bios, and i think you will all agree, its a nailbiting process, evertime i do it, i panic a little.

now what if a newbie guy comes along, "hey AOD, im a O'clocker now" changes a few settings and corupts the bios?

for a newbie thats an RMA, for us its a bios flash

i love the concept, really i do, but i dont think its stable enough for widespread newbie use yet