Weird Radeon 3000 series driver issue.

Jimsey0000

Commendable
Apr 18, 2016
4
0
1,510
Heya guys.

This has got to be the strangest video card issue i've ever seen. Been building computers since 2000 or so, and never seen anything like it.

Basically, i'm using a Asus M5A87 motherboard, I've bought two different 3000/4000 series cards (3850, and 4550) since my onboard 760g graphics aren't cutting it anymore. both of these cards only work with Catalyst 9.5 series drivers from 2009.... and they both give weird artifacts in certain programs; like in mount and blade warband, the faces will be missing, followed by triangles/artifacts etc same thing goes for other games around 2012 era, like GW2. old games from the early 2000's like DAOC and SWGEMU work fine though, so i figured 'must be the drivers' so when I update the drivers to any catalyst version past 10.9 or so, the direct3d is greyed out/disabled in the DXDIAG utility. I'm starting to think the 3000 series must have been the worst Radeons because I plugged in an old X1300 Radeon, and installed the latest driver (from 2010) and it works fine, no artifacts (it even runs skyrim better then the 3850 which is a sad concept honestly. No artifacts.
What is the probability of getting two different Radeon cards, both of which have the same problem like this? The 3850 was ATI vendor, brand new, and the 4550 was a HP vendor used card. it makes me wonder if it's something else. Strange that both cards would only be able to remotely function (even then, with artifacts) with a driver from 2009, and not later.
What's more is, Two different NVIDIA GT 440 cards work fine with the latest NVIDIA drivers, so I don't get it. What on earth would cause direct3d to be disabled in two different cards like that?
I used two driver sweeper programs, and reinstalled Windows XP 32 bit, which i was using, it did nothing.
 

Jimsey0000

Commendable
Apr 18, 2016
4
0
1,510
Thanks, I'll try autodetect, I don't think i could get it to work last time, but I'll reinstall one of the 3000 cards and look into it again. I own driver sweeper and DDU, they're really great programs, not sure what i'd do without them, honestly.
So anyway, Alan, have you ever heard of a problem like this before? I think i've only seen like one or two threads about it on the net out of all the forums i've been to on the internet. Not accepting new drivers even though they're winxp 32 bit, just because the drivers are newer than the hardware, really strange stuff. I always heard you're *supposed* to use the new drivers.
 

Jimsey0000

Commendable
Apr 18, 2016
4
0
1,510
Ok, the autodetect just told me to download the 14.4 catalyst, which is the latest, and i've tried it multiple times over the course of two months or so, and pretty much every official driver I used off amd's website won't work past 9.5 catalyst. I guess this will just remain a mystery. What gets me, is one of the cards is not an odd vendor or anything, it's an authentic ATI which makes this issue especially strange. If it was some oddball vendor, I could see why the drivers past 2009 wouldn't work.