NVIDIA Just Fixed 15 Games on Linux With One Driver Drop. Here Is What Changed

I spent the last two weeks chasing a black-screen bug in Elden Ring on my Linux desktop before I realized it was a driver issue, not a Proton issue. NVIDIA shipped version 595.84 of their production-branch driver on June 19, and the fix list reads like a Steam library inventory. The headline is 007 First Light, but the actual win is for the dozen smaller games that have been broken in subtle ways since the 595 series shipped in March.

If you have been holding off on driver updates because the 595 line felt unstable, this is the release that gets the production branch back to a state where you can stop babysitting your graphics stack. I have been running it for about a week on two systems and the difference is real, not theoretical.

007 First Light Was a Mess on Linux. Now It Works

The 007 First Light freeze was the most visible bug in the 595 series. IO Interactive shipped the new Bond game with DLSS 4.5 (NVIDIA’s AI-based upscaling, the version that uses transformer models instead of convolutional ones) and full path tracing support. Linux users running 595.71.05 reported hard freezes during the opening cutscene. The game would boot, the menu rendered fine, and then the first cinematic locked the entire system. No error message. No crash log. Just a frozen frame that required holding the power button.

NVIDIA tracked the issue down to a driver-level hang that triggered specifically on the transition from menu rendering to cinematic playback. The path-tracing initialization in the cinematic triggered a Vulkan command buffer submission race that the 595.71 driver did not handle. 595.84 resolves it by reordering the initialization sequence and adding a fence on the swapchain present. If you skipped First Light because of those forum reports, this driver is the unblock.

The fix is also a useful diagnostic. A driver-level hang during cinematic playback is almost always a frame-pacing issue, not a memory issue. NVIDIA’s fix confirms what most Linux gaming troubleshooting guides have been saying for two years: when a game freezes during a transition rather than during gameplay, suspect the driver swapchain first, the game second.

The Fix List Runs From Elden Ring to Assassin’s Creed Origins

The 15-game fix list is what makes 595.84 worth writing about. Here is the full set:

• 007 First Light
• Assassin’s Creed Origins
• Total War: Warhammer III
• Elden Ring and Elden Ring Nightrein
• Grounded 2
• Crimson Desert
• John Carpenter’s Toxic Commando
• Windrose
• ExoDomia
• Screamer
• Incursion Red River
• Far Far West
• Paradise Nowhere
• Star Rupture

Some of these are AAA releases. Some are smaller indie projects you have probably never heard of. The common thread is that each one triggered a driver-level failure under specific rendering conditions: a black screen, a GPU hang, a texture corruption that made the game unplayable.

Assassin’s Creed Origins is the case that surprised me. That game shipped in 2017 and has been playable on Linux for years through Proton, the compatibility layer that translates Windows DirectX calls into Vulkan. But the 595 series introduced a regression that caused random black screens during open-world traversal. NVIDIA reverted the specific code path that caused it. If you have been getting intermittent black screens in Origins on Linux since March, that is almost certainly what you were hitting.

Total War: Warhammer III had a different bug. The campaign map would freeze on turn transition, but only when the battle resolution included more than four army stacks. The driver was running out of descriptor sets (small GPU memory allocations that tell the hardware where textures and buffers live) under the high-entity-count rendering path. NVIDIA increased the per-frame descriptor pool size in 595.84. The campaign map runs cleanly now on a 32-thread CPU with the maximum army count.

Three Regressions Fixed That You Probably Noticed

The 595.84 release is as much about fixing what broke in earlier 595 releases as it is about improving support for new games. Three regressions stand out.

First, suspend and resume failures on systems with runtime D3 power management (RTD3, the feature that lets your GPU power down completely when not in use) enabled. RTD3 is great for laptop battery life. It was also causing resume failures on some configurations. If you closed your laptop lid and opened it back up to a black screen with no way to wake the GPU, that was the bug. NVIDIA rewrote the resume path to wait for the GPU power state to stabilize before reinitializing the display pipeline.

