Does AMD Overdrive work for you?

I have reinstalled AOD 2.1.5 and for my surprise there is no more system freezing after changing from red mode to green mode when AMD power monitor is on. However going to red mode still does not change pc power scheme to "always on".
I think this should be handled by AOD when you go to green mode it should change the power scheme to "minimal energy consumption" and when switching to red mode it shold set it to "always on".
Is this too much to ask for? Why couldn't be implemented? This would be far away more clever energy administration than now.

It's really awful and bothering having 3 differents softwares to adjust the system performance (AOD, AMD Power Monitor, Fusion) one should handle everything even more if you consider 3 of them are being developed by AMD. Also would be cool a more clever (automatic) system energy and processor speed administration, that changes the system power profile and system speed depending on some calculation based on cpu load and system hysteresis(http://en.wikipedia.org/wiki/Hysteresis).

Well, I have a bit of a problem. If you check out the pic i'm running a Athlon XP 3200+ and I'm getting the "Cannot detect AMD CPU." Any suggestions?

http://img124.imageshack.us/img124/826/problemjz0.jpg

That's a current issue with some motherboards and version 215, however I wasn't aware this was even supposed to work on Athlon XP's.

fresh format of vista64. AOD still will not load. installs fine. after the disclaimer screen it says AOD has stopped working???? anyone esle have this problem and know how to get it working again?

Quote:

---

Originally Posted by SkullCracka

fresh format of vista64. AOD still will not load. installs fine. after the disclaimer screen it says AOD has stopped working???? anyone esle have this problem and know how to get it working again?

---

must be ran as administrator.

works fine on DFI DK JR 790GX but not on 790FX-M2R SB600

Ok folks.. I really enjoy using AOD, but have had Hit and Misses on different boards. Sometime it works, sometime it doesn't. When I mean work, I am specifically referring to adjusting Multiplier only.

I have found narrowed down the reason on my GigaByte GA-MA790GP-DS4H / F3 Bios. I only use this board becuase of the higher vCore vs the Asus M3A79-T Dlx.

If I set the HT to 1000Mhz (5x), or any other value, i cannot change the mulitplier 1x at all. No matter what I set the Mulitplier in BIOS. If I put HT to Auto, AOD will change the Mutiplier without an issue at all.

Has anyone seen or encountered this problem? I want to drop the HT to 1000Mhz (5x), so I can try to put higher Mhz.

- Ton

Hello!

I'm running my new Phenom II on a modest M3A78-T. Ok, my problem is... I need more vcore and AOD only allow 1.45.
Imagine i adjust the vcore to 1.5 on bios, then i open AOD and change the multi... Well, the vcore drops to 1.45 cause it's the max :(

Any suggestion?

goto overdirve installation directory and change the value of the preferences.xml

to <MaximumVCoreEnabled>1<


use notepad. this should be the correct setting as far as i can remember.

Anyone able to get it to install on Windows 7 beta?

I use it out of my Vista directory, just force .dll files to be opened with regsrv, register the files manually and it runs fine.

Edit: Other than it has never worked well for me other than memory timings. Anyone know how to force it to leave your vcore alone? I tried editing the xml file and parsing that, but no go.

Thanks xPliziT for your help but that doesn't worked for me :shrug::( Anyway, that should be the way to go

Quote:

---

Originally Posted by Lathode

Anyone able to get it to install on Windows 7 beta?

---

yes, daveburt, managed to get it working and has supplied the file for you to place in your system, just follow his instructions,

link: http://www.xtremesystems.org/forums/...6&postcount=19

now where is AOD v3.0.0? cmon Macci, were waiting muhuhahhahahaha :up:

Yeah works well for me.
Gigabyte 790x MB.
Athlon brisbane 5000+ BE OCed to 2.8 Ghz.

Quote:

---

Originally Posted by soundood

yes, daveburt, managed to get it working and has now where is AOD v3.0.0? cmon Macci, were waiting muhuhahhahahaha :up:

---

