Skip to content
TroubleGrid

Assassin's Creed Shadows crashes to desktop after the NVIDIA 616.56 driver

Last verified October 2026Tested against GeForce Game Ready Driver 616.56 (released 26 August 2026) - the driver that introduced it, GeForce Game Ready Driver 616.64 (released 3 September 2026), GeForce Game Ready Driver 616.92 (released 9 September 2026) - first release to document it, GeForce Game Ready Driver 617.14 (released 22 September 2026) - last affected release, GeForce Game Ready Driver 617.42 (released 6 October 2026) - fixed here, GeForce Game Ready Driver 621.01 (released 21 October 2026) - current WHQL release; fix holds, game not listed, Assassin's Creed Shadows on WindowsGood evidence

NVIDIA has fixed this. Game Ready 617.42, released 6 October 2026, lists "Assassin's Creed Shadows may crash to desktop after extended gameplay after updating to driver 616.56" under Fixed Gaming Bugs - the same bug number it carried as an open issue through 616.92, 617.14 and the releases between. So the answer has reversed: update to 617.42 or later rather than rolling back. If you rolled back to a pre-616.56 driver to avoid this crash, you can stop. Re-checked 27 October 2026: the fix held into the new Release 620 branch - 621.01 of 21 October, now the current driver, does not list the game - but still rests on NVIDIA's release notes alone, with no independent reports either way.

NVIDIA shipped 616.56 on 26 August 2026 without mentioning Assassin's Creed Shadows in its known issues. The crash was documented two weeks later in the 616.92 notes of 9 September, attributed to updating to 616.56 and filed under open issues. It stayed open through 617.14 of 22 September, where it was the only entry left. On 6 October 2026, 617.42 moved it to Fixed Gaming Bugs - and it is the only bug that release fixes, with Fixed General Bugs listed as N/A. This page previously told readers to roll back, which was right for four weeks and is now the wrong advice.

Symptoms

  • Assassin's Creed Shadows closes straight to the desktop, usually with no error dialog
  • The crash shows up after a long session rather than at launch or in the first few minutes
  • The game was stable on the same hardware and settings before you updated the NVIDIA driver
  • You are on GeForce driver 616.56, 616.64, 616.92 or 617.14 - the crash should not occur on 617.42 or later

Why this happens

A regression introduced in GeForce driver 616.56, fixed in 617.42

NVIDIA's 616.92 notes list the crash as "Assassin's Creed Shadows may crash to desktop after extended gameplay after updating to driver 616.56 [6685219]". The wording ties the behaviour to updating to 616.56, and the bug number means NVIDIA had it on file. It appears in neither the 616.56 nor the 616.64 open-issues lists, which is why the problem went undocumented for two weeks rather than being absent from those drivers. It remained open in 617.14 of 22 September 2026, as that release's sole open issue. The 617.42 notes of 6 October 2026 move bug 6685219 to Fixed Gaming Bugs. NVIDIA has still published no root cause, and its own preamble to the open-issues list says some entries "may not have been thoroughly investigated and, in fact, may not be NVIDIA issues" - so read this as an acknowledged, version-bound regression that the vendor now says it has corrected, not as a fully explained one.

Update to GeForce 617.42 or later · Roll the display driver back, only if you cannot install 617.42 · Install an earlier driver by hand, only if rollback is unavailable too

Fixes

Update to GeForce 617.42 or later

about 15 min

NVIDIA fixed this bug in 617.42. The crash is listed under Fixed Gaming Bugs in that driver's release notes, under the same bug number it carried as an open issue for four releases.

Applies to: Windows 11, Windows 10 (version 1803 and later)

  1. Open the NVIDIA App and go to Drivers, or download the driver directly from NVIDIA's own driver downloads page. Microsoft's guidance is explicit that you should not take drivers from any site other than the manufacturer's official one.
  2. Install GeForce Game Ready 617.42 (released 6 October 2026) or any later release. A clean install is not required, but it does no harm if you have been swapping drivers to work around this.
  3. Restart if the installer asks you to.
  4. Play a long session to test - NVIDIA documents this crash as happening after extended gameplay, so a ten-minute check will not tell you anything.
  5. If you had previously rolled back to a pre-616.56 driver to avoid this crash, this is the point at which you can stop doing that and take the eight weeks of other fixes you were giving up.
  6. As of 27 October 2026 the current Game Ready release is 621.01, which opens the Release 620 branch. Taking it rather than 617.42 is fine and is what Windows or the NVIDIA app will offer you: 621.01 does not re-list this crash as an open issue, and its open-issues list is empty.

