experimental x800 version

[W1zzard]

please try if this version is more accurate for detecting x800 max oc's..

make a backup of your existing atitool.exe then replace it with the one from atitool.zip and extract terrain.zip to res\terrain.x under the atitool directory

http://www.techpowerup.com/wizzard/atitool.zip

http://www.techpowerup.com/wizzard/terrain.zip

[acrowley23]

tested it on my x800proVivo@XT with 535_567 stable...
find max Mem is working fine...exactly 567Mhz..the same get "manually"
but find max Core is going to high ..i know my last stable limit of 535-540Mhz..its not running to fast in Hell like the Versions before, but its going to high and i get a freeze.

[foreignkid]

Will test overclock later- runs 30-31 fps avg on 9600xt

[acrowley23]

Will test overclock later- runs 30-31 fps avg on 9600xt
ähm...9600XT..this is a x800 improved Version isnt'it ;) only for the findMax Error on x800 Cards...

[math]

i'm doin the test right now.

my mem goes up stable to 582mhz. Which is a right speed cuz i have a silencer 4 with mem-cooling on it.

Now stresstesting my corespeed. Which is 557mhz. I think this one is a bit high, but i'll stresstest it voor 15 mins.. so let's see what comes out of it.. Afterwards i'm gonna test it with aquamark2003.

took a "save" clock @ 550/580 and ran stable in aquamark. Got a fps of 65 which is nice i believe (xp3500+ @ 2380mhz)

so looks like its working for me @ least.

[Goldlocke]

thx W1zzard for that version.

In fact I had great consistency probs with versions .21 and .22 on my X800XT.
Maxcorespeed-detection usually gave me Restarts, because clock climbed into extremely high regions.

Version .20 was OK.

I will try .23beta2 against this experimental atitool.exe soon...

[foreignkid]

ähm...9600XT..this is a x800 improved Version isnt'it ;) only for the findMax Error on x800 Cards...
Wizard told me last night that he was having trouble getting over 40fps on x800 last night... and I wanted to prove that this could be done... I was at 30-31 fps. I'm kinda curious what kind of fps yall are getting... I know it doesnt matter, but I'm still kind of interested that i could get this high. If I'm getting fps comparable to yalls ona 4 pipeline card, something must be wrong with the algorithm, it can't be stressing your card that much. I guess its a form of bugfinding.

[Goldlocke]

