Download GeForce 361.43 WHQL game ready driver

Published by

Click here to post a comment for Download GeForce 361.43 WHQL game ready driver on our message forum
#5209236
data/avatar/default/avatar09.webp
Significant bug fixes: · [GM20x] Clock speeds remain above idle at 144 Hz on desktop. · Lag in Star Wars Battlefront with SLI enabled after updating to driver 359.06. · Momentary loss of signal after scoring first goal in Rocket League · Game crashes on certain GeForce GTX 860M notebooks Fermi GPU Changes: As of Windows 10 November Update, Fermi GPUs now use WDDM 2.0 in single GPU configurations. For multi-GPU configurations, WDDM usage is as follows: · In non-SLI multi-GPU configurations, Fermi GPUs use WDDM 2.0. This includes configurations where a Fermi GPU is used with Kepler or Maxwell GPUs. · In SLI mode, Fermi GPUs still use WDDM 1.3.
#5209238
data/avatar/default/avatar24.webp
Significant bug fixes: · [GM20x] Clock speeds remain above idle at 144 Hz on desktop. · Lag in Star Wars Battlefront with SLI enabled after updating to driver 359.06. · Momentary loss of signal after scoring first goal in Rocket League · Game crashes on certain GeForce GTX 860M notebooks Fermi GPU Changes: As of Windows 10 November Update, Fermi GPUs now use WDDM 2.0 in single GPU configurations. For multi-GPU configurations, WDDM usage is as follows: · In non-SLI multi-GPU configurations, Fermi GPUs use WDDM 2.0. This includes configurations where a Fermi GPU is used with Kepler or Maxwell GPUs. · In SLI mode, Fermi GPUs still use WDDM 1.3.
one doubt, and hdmi 2.0 for gtx 400/500 is enable to using 4k 60 hz using RGB32 in modern monitor and tv? or conmtinues limited to 4k 30 hz using rgb32 and YCc4:2:0 for 4k 60 hz
#5209239
https://forums.guru3d.com/data/avatars/m/182/182067.jpg
· [GM20x] Clock speeds remain above idle at 144 Hz on desktop. That's brilliant that they fixed this, this been issue for ages. yay
#5209246
https://forums.guru3d.com/data/avatars/m/223/223076.jpg
nice! bad that new assaing creed is too short game
#5209247
https://forums.guru3d.com/data/avatars/m/231/231492.jpg
Downloading now and installing shortly. I will report back with my results or any problems.
#5209250
data/avatar/default/avatar07.webp
Fermi So that still doesn't mean DX12 support we just got the WDDM 2.0 support correct those aren't one and the same right.
#5209254
https://forums.guru3d.com/data/avatars/m/232/232207.jpg
branch: 361_40-4
#5209256
data/avatar/default/avatar22.webp
My GTX 970 is still going to 899mhz on 1440p at 144hz. Maybe it is because i have a dual monitor setup though.
#5209263
data/avatar/default/avatar17.webp
144Hz Idle certainly ain't fixed on dual-monitors and / or SLI. It idles at 595 CPU and 3505MHz mem.
#5209264
https://forums.guru3d.com/data/avatars/m/72/72891.jpg
144Hz Idle certainly ain't fixed on dual-monitors and / or SLI. It idles at 595 CPU and 3505MHz mem.
Nor single monitors, not fixed for me either.
#5209266
data/avatar/default/avatar04.webp
Fixes...in a nvidia driver? It must be Christmas 😀
#5209275
https://forums.guru3d.com/data/avatars/m/80/80129.jpg
I don't think they intend on dropping the frequency for multiple monitors. Fury X was doing that when it launched and people were running into corruption issues. Honestly they do probably set it too high, but it's probably to avoid edge cases where corruption can occur with certain setups.
Nor single monitors, not fixed for me either.
It was only fixed for GM20x setups. 980Ti is GM210.
#5209278
https://forums.guru3d.com/data/avatars/m/73/73070.jpg
Downloading now... Let's see how it treats this GTX760.
#5209281
https://forums.guru3d.com/data/avatars/m/38/38699.jpg
Still getting a dxgmms2.sys BSOD with these on Win 10 Pro TH2 with an error of dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+3a seems like quite a few folks over on the NVidia forums were reporting the same since TH2 dropped the only fix being to revert back to the 347.88 drivers which I really did not want to do. Was hoping that this new set would fix it although I do not know at this point if it's a NVidia or MS issue with DX. :bang:
#5209283
https://forums.guru3d.com/data/avatars/m/174/174022.jpg
So that still doesn't mean DX12 support we just got the WDDM 2.0 support correct those aren't one and the same right.
They are not the same but it makes no sense to support WDDM 2.0 and not support DX12. I'm pretty sure that Fermi's got DX12 FL11_0 support with these drivers. Interesting sidenote on SLI though.
It was only fixed for GM20x setups. 980Ti is GM210.
980Ti is GM200.
#5209287
https://forums.guru3d.com/data/avatars/m/80/80129.jpg
Still getting a dxgmms2.sys BSOD with these on Win 10 Pro TH2 with an error of dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+3a seems like quite a few folks over on the NVidia forums were reporting the same since TH2 dropped the only fix being to revert back to the 347.88 drivers which I really did not want to do. Was hoping that this new set would fix it although I do not know at this point if it's a NVidia or MS issue with DX. :bang:
I mean it's probably a combination of both, obviously Microsoft made a change and Nvidia hasn't updated it's driver for that change yet. Microsoft said that the first build of TH2 made a bunch of low level changes to OneCore, pretty obvious that it was going to break stuff.
980Ti is GM200.
Good point, I'm retarded. Sorry
#5209292
https://forums.guru3d.com/data/avatars/m/232/232207.jpg
They really need in 2016, at least due to pascal launch, to overhaul their drivers, like amd crimson drivers. I mean instant load when u right click and bring nvidia control panel, and instant apply when u change something. And the most important for me at least. FRAME CAP !!!! Damn nvidia put a damn frame cap in your drivers, pls !!! Then i dont need msi afterburner installed, my OC is a bios oc, not a software, so i use afterburner only for limiting the fps. And nvidia inspector doesnt work, it does not cap it how it should, and has only some presets...

Next Page