Confirmed by the vendor.

Source: NVIDIA, NVIDIA, Microsoft, NVIDIA

Confirm which driver you are on, and that the crash pattern matches

about 3 min

The documented bug covers 616.56 up to 617.14 and is fixed in 617.42, so your driver version decides whether the rest of this page applies to you at all.

Applies to: GeForce Game Ready 616.56 and later

  1. Open the NVIDIA App, or the NVIDIA Control Panel and choose Help then System Information, and read the driver version.
  2. 617.42 or newer: the fix is already installed. If the game still crashes the same way, this is no longer the bug NVIDIA documented - see the section on when something else is wrong.
  3. 616.56, 616.64, 616.92 or 617.14: you are on a driver NVIDIA's notes associate with this crash. Updating is the fix; go back to the previous step.
  4. Older than 616.56: this regression does not apply to you, and a crash you are seeing has another cause.
  5. Check the shape of the crash too. NVIDIA documents a crash to desktop after extended gameplay. A crash in the first few minutes, a hang on the loading screen, or a crash that also happened before you updated is a different problem.

Confirmed by the vendor.

Source: NVIDIA, NVIDIA, NVIDIA, NVIDIA, NVIDIA

Roll the display driver back, only if you cannot install 617.42

Check before applyingabout 10 min

This was the workaround while the bug was open. It still removes the cause, but updating is now both simpler and cheaper, so this is a fallback for machines that cannot take the new driver.

Applies to: Windows 11, Windows 10

Before you do this

Rolling back leaves you on a driver from before late August 2026, so you give up the three display fixes in 616.92, the DisplayPort wake-from-sleep, Samsung Odyssey G95NC HDMI and Judgment launch fixes in 617.14, and the Call of Duty: Modern Warfare 4 Game Ready support in 617.42. Since 617.42 fixes the crash outright, that is a cost with nothing to show for it in most cases. If Roll Back Driver is greyed out, Windows has kept no previous driver and this route is not available to you.

  1. Try the update first. Rolling back costs you every fix since August 2026 and NVIDIA has now fixed this specific crash, so there is no longer a reason to prefer this route.
  2. Right-click Start and choose Device Manager.
  3. Expand Display adapters, right-click your NVIDIA GPU and choose Properties.
  4. Open the Driver tab and select Roll Back Driver.
  5. Pick a reason when prompted, confirm, and restart if Windows asks you to.
  6. Treat this as temporary and move to 617.42 or later when you can.

Source: NVIDIA, Microsoft, NVIDIA, NVIDIA

Install an earlier driver by hand, only if rollback is unavailable too

Check before applyingabout 20 min

When Windows has not kept the previous driver and 617.42 genuinely cannot be installed, the same result is reached by downloading an earlier release yourself.

Applies to: Windows 11, Windows 10

Before you do this

Windows will not install an older driver over a newer one through the automatic path, and a manual display-driver swap blanks the screen briefly while it completes. Do it from the desktop rather than mid-game, and keep the installer for your current driver so you can return to it. As above, this gives up every fix since August 2026 to solve a bug that 617.42 already solves.

  1. Exhaust the two steps above first. This is the most work for the least benefit now that a fixed driver exists.
  2. Download a GeForce release published before 616.56 from NVIDIA's own driver downloads. Microsoft's guidance is explicit that you should not take drivers from any site other than the manufacturer's official one.
  3. Right-click Start and choose Device Manager, then expand Display adapters.
  4. Right-click your NVIDIA GPU and choose Update driver, then "Browse my computer for drivers".
  5. Point Windows at the folder you extracted the older driver into and continue.
  6. Restart, then test with a long session.

Source: NVIDIA, Microsoft

