NVIDIA GeForce 301.40

[applejack]

Originally Posted by Firestorm

Enhancing does nothing for the gamr either. We need a proper AA flag and there isnt one yet.

there is a proper AA flag (0x004412C1), works good for both TrSSAA and SGSSAA.
you also have to set "Antialiasing Behavior Flags: None" for it to work.

Check this thread for some screenshot comparisons.

[The General]

Haven't played any other games but APB Reloaded. I am getting amazing performance with them, everything is so much smoother, no Stuttering anymore like i was getting with the rest of the drivers. Hope the rest of the games work well, going to be testing out Crysis 2, BF3 and Syndicate later.

[mikeysg]

I've installed this driver into my AMD rig with a GTX670 + GTX560 Ti (PhysX) and I like what I see, particularly that the GTX560 Ti is recognized now and I've enabled it for PhysX. Odd thing though, my framerate for Metro 2033 and Hard Reset drop by about 1fps each but I'm not bothered by it, so far, it seems to be stable and I've had no graphic glitch or texture corruption of any kind.

[Amigafan35]

Has anyone else had the red screen issue with these drivers, only had it once with this set, happened once with the previous driver I was using, I've just done a quick search on google & I see this red screen issue is rather common with the gtx 680! Driver issue?

[evgenim]

Fix problem with clocks is simple, just use Nvidia PowerMizer. Turn off all power save options and get stock clocks.

[PsyChoFOk]

Hey Guys, I also Loaded these and am happy, but earlier today for some reason running F@H or new Photoshop CS6 64bit driver restarts and sometimes even BSOD. anybody else experiencing this? and whats the best way to keep my profiles and do a clean install of these drivers Windows 7 64 bit?

Thanks in advance.

Almost forgot. getting about a 3Mhz throttle on the clocks? anyone else see this bug? my card is pre overclocked to 800Mhz 1600Mhz and 2000Mhz but all programs tell me it's 797Mhz 1597Mhz and 1997Mhz.

[dchalf10]

I have the stuttering bug too.

Playing games it varies between 54 and 60 frames almost constantly.

I thought something was wrong until I read about the vsync problem.

Boost clocks don't work properly in all games either. In Fallout 3 they drop down to 715mhz which causes it to go below 60 frames, but when it does work in fallout 3 the frame rates are 60 constant.

[aayman_farzand]

NVIDIA Responds to Reports of Kepler V-Sync Stuttering Issue

Over the past month, users of NVIDIA GeForce Kepler-based graphics cards have been reporting intermittent stuttering in games, with v-sync enabled. A fairly long thread on NVIDIA forums formed the rally point of users noticing the issue, although the issues weren't universally reproduceable. Tom's Hardware sought a statement from NVIDIA on the issue. In its statement, NVIDIA said that it is looking into the issue, extensive testing has to be done, and that gamers noticing the issue should force v-sync to stay disabled via NVIDIA Control Panel.

We have received reports of an intermittent v-sync stuttering issue from some of our customers. We’ve root caused the issue to a driver bug and identified a fix for it. The fix requires extensive testing though, and will not be available until our next major driver release targeted for June (post-R300). For users experiencing this issue, the interim workaround is to disable v-sync via the Nvidia Control Panel or in-game graphics settings menu.

[PowerK]

Currently using two GTX 690 in Quad-SLI with v301.40 driver.

To force AA through nVIDIA driver for Diablo III, I disabled in-game FXAA.
Then, I used nVIDIA Inspector with compatibility flag = 0x004412C1 as described in this post.
http://forums.guru3d.com/showpost.ph...2&postcount=25

When 690 Quad-SLI is enabled (4-GPU Alternate frame rendering 2), while playing Diablo III, I get random 'display driver stopped responding error' and my PC would hard lock on me.. making me to hard reset the system.

If I disable Quad-SLI and stick with Single GPU performance mode, the forced anti-aliasing with the above compatibility flag in nvidia inspector works fine without any stability issues.

If I don't use the nvidia inspector, and stick with default settings of ForceWare v301.40, (with Quad-SLI enabled by default) no problem. (but I have to bear blurry FXAA of Diablo III)

[GhostXL]

I know I have HD 7970's but I'd like to chime in on some things about TERA.

Guys your issues isn't your card or drivers in this case. It's the game. AMD is having no better luck in the FPS department. If you play at 1080p with 8xMSAA you should be just fine.

Higher resolutions will prove to be difficult to obtain that 60 FPS mark. Even with HD 7970 Crossfire, it's having issues. They say SLI/Crossfire isn't supported in TERA, which is true to an extent, but I get a better minimum FPS with crossfire enabled.

Congested towns and Velkia I too can dip to mid 30's and sometimes high 20's on A Crossfire setup, or Single card.

[Darren Hodgson]

Originally Posted by dchalf10

Boost clocks don't work properly in all games either. In Fallout 3 they drop down to 715mhz which causes it to go below 60 frames, but when it does work in fallout 3 the frame rates are 60 constant.

That's because the game engine Fallout 3 uses is comparatively old and less demanding. The GTX 6x0 cards are designed to maximise performance while being efficient power wise. So it downclocks the GPU when v-sync is enabled because it can still run the game at 60 fps. I saw the exact same behaviour in Skyrim yet the game ran at 60 fps at all times.

The solution is to either force v-sync off (so the game will run as fast as it can) or, if you prefer v-sync, set the game profile's Performance to "Prefer maximum performance" or set that in the Global profile (which is what I've done to prevent these sub-1,006 MHz drops on my GTX 680s).

[Radical_53]

Instead of vsync the framerate limiter does a pretty nice job. The gpu clocks up and down according to load but the framerate will stay right where you set it to.

[Darren Hodgson]

How come only EVGA Precision X has the framerate target option and not MSI Afterburner v2.2.1?

[dchalf10]

Originally Posted by Darren Hodgson

That's because the game engine Fallout 3 uses is comparatively old and less demanding. The GTX 6x0 cards are designed to maximise performance while being efficient power wise. So it downclocks the GPU when v-sync is enabled because it can still run the game at 60 fps. I saw the exact same behaviour in Skyrim yet the game ran at 60 fps at all times.

The solution is to either force v-sync off (so the game will run as fast as it can) or, if you prefer v-sync, set the game profile's Performance to "Prefer maximum performance" or set that in the Global profile (which is what I've done to prevent these sub-1,006 MHz drops on my GTX 680s).

Cheers, I'll try setting it to maximum performance.

The problem wasn't that it was downclocking though. The problem was that it was downclocking so far that the frames would go below 60.

The game was using only like 20% GPU usage and it even dropped into 2D clocks ( likely as a result of the small load ).

Other times it would drop down to 600-715 and most of the time it would run at 60 frames even at these low clocks, but sometimes the frames would dip and the boost clock would not compensate.

I think Nvidia said they are fixing the boost clock so it refreshes clocks more frequently, hopefully this will fix it.

[Darren Hodgson]

@ dchalf10 - Personally, I prefer to set maximum performance in the Global profile to avoid the kind of behaviour you're seeing. The card will still clock down to 2D speeds on the desktop but as soon as any game is launched it'll ramp up to 3D speeds and stay there until you quit the game. That is far more preferable for games in my experience than having the clocks dropping down for an FMV cutscene or loading screen then ramping up again when the game starts. Sure, it wastes more power but not so much that you're ever going to notice.