I used .23beta2 -> max core detection climbed to high 610MHz on my X800XT. There the 3D window got all yellow with instant System freeze. :(

Exchanged atitool.exe and added terrain.x -> same thing :(

edit: oh! now my beloved version .20 does not detect max corespeed correctly. It also climbs to high regions with resulting Syslock.

[foreignkid]

9600XT - Core went to 586 and levelled out....I let it run for 15 mins or so. Tried memory next, it ran for around 30 seconds and then monitors turned off. Had to reboot.

EDIT:
Attempt 2:
Ran find max mem first, it ran to around 350, and then core ran to around 550. Is the terrain supposed to look like orange candy?
http://www.nmt.edu/~lbaker/atitoolexp.JPG

[W1zzard]

yep it is supposed to look like this.. playing with pixel shaders for load ..

i got a new idea for improving the scanning while at my gf .. will be home later today then implement it .. hope it works

[rikit_zap]

New to the board. I too had the problem described with .22 and my x800 pro. I then used the update process in this thread and it works great on my system.

If there is any more testing I can do or any more information you need let me know.
By the way did your 16 pipe soft mod with default speed and it was successfull. Raised my 3dMark03 700 points. I created a cd iso of the 3 x800 bios', dr dos and flashing utility. Let me know if it something you would be interested in.

Great Program, Great Site.

[Goldlocke]

Oh! Now that I see the pic of the new terrain. My update did not show me this new background. hmmm....maybe my installation went wrong...
I will try .22 and this exp. version tonight...

[W1zzard]

new test version .. compare max load and max scanning temps of the version with the terrain and this version:
http://www.techpowerup.com/wizzard/ATITool_0.0.23x800.exe

also check if artifact detection is better or worse than with the terrain

[acrowley23]

Oh! Now that I see the pic of the new terrain. My update did not show me this new background. hmmm....maybe my installation went wrong...
I will try .22 and this exp. version tonight...

what for a backround did you mean?


@wizzard..the new exp version doesn't work...when i try to start 3d view it gives me a crash.. Tray Icon is gone and AtiTool is terminating...
What about Temps? should be the Temps of the other 1 exp x800 vers wrong? Produce it wrong Temps?...
For me the Temps with 1 exp Version are the same as ever ??

[Jeronimo]

So the new version is without terrain or do you need the terrain with it. It is a bit confusing to me.

[Jeronimo]

It gets even better: This version crashes when trying to open the 3D window. With or without terrain.

[rikit_zap]

I installed with the upgrade option and it ran fine, yet with the old terrain. I then saved a copy of of the program file and .dlls, uninstalled then installed with the new installer. It exited with an access violation on viewing 3d. I then replaced the program file with the old x800 terrain version and it now runs with a diffrent terrain, the new one I suppose. I did no testing as I am sure this is not how you wanted it to run. I do have VC++ and can open into the debugger on the error and view the asm. If this will help you I can send you a copy of the code fragment that it is stopping on.

[Jeronimo]

Does not work for me, keeps crashing when opening 3D view

[acrowley23]

I installed with the upgrade option and it ran fine, yet with the old terrain. I then saved a copy of of the program file and .dlls, uninstalled then installed with the new installer. It exited with an access violation on viewing 3d. I then replaced the program file with the old x800 terrain version and it now runs with a diffrent terrain, the new one I suppose. I did no testing as I am sure this is not how you wanted it to run. I do have VC++ and can open into the debugger on the error and view the asm. If this will help you I can send you a copy of the code fragment that it is stopping on.

but theres no new terrain file??

[Jeronimo]

I also do not see a new terrain file. The original experimental build does not make my core heat up (stays around 50 were 69 is normal) when using the new terrain. So is it more of a memory stress build?

[W1zzard]

bleh ... the last test build had a really stupid bug ...
fixed version: http://www.techpowerup.com/wizzard/ATITool_0.0.23_x800.exe

[Freddy23]

bleh ... the last test build had a really stupid bug ...
fixed version: http://www.techpowerup.com/wizzard/ATITool_0.0.23_x800.exe

Results seem to be ok. I get 533/567 : this is also what I tested in games and benches. But there is a little bug: if ATItool finds an error in the first seconds after starting 'Find max core' (core already oc'ed >540mhz) it runs down to <500mhz because it always finds errors. Temperature looks good, I get 60-70 degrees, that's what I get in games too. W1zzard, i suggest you should always reset the clocks to default speeds before 'Find max Core/Mem' button is used.

Update: I think the error detection for the core doesn't work properly at all: I get even errors when starting 'Find max core' with 470mhz core speed.

[W1zzard]

freddy: you get those errors instantly or after some time?

[Freddy23]

Hi W1zzard, I get those errors after 2 seconds (nearly instantly), but not every time I start the 'find max core'...
Ok I found the problem, the memory caused errors in the 'find max core' procedure.I think it must be something with the Mem timings (seems to be a similar problem like the 'weird screen garbling' issue). I noticed ATITool uses other settings for my mem then my graphic card bios (Sapphire.X800XT.256.Samsung16.bin). I will need some time to see what is causing the errors (RaBIT shows timings of the bios and I will try to change some of them in ATItool to get this fixed, perhaps it'll help others with same problems)

[acrowley23]

Hi W1zzard, I get those errors after 2 seconds (nearly instantly), but not every time I start the 'find max core'...
Ok I found the problem, the memory caused errors in the 'find max core' procedure.I think it must be something with the Mem timings (seems to be a similar problem like the 'weird screen garbling' issue). I noticed ATITool uses other settings for my mem then my graphic card bios (Sapphire.X800XT.256.Samsung16.bin). I will need some time to see what is causing the errors (RaBIT shows timings of the bios and I will try to change some of them in ATItool to get this fixed, perhaps it'll help others with same problems)


whe thats true, that AtiTool use other Timings as the Bios does, that could be the Reason for the Weird Screen garbling issue...i will compare my working 500_500 XT Bios with Rabit 1.5 and the AtiTool latest version MemTimings... But i tell it again..with the Connect3d xT500_500 Bios the Weird Screen gambling Bug is fully gone for now over 8 Days!! :)
@Freddy..perhaps you test it??!!

But with ArtifactScan i've no Probs. not with Ram and not with Core...works fine!
But what about Temps??My Temps are already fine..with each version the same i think so!!
Idle 33C /load 63C

[Freddy23]

But i tell it again..with the Connect3d xT500_500 Bios the Weird Screen gambling Bug is fully gone for now over 8 Days!! :)
@Freddy..perhaps you test it??!!


I'll give it a try, thanks acrowley.

[rikit_zap]

Found Max Core at 525 and Max Mem at 531 @ 65C

I also ran max core by starting at different oc's
(500, 510, 515) and it found close to the same max core each time.

[W1zzard]

atitool doesnt use other timings .. its just that rabit interprets the register contents differently or atitool ..

rikit: how close is that to your real stable artifact free oc?

[acrowley23]

yehyo...compared te memTIMINGS!!
Wizzard..there are totally different Settings from
AtiTool used as my XT500_500Bios shows in rabit1.5!!
example :
Mem trcdrd : AtiTool=7clk / Rabit 1.5 shows from Bios = 8clk
Mem trcdwr: " =6clk / " " = 4clk
mem trp : " =5clk / =8clk


and so on....
Can compare everythingwhen you wanted, but ist 90% different!
What now? is it normal ? Bug? OK.all is working fine no question..
The weird Screen gambling Bug is gone with xt500_500 Bios..but the MemTimings are different..i think the Timings shown in Rabit1.5 are 100% correct!..

Wizzard, what do you think about ?

[acrowley23]

atitool doesnt use other timings .. its just that rabit interprets the register contents differently or atitool ..

rikit: how close is that to your real stable artifact free oc?


OK..but whats for real? Rabit 1.5 or AtiToolTimings?
Is it a Problem or not ?....seems to be not ,cause there are no probs..

When User are changing the Timings with Rabit 1.5 or AtiTool,they are wrong ?? That's risky or what, cause the Timing are shown with rabit or AtiTool maybe are wrong ??? Confused :eek: That would be hard.....
i dont think the rabit1.5 shown timinmgs are wrong....
and i think too its very important to clear this........

[rikit_zap]

That's 10 minutes artifact free.

3dMark03
Loop 3 times game tests 3dMark03.
Temp Maxed at 65C for one reading.

It's the same if I run it up manually.

[W1zzard]

you are right ..at least 4 atitool mem timings settings are wrong .. i'll work on this asap .. probably revamp the whole memory timings editor

[D3aDl0cK]

hi,
i want to test a new version of ati tool, beacause of the improved findmax.. function on x800s.
But i´m a little bit confused which one to take,
can anyone give me advice? (c or s?)

The 23beta on site3 or the update of the 22 (file and terrain) ?
I have the 22 running atm.
Thx for help.

[W1zzard]

the latest experimental x800 version is this:
http://www.techpowerup.com/wizzard/ATITool_0.0.23_x800.exe

the latest 0.0.23 beta is beta 2

the experimental one is probably more instable and does not work on non-ps 2.0 cards but should work better on x800

[Freddy23]

you are right ..at least 4 atitool mem timings settings are wrong .. i'll work on this asap .. probably revamp the whole memory timings editor

The new beta shows great improvements for X800 users, better GPU load and very good max. overclocking prediction...only the problem with the mem timings is left (just for some X800 users). I think when this is fixed the 'weird screen garbling effect' will be totally gone too. This will be the ultimate tool for X800 users soon :D
GR8 work W1zzard!

[D3aDl0cK]

danke W1zzard!
macht nix, dass die instabiel iss, iss ja auch ne beta.
ich denke, dass dir dann das womögliche bug-feedback auch was hilft.
(Da du uns ja kostenlos das ati-tool zur verfügung stellst, bin ich gern bereit auch als tester zu fungieren)

[acrowley23]

you are right ..at least 4 atitool mem timings settings are wrong .. i'll work on this asap .. probably revamp the whole memory timings editor


dont't understand 100% actually...OK Rabit 1.5 Timings are correct!
And AtiTool's Timings are wrong ... but what kind of wrong ??

Is it only shown wrong ? only wrong interpretation? Or does AtiTool really give the incorrect Timings on the Card....can't believe that, because there must be more "big" crashes in this case...mhhh
...... little bit confusing for me...... :confused:
And can we finally say,that maybe the Weird Screen gambling Bug is a product of wrong Timings they're given on the x800 from AtiTool??

GrEEtz

[W1zzard]

its just the display of values .. the list entries have the correct values but the wrong labels

[Jeronimo]

No more terrain in latest experimental buid?

[W1zzard]

not needed i think .. compare temps .. i'd even go as far and say no more heatup phases needed ...

[acrowley23]

its just the display of values .. the list entries have the correct values but the wrong labels

allright.....but for me ,when i'm going to tweak the mem Timings, i better use directly rabit 1,5...
Could you fix the incorrect displayof the values next time...
And th weird Screen gambling Bug isn't a Error cause of diretly wrong Timings from AtiTool..because the Timings are not wrong, their are only displayed incorrect...OK.
But somewhere the Timings in some Way must be the trigger for this...how ever actually for me its gone with xt500_500 Bios (Day12 unless freeze) :)

[W1zzard]

atitool never ever changes memory timings except when you click apply in the mem timing editor

wrong values will be fixed in next version

[acrowley23]

atitool never ever changes memory timings except when you click apply in the mem timing editor

wrong values will be fixed in next version


sure....allright next Version...nice Work! :)
I usually never change any Mem Timings..for me its to risky ,cause i don't know
exactly how the different values are working..

Nice idea to to implement Profiles... :) may you make them saveable as like the fanControl..

