• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

x64 ATI Driver Problem

zutme

Weaksauce
Joined
Apr 28, 2005
Messages
109
I decided to give Windows XP x64 a try and everything is working well except for ATI's drivers. I am trying to use Catalyst 5.10 for Windows x64. First off the driver installer identifies my card as X800 series instead of X800 XT Platinum Edition. Ignoring this I tried some things and the drivers seem to work perfectly in non-3D applications, but any game I try to run there are massive graphical problems. In Quake 4 there are weird black squares at even intervals overlaid on top of the picture. In Battle for Middle Earth there are odd lines of color covering the display. I decided I would go update the drivers in windows with the X800 XT driver. This had no effect. In the 3D section of the Catalyst Control Center where it shows the racecar with some graphical errors similar to the ones in Quake 4 but much less regular. In dxdiag the Direct3D tests look normal. Is this artifacting? The errors remind me of artifacting in some ways, but why would they start with the new OS/driver install? I'm guessing its the drivers or the way I installed them. I wish there were Omega drivers for x64 cause they seem to have always worked better for me. Anyway any advice would help because I'm getting very annoyed by this.
 
well, i knew the win64 edition had some bugs in it. but ive never heard of driver issues. most intresting. it may be a card issue. try reinstalling drivers. if it dont work it may be card problems
 
I wanted to update this thread to tell anyone who comes across it in the future that this turned out to be a hardware problem not Win x64.
 
Back
Top