One user reporting it seems to work for them on a Ada GPU. So i guess its an issue (maybe) only on blackwell.
Edit: One more user reporting it works on 3060 Ti
One user reporting it seems to work for them on a Ada GPU. So i guess its an issue (maybe) only on blackwell.
Edit: One more user reporting it works on 3060 Ti
With the 595 driver, yes. The freezing does not seem to be affected by the proton version.
performance wise on 590 the proton version doesnt seem to impact much, iāve seen at least one other 50 series owner impacted by this. As far as playable goes i wouldnt say the game is particularly stable on 590 either.
On windows there seems to have been a specific fix for crashing on 595 for crimson desert.
This was my exact experience as well with 595 on RTX5090. Im sorry I canāt gather logs due to Denuvo lockouts, as I tried multiple protons. Freezes on the loading screen directly after pressing play or new game. RTX on or off no change.
With the 590 series and also 595.45.04 I am experiencing graphical corruption in the original 1998 Resident Evil 2 as sold on GOG.
The text in this game has some glitched pixels and foreground objects (objects you can walk behind) have outlines in the form of squares.
On RTX 4070 Super/RTX 5080:
For comparison on Ryzen Graphics:
Both my RTX 4070 Super (on 590) and RTX 5080 (590 series and 595.45.04) are affected by this. At first I thought it may be an issue with anisotropic filtering but none of the options in the launcher seem to change anything.
Switching over to the integrated Ryzen Graphics of my Ryzen 5 7600, the corruption disappears and the game plays completely fine however now menu graphics are a bit warped.
The original Resident Evil and Resident Evil 3 play completely fine.
My setup:
Ryzen 5 7600
RTX 4070 Super/RTX 5080/Ryzen Graphics
OS: Bazzite Nvidia open
no problems for me on hyprland, with minecraft 1.8.9, forge, and a few mods
My current setup:
Core Ultra 5 245K
RTX 5070
OS: openSUSE Tumbleweed
With the 590 series and also 595.45.04. Elden Ring, when I load a player, enters in infinite freeze in the loading screen (Steam with Proton 10.0-4) until I kill the game.
The only workaround I found to fix the issue (after a lot of tries) was do this 2 steps:
MANGOHUD=0 %command% in parameters of the game.GE Proton 8-32 and select it as forced compatibility.Before, with 580 series (in a i5 6600K, GTX 1070, openSUSE Tumbleweed) runs good with Proton 10.0-4.
I attached the log with Proton 10.0-4.
team-1245620.tar.gz (210,7 KB)
Super Jigsaw Puzzle: Generations donāt start in Steam with Proton 10.0-4 and driver 595.45.04. No workarounds found.
By the other hand, the game works if I install the Vulkan Beta driver 595.44.03.
I attached the log with driver 595.45.04
steam-1036950.tar.gz (24,3 KB)
Regards
After upgrading to 595 release Desktop Environment freezes after boot (cant open any app).
590 work fine.
Hardware Information:
Software Information:
nvidia-bug-report.log.gz (503.4 KB)
Tracking this issue under Nvidia bug ID 6012396.
Upon next unlocking, please try the 580.142 driver, it seems to work okay with this game. Unfortunate that 590 seems to have performance regressions and 595 hard locks upon reaching the end of shader compilation.
@abchauhan
Sorry for forgetting attach the bug report done by āsudo nvidia-bug-report.sh --extra-system-dataā
Here it is, hope the brightness control problem could be solved :D
Also, other logs are also appended, hope they may help fix the bug.
Best Regard and keep healthy š
nvidia-bug-report.log.gz (1.9 MB)
nvidia-smi.log (1.6 KB)
dmesg.log (119.0 KB)
journalctl-boot.log (618.3 KB)
New Driver dropped Driver Details | NVIDIA ```Highlights since R595 Beta Release, 595.45.04
Fixed a regression introduced in the 580.119.02 driver release which caused some X11 compositors (e.g. picom, Xfwm) to blink:
https://github.com/NVIDIA/open-gpu-kernel-modules/issues/986
https://github.com/yshui/picom/issues/1488Fixed a bug that would prevent kwin_wayland from being able to wake up display under certain scenarios.
https://forums.developer.nvidia.com/t/bug-external-monitor-fails-to-wake-up-from-powersave-mode-if-refresh-rate-is-higher-than-30hz/316612Fixed a bug that causes a kernel crash when display docks or other DisplayPort MST configurations are disconnected from the GPU.
https://forums.developer.nvidia.com/t/kernel-null-pointer-dereference-in-nvidia-modeset-during-thunderbolt-dock-disconnect/359280Fixed a bug that caused kernel panics on Linux kernels configured with CONFIG_RANDSTRUCT_FULL or CONFIG_RANDSTRUCT_PERFORMANCE:
https://github.com/NVIDIA/open-gpu-kernel-modules/issues/1033Improved support for falling back to system memory when available video memory is low, to help prevent Wayland desktop freezes.
Fixed a bug that caused nvidia-drm to report errors in the system log and fail to enumerate connectors on some DisplayPort MST configurations.
Fixed a bug that could cause a kernel crash on driver initialization on some DisplayPort MST configurations.
Fixed a regression introduced in the 575.xx driver series which prevented EGL-X11 applications from starting on SLI Mosaic.
Fixed a bug that could cause flickering in VRR on some HDMI displays.
Fixed a regression, introduced after the 470.xx release series, that could cause four 4k monitors, driven as separate X11 X screens on one GPU, to fail modeset.
Fixed kernel module build issue with Linux kernel v6.19.
Fixed a bug that could cause an Xid error to be reported in the system log, along with a VK_DEVICE_LOST API error, when repeatedly resizing Vulkan application windows.```
Incursion Red River has an black screen issue with 595.58.03
didnt happen on 590
nvidia-bug-report.log.gz (823.0 KB)
EDIT:
with PROTON_VKD3D_HEAP=1 game works
Forever Winter locks up immediately upon shooting any drone enemy. This only happens if the game thinks you have an Nvidia GPU and can be worked around with PROTON_HIDE_NVIDIA_GPU=1.
Systemd Journal shows the previously reported xid109 as previously reported here Xid109 CTX SWITCH TIMEOUT Driver Crashes In Many Applications
Update to Bug #5958747 on 595.58.03 drivers
Age of Empires II: Definitive Edition
- RTX 5080 (PC): The game initially launches normally, and the video intro plays. However, at the moment the main menu should appear, I am left with a black screen.
- RTX 4080 (Laptop): The behavior is identical in dGPU mode.> * Note: Interestingly, in Hybrid (Intel + NVIDIA RTX 4080) laptop mode, the game menu displays normally and consistently, despite the game correctly utilizing the dGPU.
Itās always the same error after black screen appearerr: Presenter: Failed to create Vulkan swapchain: VK_ERROR_INITIALIZATION_FAILED
Itās fixed.
Indiana Jones and the Great Circle
- RTX 5080 (PC): The game rarely launches successfully. I managed to get it running in āSafe Modeā with default graphics settings. However, after changing the resolution to my monitorās native 3440x1440 and restarting, it failed to launch again. While the taskbar shows the game is running and audio is audible, visually there is only a small flickering square in the top-left corner of the screen.
- RTX 4080 (Laptop): I was unable to consistently reproduce this issue on the laptop; with one exception where it behaved identically to the PC, the game generally works normally.
On both the RTX 5080 PC and RTX 4080 Mobile, HDR cannot be enabled in Indiana Jones. I receive the message: āHDR mode is not supported by hardware.ā This worked previously 15 minutes before on version 590.44.01 on my laptop.
HDR continues to work correctly in other tested titles, including Red Dead Redemption 2, Cyberpunk 2077, and The Witcher 3.
Still broken.
nvidia-bug-report.log.gz (755.9 KB)
steam-813780.log (2.6 MB)
Crimson Desert is also still broken on 50 series cards, though that wasnāt reported to be fixed.
nvidia-bug-report.log.gz (754.7 KB)
steam-3321460.zip (7.1 MB)
The issue re: building the DKMS on kernel 6.19+ still persists with the new 595.58.03 driver release, as described in this issue: Objtool: 'naked' return found in MITIGATION_RETHUNK build with pre-compiled blobs on kernel 6.19
You recently tracked this as Bug #4452776
The v595.58.03 driver is catastrophic !
The exploding meshes bug (5649065) got only worst, making this driver totally unusable to render with native Open GL !
Here is a short video demonstrating the bug: ExplodingMeshes-NVIDIA-595.58.03.mkv
And here is the bug report log:
nvidia-bug-report.log.gz (335.3 KB)
Unsure if related to 5649065 but Iāve been experiencing similar mesh corruption in Substance Painter since driver 580 and ongoing where the mesh disappears or corrupts while painting it