NVIDIA GeForce 301.24 Beta Drivers - Page 15

Axaion · 04-16-2012, 08:09 | posts: 28 | Location: moon

Quote:

Originally Posted by ice445

Nvidia inspector reports "Let the application decide" as "0" when that's not possible anymore. Nvidia removed the zero option.

My point exactly, which sucks :|

IcE · 04-16-2012, 08:27 | posts: 6,996 | Location: Toledo, Ohio

Quote:

Originally Posted by Axaion

My point exactly, which sucks :|

Not really, zero was never really intended to be used. Pick between 2 and three, that gives the smoothest experience at least in my testing.

Axaion · 04-16-2012, 08:36 | posts: 28 | Location: moon

Quote:

Originally Posted by ice445

Not really, zero was never really intended to be used. Pick between 2 and three, that gives the smoothest experience at least in my testing.

I have never ever had problem with setting it on 0.

Radical_53 · 04-16-2012, 08:39 | posts: 2,259 | Location: Germany

Quote:

Originally Posted by ice445

Not really, zero was never really intended to be used. Pick between 2 and three, that gives the smoothest experience at least in my testing.

And it adds a noticable input lag. I can still choose zero (couldn't do this with the previous .10 set also) and I usually pick 0 or 1, depending on the game. The faster it is the more I lean towards 0.

Axaion · 04-16-2012, 08:41 | posts: 28 | Location: moon

Quote:

Originally Posted by Radical_53

And it adds a noticable input lag. I can still choose zero (couldn't do this with the previous .10 set also) and I usually pick 0 or 1, depending on the game. The faster it is the more I lean towards 0.

now im just unsure if it was with this driver or the .10 set i couldent use 0.. im fairly sure its both though..

Radical_53 · 04-16-2012, 09:50 | posts: 2,259 | Location: Germany

It works for me on this set and the previous set (.10) had zero as its default value (couldn't choose it manually, Inspector reported default as zero though).

phawkins633 · **pink dots -** 04-16-2012, 16:10 | posts: 3

I have a 560ti..never overclocked...system not overclocked...296.10 and above have pink dot problem....that's pretty much it...it seems while Nvidia is striving to squeeze another 5% speed, it has cranked some cards just too high...I mean the last time I saw this was with the 8800gts 320 when everything from driver tweaks to baking in the oven were used to try and fix this....although driver related, it still smacks of being hap hazard....and on Nvidia's own forum they say they are having trouble replicating this problem...that's heard to believe considering the number of cases that are popping up all over the web...c'mon Nvidia...some of us still use older (non 6xxx) cards....

Wrigleyvillain · 04-16-2012, 18:23 | posts: 115 | Location: Chicago

My 480 loves these. BF3 and Skyrim, mainly.

BarryB · 04-17-2012, 00:28 | posts: 563

Still no go for me? It seems AA is causing the problems, tried BF3 and the same stuttering happens as in Skyrim, turn off AA and they're fine? Why?

PirateNeilsouth · 04-17-2012, 00:30 | posts: 1,613 | Location: Manchester

Quote:

Originally Posted by phawkins633

I have a 560ti..never overclocked...system not overclocked...296.10 and above have pink dot problem.

Yep it's happened to a few people!

Netherwind · 04-17-2012, 08:54 | posts: 441 | Location: Sweden

15 pages is a lot to go through

Would 680 owners say that this driver is an improvement over 301.10 or not?

Darren Hodgson · 04-17-2012, 08:57 | posts: 9,731 | Location: England

Quote:

Originally Posted by Netherwind

15 pages is a lot to go through

Would 680 owners say that this driver is an improvement over 301.10 or not?

I'd say it was exactly the same personally as is v301.25 which I'm using now. There are obviously fixes and tweaks between the different drivers but I haven't noticed them. In my experience, it always better to use the latest driver for that reason but if you're not having any problems with games and applications you're using then there's no reason to if you adopt a "if it ain't broke, don't fix it" policy.

RagDoll_Effect · 04-17-2012, 10:42 | posts: 3,923 | Location: Australia

Quote:

Originally Posted by phawkins633

I have a 560ti..never overclocked...system not overclocked...296.10 and above have pink dot problem....that's pretty much it...it seems while Nvidia is striving to squeeze another 5% speed, it has cranked some cards just too high...I mean the last time I saw this was with the 8800gts 320 when everything from driver tweaks to baking in the oven were used to try and fix this....although driver related, it still smacks of being hap hazard....and on Nvidia's own forum they say they are having trouble replicating this problem...that's heard to believe considering the number of cases that are popping up all over the web...c'mon Nvidia...some of us still use older (non 6xxx) cards....

It's happened to me pink screen dots, but with these drivers, it's fixed... Hope it fixes for you soon.

regards,
Ragdoll.

Sunnijim · 04-17-2012, 11:23 | posts: 1 | Location: South Africa

Ya these drivers gave me issues. They installed fine, and worked well at first. Then Skyrim became extremely jumpy, and unplayable. Restarted the game, and the loading screen was jumpy and the loading process wouldn't end. Tried BF3 and that was also jumpy. Restarting the computer didn't help. BF3 even went into what looked like an old school 3d mode (with red and green shading). So I rolled back to the previous driver : )

Netherwind · 04-17-2012, 12:01 | posts: 441 | Location: Sweden

Quote:

Originally Posted by Darren Hodgson

I'd say it was exactly the same personally as is v301.25 which I'm using now. There are obviously fixes and tweaks between the different drivers but I haven't noticed them. In my experience, it always better to use the latest driver for that reason but if you're not having any problems with games and applications you're using then there's no reason to if you adopt a "if it ain't broke, don't fix it" policy.

Thanks, I'll try 301.25 and see what happens. They usually say, don't fix it if it ain't broken but as you say it never hurts to have the latest drivers due to optimisations and the like.

Flakman · 04-17-2012, 15:11 | posts: 393

Been running these since release, I have zero issues with them. No more pink dots like I got with the 296.10.

Good drivers so far.

Mufflore · 04-17-2012, 18:25 | posts: 9,542 | Location: UK

Quote:

Originally Posted by Sunnijim

Ya these drivers gave me issues. They installed fine, and worked well at first. Then Skyrim became extremely jumpy, and unplayable. Restarted the game, and the loading screen was jumpy and the loading process wouldn't end. Tried BF3 and that was also jumpy. Restarting the computer didn't help. BF3 even went into what looked like an old school 3d mode (with red and green shading). So I rolled back to the previous driver : )

The fix is to untick "Enable sterescopic 3D".

Zybane · 04-17-2012, 23:13 | posts: 30

Anyone see this crash before:

I'm getting that in all games now. Pretty much have tried everything, set system overclock to default, removed precision X and ran GPU's at default, default NVIDIA control panel options, ran 4-way SLI, 1 GPU, Surround Mode, Single display mode, tried drivers: 301.10, 301.24, 301.25, PCI-E 2.0 mode, PCI-E 3.0 mode. They all crash. Wonder if those stupid multiple Direct X installs that Steam does every time a new game is installed screwed something up. Gah I don't feel like re-installing windows again.

PhazeDelta1 · 04-17-2012, 23:35 | posts: 9,343 | Location: 90° N

I got it a couple time. Try this, uninstall the drivers, then select clean install when you go to install them again. i havent seen that error since.

aayman_farzand · 04-18-2012, 00:40 | posts: 718

I've been using it since day one. Perfectly fine in BF3 and no driver crashes/downclock issues.

I did have some trouble getting the driver to install at first, the older one was not removed properly. But other than that everything has been smooth for me.

sapo_joe · *Last edited by sapo_joe; 04-19-2012 at 00:49.*

I noticed that when I leave the computer on for a long time (I almost don't restart it, as there are lots of downloads going on), it gets stuck at the 2D clock (50Mhz), and it gets back only if I restart the PC. This is very annoying, and is really making me miss my good old Radeon HD 5670...

BUT, I loved adaptive Vsync and FXAA, so, I'm eagerly waiting for the fixes... NVIDIA PLZ, HELP US!!!!!!

HolyLiaison · 04-18-2012, 06:50 | posts: 56 | Location: Minnesota

Quote:

Originally Posted by sapo_joe

I noticed that when I leave the computer on for a long time (I almost don't restart it, as there are lots of downloads going on), it gets stuck at the 2D clock (60Mhz), and it gets back only if I restart the PC. This is very annoying, and is really making me miss my good old Radeon HD 5670...

BUT, I loved adaptive Vsync and FXAA, so, I'm eagerly waiting for the fixes... NVIDIA PLZ, HELP US!!!!!!

Yeah this happens to me too. It's frustrating, but it's not so bad if you have an SSD boot drive.

angmar · 04-18-2012, 12:14 | posts: 1,025 | Location: Monmouth County, NJ

These drivers are hands down the worst drivers I have ever tried in recent memory. Been having a lot of issues with these including sever screen tearing assassins creed revalations and the gpu clock downclocking when I am not even getting stable fps. Switching back to 296.10...

nick0323 · *Last edited by nick0323; 04-18-2012 at 13:20.*

My GTX470 loves these driver to bits, played 5 hours of BF3 followed by 5 hours of Skyrim without a restart and there wasn't even a hint of a slow down, lag, jittering, stuttering etc. I applaud you nVidia.

This is the main reason I still run a GTX470 and haven't upgraded to the GTX6XX yet.

EDIT - Also to add I installed these over the top of the previous WHQL drivers using the Clean Install option. Never has installing a driver been so pleasantly easy.

sapo_joe · 04-18-2012, 13:46 | posts: 172 | Location: Brazil

For people like me, having the 2d/3d clock problems, I recommend getting the latest 295 family drivers here: http://www.station-drivers.com/page/...0forceware.htm

They're shown as 296.25 but are actually 296.39 (crazy french!).

Updated to them and the problem seems to be gone. Anyway, I miss FXAA...

(

edit:

Just tested it people. 296.39 is flawless, clocks work as expected (up in 3d, down in 2d), image quality is good, and performance is great! Now, I'm waiting until nvidia releases a driver fixing the clock issue. And I mean, that should be mentioned in the "driver fixes".