GeForce 355.82 WHQL driver download

Videocards - NVIDIA GeForce Windows 10 | 11 671 Updated by Hilbert Hagedoorn

Click here to post a comment for GeForce 355.82 WHQL driver download on our message forum
#5151010
https://forums.guru3d.com/data/avatars/m/251/251394.jpg
Thought I'd post it. Open Issue- [355.82] Memory clock reported as 0 MHz if P-state is P0. At times, same report with P2 P-state. P0 state is the state while gaming. I'd ignore it if it was with some other P states. I always check if my overclocks are applied or not, multiple times. Damn OCD........
#5151188
https://forums.guru3d.com/data/avatars/m/242/242134.jpg
Lol. But thats the problem. Now that u have proof (that something is going on), its feeds the ocd... ;-) Not playing any of the games mentioned anyway, and since all previous probs i had with drivers/GFE are gone with 355.80 anyway....
#5151383
https://forums.guru3d.com/data/avatars/m/255/255012.jpg
This is weird: There's a 355.83 beta driver out too, but all it adds afaik is GameworksVR (for Oculus Rift) but it isn't available on Nvidia's driver page, only on the developer site (here)
#5151384
data/avatar/default/avatar29.webp
This is weird: There's a 355.83 beta driver out too, but all it adds afaik is GameworksVR (for Oculus Rift) but it isn't available on Nvidia's driver page, only on the developer site (here)
Because it's not a BETA driver, it's a developer driver.
#5151398
https://forums.guru3d.com/data/avatars/m/224/224796.jpg
My install on one of my laptops seemed to hang on "installing PhysX software" portion, but after killing it through Task Manager it seems to have installed everything and says it's using the new driver. Windows 10 and 980m of what it's worth.
#5151680
https://forums.guru3d.com/data/avatars/m/251/251394.jpg
I'm waiting for another "wonder driver" but I don't think that it's gonna come soon.
#5154270
data/avatar/default/avatar26.webp
Not sure wich of my games that does this, or even programs that use my GPU, but after using it, where i clocks up to just standard mhz on core and memory, it never goes below that, and my powerusage stays locked on a 45% instead of the 10-15% i normaly get when idling on desktop... Went back to 355.80 and it now idles as normal. Not sure if others have the same problem? (using a 780GTX and windows 10 home) Only noticed it because of my G510 display where i have msi afterburner show the clocks, powerusage ect.
#5154273
https://forums.guru3d.com/data/avatars/m/230/230424.jpg
Not sure wich of my games that does this, or even programs that use my GPU, but after using it, where i clocks up to just standard mhz on core and memory, it never goes below that, and my powerusage stays locked on a 45% instead of the 10-15% i normaly get when idling on desktop... Went back to 355.80 and it now idles as normal. Not sure if others have the same problem? (using a 780GTX and windows 10 home) Only noticed it because of my G510 display where i have msi afterburner show the clocks, powerusage ect.
Yep same issue. Been having this problem since 35x.xx. The only thing that fixes it is either luck that the clocks dont lock or a restart of the pc.
#5155709
https://forums.guru3d.com/data/avatars/m/263/263498.jpg
What's with all these driver issues lately? Before I always updated but I haven't done for a long time now.
#5155722
https://forums.guru3d.com/data/avatars/m/80/80129.jpg
What's with all these driver issues lately? Before I always updated but I haven't done for a long time now.
Nvidia's drivers under Windows 10 are just bad. I don't really get why either, they were pretty pro-active about getting drivers on the insider builds. People reported all kinds of issues and they were just never resolved (the SLI memory issue was apparent for nearly 6 months and it didn't get fixed until like 2 months after release).
#5155741
https://forums.guru3d.com/data/avatars/m/263/263498.jpg
Nvidia's drivers under Windows 10 are just bad. I don't really get why either, they were pretty pro-active about getting drivers on the insider builds. People reported all kinds of issues and they were just never resolved (the SLI memory issue was apparent for nearly 6 months and it didn't get fixed until like 2 months after release).
I'm still on 8.1, and wonder of the issues persist there as well?
#5155744
https://forums.guru3d.com/data/avatars/m/80/80129.jpg
I'm still on 8.1, and wonder of the issues persist there as well?
No idea. Honestly it's hard to gauge what issues that people are having that are caused by the driver itself, a configuration issue, or just user error, let alone across multiple OS's. All I know is that W10 seems to be an issue for Nvidia.
#5155838
https://forums.guru3d.com/data/avatars/m/263/263498.jpg
Good point, it's never as clear cut as that. Maybe I'll give it a go.
#5155885
https://forums.guru3d.com/data/avatars/m/206/206905.jpg
Been using 353.38, works flawlessly with everything so no need to change it.