Enable higher overclocks in CCC with reg entry

[RacerX]

Okay, so how about this version: Attachment 23933
It will also go correctly though "holes" in the registry key sequence, like for your 0000, 0002, 0003. With the 0001 missing, I mean.


That's not only a lot of work, but also needs to be maintained. And it's sorta uncool, don't you think?

Cool, will try that one.

yeah, just joking with you, believe me we all appreciate all your hard work.

[RacerX]

Ok,
running into a glitch.
for some reason it doesn't show the gpu slider upon reboot.
I left the default values, and only changed the od limits.
This particular card has the asus Bios (810 default clock)
tried it with 800 and 810 and it didn't work, the slider is gone.

Trying the previous version now, will reboot and report back.

[RacerX]

Ok, another glitch.
Actually, it's in this version and the last version.
Somehow I didn't catch it in the last version since I was mainly looking at the under clocks.

Both versions, regardless of setting it at 800 or 810 default clock the slider, cause the gpu slider to disappear in CCC.

I then ran the original program you made and it works fine.
the slider is back.

[BAGZZlash]

Ok, another glitch.
Actually, it's in this version and the last version.
Somehow I didn't catch it in the last version since I was mainly looking at the under clocks.

Both versions, regardless of setting it at 800 or 810 default clock the slider, cause the gpu slider to disappear in CCC.

I then ran the original program you made and it works fine.
the slider is back.

Could you compare the .reg-files created by v0.01 and v0.03 in order to find out what's causing this?

[RacerX]

Ok, working on it now.
I found the discrepancy between v01 and v02.
Also, I found another problem which was my fault.Sorry!

i told you default was 800, but I forgot I originally went off the Asus BIOS which is 810.
I ran v03 with all defaults, but with 800 and 810, so i can compare them all.
Once i post the line error that i found, along with the code for 800, I think you'll have the right info for this.
ALso, I think 800 is a better default, and those with an Asus BIOS or other factory OC'd card can then modify theirs up with the sliders.

Give me a few and I'll post the relevant info.

[RacerX]

Ok, here's the info:
I also attached the files so you could look at them as well.

Hopefully this makes sense.

V01 - 6th line last part:
01,00,00,00,50,c3,00,48,e8

V03 - 810 default
6th line last part:
01,00,00,50,c3,00,00,48,e8,


Notice on the original one the sequence is:
00,50,c3
on V03 it's:
50,c3,00



Now difference between a 810 default clock and 800:

V03-810 line:
Line 5, in the middle:
68,3c,

V03-800 line:
Line 5, in the middle:
80,38,


What I'll do know is fix the part on line 6 and do an 800 default to see what it does, then I'll do the same with some lower clocks to test that everything shows up.
At this point I doubt the driver will let me lower 3D clocks, below defaults but I'll test it out and let you know.
If not that's okay, once this is fixed, people can still put in there defaults so this should work now.

If all goes well, I'll be back to post in a few.

[RacerX]

2 things.
First, on all the above files, they have the OD limits changed to 1000/1500

Second, that worked.
I changed this around:
V01 it's 00,50,c3
V03 it's 50,c3,00"

and V03 worked now.

Also one good side note is that I used the one above for the 800 default, and Mine still shows the 810 default.

I need to fix the driver install on the other test system with the Sapphire BIOS (800 default) and I'll test this on that as well, so that's good.

Now I'll run V03 with lower defaults, and manually fix line 6 and see what I get.

Report back in a few.

[BAGZZlash]

V01 - 6th line last part:
01,00,00,00,50,c3,00,48,e8

V03 - 810 default
6th line last part:
01,00,00,50,c3,00,00,48,e8,

Damnit, eagle eye, I just didn't see it. Great work! That will most likely be the reason, simple bug in my coding work.

Here, try this very virgin v0.04: RacerX.zip

[RacerX]

Cool, tried it on the Asus BIOS and it seems to work, just need to test the lower clocks.



Also, just fixed the Sapphire clocks on the test system and loaded drivers.

Downloaded and just ran it for defaults, plus 1000/1500 and did a reboot.

Works with one minor glitch.

Since The original file I did actually had an 810 default clock in it, (oops, I know my bad.) the OD shows 810 instead of 800 on the Sapphire, so it automatically did a slight OC.

I ran GPUz to verify, and it shows 800/1250 defaults and 810/1250 current.

The important thing is this doesn't seem to flake out the control sliders.

I'll play with the lowers on both computers to see what it will do.

I'm kinda thinking the driver won't let it but we'll see anyway.

[RacerX]

Well I stand corrected.
Just tried 450 instead of the default 500 and it worked.
GPUz shows current clock 450 as well.

I also changed the uppers to be sure it was reading them.

Now the question is, what will changing that lower do?


I'll start a few benches to see if it locks the clock in 3D to 450 or if it will still jump to 800.
Also need to try it at 800 and try and run something that would cause it to run at 500 to see if it actually runs at 450.

Also, I'm thinking I'll play with the profile file too, and drop the new lower to 450 to see if that sticks and try to run something, maybe a video to get those lower clocks to kick in.

going to change the lower to 450 for this card to and reboot to make sure it works on both cards correctly.

[RacerX]

Ok, I guess I only stand partially corrected.
Earlier I was playing with lower clocks trying to tweak things from v3, but I couldn't get it to show anything lower than the 500.

Since the other test computer seemed to work fine, took me a few but I figured it out.

On the test system, upon restart from the driver install I ran the reg file and did another restart.

Opened CCC for the first time and the 450 lower was there in OD, BUT I hadn't unlocked it yet.

