Nvidia GeForce 306.97 WHQL Download and Discussion

You dont have to, it should be enabled by default for IvyBridge, that's if your mobo supports pcie3.0 in bios.

 

i dont have ivi bridege mb
nvidia cp says gen 2 and gpuz says gen 3:bang:

 

... I said if you have a IvyBridge cpu it should work, that's if your mobo has a pcie3.0 option in bios.

And if gpu-z shows it it must be working. Good luck :nerd:

 

NVIDIA GeForce Kepler PCIe 3.0 mode-enabling patch for Sandy Bridge-E systems

http://www.techpowerup.com/download...nabling_patch_for_Sandy_Bridge-E_systems.html

Yes it works for me on Asus x79 WS, Gigabyte x79 ud7 + 3-way GTX 680 sli. All ports pci-e 3.0

 

it doesnt really matte pci 3.0 gives minimal boost over 2.0, games simply dont utilise it enough

http://www.hardocp.com/article/2012/07/18/pci_express_20_vs_30_gpu_gaming_performance_review/2

 

pebkac, they all work fine for us...

 

looking at his system [providing it is his current system], he is running a 200 series card... not a 600 series like yourself and many others in this thread.
unless you have tested this driver set using a 200 series card, then your comment is a tad bit condescending and irrelevant my friend.

 

Every time a new driver comes out you get the same few people that bitch about how they can't install it or how they always have the same problem.

I've been using Nvidia drivers for years and there have only ever been a few issues that I can attribute to the drivers. I think 90% of driver issues is with the hardware setup / PC / or user.

If he's had problem with every driver kit since 296.10, he's doing something wrong or it's time to wipe it and reformat the machine.

 

For some reason, with these and the last driver revision, I can't get triple buffering working with OpenGL games. Namely, the two I play are Doom 3 and Stranger's Wrath. Anyone else have a similar problem?

 

Guys, I've noticed that these last WHQL have worse IQ than previous versions, someone else has noticed?

 

Screenshots would be nice. I haven't noticed anything, I do set Texture Filter Quality to High Quality everytime I install a driver.

 

To follow-up on the problem I was having with getting triple-buffering to work in OpenGL, forcing anti-aliasing fixes it. Either in-game or through drivers.

 

Not always true. Hardware configs can flat out deny driver installs for weird reasons. His system being aged could honestly have something to do with it.

Everybody can format when a "problem" arises, but do people dare to use their heads first? Not very often.

 

Pics or it didn't happen.

 

Sorry folks, I already uninstalled the 306.97 and now I'm testing the 306.94.
Regarding the graphic quality, it was an impression I had.
I do not know, it seems that both games as the Windows desktop looked more opaque.
But again, it was just a perception I had ... maybe I'm wrong

 

Just had a BSOD while playing Borderlands 2. (Windows 7 x64)

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1042

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF8800F4456CC
BCP3: FFFFF8800209B4A8
BCP4: FFFFF8800209AD00
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\102112-6224-01.dmp
C:\Users\Ethan\AppData\Local\Temp\WER-9172-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

 

The drivers have had a bug regarding triple buffering for some time. It seems related to corrupt or invalid settings within profiles. Resetting the profile to defaults and reapplying triple buffering using NVCP usually fixed it for me in the past.

However, currently using 306.82 drivers, and having similar issues. Triple buffering combined with standard vsync in OpenGL acts like adaptive vsync. That is, when FPS is at 60, there is no tearing, but if FPS is lower than 60 then tearing occurs (confirmed in both Heaven and Rage). I double and triple checked that I actually applied standard vsync and not adaptive.

Update - A clean reinstall of the drivers remedied it for the time being, but it also wiped out my custom resolutions and refresh rates (somehow it's probably all related).

 

**** Just had a BSOD in Hitman Sniper Challenge on W7 x64 SP1, also IQ is not that good with these drivers especially in some games with AF enabled...

 

Screenshot it.

 

I report Assassin's Creed 1 is no longer working properly on Windows 8.
For a certainty, this and the last WHQL driver aren't good for it.

On DirectX9 it starts, but it has 3 seconds lock-ups everytime you kill someone.
On DirectX10 it doesn't start at all.

FXAA and any other kind of AA from the nVidia Control Panel don't work also. not even with nVidia Inspector.

Also, I never understood why the game disables in-game AA if you run the game in 1080p and higher.