Nvidia's known-issues list carried one GeForce bug for seven drivers, then dropped it

Nvidia's known-issues list carried one GeForce bug for seven drivers, then dropped it

Nvidia's Windows release notes listed the same GeForce bug as an open issue in seven consecutive drivers, from 610.47 on May 26 through to 616.92 on September 9. It is not in the notes for 617.14, published on September 22, and that driver does not list it as fixed either.

A crouching figure in long grass beneath a raised wooden building at night in Assassin's Creed Shadows, with the game's on-screen prompts visible

The single open issue Nvidia still lists for 617.14 is a crash to desktop in Assassin's Creed Shadows. Image: Ubisoft

The entry reads, in Nvidia's own wording, "Prefer Maximum Performance" Power Management Mode may not be applied correctly [6007998]. Searching all eight release-notes PDFs on Nvidia's own download server for the string 6007998, at 20:10 UTC on October 5, returns one hit in each of the seven older documents and none at all in 617.14.

The seven are 610.47 of May 26, 610.62 of June 16, 610.74 of July 7, 610.88 of July 28, 616.56 of August 26, 616.64 of September 3 and 616.92 of September 9. That is about 15 weeks and two driver branches. The same search comes back empty on 596.49 of May 12, a Release 595 driver, so the entry appeared with the Release 610 branch and carried on into Release 615, the branch 616.56, 616.64, 616.92 and 617.14 all belong to.

Nvidia named three fixes in 617.14, and this was not one

617.14 records one fixed gaming bug, a launch failure affecting Judgement, Lost Judgement and Virtua Fighter 5 R.E.V.O. [6681537]. It records two fixed general bugs: no picture on a Samsung Odyssey G95NC connected over HDMI [6771206], and certain monitors failing to wake from sleep over DisplayPort [6757568].

Its open-issues list now holds a single entry, a crash to desktop in Assassin's Creed Shadows after extended play [6685219]. Those four items are the whole of what 617.14 calls fixed or open, and bug 6007998 is in none of them.

Nvidia says the lists are only a subset

Every edition of the notes carries the same caveat: "This list is only a subset of the total number of changes made in this driver version." An entry leaving the open list without turning up on a fixed list is therefore not evidence that the bug was repaired, and not evidence that it survived the update.

Nvidia's notes also never say which GPUs, which laptops or which games were affected, and never describe what incorrectly applied power management looked like to the person using the machine. What the documents do establish is the listing itself: present seven times, then absent, with no line of text marking the change.

The known-issues list is one of the few things a GeForce owner can read before deciding whether to update, and a driver version on its own can decide whether software runs: Valve tells SteamVR users that their Nvidia driver files have to match each other exactly or the headset drops to error 303.

Gaps between what a graphics vendor documents and what it has actually shipped are not rare. AMD's Adrenalin numbering produced one in late September, when CD Projekt Red pointed The Witcher 3 players at an AMD driver version that had not shipped.

Nothing newer has arrived for GeForce since. Nvidia's own Game Ready announcement of September 22, still the most recent driver post on its GeForce news feed when read at 20:10 UTC on October 5, sends owners to 617.14 WHQL. The next edition of the notes is the earliest point at which bug 6007998 could return to the open list, or stay absent from it without comment.

Leave a Comment

Your email address will not be published. Required fields are marked *