Problem with nVidia drivers

[Eddyall]

So I had a problem with my driver where the first game launch would freeze or sometime the whole computer so I installed the 320.49 and now it just show a black screen and I can't see the error report I think I'm getting.

So does anyone knows last time the driver were okay because looking on google tells me it's been happening for some times now, GPU is a GTX570 DCII.

[M-ursu]

 320.49 should be fine.

[Volbet]

Do you have any overclocks on the card?

[Eddyall]

 320.49 should be fine.

 

 

Do you have any overclocks on the card?

 

Yes from EVGA software but it's close ATM, I'm downloading the lasted to see if it could be that. 

[M-ursu]

 

[Volbet]

Yes from EVGA software but it's close ATM, I'm downloading the lasted to see if it could be that. 

Use Precision to set your card back to its default speed. It sound like you have a unstable overclock

[Eddyall]

Use Precision to set your card back to its default speed. It sound like you have a unstable overclock

 

My overclock as been stable for a year/a year and ½ now.

And reinstalling Precision didn't do a thing.

[Locke290]

Go back to 314.22 I believe it was, those were rock stable for the GTX 500 series in my experience.

You could also try the latest beta drivers, the newest beta drivers are better then the 320.49 for me anyway.

 

 

To be quite honest, I think all the newer drivers from NVidia are crap.  Since 320.49 I can't run any game without v-sync on or the game crashes on startup.  You could try making sure v-sync is on.

[Eddyall]

Go back to 314.22 I believe it was, those were rock stable for the GTX 500 series in my experience.

You could also try the latest beta drivers, the newest beta drivers are better then the 320.49 for me anyway.

 

 

To be quite honest, I think all the newer drivers from NVidia are crap.  Since 320.49 I can't run any game without v-sync on or the game crashes on startup.  You could try making sure v-sync is on.

 

I try 314.22

[FireFox]

inflatable_unicorn_horn_for_cats.jpg

 

Cat's love it, apart from that one lol

[Volbet]

My overclock as been stable for a year/a year and ½ now.

And reinstalling Precision didn't do a thing.

Silicone degrades over time, so your overclock might not be stable anymore 

[Eddyall]

So I try to reset the overclock, didn't do a thing.
And I seem to be getting the same problem with the 314.22 driver.

 

Edit what's fun is when it's going to be fix like magic by itself in 2 days.

Are the drivers in beta still frying card because I don't have an instinctor available.

[Locke290]

I think those were pre-320.49 beta drivers I heard of card frying.

 

Enable v-sync on through nVidia control panel and try playing a game.

 

If using Steam, set the launch options for that game to -windowed

 

Try those.

[Eddyall]

Well playing in DX9 cause "lagging" but reading on google one of the problem I'm having may be cause by a trojan so I'm getting rid of this one first.

[Eddyall]

Well 285 seems to work for now...

[Eddyall]

So I've test a bunch of thing and ruled out the following:

-Overclock, if it's bad than putting it back to default change nothing

-Drivers, when back between 285 and 320 I have to wait 2 to 30 seconds more for things to crash

-Probably not cause fully by Directx 11 since Darksiders 2 and XCOM: EU work AFAIK

-Probably not cause by a Trojan

 

I'm not getting error report when it crash but they were pretty varied with APPCRASH and a few BEX (can not find anything good on this or BEP online) and most of the time it said "StackHash_#x#x"

 

Looking at crash dump file for Shogun II all of them seems to have this line

 

Exception information    The thread tried to read from or write to a virtual address for which it does not have the appropriate access

 

Does this give anyone any idea?

[R4STABAN]

Any driver from nvidia beyond the 306.xx set is just utter crap.

[MaxFrags]

Try going into the Phsyx settings in the control panel, and change the Phsyx processor to anything but auto. It worked for my 670

[Eddyall]

Try going into the Phsyx settings in the control panel, and change the Phsyx processor to anything but auto. It worked for my 670

 

I kind of hope this doesn't work because it would be so stupid

Well no it didn't but you just made me realized that most PhysX games work but not the others.

 

Any driver from nvidia beyond the 306.xx set is just utter crap.

 

Well none of them seems to like me ATM 285-326

[MaxFrags]

Hmm. I think it's a bug in the driver

[Eddyall]

Hmm. I think it's a bug in the driver

 

Going back and forth between them the symptom change even if I reinstall the same driver.

 

285 work okay

try 306, it fails

go back to 285, doesn't work anymore

 

or I just wait a day and a stable driver fails for no apparent reason.

[CadillacVic]

Going back and forth between them the symptom change even if I reinstall the same driver.

 

285 work okay

try 306, it fails

go back to 285, doesn't work anymore

 

or I just wait a day and a stable driver fails for no apparent reason.

They just released 326.41 Beta which seems to be fixing a lot of problems they were having. People seem happy with this new release over at the Nvidia forum.

 

@M-ursu

 

Drivers 320.49 were horrible drivers in general but for some 500 cards it killed them.

[Eddyall]

They just released 326.41 Beta which seems to be fixing a lot of problems they were having. People seem happy with this new release over at the Nvidia forum.

 

@M-ursu

 

Drivers 320.49 were horrible drivers in general but for some 500 cards it killed them.

Well if the beta driver isn't frying card anymore I'll go for it since it can't be worse. I hope I didn't just jinxed myself.

[CadillacVic]

Well if the beta driver isn't frying card anymore I'll go for it since it can't be worse. I hope I didn't just jinxed myself.

It could be out of Beta by now it takes a week for Microsoft to certify them WHQL could be a different number as well.

[CadillacVic]

Well if the beta driver isn't frying card anymore I'll go for it since it can't be worse. I hope I didn't just jinxed myself.

Looks like you got options 326.41 and 326.80 (NEW) both BETA and from the looks of it NVIDIA has solved that damn TDR error on 326.80.