Yeah!!! Where is AOD3.0?? They have been anounncing it for almost 2 months! :S
It doesn't look well of AMD announcing something months before just to do some noise.. not serious..
Maybe something it's going on in AMD since also ATi Catalysts drivers doesn't reach users desires. :(

Quote:

---

Originally Posted by Marco André

Hello!

I'm running my new Phenom II on a modest M3A78-T. Ok, my problem is... I need more vcore and AOD only allow 1.45.
Imagine i adjust the vcore to 1.5 on bios, then i open AOD and change the multi... Well, the vcore drops to 1.45 cause it's the max :(

Any suggestion?

---

Same :( Can only manage 1.25 max.

Program works though:
MA78GM-S2H SB750/780G
Windows 7
AM2 X2 4600+

Quote:

---

Originally Posted by Polaco

Yeah!!! Where is AOD3.0?? They have been anounncing it for almost 2 months! :S
It doesn't look well of AMD announcing something months before just to do some noise.. not serious..
Maybe something it's going on in AMD since also ATi Catalysts drivers doesn't reach users desires. :(

---

A whiner-thread per exellenece!

Thread starter showing very little respect for knowledgeable people trying to help/explain.

This has been pointed out before:
AOD is a software.
It relies on reading Bios/extracting PLL-info.. really "low-level" things.
Some MB/Bios-manufacturers implement "feature" to make AOD not work.
(eg Asus M3A78-EM or similar.. only allowing increments 0.05, 0.1..etc on Vcore.. and nothing else).

If you want full control on OC, do it from Bios, or find a utility suitable for your system.
K10STAT is one utility that allows adjustments of VCore.. and multi's.
I have found that it *may* allow you to adjust VCore more/better than AOD if you need it (usually only downwards).
But you need to understand it is "VID-based" and shows 1.35 as "current" after boot-up, even if you have set 1.45 in Bios.
Having CPUZ "open" will show the effects of using K10STAT to change VCore.

But still, Bios is the place to OC.
AOD, SetFSB, K10STAT.. and more.. are "just" tools to make it more convenient for further adjustments/testing from Windows.

Quote:

---

Originally Posted by TL1000S

A whiner-thread per exellenece!

Thread starter showing very little respect for knowledgeable people trying to help/explain.

This has been pointed out before:
AOD is a software.
It relies on reading Bios/extracting PLL-info.. really "low-level" things.
Some MB/Bios-manufacturers implement "feature" to make AOD not work.
(eg Asus M3A78-EM or similar.. only allowing increments 0.05, 0.1..etc on Vcore.. and nothing else).

If you want full control on OC, do it from Bios, or find a utility suitable for your system.
K10STAT is one utility that allows adjustments of VCore.. and multi's.
I have found that it *may* allow you to adjust VCore more/better than AOD if you need it (usually only downwards).
But you need to understand it is "VID-based" and shows 1.35 as "current" after boot-up, even if you have set 1.45 in Bios.
Having CPUZ "open" will show the effects of using K10STAT to change VCore.

But still, Bios is the place to OC.
AOD, SetFSB, K10STAT.. and more.. are "just" tools to make it more convenient for further adjustments/testing from Windows.

---

hey thanks :up: we all really needed you two cents, if you care to read even some of the posts, you would realise this is old news.

looks like your trolling actualy, are you? :rofl:

Quote:

---

Originally Posted by TL1000S

A whiner-thread per exellenece!

Thread starter showing very little respect for knowledgeable people trying to help/explain.
blah, blah, blah..
....

---

Ok, first of all. A company like AMD can not release a product that it's announced as a "secret weapon" when it has so many bugs as previous versions had and also that don't provide some more intelligent or progressive auto overclocking / auto power managment feature. Instead they should state AOD as Derringer hidden in a poket which it's quite different than a "secret weapon".

I really wish this tool would have been as stated. I really really like AMD and ATI they are absolutley awesome. (All my cpu's and video cards had been of them ever before AMD bought ATI and I always have been happy with their products including now).

I just feel that the software isn't at the same level that they hardware. That is just my opinion and anyone can say whatever he wants. In the end companies could benefit from users reviews and opinions.
Where we would be if AMD doesn't existed? Paying 1000u$d a CPU maybe?.


all the best.

I've attempted to keep current on this issue.... but I have found a bug in AOD I have not read about. Perhaps someone posted somethign about it... but I didn't see it. IF NOT then:

HEY PEOPLE: I FOUND A BIG BUG in AOD. (Shocking, no?)

=======
When running AOD I see the following behavior:

If I have a single video card and use a single monitor... AOD shows 1 GPU in the "GPU STATUS" screen in AOD.

If I have a single video card and use dual monitors... AOD shows 2 GPU in the "GPU STATUS" screen. It apparently "mirrors" or "ghosts" the card because of the two monitors. But AOD works okay.

If I have 2x4850 and a single monitor hooked up... AOD starts up and shows 2 GPU in the "GPU STATUS" screen.

If I have 2x4850 and dual monitors hooked up... AOD starts up and shows 4 GPU in the "GPU STATUS screen. So 2 real and 2 "Ghost" monitors. But AOD works okay.

If I set it to 3x4850 and a SINGLE monitor is hooked up... AOD starts up and shows 3GPU in the "GPU STATUS screen. Yes... it correctly shows all three. And AOD works okay.

========================================
AND the Crowning PROBLEM: (And what I think is doing it.)

If I have 3x4850 and dual monitors... AOD crashes while trying to start.

I suspect that it is attempting to show 6 GPU in the "GPU STATUS" screen. Three "real" cards and three "ghost" cards. But since it can't.... it fails with a APPCRASH AMD Overdrive.exe error. (In the QtGui4.dll which is a GUI library... it is trying to put 6 GPU status into space of 4. KABLAM.)

You CAN set Crossfire to use 2x4850, start AOD, and then set it back to 3x4850 back on...... that will work if you need AOD.

:-( No go here Maybe they will update AOD tomorrow with the Cat 9.2's? Wont work with my BE 720 and GB 790X

Quote:

---

Originally Posted by soundood

yes, daveburt, managed to get it working and has supplied the file for you to place in your system, just follow his instructions,

link: http://www.xtremesystems.org/forums/...6&postcount=19

now where is AOD v3.0.0? cmon Macci, were waiting muhuhahhahahaha :up:

---

Sweet. thanks.:up: