GeForce 516.59 driverIt is the trouble information of. NVIDIA official known bugs and user reports noticed on overseas GeForce forums are translated. User reports do not occur in all environments and may be environment dependent. I hope it will be helpful for those who are suffering from similar problems.
NVIDIA Official: Known Bug (Release notes + forum)
-If the installation error “An unknown error has occurred” occurs when you try to install the 516.59 driver, install the 516.40 driver once, and then reinstall the 516.59 driver. 516.40 driverHereYou can download it from. ［New］
-When playing F1 22 in VR mode, the game may crash randomly. ［New］
・If HDR is enabled in the Windows display settings, the image may be overexposed when recording a DirectX 12 game with ShadowPlay.
-In an Ampere GPU (RTX 3000 series) environment, when connecting to an audio / video receiver via HDMI 2.1 and playing with Dolby Atmos, the sound may be interrupted.
-If you connect an HDMI 2.1 TV to the GeForce RTX 3000 series and the TV is turned off, the separately connected PC monitor may not wake up from sleep on the display.
-In an environment using non-native resolution, switching HDR on / off in the game will make the game unstable.
-In an environment where “NVIDIA Image Scaling” is enabled, the video played on Microsoft Edge may be displayed in green when returning from hibernation (hibernation) or booting with Fast boot.
-In an environment where DSR / DLDSR is enabled, the display may flicker temporarily following the monitor wakes up from sleep.
-Artifs may be displayed in Jurassic World Evolution 2 purchased from the Microsoft Store.
-In Prepar3D, a blinking black box is displayed in the light.
-In the MSI notebook PC “GE66 Raider 10UG” and “GE76 Raider 10UH” environment, the brightness setting of Windows does not work when used in dGPU mode.
-It may freeze randomly when Destiny 2 is running or playing.
User reporting bug
-The bug that has occurred before, “Oculus Rift S / Pimax Vision 8K X / HP Reverb G2 is not detected in GeForce RTX 3090 Ti environment” is not written in the fixed bug, it is a known bug. Not listed in. What happened?
・ ↑ The bug that VR headset does not work on RTX 3090 Ti has not been fixed yet.
・ The problem of flicker in the water of Assassin’s Creed Origins has not been fixed yet.
・NVIDIA: ↑ As a result of investigating this bug, it turned out to be a bug on the game side. We will contact the game developers.
-ASUS TUF Gaming F15 FX506HEB (RTX 3050 Ti) In a notebook PC environment, the GPU clock is always idle (210 to 307MHz). This bug started at 516.40 and continues at 516.59. The last driver to work properly was 512.95.
-Star Wars Battlefront II may become unresponsive for 516.40 and 516.59. If you roll back to 512.95, the game will work fine.[RTX 3070 Ti]
-I am using 3 monitors. Of these, if you try to use F1 22 on monitor 3, which is a clone of monitor 2 (main monitor), it will crash and the screen will be messed up as shown in the video below. Unclone works fine.
-Corsair iCUE no longer detects the GPU. (* This bug is516.40(It is generated from)
-I am using a Lenovo Legion 5 Pro notebook PC (RTX 3070 / Windows 11). The HDR color is wrong and the brightness slider does not work properly. After rolling back to 512.95, everything went back to normal.
・ BSoD and game crashes occur 2 to 5 minutes following 516.59 is installed.[RTX 2070]
・ After updating to 516.59, I can no longer use my PC. Ten seconds following opening the game, my PC went black and nothing worked. It was completely normal before the update.[RTX 2070 SUPER]
-Stutter will occur in Warzone following setting to 516.59.[RTX 3070]
-When updating to 516.40 or 516.59 in the Razer Blade 17 2022 (Core i7-12800H / RTX 3080 Ti) environment, the external monitor is not detected. It will be detected if you switch back to 512.95.
A new known bug has been added that causes the game to crash when playing F1 22 in VR mode. In addition, it has been reported that playing the game in a multi-monitor clone monitor environment causes a crash. Please be careful if you are playing.
Also, since 516.40, there have been multiple reports that something went wrong. It is said that it can be fixed by rolling back to 512.95, so if you are having trouble with similar problems512.95Try rolling back to.