On my main system it wouldn't take, so I deleted the reg key to re-lock the OD, did a reboot and it was there with 450 instead of 500.

So, here's the reg key to re-lock the OD if need be:
HKEY_CURRENT_USER\Software\ATI\ACE\Settings\Dashbo ard\Graphics\Overdrive5

On the right hand side is the time it was unlocked. Just delete that entry.

restart, and the OD will be locked again.

Then you can just unlock it and use it as usual with the new lowers.


Just ran heaven for a bit on the test computer and it was running at 450/1250, so the 3D clocks did drop.
Put it back to 800, and will try to get something to run it at 500 and see if it runs at 450.
will edit the profile as well to see if that helps or does anything.

[RacerX]

Well, it actually did lower the 500 clock to 450.

I finally found a use for the sample videos in Win 7.

Ran the sample video and it ran at 450 instead of 500.

Put OD back to 500 did a restart, and ran the video again, and it ran at 500.
Just did it 1 more time back at 450 and it ran the video at 450.

Also, checked the profile file and it still shows default 500, so the driver is reading the OD limits.

So it does look like it's possible to run lower gpu clocks, now need to play with the memory clocks to see if that works too.

[RacerX]

Lower memory clocks seem to work too.
dropped it to 1150 and did the video test.
instead of 1250 it was showing 1150.

One odd thing, which isn't because of this, but worth noting.
I notice the clocks like to jump around bit in GPUz, and even in full windowed mode om the video, clocks will sometimes go low as 250/150, up to the 500/1250 defaults.
sometimes the clocks will do 500/650.
The odd thing was that when I dropped the memory clock lower, it also did a new lower of 450/300.
Not sure if it's a fluke or what?

Anyway, point is, this version seems to work to allow both lower and upper limits to be changed in OD.

[BAGZZlash]

Cool stuff!
So bottom line is: Everything works as a user would expect from the GUI? Maybe I can just remove the hint for the first two frames again?
I'll add an overdrive-relock-feature, cool thing I think.

[BAGZZlash]

Okay, even though we released before (I guess we were hungry for it ), maybe this v0.05 could be considered our first stable release: RacerX.zip

One thing is important: Consider a user not having a 6950, say, he has a 6850. What happens if he runs the programs? He sees: "Cool, increase overdrive upper limits! But what about this lower limit and default clock stuff? - Nah, I don't care."
So he'll just change the upper limits to the values desired and leaves the other sliders at the standard settings (500/1250 for lower limits, 800/1250 for default clocks).

What happens: Will these settings be applied? Will some sliders in the CCC disappear? Will he dramatically overclock his card (due to default clocks), which may damage his card?

[RacerX]

Cool, I'll play with this version, and work on an instructional update so people will have the exact sequence needed to run this properly.
With stock lowers they should be fine, but with lowers below that, they'll need to do the lock/relock sequence, unless it's a fresh install.

Also, I think keeping the warnings on those sliders will be good, which will be included in the instructions, so that they set the correct defaults for their card.

These cards have a lot more power management built in then initially seen.
For instance, when i talked about the earlier test and watched the video sometimes lower memory clocks dropped to 625, well with the adjusted lower setting, AB now shows options to lower memory down to 625, and gpu to 405, even though OD lower limit is set to 450 atm.
Without changing the default lowers, AB showed the 500/1250 lowers.

So I'd recommend people leaving the lowers alone, unless they know how low their card can go without losing stability.
For this 6950 it played the video at 250/150 in certain spots, but did those fluctuations to higher clocks.

right now for testing, I'll leave the lowers to 450/1150 instead of 500/1250 default on this card, to see if any stability glitches occur.
I don't think they will, since the card seems to throttle up speeds when needed anyway.

[BAGZZlash]

Also, I think keeping the warnings on those sliders will be good, which will be included in the instructions, so that they set the correct defaults for their card.

Okay, seems like a good strategy. However, I'd much rather like if it just worked as expected, though.

[RacerX]

yeah, I hear ya

I think we're close though.

I think the "default" clocks are the last part at the moment.
I think somewhere in the reg file it still holds the original default of my 810/1250, so even though someone with a 6970 sets the default slider in this program to 880/1350 and OD shows those defaults, when someone hits the default button it causes it to revert to the 810/1250 instead of the default they entered.

If we can overwrite that, when someone enters the defaults, not only will it list them in CCC, but if they hit the default button it will also stay at the original default clocks they set with this program and not the 810/1250 it seems to be doing.

Worse case, if you need me to I'll flash the second card with a 6970 BIOS to test things out if need be, maybe making the original file I showed, but pulling it from 6970 settings to see what is changed from one to the other.

If we figure that part out when they run this program and set the default clocks, it will write to that correct part as well and all should be good.

[RacerX]

Okay, we have the latest build (v10) available.
The key difference is that it also includes sliders for the 2D clock defaults, which should fix the 68xx glitches.

I'm working on some detailed instructions, for example hitting the default button if some sliders are initially missing, and any other troubleshooting glitches.
The reason for this is that the driver reads these values, and OD confirms them and checks/updates the profiles file.


Before running this, be sure to backup your profiles.xml file, usually found here:
C:\Users\"YOUR USERNAME"\AppData\Local\ATI\ACE


Also, be sure to enter the correct default values for your card!

EDIT:
As usual, BAGZZlash's talents shine through! just updated this to v11, which has a button to automatically backup/restore the profile.xml file for everyone.

[Hornet331]

Just want to let you guys know that it also works for a HD5870.

Im on Vista 64bit and as you can see the latest version of the tool works great.