New 295.51 drivers are out.

I wonder if they are crashing pieces of shit, like most of the other drivers Nvidia seems to put out lately?
 
I wonder if they are crashing pieces of shit, like most of the other drivers Nvidia seems to put out lately?

/looks at Pitbully's sig hardware

AMD fanboy much? I just left 6950 crossfire after 2 months specifically to get back to Nvidia's drivers. You can make alot of arguments in favor of AMD's cards, but suggesting their drivers are better than Nvidia's is frankly laughable. I have never had more driver related issues than over these last two months.
 
I actually have had a ton of Nvidia cards and still have one in this machine now waiting on an RMA. The Nvidia driver crashes about 3 times a day. I don't think I compared them to anything either.
 
AMD fanboy much? I just left 6950 crossfire after 2 months specifically to get back to Nvidia's drivers. You can make alot of arguments in favor of AMD's cards, but suggesting their drivers are better than Nvidia's is frankly laughable. I have never had more driver related issues than over these last two months.

Ya no kidding. I liked my 5870 over all. Not at all sorry I spent the money, it gave me a year of good performance. However, the drivers are not up to par with nVidia. Much happier with the 580 drivers.
 
I wonder if they are crashing pieces of shit, like most of the other drivers Nvidia seems to put out lately?

Haven't had any real issues for several years... negligible ones at most. Sounds like PEBKAC if they're "crashing pieces of shit" for you :(.
 
I wonder if they are crashing pieces of shit, like most of the other drivers Nvidia seems to put out lately?

Never had any problems here. Sounds like PEBKAC.

EDIT: LOL, wrote that before I even read the post above mine. :D
 
Never had any trouble with nvidia in the almost 2 years of owning a 460 sli setup. The only game that was messed up was dragon age 2 out of 98 i own..
 
you guys have got to be kidding. 290.53s were buggy as hell. somehow they destabilized my ram/mem controller and gave me hard locks, BSODs, and black screen reboots until i manually wiped every x.53 file after uninstall. i would also like to know if these 295s are bugged
 
you guys have got to be kidding. 290.53s were buggy as hell. somehow they destabilized my ram/mem controller and gave me hard locks, BSODs, and black screen reboots until i manually wiped every x.53 file after uninstall. i would also like to know if these 295s are bugged

no you've got to be kidding, i've been running 290.53 since it came out, on my main machine, no issues, if you are having those issues above i'd look toward other factors
 
/looks at Pitbully's sig hardware

AMD fanboy much? I just left 6950 crossfire after 2 months specifically to get back to Nvidia's drivers. You can make alot of arguments in favor of AMD's cards, but suggesting their drivers are better than Nvidia's is frankly laughable. I have never had more driver related issues than over these last two months.

Did the same thing as you. Had 6950's in x-fire for the past 4 months and couldnt stand all the AMD driver problems. Sold them and bought GTX 570's in sli and loving it so far.
 
I keep having the smoke flash that comes of buildings in Karkand i tired all the driver no fix its the only map i have a problem with. does anyone else have this?
 
I just noticed the custom res tweaks they made to these. I might have to re-install Crysis Warhead since the option to un-force 24Hz should finally work again.
 
you guys have got to be kidding. 290.53s were buggy as hell. somehow they destabilized my ram/mem controller and gave me hard locks, BSODs, and black screen reboots until i manually wiped every x.53 file after uninstall. i would also like to know if these 295s are bugged
I've been using those betas since they were released on my system in the sig with no problems at all. In fact they have been some of the most stable NVIDIA drivers I've used with my 580s. Your problem lies elsewhere, my friend.
 
Flawless so far, 560ti 384 2 gig. Havent had a 2d driver crash, YET, since trying these from 285.62. Overclock seems fine also.

And. best of all, they didnt gimp the fan speeds on accident and nuke my 650$ card....still sore from the 196.75 fiasco.
 
you guys have got to be kidding. 290.53s were buggy as hell. somehow they destabilized my ram/mem controller and gave me hard locks, BSODs, and black screen reboots until i manually wiped every x.53 file after uninstall. i would also like to know if these 295s are bugged
The 295.51 drivers caused Skyrim to give an Error Code 51 in Steam and would not launch on my desktop system. Others have experienced this as well. Reinstalling the 290.53s solved the issue for me. Those drivers have been very solid.
 
Flawless so far, 560ti 384 2 gig. Havent had a 2d driver crash, YET, since trying these from 285.62. Overclock seems fine also.

And. best of all, they didnt gimp the fan speeds on accident and nuke my 650$ card....still sore from the 196.75 fiasco.

the 295's were bad for me. very bad. BSOD watching a damn you tube of all things..

However, in another thread.. not driver related specifically..but card related...someone mentioned.. shutting down for 5 mins, including unplugging the PSU

I did that last night before gaming ( I uninstalled the 295's and am back on the 290's ) .. well what do you know.. not a single problem all night.

seems the powering down, including the powering off the PSU ( I even hit power button while unplugged to dump any Caps charged. )

IS a fix.

If you are having driver kernal restarts, or any more issues.. try this method..and see if it works for you..It did for me..

and to this post I quoted.. man.. Im so with you

those freakin 196 drivers smoked my gtx8800.. and I was hesitant to go nvidia again...

but..so far .. so good.. especially with this power down fix...
 
the 295's were bad for me. very bad. BSOD watching a damn you tube of all things..

However, in another thread.. not driver related specifically..but card related...someone mentioned.. shutting down for 5 mins, including unplugging the PSU

I did that last night before gaming ( I uninstalled the 295's and am back on the 290's ) .. well what do you know.. not a single problem all night.

seems the powering down, including the powering off the PSU ( I even hit power button while unplugged to dump any Caps charged. )

IS a fix.

If you are having driver kernal restarts, or any more issues.. try this method..and see if it works for you..It did for me..

and to this post I quoted.. man.. Im so with you

those freakin 196 drivers smoked my gtx8800.. and I was hesitant to go nvidia again...

but..so far .. so good.. especially with this power down fix...
If you're havin kernal panics I feel bad for you son, I'm runnin 295 betas and BSOD is done.

I'll show myself out now...
 
in case any Arkham City players are interested, the latest beta drivers come bundled with a new PhysX version which according to the release notes- "Fixed a bug that caused cloth (paper) to jitter in Batman: Arkham City"
 
Damn I hope this fixes BF3 crashing in mulitplayer.

i also had random crashes where the little balloon would pop up saying the driver crashed and was recovered successfully, but the only way i could get back into BF3 was killing the process and restarting the game.

i was hoping this driver would fix it, but alas, half way through my second map i was greeted to the same little balloon again :(

anyone with this problem have any luck fixing it?
 
i also had random crashes where the little balloon would pop up saying the driver crashed and was recovered successfully, but the only way i could get back into BF3 was killing the process and restarting the game.

i was hoping this driver would fix it, but alas, half way through my second map i was greeted to the same little balloon again :(

anyone with this problem have any luck fixing it?

If you are oc'ing, I found that caused the same issue for me when my oc was too much.
 
Last edited:
i also had random crashes where the little balloon would pop up saying the driver crashed and was recovered successfully, but the only way i could get back into BF3 was killing the process and restarting the game.

i was hoping this driver would fix it, but alas, half way through my second map i was greeted to the same little balloon again :(

anyone with this problem have any luck fixing it?
speedy.. Im telling you man.. it worked for me.. try the thing I mentioned.. before getting ready to play.. do a shut down, then power off the PSU for like 5 mins.. like even pull the plug whatever..

then boot up and play. So far... it has stopped the driver stopped responding issues..

maybe its a design flaw ..I dont know.. something about the cards building up magnetic fields..but full power down seems to make a difference.. try it..

a 5 min investment fro problem free gaming isnt a real solution..but if it works... screw it..
 
The 295.51 drivers caused Skyrim to give an Error Code 51 in Steam and would not launch on my desktop system. Others have experienced this as well. Reinstalling the 290.53s solved the issue for me. Those drivers have been very solid.

I actually just ran Skyrim the other night with these drivers and did not encounter that error. So it's clearly not a global bug.
 
If you are oc'ing, I found that caused the same issue for me when my oc was too much.

i do have an OC, but the issue is still present even if i play without it.

speedy.. Im telling you man.. it worked for me.. try the thing I mentioned.. before getting ready to play.. do a shut down, then power off the PSU for like 5 mins.. like even pull the plug whatever..

then boot up and play. So far... it has stopped the driver stopped responding issues..

maybe its a design flaw ..I dont know.. something about the cards building up magnetic fields..but full power down seems to make a difference.. try it..

a 5 min investment fro problem free gaming isnt a real solution..but if it works... screw it..

i tried this and a few minutes into my first game i got the same driver stopped responding and has been recovered message :(

ill try it again later tonight, but im still open to more suggestions to fix this !
 
I actually just ran Skyrim the other night with these drivers and did not encounter that error. So it's clearly not a global bug.
Yeah, it works fine on my laptop. It only affected my desktop. It might have something to do with the latest Skyrim patch.
 
This driver also screwed up my STEAM application. Can't load any of my steam games. Getting ready to do a manual clean uninstall of NVIDIA drivers and a fresh clean install of 295.51.

Hopefully I don't have to do a clean install of STEAM. :mad:
 
Last edited:
I want to mention that I get the same recovery error when my videocards are:

OC'd too high and are at the point where they will begin artifacting but I didn't notice it before. Dude who cares my chick in WoW has purple triangles for lips! I'm getting 10 more fps!

New drivers optimized SLI so that it works so much more efficiently that my old OC is now running my cards too hard. Before SLI for a game wasn't really working so I OC'd the cards higher to get more performance. Scaling back my OC fixes the problem.

Whenever it is time to clean the dust bunnies out of my case. Any extra heat in my case causes my cards to display the Nvidia recovery message.


Now does that mean that I am trying to tell you'll that your problem can't be the Nvidia driver's fault? No, I am sure there is a reason that these are Beta and not Release quality. If they don't work for you then please report what problems that you are experiencing so that they can fix it in the future release.
 
I want to mention that I get the same recovery error when my videocards are:

OC'd too high and are at the point where they will begin artifacting but I didn't notice it before. Dude who cares my chick in WoW has purple triangles for lips! I'm getting 10 more fps!

New drivers optimized SLI so that it works so much more efficiently that my old OC is now running my cards too hard. Before SLI for a game wasn't really working so I OC'd the cards higher to get more performance. Scaling back my OC fixes the problem.

Whenever it is time to clean the dust bunnies out of my case. Any extra heat in my case causes my cards to display the Nvidia recovery message.


Now does that mean that I am trying to tell you'll that your problem can't be the Nvidia driver's fault? No, I am sure there is a reason that these are Beta and not Release quality. If they don't work for you then please report what problems that you are experiencing so that they can fix it in the future release.

It was working perfectly fine before I install the driver.

Once I do a clean install I will better be able to determine if I'm having problems with the driver or with my card.
 
Speedy.. and others..

maybe the power tip isn't your issue.. it certainly would be irrelevant to drivers anyways..

but it did resolve my "driver stopped responding" issues.. the trick though.. is to remember to turn off the psu as well.. I actually unplugged it.. and hit the power button.. which cleared any charge stored in capacitors as well...

whatever it is... it made a difference for me..

I had been thinking my Sea Sonic 750 wasn't enough.. that maybe I need to get a bigger PSU.. but I dont believe that to be the case at this point.. Im not running sli.. just a single MSI Arctic Frozr gtx580
 
Uninstalled the driver and steam cleanly then did a clean install and now everything seems to be working fine. Something in the driver didn't like steam or my prior driver.
 
Back
Top