Does AMD Overdrive work for you?

[soundood]

simple question really, does it work for you?

and by working i mean, all the sliders work and you can adjust whatever options it gives you, that being differant options for differant chipsets. and also not leave you with an unstable system after use, ie: corupted bios, recurring windows BSOD, you get the picture

as this is very black and white, it is either a 'yes' or 'no' option, i was going to put 'sometimes' in, but i dont see the point.

i also havent put an 'end' time for poll, we can decide urselves when the the thread dies, or we have enough info to make a decision between us, we are after all, all grown ups. ;-)

feel free to post specific problems you have found with any release form the following,

AMD OverDrive™ Utility 1.0 (2007-5-23)
AMD OverDrive™ Utility 1.1 (2007-5-31)
AMD OverDrive™ Utility 1.1 (2007-6-1)
AMD OverDrive™ Utility 1.2 (2007-6-8)
AMD OverDrive™ Utility 1.3 (2007-6-18)
AMD OverDrive™ Utility 1.4 (2007-6-20)
AMD OverDrive™ Utility 1.5 (2007-7-11)
AMD OverDrive™ Utility 1.6 (2007-7-16)
AMD OverDrive™ Utility 1.7 (2007-7-31)
AMD OverDrive™ Utility 2.0 (2007-8-10)
AMD OverDrive™ Utility 2.0.1 (2007-8-17)
AMD OverDrive™ Utility 2.0.2 (2007-8-24)
AMD OverDrive™ Utility 2.0.3 (2007-8-31)
AMD OverDrive™ Utility 2.0.4 (2007-9-14)
AMD OverDrive™ Utility 2.0.6 (2007-9-25)
AMD OverDrive™ Utility 2.0.7 (2007-9-28)
AMD OverDrive™ Utility 2.0.8 (2007-10-12)
AMD OverDrive™ Utility 2.0.9 (2007-10-23)
AMD OverDrive™ Utility 2.0.11 (2007-11-26)
AMD OverDrive™ Utility 2.0.12 (2007-12-11)
AMD OverDrive™ Utility 2.0.16 (2008-01-18)
AMD OverDrive™ Utility 2.0.17 (2008-02-26)
AMD OverDrive™ Utility 2.1.0 (2008-03-14)
AMD OverDrive™ Utility 2.1.1 Beta (2008-06-02)
AMD OverDrive Utility 2.1.2 (2008-06-11)
AMD OverDrive Utility 2.1.3 (2008-09)

[macci]

Interesting poll, thanks for setting it up soundood

if it doesn't work for you I would like to hear what problems you are seeing, please also list some system details if seeing issues, such as:

mobo model:
BIOS version:
OS version and if its 32 or 64bit:
CPU model:
AOD version:

please note that AOD 2.1.3 is available now - LINK

UPDATE: AOD 2.1.4 is available - LINK

[soundood]

yeah no problem,

abit AX78
bios v13 (latest)
Vista/XP 32 bit (dual boot)
CPU 9850BE

ok, i set CPU multi to 10 say, reduce HT multi to 7 say, increase HT referance clock to 205 mhz, and wham BSOD, this is the same using many differant variants in CPU multi and HT multi, (all lower than stock, to test HT referance)

NB vid, cant and wont go higher than 1.3 v (although bios allows it)

incorrect readings of CPU vid, allways sais 1.3 v, even though its 1.4v in bios, how do i adjust that in the knowledge its wrong?

board status tab gives me no info on CPU voltage, although it sais 1.3v in performance options,

no GPU status for nvidia 9600gt, or is that intentional?

system info/diagram: no info that i have a graphics card at all, shows nothing on PCIe.

auto clock is useless, and even worse than Nvidias nTune effort

and lastly, (if there is a last) coruption of bios, if any settings are 'applied' that are to do with CPU Multi or HT Ref.

hope this helps

[NaMcO]

Works flawlessly.

[soundood]

Works flawlessly.

could you give us your rig specs? as you got the intel rig in your sig? mobo cpu, and graphics card would be great

7 for 1 against so far, not looking good, maybe im wrong after all?

[NaMcO]

I will have to apologise because apparently i misread. I was thinking Catalyst overdrive which works on my HD2900XT with no problems. I read your post now, dug it in google and noticed i screwed up :P

Once again i'm sorry for my mistake.

[soundood]

I will have to apologise because apparently i misread. I was thinking Catalyst overdrive which works on my HD2900XT with no problems. I read your post now, dug it in google and noticed i screwed up :P

Once again i'm sorry for my mistake.

lol, thats -1 to the yays then, thank you for correcting it

[Baam]

It works, but not that great. I get better overclocks through bios. Also ACC is blanked out on my GX motherboard. Using version 2.13

[macci]

thanks for the details and feedback soundood

definitely a bad experience there and quite different from what I have seen on other boards I've tried.

let me ask you a few extra questions and then we can move forward with this and get someone to fix it. In short it seems that the board needs a new BIOS to get these things fixed.

ok, i set CPU multi to 10 say, reduce HT multi to 7 say, increase HT referance clock to 205 mhz, and wham BSOD, this is the same using many differant variants in CPU multi and HT multi, (all lower than stock, to test HT referance)

