I have a 750MHz Duron system, 196 megs RAM, 52x CD-ROM drive, not that any of that matters. What matters is my graphics card; NVidia Geforce2 MX 200
After i have selected my options in the menu screens of games i TRY to play, i start the game. At the load up bar, it freezes at the same place, everytime, just as (i think) it starts initialising the graphics card.
I have downloaded the latest drivers, ver 4.13.01.2181
Still the same effects.
This happens PARTICULARLY in Electronic Arts games, for example, NHL2000, and 2001, Need for Speed 3,4 and 5.
There’s two sets of drivers you need. The first is the drivers for your motherboard. If you have a Via Chipset based motherboard you can get them at http://www.viatech.com. Otherwise, try to download from the motherboard manufacturer’s website.
Second, I don’t think you’re downloading the proper drivers. The current version is Detonator XP 21.81, and can be downloaded from http://www.nvidia.com. I hope this helps.
Without knowing the exact manufacturer and model of the motherboard I can’t tell you exactly what drivers to get. But, if you go to their website and look up the specs, you should see it telling you the chipset that is used. If that chipset is made by Via (Via KT133, or KT133A), as is most likely the case, then you go to http://www.viatech.com and download their 4-in-1 drivers. The current version is 4.33. Without these drivers, AGP graphics will not function, the system will be slow, and crashes may often occur.
The FCC-ID may be listed in the manual. If not, you can try poking around the manual, seeing if it has a support or warranty contact that references the manufacturer. As a last resort, the FCC-ID will be printed somewhere on the motherboard, though maybe on the back. If you find this FCC-ID, go to http://www.windrivers.com and enter it into the FCC-ID search at the bottom of the page. That will give you a manufacturer and model name.
you might also want to try updating your system’s directx – the current version is 8.0a (I believe) – many games have the very issue your describing, and updating the directx often solves it.