Discussion in 'Videocards - NVIDIA GeForce Drivers Section' started by Cyris, Jun 26, 2015.
So far so good, Ive been playing Witcher 3 the whole day and not a single TDR nor game crash.
Why the maximum feature level I'm getting for dx12 is still 11.0 (in dxdiag) ?
Tried driver on gtx750ti.
Maxwell V1's (GTX 7xx series) aren't feature level 12.1 cards, they'll support dx12 but under feature level 11 ish (tier 2 compatibility).
As for maxwell V2's (GTX 9xx series) they do have tier 3 support however there's some issue with the 10130 build which causes them to only show up in dxdiag with a max feature level of 11.1.
Ah, so that's because of 10130, I was afraid it happens beacuse of egpu setup (I can observe same thing with 980 as well), thanks.
Hopefully now the boards can come back to analyzing performance in games, which seems to have taken a huge back seat to all the bugs.
Nice drivers allowed me to overclock my 970's a little further!!
1528MHz/4001MHz (no voltage increase)
Played 4 hours last night of Witcher 3 and about 2 hours of BF4 no issues at all.
Also I got this score in 3DMark Demo
The score could of been higher I forgot the change power profile in control panel to "high performance" so this was with it on "balanced".
Sorry--I don't think you understand the situation. Specifically, the GTX 980 Ti hasn't worked in Windows 10 (and I manually checked the 6 last releases in Windows 10 Build 10130 to be sure). The usual tricks, including adding a line in the installer's .INF, don't work. There have been a few threads on this subject to date, if you're interested in learning more. You'd think that the GTX 980 TI would work if the regular GTX 980 works, but that hasn't been the case.
Hence my question. As I said earlier, I'm afraid that everyone with a GTX 980 Ti has jumped back to Windows 7 or 8.1, and nobody wants to spend the time to wipe their system and try Windows 10 again without some assurance that this is not a waste of time.
So far its good.
I do have my 970 only on 1471/7400 but I'm not oc-ing card more then that anyways since it doesnt make noticable difference for me.
I'm currently running the Win10 64x 353.38 driver with the 980Ti, can guarantee you it works.
353.38 and 353.30 are working out of the box with 980Ti on Windows 10 (10130), while 347.88, 350.05 and 350.12 are working with a modded .inf.
I can't comment on 352.63 and 352.84 as they were already crap on my 680s SLI before upgrading to 980Ti so I didn't try to mod them at all.
BTW, for 353.38 and 353.30, only the Windows 10 version of the driver will work. 347.88/350.05/350.12 are Windows 7/8 drivers but are working on Windows 10, yet with - obviously - no DX12 support. No other Windows 7/8 driver will work on Windows 10 for the 980Ti, be it newer or older than 347.88/350.05 and 350.12 though.
Hope it helps.
Good, new drivers so I can test too if they are realy more stable than previous.
Though if I go to Nvidia site they are not in driver section. Good find from Cyris I suppose.
The hotfix drivers are usually posted on the GeForce forums.
Ok, my bad, I thought you were just looking for win10 driver link.
I don't know, but for sure they will give it support once it out.
Found a tiny bug in the new Win 10 non whql or hot fix 353.38 driver. noticed it while checking res on 2nd and 3rd monitor. Refresh rate doesn't display until you click native, then refresh rate displays. Then switching from 75 to 60 Hz and clicking apply, It does not save the change.
Display pixellation issues here. 980ti user.
Disabling hardware acceleration in Chrome/update - (and) Firefox causes it to happen.
Only happens at 1440p, doesn't affect 1080p.
With all drivers for the 980ti I've had this issue
I know I can just leave hardware acceleration on in the browser, but I need to know if there is a fault with the card as down the line if I need to sell it and if the damn things faulty.. :bang:
Fixed for me, no problems running chrome or MSI AB.
Ok, just had my first error ("Display driver has stopped responding"). Went to get coffee and came back w/screen saver on. Moved mouse to terminate screen saver and afterwards cursor froze on screen as I was going to click on icon. Nothing was open on screen when this happened. Error window appeared and recovered ...
So it's been about 18 hours w/o any error. Will keep these to see if there is any acceleration of error occurrance (happened with other v. 350+ drivers).
Managed to play all night with chrome open, HW Accel on, and even went back to a mild OC on my card without a crash. Hope it remains steady.
Nice! Downloading now!
I think chrome itself has some issues that needs to be addressed with hardware acceleration. Can do a search and find a bunch of people with the issue.