Yet more Intel chanting going on ....eh?
Printable View
Yet more Intel chanting going on ....eh?
Well check this out before i posted in the thread i down loaded the newest aod to check how it was coming along so i play around with it a litte bit to see what up .Now i'am been trying to get 3.1 to work as a 24/7 clock been using 3.0 . So i drop my FBS speed and trying more mulit to see if i can get it to work more stable at a highter clock and the short time i use AOD to day it had turn off my ACC in my bios with out ask me to do so .It stuff like that can piss someone off .The next thing you know you see a thread ACC dosen't work the guy talking trash all beacuse AOD turn the ACC off in the bios with out him knowing his overclock came out the same as before so the dude piss i can see this happening .It just happen to me but i cought it when decloclk my fbs and upping my mulit.
Exactly my experience with AOD same board, same versions. Haven't tried the newest yet.Quote:
Originally Posted by AMDDeathstar
It works well on the MSI K2Plat though, just one or two issues but nothing bad.
Excellent feedback folks :up:
The good news is that most of the bugs listed here are already root caused and fixed in version 2.1.4 that should be out soon (ETA=next week).
Lightman,
Thanks for the feedback. the CPU multiplier bug that appears in some cases (loading a profile, applying default settings) has been fixed in 2.1.4
merkk1,
max HT link multiplier detection bug (limited to x5) as well as ACC not being visible in AHCI / RAID mode are both fixed in 2.1.4. you are running with SB750 board but AOD defaults to red skin and ACC item is disabled (even if SBIOS enabled it), right (not the black skin)?
it sounds like you have adjusted the CPU Vcore OFFSET value in the SBIOS?Quote:
I can change the volts in the clock/voltage screen from 1.3v as shown to 1.3125v it shows wrong in the cpu status screen, it says it 1.3125v but if i go to the board status screen it shows its gone from 1.35v to 1.37v and thats what it really is.
There are a couple of things to keep in mind here:
1) AOD slider adjusts the CPU VID value - this may or may not be the Actual CPU Vcore value (thats why its "CPU VID" not "CPU Vcore"). if you leave your SBIOS at default then CPU VID = CPU Vcore,
2) if you manipulate the CPU Vcore level by hardware rework (VR) or via SBIOS Vcore control that uses the OFFSET method (adds voltage on top of the VID value) the CPU VID value is not the same as CPU Vcore level. In this case the voltage does go up if you adjust the VID but you should be aware of the OFFSET you have adjusted in SBIOS (or via VR) to ensure you keep the CPU Vcore at the desired level. checking thru the HW monitor is a very good idea (like you had done).
3) ideally the SBIOS should tell AOD about the amount of OFFSET (this happens on the MSI 790FX board for instance where you have two sliders for Vcore: CPU VID and CPU Vcore - CPU Vcore slider adjusts the amount of OFFSET on top of VID value) - I'll check if we can get a new BIOS spin to get rid of this concern on the FXN board.
Cooper,
Yes, its possible to apply custom skins. I'll post the old default skin ("classic AMD Green/Black") and some instructions later today (its very simple).
as my dear old nana used to say, if you havent got anything to say, then dont say it,Quote:
Originally Posted by keithlm
and thank you for putting me on your ignore list, :up:
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
Not a bad idea.Quote:
Originally Posted by keithlm
---
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.
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..Quote:
Originally Posted by Particle
Ohh.. Soundood....wher is the OC database..I have a 3.4ghz to post and I used AOD to do it...
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...
Daveburt714,
"NB Core" should be the 790FX Chipset core voltage. CPU NB VID slider is for the IMC.
the last couple of versions have a VID limit set to 1.45V, the more xtreme users who want to run above 1.45V need to change the value of "MaximumVcoreEnable" from 0 to 1 in Preference.xml (AOD installation folder)Quote:
Originally Posted by AMDDeathstar
Much betterQuote:
Originally Posted by macci
Thanks
24 yays = 72.73%
9 nays = 27.27%
so just over a quarter of technicaly minded peeps cant get this to work with latest version.
this in a real world percentage would be a little higher i believe, but that is irelevent,
for over a quarter it doesnt work, not exactly promising, but Macci can decide for himself if that is acceptable,
i dont, and anyone in there correct mind, would asses this as a failure, and look to releaseing an 'updated' software to remedy 'so called bugs'
but as we have seen, AOD has had umpteen revisions, has in my opinion, has never really got this together, and i have little hope of this ever working.
i therefore would say i am correct in all my comments, regardless of how many successes, again it fails for a quarter of people using it.
end of story for now, lets see if there is any other votes in the poll.
PS: if you wonder why i make it 24 yays, then one guy polled wrongly, and posted to correct the situation, just before the hounds come out to 'question' my opinion.
lol
Hi everyone,
I'm afraid to say it doesn't work.
It locks the system as soon as I select a value of 2 or higher in performance window in the "novice mode" and clicking "apply".
It fails to detect the GPU core value too, temp it's detected.
It only support clicking the red button and increasing the performance to "1".
I'm using AOD 2.1.3 and Catalyst 8.8.
Motherboard: MSI K9A2 Cf f v2
CPU: AMD 9550
Video: Visiontek 4850
I have tried MSI dual core center and it works nice, but i have disabled it when trying to use AOD.
AOD never worked before except once. Then when I updated it never worked again.
Anyone knows what to do.. this it's a bit sad for AMD.
greetings!
Hello folks!
My first post, and the first thing I want to say is a BIG thanks to Macci!!
So, my sig is accurate, I'm using Vista HP x86 and a single 3870x2. 2.1.3 version of AOD. BIOS is F6, Rivatuner, ASUS GamerOSD and ASUS Smartdoctor running. CnC is disabled but does work when enabled but causes a severe performance drop.
My ocing is pretty lame so I'll avoid that and bring up a couple other issues.
BTW, thanks for explaining that cpu vcore vs. cpu vid and the offset (which I've never seen in my BIOS, but never looked for either.)
1) on the gpu monitor page it shows 4 active cores, the right side is a duplicate of the left and temps/gpu usage reflect that.
2) after some exasperation with 2.1.2, I put in 2.1.3 loaded it up, dragged it to the extended desktop monitor, fired up Crysis and it started thrashing my DVD drive and refused to load.
Tried it again without AOD and no problem. Tried it again with AOD on main desktop and Crysis failed before the first logo screen and then gave me a BSOD referring to memory management. In fairness, I've also seen this BSOD on rare occasions when the computer is left to enter S3 sleep without AOD even installed.
3) please incorporate a fan control, speed vs temp.
And thanks again Macci. :clap:
Looking at the errors log of AOD it seems to find like 30 of them but they don't give me any clue of what could be going on..
Wrote this on the AMD forums but someone there suggested I put it in here.
I have problems with AMD Overdrive. From version 2.1.2 and now with the bugfixed 2.1.3 I can't get it to automatically apply settings on bootup even if I set it to do so. It worked perfectly with 2.1.0 and I would continue to use that if it hadn't had the crash after aug 30 bug. As it is now I have to apply settings manually on each bootup.
The second problem is with the GUI itself. This also started with 2.1.2 and is still there with 2.1.3.
I can't see what checkboxes are selected or not. I'm providing a screenshot to show how it looks.
http://lakrits.mine.nu/AOD-bugged.gif
My system is as follows:
Gigabyte GA-MA790FX-DS5 : Athlon 64 X2 5200+ : 2x1Gb Apacer DDR2-800 : Sapphire HD3870X2 : WD Caviar 250Gb SATA-II : Win XP SP3 (2 installations, one day-to-day and one clean with only drivers and one game installed. Same problems on both.)
I also just noticed, I haven't really checked before since I always use CCC to tune my gfx card, but AOD only shows it as one GPU. Don't know if this is correct or not. Using Catalyst 8.6 since both 8.7 and 8.8 are causing stability problems on my system.
I answered no only because the ACC blank, but other than that everything works fine.
I just never really cared much for any software overclocking tool no matter how good it is.
Guess i am just used to doing it in the bios.
I have also noticed as other users has reported that sometimes when I click the apply button the speakers start making a strange noise, like interference.
As far as it goes seems that for 1/3 of the users this tool goes no where. (soundood it's right)
It's a lack of respect to the consumers to release something such in a beta state to the market at least they should warn about it.
Also why MSI can release an stable overclocking product and AMD that are the designers and manufactures can't?
I really like AMD and ATI and wish they could solve this issues soon.
Something cool that I have seen in "MSI DualCore Center" tool is that it downclocks the CPU if you are not using it and increases it to the selected overclock when it's under heavy load.. I guess this is something AMD overdrive could consider.
Also please include a fan control on ATI catalyst! :(
greetings,
Polaco
Actually i have had that happen to me with The overclock
utility Fox-one and AOD where the computer locks up and
the speakers have a high pitch squeal. Almost :banana::banana::banana::banana: myself
with that sound coming out of my old Klipsch 4.1 400 watt speakers.
I have installed the new Catalyst 8.9 and then reinstalled AOD2.1.3 the problems have not changed.
Also have installed AMD Fusion Gaming Utility it seems to run ok with the default profile. That's all I could test.
Waiting for AOD 2.1.4 anxiously...
You've had nothing to say since page 1, yet you continue to say it.Quote:
Originally Posted by soundood
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.
2.1.4 is official and will be released tomorrow, which should mean it will be on the website also. :DQuote:
Originally Posted by Polaco
This bug found its way to the two releases you mention, 2.1.4 takes care of this issue as well.Quote:
Originally Posted by Liqourice
This might depend on the Windows eye-candy settings that are used. I remember seeing the same thing.Quote:
The second problem is with the GUI itself. This also started with 2.1.2 and is still there with 2.1.3. I can't see what checkboxes are selected or not. I'm providing a screenshot to show how it looks.
the "hotfix" could be to return to the classic skin - please check the instructions from this post
Need to investigate this further, reading thru some of the posts it seems that this doesnt appear in Vista. So could be OS related bug. Thanks for reporting this one.Quote:
I also just noticed, I haven't really checked before since I always use CCC to tune my gfx card, but AOD only shows it as one GPU.
AOD 2.1.4 is available - LINK