direct 3d crash with geforce2 & XP

[Ferris]

running a Creative GeForce 2MX 32mb AGP with nvidia 21.83 WHQL drivers on XP Pro 2600, and have been doing so with no problems with direct 3D for a couple of weeks or so.

i noticed the prob first when one of my direct 3D based screensavers (the new MS XP one) starts up, it will crash the OS with a BSOD and an error in nv4_disp. so i reinstalled the drivers and the problem remains. also tried using the original XP supplied drivers and the new creative 21.85 ones. also removed the card and let XP find it again. still probs.

basically my machine now crashes when i use a direct 3d app or game. this only started happening yesterday after using direct 3d with no probs for quite a while.

any ideas lads?

[Gojo]

I just installed XP and am having the same problem when I try to run any 3D app. System crashes and tells me my GeForce Driver is the problem.
I've installed about 5 different drivers to no avail: Tried Default XP drivers, 21.83, 21.85, and 12.90. Also the latest Leadtek drivers (I have a Leadtek GeForce2 GTS)

Still crash whenever a 3D app starts.
Argh!
Help!

[Ferris]

i sympathise mate. weird thing is, my direct 3d worked fine until yesterday! i even resorted to going back to a restore point a week ago. think it may be a prob with DirectX 8.1, and until MS release a final vers (i think the beta is all that is available), i'm well stuck.

[Gojo]

Add 21.88 to the list of Drivers I've tried.
They just released it this morning, I'm still crashing.
Sigh.
Will probably re-install Win2k or 98Se.

[Ferris]

im wondering if my crashing may be monitor related. when i click on properties > settings > it lists my monitor as "default". weird. a few days ago it was a "plug and play" and a week ago a "sampo 800u" (which it is!). also, the monitor folder from device manager has strangely disappeared, and the option to change monitor in properties > advanced is now greyed out. can't seem to be able to install my monitor again. :/

when i highlight a direct 3d screensaver it shows the small example working fine, if i preview it, *cRasH BsOd*. games don't work anymore, period.

my issue is definetly not a video card driver one, like yourself i have tried practically all detonator drivers up to 21.88.

did your direct 3d ever work?

[Gojo]

Nope, never worked. I just installed XP yesterday. I just heard on another forum it may be due to my particular version of XP. Lets just say I have the 'cheap' version.
I'll try again in a few days with the 'more expensive' version when I get it from Best Buy. From what else I've seen I really like XP.

[Fubarian]

I get an infintate loop - says nv4_disp caused blah blah blah.

[Ferris]

ditto Fubarian, thats the info i get on the BSOD, "infinite loop". any solutions? ;)

[Gojo]

Also Ditto on the infinate loop.
So far no solution.
Sigh.
:o

[Ferris]

fixed! but i could have swore i done this before!

to cut a long story short, i uninstalled my gfx card via device manager and shutdown. XP detected the card as a standard vga on boot and asked for drivers, so i installed the default XP driver for the geforce2mx (vers 5.1.2001.0) and things have worked fine so far. direct 3d is no longer crashing. i even have a load of wee fish again swimmin in my monitor after 10 mins.

maybe theres a prob with the 21xx drivers, but i did have 21.83 WHQL running fine a few days ago. anyway, im not gonna tempt fate and install any new drivers until this issue is addressed at a later date.

good luck lads, hope you have some luck.

[Gojo]

Wahoo! :D
Good for you Ferris!

That doesn't seem to work for me. Everytime I un-install my driver, XP re-installs it on startup.
Sigh.

[Gojo]

You've got to be kidding me.
I just read on the Microsoft support newsgroup that some guy's Nvidia problem went away when he reset his bios.
I figured, why not? and reset mine.

>>>>> 3D APPS WORKED LIKE A CHARM! <<<<<<

Ok, now to tweak my Bios settings to see what caused the problem. You're not gonna believe this but my 3D apps fail when I set the system Bus speed over 100 Mhz.
What???
I'm supposed to be running 133!
I suspect its stinking VIA problems.

Funny thing is my system worked like a charm under Win2K.

What gives?