GeForce 456.55 WHQL driver download

#5836166

toyo

2020-09-28 17:41

MajorMagee:

Yes, just checked and it appears to be fixed in this release.

Thanks!

#5836170

garyb

2020-09-28 17:53

Scrolling on facebook then flashing webpage using Microsoft edge browser gives error (display driver nvlddmkm stopped responding and has successfully recovered) same issue with 456.38. No such problems with driver version 452.22.

#5836179

windrunnerxj

2020-09-28 18:12

Amaze:

Fixed Issues in this Release

Pretty underwhelming list of fixes, but at least the EventLog bug was fixed I guess. Not sure why nvtopps still has to be active every second on GPUs that don't support automatic tuning, that is assuming it's the only thing it's responsible for.

#5836182

V3RT3X79

2020-09-28 18:19

garyb:

Scrolling on facebook then flashing webpage using Microsoft edge browser gives error (display driver nvlddmkm stopped responding and has successfully recovered) same issue with 456.38. No such problems with driver version 252.22.

But..... who still use microsoft edge / explorer in 2020 ? mostly use chrome

#5836186

garyb

2020-09-28 18:27

V3RT3X79:

But..... who still use microsoft edge / explorer in 2020 ? mostly use chrome

New version.

#5836188

SpajdrEX

2020-09-28 18:29

Seems that a new driver helped alot of people with CTD with Ampere cards https://new.reddit.com/r/nvidia/comments/j1ccfq/game_ready_driver_45655_faqdiscussion/

#5836189

JamesSneed

2020-09-28 18:34

SpajdrEX:

Seems that a new driver helped alot of people with CTD with Ampere cards https://new.reddit.com/r/nvidia/comments/j1ccfq/game_ready_driver_45655_faqdiscussion/

@Hilbert Hagedoorn I do wonder if there is some performance regression with this CTD fix? It seems like you would want to lower boosts or add some levels of boosting to more slowly ramp up to reduce the large current demands. Anyhow I think its worth testing a couple games to see if there is a performance regression.

#5836193

Exostenza

2020-09-28 18:49

Is the DCH control panel more up to date than the standard control panel or do the version numbers not correspond to the same thing between the two? I have been using standard drivers but if the DCH control panel is more up to date then I would not have a problem moving to the DCH drivers. Thanks

#5836200

disq

2020-09-28 19:03

DCH Control Panel has version 8.1.958.0, dunno about Standard

#5836206

ManuelG

2020-09-28 19:35

Mbi2011:

Didn't fixes this issue for me - https://forums.guru3d.com/threads/nvidia-game-ready-driver-456-38-download-and-discussion.434248/page-4#post-5831564

We just fixed this issue. Fix should be in next driver.

#5836207

Party Poison

2020-09-28 19:35

V3RT3X79:

uh...Reflex for fortnite? why put that technologies in a little kid's game..... 🙄 🙄

Shit I can't stand fortnite, But to question why they added new tech to one of the biggest games on the planet just shows a purposeful ignorance and a shite attempt to be edgy.

#5836208

ManuelG

2020-09-28 19:35

PhazDelta:

i update my driver and i did not see any Nvidia Reflex in the game option what wrong ?

Call of Duty will require the game update. Then you can enable Reflex from the in game settings.

#5836209

Herochild

2020-09-28 19:36

Is the valve index HDCP error fixed? It’s not listed in the Known Issues anymore.

#5836215

Bomastus

2020-09-28 19:59

Anyone know if the Divinity Original Sin 2 issue with HAGS is fixed?

#5836217

Ojref

2020-09-28 20:06

Right back to Fallout 4 CTD's during game loading. Sigh.

#5836222

Cierpik182

2020-09-28 20:29

Reverting back to 446.14... those are the latest that work for me and don't have problems with HDR and madVR. During installation of both the 456.38 and 456.55 driver my monitor (Acer XV273K) loses signal from the GTX 1080 ("no signal"). The monitor is connected via 2 displayport cables for the 144Hz mode. Anybody heard about this problem or knows a solution? Would be grateful for any help... EDIT. I did use the latest DDU before installing any new drivers

#5836227

Im_Special

2020-09-28 20:41

ManuelG:

We just fixed this issue. Fix should be in next driver.

Any guess/idea for when that one is coming out? Like, in a week, two weeks, three+... I might just hold out for it then if it's sooner rather then later, to save me from constant drivers updating.

#5836233