52.16 Problem

quantumn0de

Distinguished
Nov 4, 2003
5
0
18,510
I am running an FX 5200(I know it's not that great, but I needed a cheap solution at the time) and after a much needed format of my recently built system I decided to upgrade all of my drivers. The first drivers I installed after my mainboard drivers were the detonators that shipped with the card, 44.03. I then proceeded to the Nvidia website to see what the latest drivers were. I downloaded the 52.16's and installed them. I must say I saw a wonderful performance increase over the 45.23's I had been using before the format. They appeared to be stable through several hours of play during a small LAN party with my friends. Later the next day when I moved the computer from our LAN location I was playing a couple of games and noticed some flickering which also happened sporadically within a few minutes after exiting a game. That may be a monitor issue as I have yet to reproduce it on other monitors and it has happened just rooting around in Windows.

And the problem begins:

Upon moving the computer a second time(still with the 52.16's installed) I attempted to start the computer and within a brief second following the Windows XP loading screen a blue screen(from what I could read some kind of STOP error) flashed for a split second and the computer restarted. This would continue as long as I tried to start Windows normally(I was able to start in Safe Mode, in hindsight, probably because the drivers were not loaded). Having so many things to try and attempting to get my computer going again as soon as possible I decided not to mess around with the drivers too much. After all, I had updated all of my drivers and had no reason to believe that any one of them could be the problem especially since the computer ran fine for so long. I had done minimal work as far as restoring my computer after the format so I decided to try formatting it again. Actually I first tried repairing my Windows installation but when it got to 'Setup is starting windows' I got a similar blue screen with a stop error. This same screen appeared the first few times I tried to clean install Windows after formatting the second time. Leaving the computer alone for a day allowed me to install Windows upon returning to the job.

So I knew then that it wasn't a problem directly related to any piece of hardware or the abuse of that hardware.

I then proceeded to install the drivers for all of my devices again. I again started with the mainboard drivers and the necessary utlilties that came with my motherboard. Then I tried the graphics drivers, again installing the shipping drivers and then immediately the 52.16's. This time, however, the drivers failed to install several times(upon restarting the drivers simply rolled back to 44.03). This was the way I had done the update the time it worked, no reason for it not to work now, however, I tried installing the 45.23 drivers both first and over the 44.03's then moving on to the 52.16's. On both occasions the 52.16's installed just fine, but upon restarting I was confronted by the blue screen and continuous restart.

Therefore, it must be the drivers causing the problem. Sure enough, dropping into safe mode and uninstalling the drivers allowed my computer to boot just fine.

So here I am, stuck with underperforming drivers wishing that the 52.16's could have worked just a little bit longer. If anyone knows where I could find some earlier 5x.xx drivers I would like to know. I hear they yield some performance increase. Otherwise I pose the question:

Has anyone else heard of/experienced this problem with the new official release?

Thank you in advance for your help.
 

Vapor

Distinguished
Jun 11, 2001
2,206
0
19,780
That is weird...the only time I had the 52.16 drivers crash on me was when I forgot to turn on my big fan blowing air in (OCed 4400s like air) and it crashed after about 30 min of Halo. I would recommend that you roll back to 45.23 for now (can be found on nVidia under the Win98se/Me section). Look around for 51.75s if you really want the 50series--IMO it isn't worth it.

RDRAM = (ENEMY)^2
 

quantumn0de

Distinguished
Nov 4, 2003
5
0
18,510
Well, it wasn't so much a crash as a failure to load due to some conflict or incompatibility. The drivers simply don't work and it's terminal. Thanks for the reply though. I emailed my card manufacturer about the problem, that's what Nvidia says to do for support. Maybe they'll figure it out.
 

Thor1182

Distinguished
Sep 2, 2003
36
0
18,530
tyr finding the det. removal tools from 3dguru inbetween driver changes. If you use the 53.16 straight from the get go you might not have any problems. Det. drivers are known for having lingering effect on the system.

I'm a Computer Science and Electrical Engineering Student, not English, nor will I ever claim to be.
 

Thor1182

Distinguished
Sep 2, 2003
36
0
18,530
I finished reading the rest of your post and now confused... what OS are you using again? I'm using XP with a FX5600 Go card and the only drivers I ever put on here are the 52.16. Granted I haven't found a way that shows what version the drives are directly becuase all the version stuff is somehting like 6.x..... nowhere does it say forceware 52.16......

I'm a Computer Science and Electrical Engineering Student, not English, nor will I ever claim to be.
 

quantumn0de

Distinguished
Nov 4, 2003
5
0
18,510
I will most certainly attempt this as I have not yet tried the 52.16 after all remains of the old detonators are completely gone. Perhaps there is some lingering effect from the old drivers that is causing the problem.

Using Windows XP Pro w/ SP1

<P ID="edit"><FONT SIZE=-1><EM>Edited by quantumn0de on 11/04/03 06:19 PM.</EM></FONT></P>
 

quantumn0de

Distinguished
Nov 4, 2003
5
0
18,510
Unfortunately this did nothing to alleviate my problem. The 52.16 drivers still cause the blue screen and continuous restart when installed and other 5x.xx series drivers either do not install correctly or cause the computer to believe it needs to install drivers for the graphics card automatically and reboot. Additionally, the detonator removoal program RIP would not work. It threw an error when I tried to run it. Don't know what to do now.