Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

nVidia 52.16 drivers generate Windows Explorer error ?

Status
Not open for further replies.

Grunt2002

Programmer
Apr 26, 2002
84
BE
Hello,

I am not sure about this 'conflict' and have no idea of what could be the reasons :

I installed the latest whql certified nvidia forceware drivers (52.16) on two systems running windows 2000 pro sp4 and 2000 server sp4.

The drivers successfully installed, and I had no display trouble having completed the installation.

However, when trying to open the Control Panel, I got a message box reporting a Windows Explorer error, with the message 'WE has encountered an internal error and will be closed by windows.... <memory address> : memory cannot be read'.

Then it closed. Accessing the device manager showed no hardware conflicts nor something special.

The behaviour was exactly the same on both machines. I only had problems when trying to access the Control Panel.

The workstation has a geforce fx5200 video card and the server a 440 mx one.

This is definitely solved by uninstalling the display adapter from the device manager, and restoring former nvidia drivers (44.03 or 30.82 for sample).

Anyone ever heard of something similar ?

Thanks,

Grunt
 
There have been several reports of issues users have been experiencing with v52.16. My opinion, the 50 drivers were very much rushed to fix directx 9 performance issues with the 40 series drivers. Give it a couple more driver releases before upgrading.
 
So maybe it should not be 'whql certified' [angel] ???

Thanks for posting,

Grunt
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top