Known issues

  • Bug 6685219 is fixed. NVIDIA listed "Assassin's Creed Shadows may crash to desktop after extended gameplay after updating to driver 616.56 [6685219]" under Open Issues in 616.92 of 9 September 2026 and 617.14 of 22 September, then moved it to Fixed Gaming Bugs in 617.42 of 6 October 2026. It is the only bug 617.42 fixes; Fixed General Bugs reads N/A. NVIDIA never published a workaround while it was open.

    Affects 616.56, 616.64, 616.92, 617.14 · Status: fixed

  • Re-checked 27 October 2026, three weeks after the fix shipped: still no independent confirmation, and nothing contradicting it. The claim rests on NVIDIA's own release notes - the vendor stating it directly, not players reporting back after the long sessions this crash needs. It has at least survived a branch change: Game Ready 621.01 of 21 October does not re-list the game. Still crashing on 617.42 or later after a long session? That is new information worth having.

    Affects 617.42, 621.01 · Status: unknown

  • The other 616.56 regressions were cleared earlier: 616.92 fixed browser flicker [6673430], virtual displays [6674464] and Remote Desktop black screens [6687328]; 617.14 fixed the Judgment/Virtua Fighter 5 launch failure [6681537], DisplayPort monitors not waking from sleep [6757568] and the Samsung Odyssey G95NC over HDMI [6771206]. 616.64 fixed nothing at all. With 617.42, every documented 616.56 regression is now closed.

    Affects 616.64, 616.92, 617.14, 617.42 · Status: fixed

  • The “Prefer Maximum Performance” Power Management Mode issue [6007998] was the sole entry under Open Issues in 617.42, having vanished from the 617.14 notes without being declared fixed. In 621.01 it has gone quiet again rather than been resolved: that release lists no open issues at all - the section reads N/A - and does not list 6007998 as fixed either. Treat it as undocumented rather than confirmed fixed, and if you use that setting, see the separate article on it.

    Affects 617.14, 617.42, 621.01 · Status: unknown

If none of this worked

If you are on 617.42 or later and the game still crashes to desktop after extended play, this is no longer the bug NVIDIA documented and rolling back will not help - NVIDIA considers 6685219 closed. The same applies if the game also crashed before you updated the driver, or if it crashes within the first few minutes rather than after a long session. Be careful with older advice for this game: a much-linked thread from 21 March 2025 blames NVIDIA's 572-series drivers with frame generation and G-SYNC and tells readers to downgrade to 566.36, disable G-SYNC, or cap the refresh rate at 120 Hz. That is a different driver generation roughly eighteen months back, the thread's own author edited the post to say the crash returned anyway, and another participant reported no trouble on the same drivers. Following it today would cost you a year and a half of driver fixes without touching this bug.

Common questions

Does updating to the newest driver fix this?
Yes, as of 617.42. NVIDIA's release notes for that driver, published 6 October 2026, list the Assassin's Creed Shadows crash under Fixed Gaming Bugs. This is a reversal: 616.92 and 617.14 both carried it as an open issue, so for about four weeks updating genuinely did not help and rolling back was the only option. If you are reading older advice that says to roll back, check the date and check your driver version.
I rolled back to an older driver. What should I do now?
Update to 617.42 or later. Rolling back meant giving up the three display fixes in 616.92, three more in 617.14 and the Call of Duty: Modern Warfare 4 Game Ready support in 617.42. With the crash fixed there is nothing left to gain from staying on a pre-616.56 driver.
How confident can I be that it is actually fixed?
NVIDIA moved the bug number from Open Issues to Fixed Gaming Bugs in its own release notes, which is the vendor stating it directly - the strongest signal available for this kind of fault. Re-checked on 27 October 2026, three weeks later: nobody has independently confirmed it over the long sessions this crash needs to appear, and nobody has reported it surviving 617.42 either. It has at least survived a branch change - 621.01 of 21 October does not bring it back as an open issue. Treat it as fixed, test with a long session, and if it recurs that is new information.
Is this Ubisoft's bug or NVIDIA's?
NVIDIA documented it in its driver release notes, tied it to updating to driver 616.56, and has now fixed it in a driver release. All three point at the driver. NVIDIA never published a root cause, and it prefaces its open-issues list by saying some entries may not have been thoroughly investigated and may not be NVIDIA issues, so the honest answer is that NVIDIA owned and fixed it under bug 6685219 without explaining it.
Which driver should I roll back to if I cannot install 617.42?
Whichever release you were running before 616.56 - NVIDIA's wording attributes the crash to updating to 616.56, so any earlier release is outside the affected range. Device Manager's Roll Back Driver returns you to exactly the version Windows replaced. This is a fallback now, not the recommended route.

Did this fix work?

If a step is wrong, outdated, or did not help, telling us is the fastest way to get it corrected. Reports are reviewed before new articles.

Report a problem with this page

Related problems

