Jump to content
Compatible Support Forums
Sign in to follow this  
GeForce

Forcing FSAA gives BSOD in Win2k

Recommended Posts

Hi i am using windows 2000 pro with a geforce2 gts gfx card. I currently use the 6.47 detonator drivers (i kno they r a lil old but they run really well on my system - better than some of the more recent ones too). Anyhow, recently i have found that when i go into the control panel and enable d3d aa at any setting, and tell it to force this in every program i get a bsod as soon as i start any direct3d game. However if i do not tell it to force this, but still enable aa everything is fine although it seems that my games do not take advantage of it then and i see no aa.

 

Everything else runs fine, and i also dualboot this with win98 which the same drivers and this has no problems...hope u can help me, i have tried reinstalling the drivers but its still the same and i didn't used to get this problem b4.

 

Thanks

Share this post


Link to post

Have you tried different drivers? The 10.80's are pretty fast under 2k, but I haven't tried the AA stuff on my MX

Share this post


Link to post

yep i have tried numerous drivers, newer ones like the 10.80s, 12.00s and the 7 series...but with all of these i find my aa problem is cured however my refresh rate is limited to 75hz max frown i have tried the refresh rate fix, standard monitor drivers, manufactures drivers.. (iyyama vm pro 510) and reinstalled/deinstalled more times than i care to remember but still wont go no higher thats why i stuck to the 6 series. Yet i can install the 647's, 650's or other 6 series drivers and i can go straight up to 120hz, 100hz which i use atm. If some1 knows how to fix this refresh rate problem it would be very helpful, i dont have this in windows 98 at all and all drivers operate with all refresh rates availible in that os. Thanks.

Share this post


Link to post

Ewww...

 

I'm not sure what else to tell you, as I've not done AA on my MX for obvious reasons. Not really sure what to make of the refresh rate thing you got going on either.:(

Share this post


Link to post

owww, damn... i kno that the error msg refers to nv4_disp.dll or something simalar i can remember now, but later drivers did work ok. Has anyone had experience in mixing driver versions, like maybe adding in the later version of the nv4_disp.dll?

Share this post


Link to post

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×