Since the new nvidia Drivers (596.xx and newer) there are some issues when you click ingame, vibranceGUI hogs one entire core and leads to massive Frametime spikes.
There is no problem with drivers up to:
591.67
The problem is with:
596.36 and 596.49
610.47
Summary
VibranceGUI causes frametime spikes on every single mouse click when running NVIDIA drivers from the R595 branch onwards (596.36, 596.49, and 610.47). The issue does not occur with older drivers (577.00, 591.67).
Steps to reproduce
- Install any NVIDIA driver from the R595 branch or newer (596.36+)
- Run VibranceGUI in the background with custom settings for PUBG: BATTLEGROUNDS
- Launch any game with custom settings (confirmed in PUBG: BATTLEGROUNDS)
- Click any mouse button — in-game or in menus
Expected behavior
No frametime impact from mouse input.
Actual behavior
Every mouse click produces a visible frametime spike. The spike occurs consistently, both in-game and in the main menu, regardless of what is happening on screen. The issue is not related to rendering load.
Affected driver versions
- ❌ 596.36 — affected
- ❌ 596.49 — affected
- ❌ 610.47 — affected
Working driver versions
- ✅ 577.00 — no issue
- ✅ 591.67 — no issue
Isolation / root cause
After extensive troubleshooting (ruling out VSync, FreeSync, Frame Generation, NVIDIA Reflex, frame limiter, clean driver installs via NVCleaninstall), disabling VibranceGUI completely eliminated the frametime spikes. The issue is reproducible and consistent.
The likely cause is a change in how the NVIDIA R595 branch handles NVAPI calls or its driver event/interrupt pipeline. VibranceGUI hooks into the NVAPI Digital Vibrance Control, and it appears that driver-level changes in R595+ cause this hook to introduce latency on mouse input events, manifesting as DPC-level frametime spikes.
System
| Component | Details |
- CPU: AMD Ryzen 9 5950X -> EKWB Quantum Velocity
- Mainboard: MSI MPG X570S Carbon EK X
- Ram: Crucial Ballistix Sport @ 3600 cl16
- GPU: Nvidia RTX 4090 FE -> Alphacool Core FE
- PSU: be quiet! Straight Power 11 1000W
- NVME 1: Samsung 970 EVO Plus 500 GB (OS)
- NVME 2: Samsung 970 EVO Plus 250 GB
- SSD 1: Crucial MX 200 1 TB
- SSD 2: Samsung 860 Evo 2 TB
- SSD 3: Intel 540 120 GB
- Optical: LG BH10LS30 Blu-Ray writer
- Case: Fractal Design Define XL R2
- OS: Microsoft Windows 11 Pro (25h2)
- Monitor 1: Gigabyte M32U
- Monitor 2: Dell P3223QE
- Monitor 3: BenQ EW3270
- Keyboard: Wooting 80HE
- Mouse: Pulsar X2 Mini Wireless
Additional notes
The R595 branch introduced significant changes to the driver presentation pipeline, including NVIDIA Smooth Motion and restructuring of the Display Container processes. It is possible that the timing of NVAPI DVC calls has become more sensitive to interrupts in this branch.
Happy to provide FrameView or PresentMon captures if helpful.
Since the new nvidia Drivers (596.xx and newer) there are some issues when you click ingame, vibranceGUI hogs one entire core and leads to massive Frametime spikes.
There is no problem with drivers up to:
591.67
The problem is with:
596.36 and 596.49
610.47
Summary
VibranceGUI causes frametime spikes on every single mouse click when running NVIDIA drivers from the R595 branch onwards (596.36, 596.49, and 610.47). The issue does not occur with older drivers (577.00, 591.67).
Steps to reproduce
Expected behavior
No frametime impact from mouse input.
Actual behavior
Every mouse click produces a visible frametime spike. The spike occurs consistently, both in-game and in the main menu, regardless of what is happening on screen. The issue is not related to rendering load.
Affected driver versions
Working driver versions
Isolation / root cause
After extensive troubleshooting (ruling out VSync, FreeSync, Frame Generation, NVIDIA Reflex, frame limiter, clean driver installs via NVCleaninstall), disabling VibranceGUI completely eliminated the frametime spikes. The issue is reproducible and consistent.
The likely cause is a change in how the NVIDIA R595 branch handles NVAPI calls or its driver event/interrupt pipeline. VibranceGUI hooks into the NVAPI Digital Vibrance Control, and it appears that driver-level changes in R595+ cause this hook to introduce latency on mouse input events, manifesting as DPC-level frametime spikes.
System
| Component | Details |
Additional notes
The R595 branch introduced significant changes to the driver presentation pipeline, including NVIDIA Smooth Motion and restructuring of the Display Container processes. It is possible that the timing of NVAPI DVC calls has become more sensitive to interrupts in this branch.
Happy to provide FrameView or PresentMon captures if helpful.