Nvidia 40.72 drivers

[benjamat]

I run a geforce 3 (gladiac 920) and on updating to the latest drivers I find that when I click on the geforce3 tab in display properties I get a message saying there is a problem with running DLL as an app and when I click on dont send windows drops out of display properties.
I have noticed on Guru3d that others are having this problem and have tried using the 30xx - 40xx fix shown there but to no avail.
Can anyone tell me how to get around this problem.

many thanks

 

[Brian48]

You didn't uninstall the previous drivers correctly. Unless you want to manually remove all the drivers files and edit the registry by hand, I recommend you deinstall current the drivers via "Add/Remove programs". After which, reinstall with the previous version that you were using. Once you have the previous version installed, deinstall it again via "Add/Remove programs". The deinstaller will know which files to remove.

After you reboot, give the v40.72's another try.

 

[benjamat]

When I uninstall drivers it goes back to 29.58 which I assume is the base driver in SP1, I cannot get back beyond this. When I re-install40.72 I still get the same error message when trying to start the geforce property panel.

 

[BlvdKing]

Funny, I just click on the .exe and install over the old drivers. It has always worked for me.

 

[ROTC1983]

Originally posted by: BlvdKing
Funny, I just click on the .exe and install over the old drivers. It has always worked for me.

Yeah, that is all I had to do...

 

[Mem]

benjamat,I had similar problem with geforce tab,this is how I fixed it,uninstall the old drivers & reboot ,I then deleted the Nvidia folder in Windows Explorer,I installed the new 40.72 drivers (make sure anti-virus is disabled).Reboot and then apply that patch,run step 1 and 2 reboot and done,don`t do the last option where it says reboot and install 40.xx drivers,this is wrong.You have to apply the patch after install of 40.72 drivers and just reboot.That worked great for me.


Patch link.

 

[benjamat]

Thanks a lot, am trying this now, strange that nvidia have not acknowledged this common problem.