Sources

  • NVIDIA · Release notes · checked Oct 27, 2026

    • Driver 617.42 lists "Assassin's Creed Shadows may crash to desktop after extended gameplay after updating to driver 616.56. [6685219]" under "3.1.1 Fixed Gaming Bugs", the same bug number NVIDIA carried as an open issue in 616.92, 617.14 and the releases between.
    • The 617.42 release notes are dated October 6, 2026 and carry the document id RN-08399-617.42_v01.
    • 617.42 lists "N/A" under Fixed General Bugs, so the Assassin's Creed Shadows crash is the only bug this release fixes.
    • The sole remaining entry under "Open Issues in Version 617.42 WHQL" is the "Prefer Maximum Performance" Power Management Mode bug [6007998]; the Assassin's Creed Shadows crash is no longer listed there.
    • 617.42 is a WHQL Game Ready release whose headline change is Game Ready support for Call of Duty: Modern Warfare 4, and it supports Windows 10 (Version 1803) and later as well as Windows 11.
  • NVIDIA · Release notes · checked Oct 27, 2026

    • In the 617.14 release notes of September 22, 2026 the Assassin's Creed Shadows crash [6685219] is still listed under Open Issues, and it is the only entry in that list.
    • 617.14 fixes bug 6681537 (Judgement/Lost Judgement/Virtua Fighter 5 R.E.V.O. failing to launch), 6757568 (certain monitors not waking from sleep on DisplayPort) and 6771206 (no picture on the Samsung Odyssey G95NC over HDMI).
  • NVIDIA · Release notes · checked Oct 27, 2026

    • The 616.92 release notes of September 9, 2026 are where NVIDIA first documents the crash, listing "Assassin's Creed Shadows may crash to desktop after extended gameplay after updating to driver 616.56 [6685219]" under Open Issues.
    • Driver 616.92 fixes three other regressions introduced by 616.56: intermittent browser flicker [6673430], virtual displays not being created [6674464], and Remote Desktop Protocol sessions showing a black screen [6687328].
    • NVIDIA's Open Issues preamble states that some problems listed "may not have been thoroughly investigated and, in fact, may not be NVIDIA issues".
  • NVIDIA · Release notes · checked Oct 27, 2026

    • The Open Issues list for driver 616.56, dated August 26, 2026, names only the "Prefer Maximum Performance" Power Management Mode bug [6007998]; it does not mention Assassin's Creed Shadows, so NVIDIA did not document this crash when 616.56 shipped.
  • NVIDIA · Release notes · checked Oct 27, 2026

    • Driver 616.64, dated September 3, 2026, lists "N/A" under both Fixed Gaming Bugs and Fixed General Bugs, so it corrected nothing that 616.56 introduced.
    • The Open Issues list for 616.64 names the "Prefer Maximum Performance" Power Management Mode bug [6007998] and intermittent browser flicker [6673430], and does not mention Assassin's Creed Shadows.
  • Microsoft · Support page · checked Oct 27, 2026

    • Microsoft documents rolling a driver back by opening the Driver tab in Device Manager and selecting Roll Back Driver, under the heading "Rollback the driver (if a recent update was installed)".
    • A specific driver version can be installed by downloading it first and then using Update driver followed by "Browse my computer for drivers".
    • Microsoft advises avoiding driver downloads from any website other than the manufacturer's official site.
  • NVIDIA · Release notes · checked Oct 27, 2026

    • Game Ready 621.01 WHQL, dated 21 October 2026, is the first release of the Release 620 branch and is the current WHQL Game Ready driver
    • The 621.01 Open Issues section reads N/A, and the release does not mention Assassin’s Creed Shadows under either Fixed Issues or Open Issues
    • The "Prefer Maximum Performance" Power Management Mode issue [6007998] appears nowhere in 621.01 - neither under Open Issues nor under Fixed Issues
  • Steam Community · Forum · checked Oct 27, 2026

    • A widely linked Assassin's Creed Shadows crash thread dated 21 March 2025 recommends downgrading to NVIDIA driver 566.36, disabling G-SYNC, or capping the monitor refresh rate at 120 Hz - advice aimed at the 572-series drivers of that period, not the 616 or 617 series.
    • The author later edited the opening post to say "EDIT game still crashed with the 'fix' I found just lasted a LOT longer but cant delete the thread", and added that reverting drivers "obviously didnt fix it".
    • Another participant in the same thread reported no crashes at all on driver 572.83 with G-SYNC and frame generation enabled.