Nvidia GeForce Game ready 359.06 WHQL Driver Download & Discussion

Wasn't there a hardware acceleration issue with Chrome that caused issues? No clue if it was fixed, but when I disabled hardware acceleration within Chrome my issues disappeared. Was several months ago and I'm forgetful, can't exactly recall if TDRs upon opening Chrome was the symptom. Check that feature and give it a try, can't hurt.

 

I remember back in the day when you couldn't do 3d or regular 3 monitor surround with 4 way sli. I actually had 4 way sli on a gigabyte x58-ud9 mb with 4 gtx 480's powered by a silverstone strider 1500 watt. That's when the money was there. As for "single sli" for just cause 3. I have a couple of comments on that.

One, what a waste of coding
Two, why to number 1? Because it's a slap in the face to sli owners. Now you can enable two or more cards and turn on sli and NOT use it for anything but it's turned on sli users for you to play single card just cause 3. NVIDIA, next time when a company makes a non mutli-gpu game (at least for now until just cause 3 is patched with hopefully multigpu ability) don't waste your time on putting sugar on the sh*t.

 

I've switched cards around, the default voltage was always tied to the card, not to the pci e slot.

 

Yep, that really was a slimy, disingenuous move.

 

@ Darren Hodgson ,, i've been following your posts about the TDRs that are plaguing you ,
I know its a pain in the ass but why not try i fresh install of windows 8.1 and see if you still have the same issues , if not then you know for 100% that your hardware is functioning correctly and it all comes down to windows 10 / drivers and your particular system .
Just for peace of mind

 

Nvm..

 

I don't have just cause 3,

but for those wanting SLI I was wondering if anyone tried this:

in nvidia inspector delete the just cause profile.
launch game
in right click nvidia 3d settings add profile back from "recent apps"


go back in nvidia inspector and:

set comp bits to 0000000003
set dx comp bits to 0000000003 as well

set (in hidden) the multi chip option to 0000000002

set frame rate to max available

set GPU to use default from auto to #of GPU you have
set DX GPU to #GPU you have set al values to AFR2

set sli profile override to AFR2


see if that forces/enables your sli and look for anomalies.

If you have flashing textures or strobing change AFR2 to AFR on all settings

If you have shadow flicker and light flicker only when moving, then change the comp pat bits on both lines from 0000003 to 0000002


Try it out and see

 

Display driver stopped responding and has recovered. Every time playing Tom Clancy's Rainbow Six Siege with SLI 780 Ti Enabled, ffs. Win 10.

edit: i'm not alone https://forums.geforce.com/default/...-display-driver-feedback-thread-12-01-15-/15/ :bang:

 

win10...lol. Some people love to suffer. We should split driver threads into two; win7/8 and win10.

 

have you tried using debub mode nvidia drivers? it put all cards back to nvidia defualt speeds? if so did it do same things. and I pretty sure i asked before on your other thread but to do older drivers do this/>

 

This sounds like a driver issue to me.
Try something older like 355.80 or 355.82 and report back.

Must say I haven't experienced any such issues with the latest build of Win 10 Pro myself.
And this is with a heavy factory overclock on my Zotac's (25% above reference 980 Ti).

 

battlefront framerate drops to 23 with sli, with 359.00 no problems, im using the sli profile from .06 in .00 and is working fine.

 

Idk why, but this "Debug mode" is always enabled for me no matter the driver i install i can't disable/enable it.

 

maybe ur card not support. i'm the rare user who using leadtek got debug mode working perfectly.

 

:< 780 Ti don't support debug mode. Great. :banana:
If it don't support, why is it always enabled ahaha

 

Debug mode is only meant for troubleshooting factory overclocked cards.
If you are not having any issues, I wouldn't mess around with it.

 

any performance improvements in Arkham Knight with these drivers?

 

Oddly enough, I've reduced my GPU's overclock and still get crashed since I updated to 359 branch, same with bot .00 and .06 (didn't bother with .12).

Even more annoying, with a revert back to 358.91 Shadow of Mordor does still crash, but takes far longer. Can't be the temperatures though, everything stays below 50°C on the GPUs and 5 on the CPU. I've further reduced my memory overclock (I suspect one of my cards has 'bad' vram, overclock was at 3805, now I went back to 375).

Anybody else experiencing similar behaviour?

 

No crashes here. Even the D beta works, albeit a bit laggy with much fps drops. I'm finding it harder to find stuff that doesn't work with the last few drivers.

 

Yes new drivers reduce gpu oc as you see when I got my card I easy oc it to1500 now it's 1460 and no memory oc for me I don't see any benefits

Whats yours gpu clock now?