For : MANDATORY if you use MIG. The stability fix outweighs the 3% performance hit you will take in HPC sims. Looking Ahead: R560 Leaks Our exclusive CUDA driver release news pipeline continues. We have seen early staging branches of the R560 driver, which contains a flag called --kernel-mode-only . This suggests NVIDIA is preparing a driver that can run entirely in user space, bypassing the OS kernel entirely for AI workloads—a "micro-driver" to fight back against AMD’s ROCm and Intel’s SYCL.
Rewriting the scheduler explains the bloat: The new nvlddmkm.sys (Windows) and nvidia.ko (Linux) binaries are 18% larger than the previous version. This is not a maintenance patch; it is a foundation reboot. We obtained an internal draft of the full patch notes that NVIDIA chose to omit from the public release. Here are the most critical lines: "Fixed a race condition where cudaMalloc would return a null pointer if the system had been up for more than 49.7 days without a reboot on AMD Threadripper platforms." cuda driver release news exclusive
For who use CUDA for DLSS 3.5 Frame Gen: NO . This driver introduces a 2% overhead in the transfer engine that impacts frame pacing in Cyberpunk 2077 and Alan Wake 2. For : MANDATORY if you use MIG
This is a sleeper feature. The driver now handles split-world memory addressing where the Windows Kernel and the Linux Kernel argue over the same GPU memory. Stability has gone from "crash every hour" to "crash once a week." Speaking with a senior AI infrastructure engineer at a major cloud provider (who requested anonymity due to NDA), we learned that the R555 driver series was internally delayed by four months due to a "catastrophic" bug involving Multi-Instance GPU (MIG) partitioning. We have seen early staging branches of the