Legit Reviews

I bought an ATI X1650 Pro because I had been suffering from nv4_disp.dll problems with my nvidia card. The problem got so bad that I couldn't even boot except in safe mode and I concluded the card was dead. I said to hell with nvidia. Welcome ATI and bye bye nv4disp.dll.

I have had the card for more than a month now, catalyst 8.1, everything cool until today I played medieval 2 Total War and I suffered the same old BSOD, only instead of nv4disp.dll it says problem with ati3duag.dll !!

I've searched the net and a lot of people seem to have a problem, but just as with nv4disp nobody seems to have the solution. I'm placing my hopes that someone on this forum knows something about it.

I'm afraid that the only thing I can suggest is a complete wipe of the drivers and reinstall.

But this time, run driver cleaner pro after uninstalling the drivers.

So you should, uninstall the card/drivers -> boot into safe mode -> run driver cleaner -> select both AMD and NVIDIA (as you have had both cards previously) -> reboot into normal windows -> reinstall your ATI card using the newest drivers from the ATI website.

Dan

hey, another 1650PRO sufferer just think, you got it after 8.1 came out, the damn thing wouldnt use ANY drivers until that(8.1) except what came on its disc(7.7 for me)and i dont even remember all the problems this POS has given me over the Months, i have actually been thinking of going nvidia because of it (because my previous nvidia cards game me no issues until dead, a GF4 ti4200 and ghetto moded mx2 200) but justins x850XT at the right price was my opportunity to see what a real ATI card can do(i dont care about age, come on), hope this works out better

and i think i got the ati2duag error a few times when i was on 7.7, dont remember

have you OCed it, and what are the operating temps(temps cause BSODs a LOT of the time)

Are you running dual monitors?
I can run for days on end with no problems until I enable the 2nd monitor.
Turn the 2nd one on .... and something is gonna go haywire in a short amount of time.

This happened when I was running an 8800 GTS, and it happens now running the 3870.
Just different offending drivers obviously.
Happened in Vista 32 bit, as well as 64.