View Full Version : 0.0.23 beta 9
W1zzard
10-26-2004, 10:06 AM
- Added option to use "old scanning method"
- Fixed issues in "Startup" settings
- Added Catalyst AI support for 4.9 drivers
- Added detection/overclocking/mem timings support for X800 SE AGP
- Fixed crash issue on non-ATI cards
please redownload the file if you downloaded it before 7pm gmt - the old scanning method switch was wrong as acrowley pointed out a few posts below
FizzeldFiend
10-26-2004, 10:22 AM
WOOHOO on this m8! thanks heaps!
blobster21
10-26-2004, 11:18 AM
W1zzard, could you tell me what are the differences beetween the actual and "old" method of scanning...strange enough, they seems to reach my max clocks with equal sensibility.
W1zzard
10-26-2004, 11:42 AM
blobster: new method should have higher load and be less crash-prone on x800 ..
some users (acrowley) have said they dont trust this new method becuase they lost a few mhz .. thats why this option is here
mR Yellow
10-26-2004, 11:44 AM
- Added option to use "old scanning method"
- Fixed issues in "Startup" settings
- Added Catalyst AI support for 4.9 drivers
- Added detection/overclocking/mem timings support for X800 SE AGP
- Fixed crash issue on non-ATI cards
Great, now the best app just got even better :)
Thanx for the fixes. :D
mR Yellow
10-26-2004, 11:45 AM
blobster: new method should have higher load and be less crash-prone on x800 ..
some users (acrowley) have said they dont trust this new method becuase they lost a few mhz .. thats why this option is here
But u would recommend the new one?
W1zzard
10-26-2004, 11:52 AM
But u would recommend the new one?
yep definitely .. no point in releasing something as new if its working worse :)
mR Yellow
10-26-2004, 12:08 PM
Ta ;)
acrowley23
10-26-2004, 02:17 PM
thanx wizzard...now x800 scanning is working fine again...
last about new Code....i dont have higher load Temps with new Code! I get the same max load Temp of 61C ,with old and new Code! So it has nothing to do with temps that the new code produce heavy Errors .
I think the new Code maybe produce Errors on my Mem cause i've 1,6ns Ram on the front and 2,0ns Ram on the back of my Card..maybe thats the reason for the bad Scanning with new Code and my x800 Card!
Also i'm not alone with it..Know other x800 User with same Errors on new Code.....
but i wrote enough about it in 0.23b6-8 Thread!
However..now we have the old Code back and it works fine on x800 Cards.
Wizzard...great Work...
EDIT : seems to be the otion to use old scanning isnt working right??!!
I get Artifacts with this Option! I compared it with 0.22f and it works..back to 0.23b9 and Errors again. Looks like the old code isnt working on scanning ? Option is enabled .
Lautsprecher
10-26-2004, 02:29 PM
What exactly is this "AI"-thingy?
acrowley23
10-26-2004, 02:56 PM
wizzard....when i enable "use old scanning" its NOT working! Same Errors!
BUT when i disable this Option to use old Scanning its working fine! Same clock as on 0.22 and old code!
run a few Tests...
Option "use old scanning method" must be working with new Code ...
so there must be a little mistake...
W1zzard
10-26-2004, 04:58 PM
issue confirmed .. its wrong .. i'll get a fix together and let you know here
W1zzard
10-26-2004, 05:45 PM
issue fixed - please redownload the file from the first post
acrowley23
10-26-2004, 05:50 PM
ok ThanXX
DragonKnight2k
10-26-2004, 06:33 PM
thankyou wizzard now the startup ishues are fixed and are working for me :)
andrenoites
10-26-2004, 09:24 PM
W1zzard nice release there ;)
When you predict to implement custom memory profiles? (change memory timmings at windows startup)
Tnx
ccox513
10-26-2004, 10:12 PM
Downloaded and installed 0.0.23 beta 9. When I try to find max core, max memory or just scan for artifacts, the 3D image goes totally yellow, and alll my speeds start decreasing. Also I am still getting the error message "Init of findMax: Subsequent images are different".
I am running a Radeon X700 Pro, 256MB PCI-Express vid card. Hope that helps.
Have a great day!
W1zzard
10-26-2004, 10:36 PM
Downloaded and installed 0.0.23 beta 9. When I try to find max core, max memory or just scan for artifacts, the 3D image goes totally yellow, and alll my speeds start decreasing. Also I am still getting the error message "Init of findMax: Subsequent images are different".
I am running a Radeon X700 Pro, 256MB PCI-Express vid card. Hope that helps.
Have a great day!
happens with old scanning method too?
NukeTimer
10-26-2004, 11:02 PM
Hey Wizzard,
The new Everest 1.51 Version shows me another GPU Temperature than ATITool
Which Temperature is the right?
Temps:
Everest: RAMs = 43°C | GPU = 39°C
ATITool: RAMs = 43°C | GPU = 60°C
So the GPU Temp difference is +-20°C. Which Program is wrong?
I have a 9800Pro with the R360 Core flashed to a 9800XT. The Cooler ist the ATI Silencer 3.
Sorry guys for my bad english, but I am German
15th Warlock
10-26-2004, 11:29 PM
I'm getting a difference of 11 Mhz Max core clock between the "old" scanning method and the "new" .23 beta method.
old scanner: 447 Mhz
new scanner: 436 Mhz
I'm using beta 4.11 catalyst drivers on WinXP SP2, hope this helps :)
ccox513
10-27-2004, 02:40 AM
Ok, I didn't see the option for "use old scanning method". I enabled that and now I have been able to run the "find max core/memory" without getting that error message. Currently I'm getting rock solid over clock speeds of 494.31 core/1009.28 memory on my X700 256mb PCI-Express card. That is up from 425 core/860 memory. ATITool is an awesome oc utility. And I'm not done yet oc'ing yet.
I can't wait to run the 3DMark05 test again, and see what my new score will be. At this point, its the difference of 8 pipelines that are seperating my X700 Pro from a X800 XT. The speeds I'm getting now are stock speeds for a X800 XT. And the X700 Pro only cost me $199.99.
Have a great day!
mR Yellow
10-27-2004, 06:25 AM
@Wizzard
Nice release so far. I haven't found any issues yet :D
Thanx
howie
10-27-2004, 10:22 AM
When I run ATITool I get this message:
"Direct3D Debugging Runtimes are activated. This may cause unexpected behaviour. 3D profiles and artifact scanning will most probably not work. To disable the debugging runtimes, go to the DirectX Control Panel, Direct3D and choose 'Use Retail Version of Direct3D'."
I have tried this, but it is allready checked off the way this info box says it should be.. Have been this way since 0.22, so it's no new bug.. Just don't know what to do..
By the way, great peace of work w1zzard
W1zzard
10-27-2004, 10:25 AM
howie what card/system/software ?
mR Yellow
10-27-2004, 10:38 AM
Wizzard, when is ur app going to be included with the Omegas again.
I know their was issues with the one version and Omegas.
But issues can always be sorted out ;)
W1zzard
10-27-2004, 11:26 AM
thats omegas decision .. just grab the download and install it .. not that much of an issue
howie
10-27-2004, 12:15 PM
I have a Sapphire X800 pro VIVO, now X800XT PE with default clockspeeds.. Win XP, DNA 3.1.4.10 driver...
mR Yellow
10-27-2004, 12:56 PM
thats omegas decision .. just grab the download and install it .. not that much of an issue
I agree (well thats what im doing). Ive tried ATI traytools and must say that ur app is much better and more user friendly. :)
Off the topic: I looking for a installer app(freeware if possible) to make my on install files. Which one would u recommend?
420KILLA
10-27-2004, 01:37 PM
Hey w1zzard i have a few questions and a few ideas.....so let me know when you are on again.
corny
10-28-2004, 08:54 AM
Any chance of a Geometry Instancing toggle?
W1zzard
10-28-2004, 08:59 AM
mr_yellow: nullsoft install system is what i use
corny: will look into that
kayone
10-28-2004, 10:08 AM
Can we have support for Abit KV8 Pro mobo's :p
mR Yellow
10-28-2004, 10:11 AM
mr_yellow: nullsoft install system is what i use
corny: will look into that
NSIS! I noticed and downloaded it. Nice app.
Thanx
W1zzard
10-28-2004, 02:22 PM
Can we have support for Abit KV8 Pro mobo's :p
contact me on icq/aim/msn and we will work it out
angelus
10-28-2004, 04:03 PM
x800 XT PE default at 520/560
new scanning methode:
core: 531.90 (not that much but getting a ATI silencer .. hope to reslove that problem
Old scanning methode:
core:586
but then my system crashed ... Bet to high overclocked .. BUt the weird thing was that my GPU didn't passed 66C with the old Methode ...
with the new methode .. my GPU gets 70 C in 1 second ... seriously ... 1 second
anyways .. i dont think it's normal de pc crashes after 4 minutes of OCíng .. i thought atitool is there for to scan safly?
And what about the core diffrends? to much if u ask me
kayone
10-28-2004, 07:16 PM
contact me on icq/aim/msn and we will work it out
Tried you didn't reply.. m4tteh@hotmail.com
acrowley23
10-29-2004, 08:44 PM
angelus...think the Problem isnt only heat! My Temps on AScanning (with Ati4) are the same as on 0.22 !
The new Code shows a veary (to?) early Detection on X800! Nothing New.. use the old scanning Method! This will match fine your alltime rockstable clock!
But for me only the Mem clock produce Errors .Gpu is always the same..
For me with my x800 ,the new Code isnt working 100%...no final result and a unreal low clock...
x-todd
10-29-2004, 10:06 PM
hi,
i have a 9800xt.
i was using the official 0.0.22 one, and i tried the newest beta because i heard it can get rid of the problem where GPU temp would go to 20 degrees under load, cause i have that problem.
my default speeds are 412core 365mem.
with version 22 i could run 441core 393mem no problem.
with this newest beta i get tons of yellow artifacts at my normal OC speeds.
ive tried using the new method and the old one, and both give same results.
the highest core i can get now is only 426, and i havent even tried the mem by itself, cause i know it will be crazy low as well.
is there anything i can try?
ThorAxe
10-30-2004, 12:41 AM
I prefer the new code even though it dropped my previous GPU/Mem overclock by around 10MHz. My GPU reached 558 then lowered itself to a final clock of 548.10. It took about 40 minutes to reach the final clock speeds but then remained at these levels for over 3 hours when I was finally satisfied that it was going to be stable.
I would rather that ATITool stressed my card out to the max than give me inflated overclocks as I would rather err on the side of caution.
x-todd
10-30-2004, 03:18 AM
hmm well ive been having my speeds OCed for like months now, card seems fine.
i know my card can handle it.
JohnnyFiVE
10-30-2004, 05:28 AM
hi i am new here and i used the new betas and on my 6800ultra.. i get artifacts on stock speeds :confused: :D .. i even lowered my memory speed 50mhz under stock and core 25mhz and i still get artifacts hehe.. is this happening to anyone else?
ThorAxe
10-30-2004, 08:25 AM
hmm well ive been having my speeds OCed for like months now, card seems fine.
i know my card can handle it.
Your card will problably be fine then. Mine can run 3DMark 2005 at it's highest clock speeds without a problem as well as every game that I have played. However, I did find that it would produce a noticable artifact at the same point in the Nature test of 3DMark 2003 even when ATITool 0.0.23 beta 9 had run for over 3 hours with no problems. I lowered the GPU by 8MHz and it disappeared. It just goes to show that overclocking is not an exact science.
acrowley23
10-30-2004, 11:52 AM
hmm well ive been having my speeds OCed for like months now, card seems fine.
i know my card can handle it.
sure...on my x800 the new code is giving me 100% unreal Mem clock ! I run my Mem clock of 568mhz for over 3 Month rockstable! All other Stress Tests, Apps.. match exactly 568Mhz...old Code too...only new Code produce heavy Artifacts 20Mhz lower! And i cant get a final result on new Scanning...
angelus
10-30-2004, 08:47 PM
angelus...think the Problem isnt only heat! My Temps on AScanning (with Ati4) are the same as on 0.22 !
The new Code shows a veary (to?) early Detection on X800! Nothing New.. use the old scanning Method! This will match fine your alltime rockstable clock!
But for me only the Mem clock produce Errors .Gpu is always the same..
For me with my x800 ,the new Code isnt working 100%...no final result and a unreal low clock...
i told ya .. in my last post, That my x800 XT Core gets up to 586, but then crashes .. and a windows reboot will be the results :(
So....
Old methode crashes evrey serious OCing my Core...
Newmethi gives me omg Low OC results .. which is weird since i look at my Temps.. it's to low for artifacts
acrowley23
10-31-2004, 08:18 AM
...
So....
Old methode crashes evrey serious OCing my Core...
Newmethi gives me omg Low OC results .. which is weird since i look at my Temps.. it's to low for artifacts
i know....
angelus
10-31-2004, 11:39 AM
so.. atitool doesn't work correctly on both ways of scanning if u ask me...
noway i am able to clock my core up with atitool at all ...
acrowley23
10-31-2004, 06:02 PM
no...for me old scanning is giving me 100% right GPU and MEM cock!
Only find max isnt 100%
...but Sorry....the AtiTrayTool ver 101.387 Scanner is working more near by Reality for my x800 and is more stable...
But AtiTools old Scanner is working well....hope Wizzard will not remove this Option
W1zzard
10-31-2004, 06:11 PM
acrowley: please stop telling everybody in every post about your story .. we heard you the first time .. i added the old scanning option JUST FOR YOU so i'm not going to remove it.
roibm
10-31-2004, 06:38 PM
It's funny to see all those guys crying about their broken overclock.
The very fact that you can't accept the truth makes it even funnier ;)
In the other hand I am happy with a lower overclock(talking about a perf. diff of 1% or lower, completely useless). I very much more prefer getting a rock stable system instead of 1% more perf., which you CAN'T feel it, btw.
Just for the record, I have an x800-pro vivo which runs extremely stable @ 528/558 instead of the 540/565. I decided not to go for a volt mod, btw. With the volt mod I would eventually get some 5-6% more perf. which nonetheless is not going to make me any happier :eek:
angelus
10-31-2004, 06:44 PM
it's not funny...
Wizzard.. how u explain my problem ??
W1zzard
10-31-2004, 06:56 PM
angelus: if i understand your problem correctly your card crashes at some time during scanning, no matter what .. the problem is that the x800 core doesnt create a lot of artifacts like R3XX .. it just crashes .. some chips earlier, some chips later, you might try playing with the "increase frequency after" option in settings -> scanning ..
Cynips
10-31-2004, 07:32 PM
the problem is that the x800 core doesnt create a lot of artifacts like R3XX .. it just crashes
Ahh, so that's it. I never heard this explanation before. Maybe I just missed it somewhere obvious.
Anyway, this is for the core OC only I take it? Usually I abort manually with the very first visually detectable artifact, and that works fine with default settings for my x800 Pro. For mem OC the built in artifact detection seems to work fine.
W1zzard
10-31-2004, 08:19 PM
yep its the core .. i'm sure more can be done to optimize it and i'm working on it - it's just a lot lot lot more crash happy than the r3xx cores
Stephen M. Smith
11-01-2004, 03:10 AM
I'll add my 2 cents on the new vs old scanning method. For my 9800XT, the old scanning method was a bit too optimistic, especially on the memory side. I would get some noticeable artifacts in games and systematically lowered my mem speed bit by bit until I concluded that my mem was basically not overclockable at all. Well, this is exactly what the new scanning method tell me too, so it is clearly far more accurate than the old method (for my card at least). In fact, it's dead on.
Also, while playing w/the new scanning method, I found the source of this odd display corruption that occurs when I resume from standby using Catalyst 4.8+ drivers -- it's the divider. After further testing, I can report that my LCD display will be totally corrupted when resuming from standby if my 9800XT's divider is anything less than 4.5. I've seen other report the same display corruption here and in Rage3D and I bet this is the reason...
Steve
mR Yellow
11-01-2004, 05:29 AM
The new beta works flawlessly on my system ;)
I think the new scanning method is much better than the old. U get a more stable overclock.
ThorAxe
11-01-2004, 06:01 AM
The new beta works flawlessly on my system ;)
I think the new scanning method is much better than the old. U get a more stable overclock.
I agree, although my ATITool GPU overclock was a little high for the 3DMark 2003 Mother Nature test. I had to lower it slightly for the artifacts to disappear.
acrowley23
11-01-2004, 09:15 AM
acrowley: please stop telling everybody in every post about your story .. we heard you the first time .. i added the old scanning option JUST FOR YOU so i'm not going to remove it.
Ok...you're right...Sorry! Dont want to drive you crazy....i only wanted to answer on Posts were x800 User get the same and wondering why...maybe to often....
Sure...sometimes a short answer will be better.
mR Yellow
11-01-2004, 09:33 AM
I agree, although my ATITool GPU overclock was a little high for the 3DMark 2003 Mother Nature test. I had to lower it slightly for the artifacts to disappear.
I normally as a rule find max GPU overclock and lower it by 5hz :D
Just to be safe
Qwerty
11-02-2004, 12:32 AM
on my normal non clocked, non-ati tools dxdiag runs fine, but oced and with tools running its goes insane and spins the box like yoda on cocaine. is this normal.
Qwerty
flunders
11-03-2004, 07:20 AM
I'm glad the old scanning method was included as with it I can get 600/336 (672) on my Crucial 9600XT but get small artifacts with the new scanning method on the same clock.
acrowley23
11-05-2004, 08:22 AM
the Hardware Monitor now is working well! Good Way, to only display the readable Values on non Supported Boards..
my fsc d1607 Board isnt supported by any Tools...dont know the working Chip...
opium
11-05-2004, 09:04 AM
W1zzard can you add shutdown temp or alarm?
flunders
11-05-2004, 09:22 AM
Including a "High / Low" mode like in MBM5 would be nice. I always like to see what my temps rise too on my graphics card.
Erroneus
11-05-2004, 12:43 PM
Including a "High / Low" mode like in MBM5 would be nice. I always like to see what my temps rise too on my graphics card.
MBM has a built in HIGH/LOW function in the option box and you can also make it read the values to a log file.
Diffe
11-05-2004, 02:01 PM
Is there coming refreshrate force included in ATITool?
Johnny_5
11-05-2004, 08:22 PM
Wow W1zzard. This application is awesome! I have a Mobility Radeon 9700 and ATI tool v.22 didn't seem to work. Beta 9 is working perfectly now though. Thank you!
One question for everyone: When I look at the device properties in ATI tool, it reports the Chip Type of M10. I thought that the 9700 was supposed to be a M11. What is up with that? The other settings seem to match up to other 9700s I have read about.
128MB Mem
128bit bus width
390-Core
200-Mem
It overclocks quite nicely to 450Core and 230Mem. I will try pushing it further.
Thanks again.
zer0kewl
11-06-2004, 10:44 AM
hey is there anyway to get aam to work for my raid0 card
seagate 120 gb
and western digital 120 gb ?
roibm
11-08-2004, 12:17 AM
I've been running this release since 31.10 and everything works just fine :)
(x800, 3200+ 90nm, neo2, xp)
flunders
11-08-2004, 11:27 AM
I'm glad the old scanning method was included as with it I can get 600/336 (672) on my Crucial 9600XT but get small artifacts with the new scanning method on the same clock.
Before I said I was glad of the old scanning method being including. Now I take that back. It was true that I could get 600/336 and receives no errors when scanning for artifacts... but it crashed out on some games... like morrowind. Now with the new method of scanning I get 585/337.5 (675) and every game runs stable, even morrowind... and I receive no errors in the artifact scanner. So glad I could get my real stable clock!
So I say if you get errors with the new scanning method then you card isn't stable. You need to lower it. I mean it's just like overclocking your cpu... it may run prime95 all night or Doom 3 for hours... but run 2x Prime95 with a continuous loop of 3Dmark05 for 24 hours and then see if it's stable...
angelus
11-08-2004, 05:15 PM
I get artifacts at stock speed on my x800 XT PE stock: 520/560, but in all the games i run or test, like 3Dmark05 and 3dmark03 mother nature for serveral hours .. i have seen non.
it kinda pissed me off that atitool underclocked my card, So i wanted to be sure and took a whole weekend off for just my VGA.
i have teste doom3.. ut2k4 with AA 6x and AF 16x... and Far Cry..... And offcourse the benchmarks .. but i allready said that.
The Old methode clocks my card at 596,73 ... but then it simply crashes..
Temps are:
idle: 33
Stressed: 50-56 (also on atitool, new and old methode)
Yup, Your turn to explain this ;)
blobster21
11-08-2004, 06:30 PM
the card crashes because it's an X800, there is little to no difference beetween max clock and fatal freeze....blame the X800 core (see also w1zzard's latest post (http://forums.techpowerup.com/showpost.php?p=5844&postcount=51) )
angelus
11-08-2004, 06:55 PM
but that doesn't explain my underclock with the new scanning methode..
c0d3man
11-09-2004, 03:16 AM
Sorry if this is too noobish, but the temp in AtiTool is different to Everest, I was just wondering which one is correct ?
Much appreciated.
blobster21
11-09-2004, 11:37 AM
but that doesn't explain my underclock with the new scanning methode..
Sometimes things goes wrong and you get artifacts no matter what active clock frequencies is set (even default clock)...i personnaly witnessed this weird behaviour 1 time already.
In this case Angelus, atitools doesn't seem to cope with your card at all with the new scanning method. As to why....iDONTNO :confused:
angelus
11-09-2004, 12:25 PM
Well maybe the creator can take a look at it:
i got a:
MSI x800 XT PE VIVO - Core: 420
with beta drivers 4.11 cat
mR Yellow
11-10-2004, 02:30 PM
I've read the guide about modding a x800pro ----> x800xt on ur website.
Is says it works only with x800pro vivos. Because the vivo's don't have thge lasercut?
But if i join these with conductive silver lacquer it should work? Then it should be possible.
I've got a ASUS x800pro TD (not vivo). Which bios should i use to unlock the pipes?
Im looking for a bios that just unlocks the pipes but keeps the pro speeds as i don't think my card
will beable to handle the overclock. (I downloaded the one on ur site)
Is it possible/safe to use the x800xt bios and modify it with Rabit? ie clocks speeds and disable the vivo and then use this bios to unlock the xtra pipes?
Johnny_5
11-10-2004, 06:01 PM
I have a coupld of questions about the A.I. setting in Miscellaneous options. What is it good for? Does it have any effect on Mobility Radeon 9700s?
Thanks.
mR Yellow
11-11-2004, 05:30 AM
I have a coupld of questions about the A.I. setting in Miscellaneous options. What is it good for? Does it have any effect on Mobility Radeon 9700s?
Thanks.
AI is a feature developed by ATI Catalyst crew. Its a driver feature that automatically determines the best performance for each specific game ;)
15th Warlock
11-11-2004, 01:33 PM
AI is a feature developed by ATI Catalyst crew. Its a driver feature that automatically determines the best performance for each specific game ;)
Yes, it changes some features like trilinear filtering or temporal antialaising in real time, to produce the best performance in a given situation, without (according to Ati) altering the IQ.
This feature is supossed to turn off automatically when using synthetic benchmarks, so you cannot alter the results of the score and the IQ while using such benchmarks as 3dMark, but it gives you a few extra FPS in most games, and you won't notice any difference in the IQ.
00025
11-12-2004, 09:58 PM
does anyone know if this beta version works with the new Omega drivers?
I've been using this tool for a long time since it was packaged with the omega drivers but recently Omegadriver said that their new drivers doesn't support AtiTool v0.22. So I need to know if this beta release of v0.23 supports the new omega drivers.
wazzledoozle
11-12-2004, 11:10 PM
does anyone know if this beta version works with the new Omega drivers?
I've been using this tool for a long time since it was packaged with the omega drivers but recently Omegadriver said that their new drivers doesn't support AtiTool v0.22. So I need to know if this beta release of v0.23 supports the new omega drivers.
Im using ATITool 0.0.23 beta 9, and omega 2.5.90 with no problems at all
acrowley23
11-12-2004, 11:40 PM
the card crashes because it's an X800, there is little to no difference beetween max clock and fatal freeze....blame the X800 core (see also w1zzard's latest post (http://forums.techpowerup.com/showpost.php?p=5844&postcount=51) )
my x800 also only crashes and i get no Artifacts on the Core....
angelus
11-13-2004, 12:49 PM
well atleast u dont get artifacts on stock with the new scanning methode :mad:
and with the old scanning methode it just crashes, Yes ... but lol i did it again :) This morning, .....i setted my core at 592/580, i'm a little carefull for my memory since i can't read the temp ;)
3 times 3dmark05 but saw non artifacts :) so i'm kinda happy with the results .. but still a little annoying atitools still blames about atrifacts on stock :) Since i wanne know what my memory can take...
it's still a great program wizzard.. i had great over clocking results on my 9800 pro, but would have wanted to see the same results on my x800 xt pe :P of course
iLLestOne
11-13-2004, 08:51 PM
Yea, this tool worked GREAT on my 9800pro, but seems weird on my x800xt-pe...
It tested fine w/ the core at 550, so I manually put it there after testing the RAM, and my WHOLE screen gets corrupted....I panic, reboot and it's better.....try it again and same thing happends (lol, i know) ( this was on ATItool 0.0.22, i wasn't able to dl this version til now)
So I guess for now I can only use ATItool as a temp sensor...
blobster21
11-13-2004, 11:46 PM
...and also as a gamma correction tools, not to forget it's also a great tool to change Antialiasing & Anisotropic filtering "on the fly"
helicfi
11-14-2004, 12:55 AM
Not to sound too awfully stupid, but can somebody explain to me what Antialiasing & Anisotropic filtering do in games, etc??
mR Yellow
11-14-2004, 11:35 AM
my x800 also only crashes and i get no Artifacts on the Core....
What problems r u guys getting exactly with x800's?
Ive got a ASUS x800pro and have no problems with ATI Tool.
Started testing what my max core and mem was. I got 520 on Core and 515 on mem without any artifacts. I stopped the test as my overclock just kept climbing. I'll overclock more with better cooling :D
mR Yellow
11-14-2004, 11:42 AM
Not to sound too awfully stupid, but can somebody explain to me what Antialiasing & Anisotropic filtering do in games, etc??
lol :o r u a gamer :D
Antialiasing in simple terms is a method of sampling/rendering were u remove the zagged edges seen in ur games.
Anisotropic filtering is a method of enhancing the image quality of objects located far away from the camera. Its like Trilinear F but only better. It give more detail further away to ur gaming experience.
Why when my card went to 540Mhz (X800Se) it was boiling and the pc crashed???
Luckyly without problems... the card works fine and have the same benchmarks scores...
Can it be a problem with the algorithm???
There were no artifacts... do you think it's because of the omega driver???
Or voltage problem? (may I have to overvolt?)
alder99
11-15-2004, 04:32 AM
I got an X800 Pro ViVo @ XT-PE (Core to 1,43V, 16 Pipes) and I get no Artifacts with AtiTool 0.0.22 but 1-3 Pixels Artifacts per Frame with AtiTool 0.0.23b9...
So I guess the new Detection-Engine has some flaws? I don't see any artifacts in any Games/Benchmarks.
mR Yellow
11-15-2004, 05:42 AM
Why when my card went to 540Mhz (X800Se) it was boiling and the pc crashed???
Luckyly without problems... the card works fine and have the same benchmarks scores...
Can it be a problem with the algorithm???
There were no artifacts... do you think it's because of the omega driver???
Or voltage problem? (may I have to overvolt?)
Do u have fastwrites enabled?
Try setting them to off and run ATI Tool again. Just a hunch.
ThorAxe
11-15-2004, 09:39 AM
I got an X800 Pro ViVo @ XT-PE (Core to 1,43V, 16 Pipes) and I get no Artifacts with AtiTool 0.0.22 but 1-3 Pixels Artifacts per Frame with AtiTool 0.0.23b9...
So I guess the new Detection-Engine has some flaws? I don't see any artifacts in any Games/Benchmarks.
I didn't get artifacts in AtiTool 0.0.22 either however I did in 0.0.23b9 at lower clocked speeds.
I think 0.0.23b9 is actually better because I tested my overclock with numerous games and didn't get any artifacts...........except in 3DMark 2003 Mother Nature. Therefore it appears that 0.0.23b is a more realistic test. I believe that if you get an artifact on ANYTHING then it is not stable.
My advice would be to test your card in loops of 3DMark 2003 Mother Nature to be 100% certain that your overclock is artifact free.
Omega drivers deactive fastwrites in setup... They say that it is recomended with 9600 cards or with athlon processors... :(
Well... The card was very hot... But it didn't crashed like my old 9800pro with wich Vpu Recover turn on and then the monitor became black...
This crash was like an Image freezing! The desktop and all the other window (and also atitool and mouse pointer) were freezed...
lesstjake182
11-15-2004, 07:20 PM
I was using the Find Max Core option on this ATI tool. I have an x300 SE factory clocked at 324/195. The overclocking seemed to be going well althought it did seem a little high. It reached 474 with no artifacts but then the screen spazzed out and shut off so I assumed I OC'ed too much. Now i'm afraid to use this again because i didn't get any warning that that would happen.
some1
11-17-2004, 06:11 PM
I have noticed a problem, I am using the new 4.12 betas, with my 9800xt, and ati tool, is set to load on startup, set clocks, then close, and instead, it just sits there in the system tray after startup!
ss284
11-20-2004, 06:51 AM
I'm using the artifact tester on my 6800gt, and while it doesnt report artifacts, hl2 has been giving me flashing texture problems. I'm afraid that something is wrong with the memory on the card, does the artifact tester do rigorous testing on all the ram on the card, as well as test all the pipelines? I just wanted to make sure what the texture problems are being caused by.
Thanks,
Steve
csiki
11-20-2004, 03:05 PM
i think 0.0.23 would rather add "refresh rate fix" (60hz) because such we need min 1 other application.
corny
11-20-2004, 06:12 PM
Is all ok w1zzard; LTNC?
Ex0skelet0r
11-22-2004, 08:36 PM
wizzard when im clicking hardware monitoring from settings ati tool crash. do you know why? (i have 9600pro,p4@1500mhz,512mbram)
W1zzard
11-22-2004, 10:24 PM
wizzard when im clicking hardware monitoring from settings ati tool crash. do you know why? (i have 9600pro,p4@1500mhz,512mbram)
what motherboard do you have?
zodden
11-23-2004, 06:41 AM
Is it possible that the tool runs a little too conservative when finding a max overclock?
I only say this because I just got a Sapphire X800 pro vivo a few days ago and have been doing alot of testing. I added an Artic cooler version 4, some artic silver 5 and flashed to an XT PE bios to open the 4 pipes. My temp at load max is 52.
Using the tool to check the overclock speed I get 537/550 before artifacts. I had the tool running for about 8 hours total 2 times to get that number. When it shows artifacts its always 1 or 2 in the logs.
But I can run at 555/585 without artifacts that I can see in every other test: 10 hours loop of 3dmark2001 SE, 12 hours 3dmark03, 50 nature tests looping with title menu disabled, ruby demo for hours without any problems, and played 3 hours of Doom 3 without a problem at that speed and about 7 hours of HL2.
So is it just that you decided to be extra conservative in this version? To make the OC be as safe as possible? The old test gave me a higher number yes but it would freeze the X800 before finishing.
Nice tool btw, I am glad I found it.
W1zzard
11-23-2004, 03:18 PM
Beta 10 out here: http://forums.techpowerup.com/showthread.php?p=7233
vBulletin® v3.7.0, Copyright ©2000-2008, Jelsoft Enterprises Ltd.