Geforce 361.91 WHQL Download & Discussion

I don't load up Afterburner with games but my frame rate in Kessex Hills is 100-144fps atm all graphics maxed out 1440p. I don't use super sampling but everything else is on max.

 

Power meter seems to be broken with those drivers.

 

Well, I don't play it anymore, tbh. Just log in from time to time for some daily crap items, thinking that ONE DAY, I might return to Tyria.

But considering their obsolete renderer, this might never happen. Might be something on their side. People on GW2 forums are complaining about such performance drops since January.

 

Yeah, Afterburner's Power meter seems to be broken since like 2 driver release beside this one, sometimes it works fine but sometimes it gets stuck and reports the same usage all the time, in my case it shows 13% even when playing games.

also removing the Nvidia HD audio seems to have fixed my problems in Battlefield Bad company 2 where the GPU would drop to 0% usage for like 1 second

 

Just freezes and crashes on me today. All the sudden my screen got scrambled/pixellated. Check my video card and noticed the fan wasn't spinning so I have to force reboot the machine. Running on Evga GTX 950 sc. I don't know if my EVGA PrecisionX 16 crashed so my fan wasn't spinning but wasn't doing anything heavy that would have causes the card to overheat because the card have no problem at 70-80c even with the fan spinning during heavy gaming. Last time something like this happen when there was a blown capacitors on another card but the capacitors seems fine on this card.

 

I've found my second card fan not spinning after boot. Opening Precision and clicking on the "GPU select" prompts the fan to start.

 

That's not the issue. My Precision always startup and my video card fan kick in after booting into desktop. Have no clue what happen today. Hopefully it isn't hardware issue but software(s).

 

I tested Rise of the Tomb Raider in 3 different locations on the Geothermal Valley map.

Using MSI afterburner to monitor I was GPU limited in all areas.

361.75:
Area 1 - 58.8
Area 2 - 50.1
Area 3 - 65.4

361.91:
Area 1 - 58.5
Area 2 - 51.3
Area 3 - 64.2

All within margin of error really.

 

Driver behaves strangely. I also don't seem to be able to oc same clocks like 361.81

 

soo last drivers **** the monitor.. happen to me too i have a 970.. i guess my monitor lg ips 23ea53 was ****ed... this happen to me too :

- osd monitor stop working random.
-black screen and monitor stop working random.
-black screen when i alt+enter or alt+tab in a video game. and monitor stop working , i need shut down the monitor and on it again.

iam not the only getting this problem some one can help me?

i try all ... dont ask me if i change hdmi , driversweeper ddu , etc..

iam rolling back to 361.75.


thanks

 

Been using this driver since release, has been working great so far.

 

Noticed it here, happens when Windows desktop is loading Haven't had this pausing, since the single threaded CPU days! I'm going to clean install again I think and delete those new backend folders etc ummmmmm

 

I just upgraded to 980 TI (from AMD 290X) so this is the first NV driver I've used in ages.

I also noticed that when oc'ing you get an instant crash without artifacting etc. first and the clocks fluctuate pretty much (at first thought it was normal).

Were the older drivers better in this respect? Like the previous WHQL?

 

On my Nvidia machine It's has been happening for the last couple of drivers. Every time the monitor goes to sleep mouse icon disappears.I just go to task bar and open up the internet it comes back. Also shadowplay crashes a lot of games in uplay.

 

The clocks constantly changing is normal behavior of BOOST2.0 and is linked to the TDP, the only way to disable is by disabling it with a bios mod, for that you need to know your stable overclock and voltage.

 

So how does this driver perform on older cards (500-Series)?

I have a GTX560.

 

Yea reasonable variation is normal but as pointed out the behavior is pretty aggressive, even slight downtime causes a drop in clockspeed (potentially causing stuttering).
Based on mahanddeem's post this changed with the current driver.

 

Fine so far. Tested with Tom Clancy's The Division, BF 3-4, SW BF. Dying Light.

 

Please, can anyone upload AC Syndicate's profile from this driver ? (via Inspector)

 

http://www.mediafire.com/view/fs9c67dnyyqkbqq/acsynd.nip