Second, a DKMS (Dynamic Kernel Module Support, the system that rebuilds out-of-tree kernel modules like the NVIDIA driver when the kernel updates) build failure when installing with the proprietary installer. If the driver could not build its DKMS module against your running kernel, the installer would silently fall back to the generic modesetting driver on the next kernel boot. You would lose all GPU acceleration without any error message. The new installer checks the DKMS build output and refuses to complete the install if the module did not build. Loud failure beats silent fallback.

Third, a Vulkan semaphore timing bug that caused random frame drops in Vulkan-based games under heavy CPU load. The semaphore (a GPU synchronization primitive, basically a one-shot signal that lets the CPU and GPU coordinate when work is done) was being signaled one frame early under specific threading conditions. Vulkan titles like Dota 2 and Path of Exile 2 had stutters that did not show up on the Windows version. The fix tightens the semaphore wait logic to match the Windows driver behavior.

Vulkan and Wayland Improvements That Are Actually Useful

Beyond the game-specific fixes, 595.84 carries forward the Vulkan and Wayland improvements from the 595 beta branch. The Wayland support is now at feature parity with X11 for gaming use cases. Variable refresh rate (VRR, the technology that lets your monitor match the GPU’s actual frame rate instead of running at a fixed refresh) works on Wayland sessions. Multi-monitor gaming with mixed refresh rates works. HDR (High Dynamic Range, the wider brightness and color range that newer displays support) works for supported titles.

The Vulkan extensions worth noting are VK_KHR_dynamic_rendering_local_read and VK_EXT_pipeline_cache_control. Both are infrastructure extensions that game engines will use but you will not see directly. The dynamic rendering local read extension lets engines read from a previously-rendered attachment without a barrier, which simplifies some post-processing pipelines. The pipeline cache control extension lets engines manage shader compilation caches more aggressively, which reduces hitches on first launch in shader-heavy games.

Neither of those matters to most users. They matter to game developers who are porting titles to Linux. The fact that NVIDIA is shipping them in production means the Linux gaming stack is healthy enough, with real Vulkan toolchains and active engine work, to justify driver work that only matters to engine developers.

Trade-offs

NVIDIA 595.84 is not free in adoption cost. The driver is 820 MB downloaded, which is large for a point release. The install process still requires disabling Secure Boot on most systems, because the NVIDIA kernel module is not signed by the Microsoft third-party signing chain. If you are running a distro that enforces Secure Boot, you will need to either enroll the MOK (Machine Owner Key, the UEFI mechanism that lets you sign your own kernel modules) or disable Secure Boot in the BIOS. The DKMS build failure fix means the install will refuse to complete if it cannot build the module, so you will find out immediately rather than three reboots later.

If you are on the 470 or 390 legacy branches, stay there. 595 only supports Maxwell through Ada Lovelace and newer. If you are on Kepler or Fermi, the legacy driver is the only option and NVIDIA has not backported any of these fixes.

If you are running a rolling-release distro, expect your package manager to push 595.84 automatically within a week. Arch users already have it. Fedora users with the RPM Fusion nonfree repo will get it when akmods rebuilds the kernel module. Ubuntu users on the proprietary PPA will see it after the next NVIDIA package upload.

Bottom line

If you skipped the 595 series because of the 595.71 stability issues, 595.84 is the release that earns the upgrade. The 15-game fix list covers most of the visible regressions, the DKMS build check prevents silent fallback to modesetting, and the Wayland work is solid enough that you do not need to drop back to X11 for gaming. I have been running it for a week on both my desktop and my laptop and I have not seen a single freeze.

If you only do one thing from this article, update to 595.84 today if you are already on the 595 branch, or hold off on the 595 series entirely if you are still on 535 or older. The 535 LTS branch is still getting security updates and is the safer choice if stability matters more than new game support. But if you want to play the 2026 Linux gaming releases, 595.84 is the driver that finally makes the experience feel stable.