so basically it hangs as soon as you try to adjust HT ref. clock? or does HT ref. clock adjustment work OK if you try to apply only that one slider at a time? if you keep CPU multi and HT multi at deafult and just adjust HT ref. clock it hangs? does it hang if you a smaller jump from 200 to 201 or 202MHz? or only when doing a bigger jump from 200 to 205 (or higher)?
This is probably an issue with the clockchip programming and can be solved via BIOS update (I have seen this before on another board and it was fixed by applying a different clockchip programming method - by the SBIOS).

NB vid, cant and wont go higher than 1.3 v (although bios allows it)

Please confirm that this happens with the 9850BE CPU? Also please confirm that we are talking about CPU NB VID (not Chipset voltage)? Do you mean that the slider wont go higher than 1.3V (NB VID slider) or that the actual voltage doesnt increase above 1.3V thru AOD? NB VID slider is read from the CPU directly and doesnt depend on mobo SBIOS. Black Edition CPU should allow up to 1.55V. if its a non-BE then it can be limited to 1.300V.
the SBIOS can allow higher values if its applying an OFFSET (fooling the VR) or overriding the VID value. AOD has no clue about this if the board doesnt report it to AOD (some boards do report and then you have an extra slider to adjust the OFFSET or value of Override - some boards dont, unfortunately).

incorrect readings of CPU vid, allways sais 1.3 v, even though its 1.4v in bios, how do i adjust that in the knowledge its wrong?

I assume you set it to 1.4V in the SBIOS and then AOD reads the CPU VID as 1.300v? This can happen if the board uses VID override or OFFSET control instead of just adjusting the VID value. BIOS should have the correct value in this case and you should verify the voltage thru the HW monitor.

board status tab gives me no info on CPU voltage, although it sais 1.3v in performance options

do you see any voltage values in the board status window?

no GPU status for nvidia 9600gt, or is that intentional?

AOD can read details from ATI GFX only.

system info/diagram: no info that i have a graphics card at all, shows nothing on PCIe.

this sounds like a SW bug - thanks for reporting it.

auto clock is useless, and even worse than Nvidias nTune effort

whats the issue you see with Autoclock? since this requires HT ref. clock adjustment it might be caused by the problem you mentioned above (hang with ht ref. clock adjustment due to BIOS problem)

and lastly, (if there is a last) coruption of bios, if any settings are 'applied' that are to do with CPU Multi or HT Ref.

adjusting CPU multiplier slider and hitting "apply" causes BIOS corruption?

[Cooper]

From my experience it really depends on the board. it does work in most of the cases, though I haven't checked all the features.
this thread might be a good database for AMD. Good idea

[macci]

Baam,

are you running in AHCI or RAID mode on that 790GX board when ACC is unavailable? Which BIOS version?

In some cases clocking thru SBIOS is better for finding the max clocks - especially with multiplier locked CPUs where you have to adjust HT ref. clock (and Memory clock) by more than 10%. Clocking thru BIOS allows the system to retrain memory etc that is impossible when tuning on the fly with AOD. On the other hand with Black Edition parts you should see the same results from BIOS and with AOD (assuming you dont need to increase HT ref. clock too much)

[Cooper]

btw macci this might sound irrelivant to the topic, but is it possible to implement different color schemes in AOD and allow user to change them. My eyes simply popped out in few minutes after seeing black text on red background

[Baam]

Baam,

are you running in AHCI or RAID mode on that 790GX board when ACC is unavailable? Which BIOS version?

Yes I am running raid with P03 bios version.

[macci]

Baam, thanks for confirming that. AOD 2.1.4 has a fix for that ACC bug. Should be out next week.

[Baam]

Thanks. I will give it a try when its out.

[Andi64]

Works great! It's a nice tool for those who don't know or want to use the BIOS.
But I don't like using it I only use software adjustments when the BIOS doesn't have the options I need.

Mobo model: DFI DK 790FX / MSI K9A2 Platinum
BIOS version: Latests official on both
OS: Windows XP 32b / Vista Ultimate 64b on K9A2
CPU model: Phenom 9850 BE
AOD version: 2.1.3

[demonkevy666]

older bios don't like to work with it well.

[MrMojoZ]

older bios don't like to work with it well.

Got to be careful saying that, people get mad when you infer the board is at fault.

[RhoXeD]

my 9850BE + MSI K9A2 Platinum AOD works flawlessly

now on my 9550 + ECS A780GM-A 90% of the options dont work, and its pretty useless compared to the BIOS

[hokiealumnus]

I have an AX78 as well and AOD won't allow Vcore adjustment. As such, since the Phenoms take pretty heavy Vcore adjustments on an SB600 board, I haven't been able to test anything else out. I assume the other adjustments work besides Vcore, but since it's locked, there is no sense in trying. I prefer BIOS OC'ing anyway.

[Particle]

AOD 2.1.0 and 2.1.2 both have worked well for me on the following gear:

MSI K9A2 Plat, BIOS unknown
Phenom X4 9850 BE
Windows Server 2008 Enterprise x64

