Yes, it works great
No, it just wont work properly for me
FX-8350, Powercolor ATI R9 290X LCS, OCZ Vertex 4, Crosshair V Forumula-Z, AMD Radeon DDR3-2133 2x8Gb, Corsair HX1000W, Thermaltake Xaser VI, Xonar D2X, Water Cooling 140.3
merkk1, i have the same board, i actually think the foxxone software conflicts with aod. i tryed foxxone first after flashing my bios to the latest level.it worked ok. then i installed aod and it would not work. uninstalled foxxone and aod worked perfect.
as my dear old nana used to say, if you havent got anything to say, then dont say it,
and thank you for putting me on your ignore list,
thats 5 anymore?
and also this is around the 10th time i have heard the vapourware v2.1.4 of AOD mentioned, this non excisting ware is going to solve a lot of problems i believe
i truly hope for AMD's sake it does, because i have heard this around 10 to 15 times in the past, and it has never worked, and as much as i hate to say it, if peeps come on here and report it has bugs, i will laugh my socks off, i wont quite say 'told you so' but you will get the drift when it happens.
also where is the logic of even releasing v2.1.3? if there is a v2.1.4. up for release the week after? why not just wait and release 2.1.4. as 2.1.3. and miss out this still handicapped version?
seems a bit skittish to me
got cool and quiet enabled? wonder why those Everest CPU results are taking a hit? read this:cool and quiet problems, theorys from Anandtech
and please remember folks, even one small bug here, merits a fail (and also a no vote). from misreading on your CPU VID say through to not seeing your full list of componants in status monitor, it is the only way this will be fixed. thank you
Last edited by soundood; 09-13-2008 at 12:14 AM.
You've had nothing to say since page 1, yet you continue to say it.
A no vote in the poll doesn't necessarily say the user finds AOD useless.
I find it improbable that any software works in 99.9% of machines out there. Too many different setups. I also find it incredible that you believe your hardware can't possibly be faulty. I have fixed many machines whose hardware couldn't possibly be the culprit.
The only bully I see in this thread is you. You shout louder, longer, and more often than anyone else here. Might I invite you to visit another thread.
Only problem I have is only 1 GPU is shown.
5400+ (65 nm) 3.2 Ghz @ 1.344v
Tuniq Tower
DFI DK 790FX M2RS
2 Gb Adata DDR2 5-5-5-15
HD 3870 X 2 crossfire
Coolermaster RC690
Antec Earthwatts 500
as i said before i can name you 100 pieces of software that work flawlessly on windows, after half of the revisions
yes i do speak longer, its called having something to say, unlike you, who decides to flame bait with stupid comments, how you work out im shouting is beyond me, you got a microphone in my house?...lolThe only bully I see in this thread is you. You shout louder, longer, and more often than anyone else here. Might I invite you to visit another thread.
and so we kick off with v2.1.4, anyone got a problem?...lol
then it doesnt do what it is supposed to do, therefore a fail...lolOnly problem I have is only 1 GPU is shown.
and so we kick off with v2.1.4, anyone got a problem?...lol
Last edited by soundood; 09-19-2008 at 08:42 AM.
AOD v2.1.4., here we go again (all performed on a clean image (no previous AOD) of Vista 32 bit)
1) lock up and squeeling from speakers, when HT ref slider moved by 5 mhz and hitting apply, (rig at stock 2.5 gig, stock multi and stock HT ref in bios)
2) moving multi slider from 12.5 to 13 results in same lock up as above
2) nothing but temps in status monitor/ board status
3) nothing in GPU status (cause its an nvidia card doh)
4) system information/diagram view no card detected in any Pcie slot
same old, same old here, as far as i can see nothing has changed, how you doing macci with that new AX78 of yours?
i will give this poll 7 more days, combining input from other users at AMD forums, and two other well known forums, i fully intend to publish these results, good or bad, using this and other data to back up my claims. including me, i have allready seen 5 to 6 cases of this not doing anything new, and has not fixed a number outstanding issues, that were meant to be addressed in the 2.1.4. release.
since the last 'discussion' i have managed to get hold of two other mob's, for the purposes of being fair, i wll not mention the makers, other than i have 1 more SB600based board, and one SB750 based board, both leave a lot to be desired with AOD 2.1.4. so far, although i have still to bench them with a 9850BE yet, both have been benched with 5000BE x2.
and of course i will pass on my results ...lol
let the flame baiting begin...lol
Last edited by soundood; 09-19-2008 at 09:11 AM.
Your problem is the simple fact that abit did not support AOD functionality with the AX78. If the BIOS support is not there, then AOD is not going to operate correctly. Change boards or complain to abit, otherwise you will continue to have problems. It really is that simple.![]()
i do hear you and have taken it on board, but its not about ABIT, where does it say in this release that it works on certain boards? and doesnt for others.
in the marketing it states you need a 7 series chipset, i have it. but AOD doesnt work. who's fault is that? AMD like any other designer has tight control on there 'referance' designs, hence why nearly all the 770 boards are the same.
as for changing boards, you didnt read my post correctly, i bnow have three mobo's here, 2 x sb600's and 1 x SB750, all are showing problems with AOD, granted small probs, but probs all the same.
it is really that simple
ohh and for every post i have here telling me i am at fault or the board is at fault or andy pandy is at fault, i have one that says otherwise, i also have a lot of support in this, i dont stand alone here, like a newbie. i know exactly what i am talking about. and will continue with this until i see an acceptable resolution. ie: if AMD releases this software with a compatible board list.
Last edited by soundood; 09-19-2008 at 09:57 AM.
On the AX78, are you really seeing BOTH of these problems when using a Phenom CPU or one with Phenom and one with K8 (the 5000BE X2 you mention in your post)? I'm asking as this is NOT in line with what I see on AX78.
I am seeing issue #1 if I use a Phenom on AX78 and issue #2 if I use a 5000BE X2.
I dont see #2 with Phenom and I dont see #1 with K8.
Issue #1 has to do with Clockchip programming (as I previously mentioned). the board (SBIOS) is programming the clock a bit too aggressively when AOD requests a clock adjustment on the fly. The fix is to change the clock programming code in the SBIOS. Unfortunately this has not been implemented on this particular board's SBIOS.
In case of K8 CPU (5000BE X2) this doesnt usually cause any issues (in fact I could jump from 200 to 240MHz in one shot without any issues w/ 5000BE X2). With Phenom a bigger HT ref. clock adjustment (on AX78) usually hangs the system. But it does work OK if you go in 1MHz steps.
I got it up to 224MHz (from 200MHz) via AOD when I adjusted 1MHz at a time - these steps:
1) set slider to 201 (it sets it back to 200MHz)
2) set slider to 202 (it sets it to 201MHz)
3) set slider to 203 (it sets it to 202MHz)
4) continue as far as needed
In case of Phenom the HT ref. clock is used for Fine tuning (As all the relevant multipliers are unlocked). so you dont usually need to adust this very much.
With Phenom 9600BE (I also tried 9850BE) I didnt see any problems adjusting the CPU multiplier or HT multiplier values (yes, I did try all HT multipliers and a number of HT+CPU multi combos). Please confirm if you saw this problem with Phenom or K8 (AX78 has problems with K8 and CPU multiplier, more details below).
Here is a screenshot of Phenom 9600BE with AOD 2.1.4 on AX78. I tuned the following items (system was booted up at default values from SBIOS):
CPU Multi to x13 - OK
HT Multiplier down to x7 - OK
adjusted CPU VID and CPU NB VID - OK (also measured with multimeter to confirm)
adjusted Memory voltage - OK (also measured with Multimeter to confirm)
adjusted HT ref. clock 1MHz at a time up to 224MHz (from 200MHz)
end result: a bit over 600MHz OVCK with default aircooling, all done on the fly with AOD on AX78.
Issue #2 was not seen on my AX78 (BIOS 1.3) with Phenom 9600BE or 9850BE. No problems with CPU multiplier or HT link multiplier adjustments with Phenom CPU (yes, I did try all HT multipliers and a number of HT+CPU multi combos).
I did see a problem with K8 (5000BE X2) though and it appears that AX78 SBIOS has fundamental problems with CPU multiplier control. CoolNQuiet doesnt work either - the multiplier is adjusting VERY slowly and to incorrect values (it goes to the low state even if OS is in High Performance mode). AOD and CoolNQuiet use the same commands to request multiplier changes, in case of this board the SBIOS doesnt do it correctly.
With K8 CPU the HT ref. clock slider and all voltage controls worked as they should though.
Here is a quick example of AOD clocking with K8 on AX78 board.
Note that the CPU VDDC slider tells you the actual CPU voltage in case of K8 CPU (as it controls the OFFSET on top of CPU VID value).
the HW monitoring chip on this board is not supported by AOD at this point.2) nothing but temps in status monitor/ board status
Is this with K8 or Phenom?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?
In case of Phenom I didnt see an option to dial in the actual voltage in AX78 SBIOS, there was an option to adjust the OFFSET (+0.xx V) but no option for adjusting the CPU VID value or the actual CPU Voltage value (to 1.3 or 1.4V).
I didnt see a problem with CPU NB VID slider on AX78 when using Phenom CPU (see the screenshot - its at 1.45V and can go up to 1.55V).
Note that with K8 CPU there is no separate control for CPU NB VID.
With K8 CPU the CPU Voltage item (in SBIOS) is different and you can adjust the actual value (not just the offset). If I set it to say 1.400V then AOD would read the CPU VDDC slider at 1.400V (CPU VID at 1.300V as 1.400V actual voltage is achieved via OFFSET on top of VID value).
example:
such as?has not fixed a number outstanding issues, that were meant to be addressed in the 2.1.4. release.
What is the problem then? "For the purpose of being fair" you should mention the problem you see and the board (+SBIOS) you used. Then we can get it fixedsince the last 'discussion' i have managed to get hold of two other mob's, for the purposes of being fair, i wll not mention the makers, other than i have 1 more SB600based board, and one SB750 based board, both leave a lot to be desired with AOD 2.1.4.
If you read thru this thread you'll see that it fixed a number of other issues as well.Told Ya So, 2.1.4 doesnt solve a thing apart from AHCI and RAID issues
as far as the accuracy of the poll:
there are folks who have voted "no" initially and now have got their AOD working (by updating to AOD 2.1.4, by updating motherboard SBIOS...) and would be voting "yes" at this point.
Last edited by macci; 10-02-2008 at 12:31 AM. Reason: added Vcore pic
Let's get this out of the way first, SB600 sucks for Phenoms, it was design for Athlon64's even then it sucked. My biggest problem with the SB600 has been the USB controller, it has cause me a quite a few problems(I destroyed a KVM switch because of it).
Hey Macci
On 2.1.4 my only complaint about it is in Status Monitor>GPU Status>Engine shows 0 MHZ
On the M3A78-T and my new sweet ride M3A79-T Deluxe the same thing happened
Otherwise AOD 2.1.4 works great on the new board![]()
i would say it works very well, 3544 mhz http://www.hwbot.org/result.do?resultId=773427 i see 3.5 or maybe 3.6 0n h2o coming soon. i think i will try to use aod to do it .![]()
macci all iterations I have used in 3 of my Gigabyte boards (790FX-DQ6, 780G-S2H and 790GP) have worked flawlessly. Thankyou.
I should add that I'm using Vista x64.
soundood your treatment and abuse to/of macci is deplorable.
He has spent thousands of hours here helping people with AMD related problems and isn't an XIP for nothing.
Pls show some respect.
Not a bad idea.
---
I can appreciate you not caring who's fault it is that AOD doesn't work, but it would be a fallacy to direct your anger at AOD if it isn't to blame. That is essentially identical to blaming Windows for not working after putting some bullets through your computer or blaming your car for not working when you're stuck in a traffic jam. It's a misdirection of focus.
Particle's First Rule of Online Technical Discussion:
As a thread about any computer related subject has its length approach infinity, the likelihood and inevitability of a poorly constructed AMD vs. Intel fight also exponentially increases.
Rule 1A:
Likewise, the frequency of a car pseudoanalogy to explain a technical concept increases with thread length. This will make many people chuckle, as computer people are rarely knowledgeable about vehicular mechanics.
Rule 2:
When confronted with a post that is contrary to what a poster likes, believes, or most often wants to be correct, the poster will pick out only minor details that are largely irrelevant in an attempt to shut out the conflicting idea. The core of the post will be left alone since it isn't easy to contradict what the person is actually saying.
Rule 2A:
When a poster cannot properly refute a post they do not like (as described above), the poster will most likely invent fictitious counter-points and/or begin to attack the other's credibility in feeble ways that are dramatic but irrelevant. Do not underestimate this tactic, as in the online world this will sway many observers. Do not forget: Correctness is decided only by what is said last, the most loudly, or with greatest repetition.
Rule 3:
When it comes to computer news, 70% of Internet rumors are outright fabricated, 20% are inaccurate enough to simply be discarded, and about 10% are based in reality. Grains of salt--become familiar with them.
Remember: When debating online, everyone else is ALWAYS wrong if they do not agree with you!
Random Tip o' the Whatever
You just can't win. If your product offers feature A instead of B, people will moan how A is stupid and it didn't offer B. If your product offers B instead of A, they'll likewise complain and rant about how anyone's retarded cousin could figure out A is what the market wants.
I don't think it is AOD... in whole... I have never had issues, no glitches, and I understand how it is working... I only have issues related to hardware..I don't have any of the boards that have been seeing issues.. but I have three that work flawless do far..
Ohh.. Soundood....wher is the OC database..I have a 3.4ghz to post and I used AOD to do it...
~1~
AMD Ryzen 9 3900X
GigaByte X570 AORUS LITE
Trident-Z 3200 CL14 16GB
AMD Radeon VII
~2~
AMD Ryzen ThreadRipper 2950x
Asus Prime X399-A
GSkill Flare-X 3200mhz, CAS14, 64GB
AMD RX 5700 XT
Ok, here is the classic AOD skin (Green/Black)
LINK
1) unzip the package to AOD installation folder, it will create a subfolder called "resource" that contains the skin files.
2) edit "preference.xml" and set the "skin scheme" to “skin-green”
3) start AOD with classic skin
macci: Pretty sure it got lost in all the controversy, but on the K9A2 is the "NB Core" slider for the 790FX chip or the NB IMC?
It hasn't helped alot as far as my IMC overclock goes, so I'm assuming it affects the 790fx chip...
AMD FX-8350 (1237 PGN) | Asus Crosshair V Formula (bios 1703) | G.Skill 2133 CL9 @ 2230 9-11-10 | Sapphire HD 6870 | Samsung 830 128Gb SSD / 2 WD 1Tb Black SATA3 storage | Corsair TX750 PSU
Watercooled ST 120.3 & TC 120.1 / MCP35X XSPC Top / Apogee HD Block | WIN7 64 Bit HP | Corsair 800D Obsidian Case
First Computer: Commodore Vic 20 (circa 1981).
Bookmarks