My GF4's Anti-aliasing problems

[Bong]

Right now I have a 128mb Sparkle GF4 Ti 4200 (4x) on a KT400 (XP 1600+). Whenever I turn on my anti-aliasing (2x/4x/quincunx) i see some visual aritfacts on some of my games (like Live2k3 and jedi outcast) but not all. Since my ti4200 is clocked at speeds higher than ti4400 (300/560), I set it back to default speeds. Still the same problem exists. I turned off my PC for an hour then turned it on but still saw those small bubbles but again only during anti-aliased mode. I tried changing the drivers, but their still there. One of things I noticed is that whenever I set the color depth to 16bit, those artifacts go away. Here's another thing that I noticed, whenever I increase the resolution (higher than 1024x768 at 32bit) the problem arises again. Im thinking that maybe it has something to do with either the RAMDAC or perhaps my monitor.

Later when I get home, I'll try to reduce my refresh rate to 60/75hz from 85hz. But I hope you guys have other suggestions. My current drivers are 30.82 from the 41.09 before.

OT: I prefered the 30.82 (whql) coz it seems that there are less disk swapping on my system with this one.

 

[jiffylube1024]

Imho, nVidia's best drivers (most stable, nicest) were the 27.72, 28.32 and 30.82 ones. Unfortunately, I have to run 40XX drivers for the best dual monitor support . I'm running the 41.09's right now and they're pretty good for me, however I don't really play games with AA on so I can't verify or refute AA performance/glitches.

 

[Viper96720]

I get artifacts on my ti-4400 if I go to 32bit color. Still has some at 16 bit but it's not as bad. It's your video card that's messed up. On the windows xp log on screen instead of a shaded ball looking thing in the upper left. It looks like a bunch of rings. Once the legacy windows drivers were being used and everything looked all nice. I tried formatting and that didn't help.

 

[Bong]

I think i dont have that problem with the win xp log on screen. its just on some games with AA / high resolutions. Do you think I should RMA? Coz im thinking that the RMA might not be considered by the store coz its only on AA problems. Its sad coz here in my place, initial testing is done on the stores.

 

[AnAndAustin]

Seems most likely a driver type issue, I've found 41.09 to be by far the best on my 4200_128MB, XP2000+, KT400 & WinXP so do try a few diff ones. Have you tried setting your whole system back to defaults, are you o/c'ing the FSB? How did you find your card could do 300/560 and what games and settings did you use to test it could run at that speed? It isn't a good idea to leave your o/c'ed component running at it's absolute limit, so if 300/560 was the fastest it would go it would be ideal to run it at 285/540 or so. You have to remember that oc/'ing stresses the component in a way it wasn't tested or designed for, and it obviously voids your warranty although you could RMA it hoping it is something which has failed unrelated to o/c'ing (like a manu defect).

 

[sep]

Originally posted by: AnAndAustin
Seems most likely a driver type issue, I've found 41.09 to be by far the best on my 4200_128MB, XP2000+, KT400 & WinXP so do try a few diff ones. Have you tried setting your whole system back to defaults, are you o/c'ing the FSB? How did you find your card could do 300/560 and what games and settings did you use to test it could run at that speed? It isn't a good idea to leave your o/c'ed component running at it's absolute limit, so if 300/560 was the fastest it would go it would be ideal to run it at 285/540 or so. You have to remember that oc/'ing stresses the component in a way it wasn't tested or designed for, and it obviously voids your warranty although you could RMA it hoping it is something which has failed unrelated to o/c'ing (like a manu defect).

What he said!

I to notice some artifacts even at less speeds. I'm going to set everything back to default (try 40.41) and cross my fingers.
-JC

 

[Bong]

300@560 isnt my fastest overclock. 315@570 is my top overclock. For the longest time, I just play with 4400 speeds. Now after experiencing this, I'll put it back to default for the meantime. I hope the problem goes away. Today ill test AA with unreal 2 w/c i just got earlier and see if it doesnt have this AA problem.