[420KILLA]

all i have to say is wizzard you are the man.....great program you have created here...im downloading experimental version now....and i will post results tommorow when i wake up.

[D3aDl0cK]

As many of you offer the "xt500_500" bios to be the best OC-bios,
what do the others of you think.
@acrowley23 what bios are you tinkering with?

Or the smsung 525/575? or doesn´t it matter which one to take, as results don´t change?

(Sry if it´s OT, please tell me when to stop ;) )

[acrowley23]

i use the XT 500_500 Bios! For me the best of all! I get 10-20Mhz more CORE Clock!
So i'm able to lower the VCoreMod. Many User reported about very good OCing with this Bios! Its the Connect3d XT 500_500 Bios from Bios Section here...
Normally a Bios doesn't increase the Gpu clock..but its real..

For me the XT-PE 526_573 isn't working well. I get much more earlier Artifacts with the Mem... best is 500_50 XT Bios!!

[Juggy]

Hey W1zzard,
I thought I'd give your latest beta a go, and share my experiences.
I started finding the max for the memory, I had it running for 15 minutes, and I noticed it didn't go further than 553.50 (which is good). Being happy with the memory speeds, I tried finding the core's max, but after a while (I think 1 or 2 minutes), my system froze up, and my screen turned black. The speed was 504.90 before it froze (thanks to that handy message after I rebooted). I also had this, when trying to speed the core up manually, in older versions. It then also froze up and went black around the 500.

I just thought I'd let you know, maybe you could do something with it, maybe it's just my card.

EDIT:
I didn't see any artifacts btw, and the temp was 62 degrees.

[420KILLA]

so wizzard.......what way do you suggest using this program effectively? Should i run find max core.....and then keep what it found to be the max core whenver i run max mem? Or should i set the clock to its default and then run the find max mem? maybe you have already written this somewhere else in the forums and i am just a noob and cant find it. Im just trying to see how i can get the max out of my x800...and it seems like you know what you are talking about....once someone or you has replied to this...i will run atitool in the best way that you can describe...and i will post my results...i just wanted to make sure i am using your program to its full potential...Thanks alot...and once again great program.

[W1zzard]

please use 0.0.23 beta 3 - it has all the changes from this version. thanks for your input