The MSI installer package for AOD has to be modified for it to install on Server 2008 (as of 2.1.2), but it runs just fine.

Only oddity on the K9A2 I've noticed is that voltages bounce around a bit between settings applications. If you set the voltage slider to a voltage and hit apply, it will likely round to the nearest 0.025V and may change around each time you apply.

[soundood]

thanks for the details and feedback soundood

definitely a bad experience there and quite different from what I have seen on other boards I've tried.

let me ask you a few extra questions and then we can move forward with this and get someone to fix it. In short it seems that the board needs a new BIOS to get these things fixed.

so basically it hangs as soon as you try to adjust HT ref. clock? or does HT ref. clock adjustment work OK if you try to apply only that one slider at a time?

EDIT: i have just tried it again, and notices something else, if i move the slider to 202mhz, and then hit apply, it moves back to 200 mhz, if i move it to 2.5 mhz it starts screaming at me throught the speakers, that is the only slider that i have moved, before hitting apply.

if you keep CPU multi and HT multi at deafult and just adjust HT ref. clock it hangs? does it hang if you a smaller jump from 200 to 201 or 202MHz? or only when doing a bigger jump from 200 to 205 (or higher)?

see above reply, same thing happens

This is probably an issue with the clockchip programming and can be solved via BIOS update (I have seen this before on another board and it was fixed by applying a different clockchip programming method - by the SBIOS).

Thats all well and good, but i have had this board around 6 months now, and i am using the lastest bios, where do i get the new one? wait for it? the guys over at abit forum havent even seen a v14 Beta yet, let alone an 'update' surely this is something that AMD would have helped them with before the release of v2.1.3. AOD?

Please confirm that this happens with the 9850BE CPU? Also please confirm that we are talking about CPU NB VID (not Chipset voltage)? Do you mean that the slider wont go higher than 1.3V (NB VID slider) or that the actual voltage doesnt increase above 1.3V thru AOD? NB VID slider is read from the CPU directly and doesnt depend on mobo SBIOS. Black Edition CPU should allow up to 1.55V. if its a non-BE then it can be limited to 1.300V.
the SBIOS can allow higher values if its applying an OFFSET (fooling the VR) or overriding the VID value. AOD has no clue about this if the board doesnt report it to AOD (some boards do report and then you have an extra slider to adjust the OFFSET or value of Override - some boards dont, unfortunately).

This is indeed a 9850BE (the rig is in my sig, with cpu-z validation), and i am talking about the cpu NB vid, the slider will move up to whatever i can set, up to 1.45v i believe, but i hit apply and it moves back to 1.3v

I assume you set it to 1.4V in the SBIOS and then AOD reads the CPU VID as 1.300v? This can happen if the board uses VID override or OFFSET control instead of just adjusting the VID value. BIOS should have the correct value in this case and you should verify the voltage thru the HW monitor.

I have set 1.4v in bios, i then boot into windows and third party HW monitor see's it as 1.4v, i open AOD it sais 1.3v, sry but i am not adjusting it, unless you can gaurentee me a new board, if it fails due to overvolting.

do you see any voltage values in the board status window?

Here you go,

AOD can read details from ATI GFX only.

Then for me this whole thing is pointless, this software should be impartial. if GPU-Z can do it, why cant AOD?

whats the issue you see with Autoclock? since this requires HT ref. clock adjustment it might be caused by the problem you mentioned above (hang with ht ref. clock adjustment due to BIOS problem)

Maybe, but the problem remains a problem,

adjusting CPU multiplier slider and hitting "apply" causes BIOS corruption?

Yes, on three seperate occasions i have had the system prime blend stable, and had a play with AOD, (as i allways do with every release, just in case low and behold it works)

after setting the CPU to stock speeds in bios, i then moved the Multi slider and HTref slider for a play, usual lock up and so on,

i then reboot, and the system wont even get 30 secs into Prime before core 4 will fail, with 3 soon after.

hope this helps

And i got to agree with cooper, although i didnt mean it, this will be very handy for the AMD guys to have a look at, that way they can try to iron out these small glitches, to the point it may just work for all, i truly hope so, becuase in theory, i think its a fantastic idea, but in order for it to be 'up there' with cpu-z, or crystal CPU, or speedfan (older) and to basicaly make all these apps redundant for AMD users, it has to work flawlessly most of the time.

and in fairness, slagging something off, without giving a chance to correct it is not good. so i would report any probs you have here, however small, so the guys can have a look, or recreate the problem to analyze.

peace

[HondaGuy]

So far so good....CnQ Enabled

[Particle]

Let's not get all bent about AOD only working with ATI cards. The tool isn't meant as a total system information and tweaking portal (yet). It's meant to provide an interface for AMD's products. Asking why it won't work with nVidia GPUs is like asking why it doesn't overclock Intel CPUs. It's not so much a bug.

[Nedjo]

btw macci this might sound irrelivant to the topic, but is it possible to implement different color schemes in AOD and allow user to change them. My eyes simply popped out in few minutes after seeing black text on red background

I had same experience
add this line in Preference file under skin tags: skin-black
much, much better, but I'd still want back white/black scheme...