Known driver issues
An issue can be open in one release and explicitly fixed in a later one. Each relationship below names its driver release; an issue disappearing from notes is not proof of a fix.
Issue rows are reviewed individually
The latest issue source check covers the 6 October 2026 Game Ready notice. Older rows retain their own review dates. Officially acknowledged means an NVIDIA source names the issue. Fixed in scope means a reviewed source ties the fix to a particular release, family, and platform.
If your problem began during installation rather than after it, use the failed-update recovery guide.
Issue records
Browser flicker issue fixed in reviewed Windows GeForce sources
NVIDIA 6673430- Status
- Fixed in reviewed scope
- Symptom
- Intermittent browser flicker on certain websites.
- Affected scope
- Reviewed Windows GeForce hotfix and regular-release sources.
- Fixed in
- GeForce hotfix 616.86, Game Ready 616.92
- Still open in
- Not listed as open in the seeded release rows.
- Prevalence
- Not established by this research.
Boundary: The fixed-in relation is scoped to the reviewed hotfix and regular Game Ready sources; it is not inherited across every family or future branch.
Assassin’s Creed Shadows crash fixed in Game Ready 617.42
NVIDIA 6685219- Status
- Fixed in reviewed scope
- Symptom
- The game could crash to desktop after extended play after updating to 616.56.
- Affected scope
- Open in reviewed 616.92 Windows Game Ready notes; fixed in the official 617.42 Windows release notes.
- Fixed in
- Game Ready 617.42, Studio 617.42
- Still open in
- Game Ready 616.92
- Prevalence
- Not established by this research.
Boundary: The fixed-in claim is specific to the 617.42 Windows release notes; it does not establish that every affected system is repaired.
Game-launch issue fixed in Game Ready 617.14 and Studio 617.42
NVIDIA 6681537- Status
- Fixed in reviewed scope
- Symptom
- Judgement, Lost Judgement and Virtua Fighter 5 R.E.V.O. could fail to launch after driver 616.56.
- Affected scope
- Historical open issue in Game Ready 616.92; explicit fixes in the cited later package listings.
- Fixed in
- Game Ready 617.14, Studio 617.42
- Still open in
- Game Ready 616.92
- Prevalence
- Not established by this research.
Boundary: Fix claims apply to the cited packages. They do not certify every machine or transfer automatically to another driver family.
Game Ready 617.42 power-management setting open issue
NVIDIA 6007998- Status
- Open in cited release
- Symptom
- “Prefer Maximum Performance” power management mode may not be applied correctly.
- Affected scope
- Official 617.42 Windows release notes and NVIDIA staff Game Ready feedback notice.
- Fixed in
- No fixed-in release seeded yet.
- Still open in
- Game Ready 617.42
- Prevalence
- Not established by this research.
Boundary: An acknowledged open issue does not prove that every system or game is affected. Check the current release notes before changing a working configuration.
How to use a status
A fixed-in row requires explicit evidence. A missing issue paragraph in a later source is not automatically a fix, and an official acknowledgement is not a prevalence measurement.
Download the issue CSV · Check compatibility scope before treating any issue row as advice for a specific machine.
Evidence trail
Sources used on this page
Source class describes ownership and form. It is not a reliability score.
- GeForce Hotfix Display Driver version 616.86Official support article
NVIDIA Customer Care · 2026-09-04
- 616.92 Windows Game Ready release notesOfficial release notes
NVIDIA · 2026-09-09
- Release 615 Driver for Windows, Version 617.42 release notesOfficial release notes
NVIDIA · 2026-10-06
- Studio 617.42 desktop packageOfficial documentation
NVIDIA · 2026-10-06
- Studio 617.42 notebook package and OEM qualificationsOfficial documentation
NVIDIA · 2026-10-06
- Game Ready 617.14 notebook package: explicit bug fixesOfficial documentation
NVIDIA · 2026-09-22
- Game Ready 617.42 feedback and issue noticeOfficial staff issue notice
NVIDIA GeForce Forums, NVIDIA staff · 2026-10-06
Core source registry dated ; later page and record revisions carry their own dates. An inaccessible link triggers source maintenance.