Screen flickering and dark flashes after the NVIDIA 616.56 driver
Update to Game Ready 616.92 or later - 621.24 of 12 November 2026 is the current release. 616.92 is the WHQL driver this bug was waiting on, and it fixes the browser flicker NVIDIA had listed as an open issue in 616.64, so you no longer need the 616.86 beta hotfix. NVIDIA never documented the wider desktop flicker on 8-bit displays, and nothing up to and including 621.24 claims to fix it, so if the flashing continues after updating, setting Output color depth to 10 bpc or rolling back to 610.88 is still the answer - and 610.88 is still what reporters on NVIDIA's 621.24 thread go back to. The 360 Hz QHD black flash stays fixed as of 621.01.
Start here
The flicker shows up on the desktop and in Chromium browsers as much as in games, which is what tells you it is a display-pipeline problem rather than a game problem. It has been reported on RTX 30, 40 and 50 series cards, on desktops and laptops, and on both Windows 10 and Windows 11, so there is no point hunting for a hardware cause. As of 22 October 2026 the position is this: NVIDIA fixed the browser flicker it documented, first in the 616.86 hotfix on 4 September and then in WHQL driver 616.92 on 9 September. The wider flicker on 8-bit output was never listed in any NVIDIA release notes, and nothing through 621.01 mentions it either way, so for that variant the workarounds below still matter. The one separately documented flash - a black flash specific to QHD monitors at 360 Hz - is now fixed in a normal WHQL driver rather than only in a hotfix.
Symptoms
- The whole screen flashes dark or white for a fraction of a second, then returns to normal
- It happens on the desktop, not only in games
- It is worst in Chrome, Edge, Discord and other Chromium apps, and while playing video
- Brightness or gamma shifts on its own for a few seconds
- The taskbar or wallpaper darkens by itself
- It started the day you installed driver 616.56 or 616.64
Why this happens
NVIDIA has confirmed the bug in the Release 615 driver branch
For the first week this was only a pattern in user reports. It is no longer: NVIDIA's own release notes for 616.64 list "Intermittent flicker may be observed in browsers when navigating to certain websites [6673430]" under Open Issues. The same notes list N/A under both Fixed Gaming Bugs and Fixed General Bugs, which means the driver released on 3 September 2026 changed nothing. The 616.56 notes did not mention flickering at all, so 616.64 is where NVIDIA first wrote it down. NVIDIA then addressed that specific browser flicker a day later in Hotfix driver 616.86. Reports outside NVIDIA match the vendor's wording — the flicker is worst in browsers — and span RTX 30, 40 and 50 series machines.
Update to Game Ready driver 616.92 or later · Roll back to driver 610.88
Reports point at 8-bit colour output
Coverage of the bug describes it affecting displays running 8-bit colour output, and the workaround people report is forcing the display to 10 bpc. NVIDIA's own wording does not name colour depth, and the 616.86 hotfix does not list a fix for it, which is the clearest sign that the wider display flicker and the browser flicker are being tracked as different things. Treat the colour depth theory as the cheap thing to try rather than a confirmed diagnosis. It only helps if your monitor and cable can carry 10-bit at your current resolution and refresh rate.
A separate black flash at 360 Hz on QHD monitors, which NVIDIA has documented and fixed
NVIDIA's bug 4846825 - "QHD monitor running at 360 Hz may have occasional black flash during gameplay" - is a distinct defect from the flicker the rest of this page covers, and it only affects QHD panels running at 360 Hz. It was fixed partly in the 617.70 hotfix in mid-October 2026 and then outright in Game Ready 621.01 of 21 October, which lists it under Fixed General Bugs. If that is your panel, updating settles it; if the flashing survives 621.01, you are looking at the undocumented 8-bit flicker instead.
Fixes
Confirm you are on 616.56 or 616.64
about 2 minEverything below assumes the driver is the cause. Two minutes here saves you from rolling back a driver that was never the problem.
Applies to: Windows 10, Windows 11
- Right-click the desktop, open NVIDIA Control Panel, then click System Information at the bottom left. The Display tab lists the driver version in NVIDIA's own numbering, so you will see 616.56 or 616.64 rather than the longer Windows version number.
- The NVIDIA App shows the same thing under Drivers, if you have it installed.
- Both 616.56 and 616.64 are affected. 616.64 shipped on 3 September 2026 with no bug fixes at all, so updating to it from 616.56 will not have helped. If you already read 616.86 you have the beta hotfix, and 616.92 or later carries the documented fix in a WHQL driver.
- Now watch where the flicker happens. If it flashes on the desktop or while scrolling in Chrome, this article applies. If it only ever happens inside one game, it is a different problem.
Confirmed by the vendor.
Update to Game Ready driver 616.92 or later
about 15 minThe fix NVIDIA documented is now in a WHQL driver, so trying it costs you nothing — unlike the beta hotfix it replaces.
Applies to: Windows 10, Windows 11
- Open the NVIDIA app and check for updates, or download Game Ready 616.92 or later from NVIDIA directly. As of 22 October 2026 the current release is 621.01.
- Install it and restart. NVIDIA lists three 616.56 regressions fixed in it: intermittent flicker in browsers on certain websites, virtual displays that could not be created, and Remote Desktop sessions showing a black screen.
- Use the PC normally with a Chromium browser open for a few minutes. That is where the flicker shows up fastest. If the flashing has stopped, you are done.
- If the desktop still flashes, your symptom is the wider flicker on 8-bit output, which NVIDIA has never documented and which none of 616.92, 617.14, 617.42 or 621.01 claims to fix. Carry on to the next fix.
Confirmed by the vendor.
Set the display output to 10 bpc
about 5 minReports cluster on displays running 8-bit output, and this variant is the one NVIDIA has never documented or claimed to fix. Moving to 10-bit stops the flicker without giving up the current driver.
Applies to: Monitors that support 10-bit colour, GeForce drivers 616.56 and 616.64
- Right-click the desktop and open NVIDIA Control Panel.
- Go to Display, then Change resolution. Select the monitor that flickers.
- Under section 3, choose "Use NVIDIA color settings".
- Set Output color depth to 10 bpc and click Apply. If 10 bpc is not offered, your monitor, cable or current refresh rate cannot carry it — skip to the hotfix or rollback below.
- If 10 bpc is unavailable, turning on Windows Automatic Colour Management is also reported to help on displays that support it.
- Use the PC normally for a few minutes with a Chromium browser open. That is where the flicker shows up fastest.
Reported to work by one user; not confirmed by the vendor.
On a QHD monitor at 360 Hz: update to 621.01
about 15 minNVIDIA documented this specific flash as bug 4846825 and now lists it as fixed in a WHQL driver. It is a different bug from the rest of this page, and it no longer needs a beta hotfix.
Applies to: QHD monitors running at 360 Hz, Windows 10 and Windows 11, 64-bit
- This step is only for QHD monitors running at 360 Hz. At any other resolution or refresh rate, go back to the fixes above.
- Update to GeForce Game Ready Driver 621.01 (21 October 2026) or later and restart. Its release notes list "QHD monitor running at 360 Hz may have occasional black flash during gameplay [4846825]" under Fixed General Bugs.
- The 617.70 hotfix was the earlier route to this fix and fixed some but not all cases. There is no reason to use it now: 621.01 is WHQL, and NVIDIA ships hotfix drivers as optional beta builds through an abbreviated QA process.
- You can also stop worrying about the Prefer Maximum Performance workaround NVIDIA used to offer for the remaining cases. It was awkward advice, because 617.42 listed bug 6007998 - that same mode may not be applied correctly - as its only open issue. With 4846825 fixed outright, the workaround is moot.
- If a QHD 360 Hz panel still flashes on 621.01, treat it as the undocumented 8-bit flicker above rather than this bug, and work through the 10 bpc step.
Confirmed by the vendor.
Source: NVIDIA, NVIDIA GeForce Forums, NVIDIA GeForce Forums, NVIDIA
Roll back to driver 610.88
Check before applyingabout 20 minThe fallback when 10 bpc is not available or does not help. 610.88 predates the R615 branch this bug arrived in, and it is still the version people on NVIDIA's own 621.14 and 621.24 feedback threads name as the last one that behaved - three more reporters said so there in November 2026.
Applies to: Windows 10, Windows 11, Still the community's last-known-good target as of 621.24 (12 November 2026)
Before you do this
Download the installer before you uninstall anything. A driver swap blanks the screen for several seconds and can leave you on the basic Microsoft display driver until it finishes, which is awkward to recover from if you have nothing to install.
First:
- Download the 610.88 installer before you start
- Go to NVIDIA's driver download page, pick your card, and download version 610.88 for your version of Windows. Save it before doing anything else.
- Run the installer, choose Custom (Advanced), and tick "Perform a clean installation". That clears the newer driver's settings rather than carrying them over.
- Let it finish and restart the PC.
- Turn off automatic driver updates in the NVIDIA App, or Windows will offer you the affected driver again.
Reported to work by 6 users; not confirmed by the vendor.
Source: DxO Forum, Steam Community, spacedesk by datronicsoft, Club386, NVIDIA GeForce Forums, NVIDIA GeForce Forums
Known issues
NVIDIA listed "Intermittent flicker may be observed in browsers when navigating to certain websites [6673430]" as an open issue in the 616.64 release notes. It is not in the 616.56 notes, and 616.64 lists no fixed bugs of any kind. Hotfix 616.86 of 4 September 2026 fixed it first, and Game Ready 616.92 of 9 September 2026 lists it under Fixed General Bugs, so it is now fixed in the WHQL branch and flicker appears nowhere in that driver's open issues.
Affects 616.56, 616.64 · Status: fixed
NVIDIA bug 4846825 - 'QHD monitor running at 360 Hz may have occasional black flash during gameplay'. Fixed in Game Ready 621.01 of 21 October 2026, which lists it under Fixed General Bugs. The 617.70 hotfix fixed some but not all cases first, with Prefer Maximum Performance as the workaround for the rest; that workaround is no longer needed.
Affects 617.42 WHQL and earlier, Partly fixed in GeForce Hotfix Driver 617.70, Fixed in Game Ready 621.01 WHQL · Status: fixed
The Prefer Maximum Performance bug that undercut that workaround has stopped being listed. Bug 6007998, 'Prefer Maximum Performance Power Management Mode may not be applied correctly', was the only open issue in the 617.42 notes. From 621.01 onward the Open Issues section reads 'N/A' and the bug is not under Fixed Issues either - still true in 621.14 and 621.24, both read on 16 November 2026. NVIDIA has neither fixed it on the record nor kept listing it.
Affects 617.42 WHQL, Not listed either way in 621.01, 621.14 or 621.24 WHQL · Status: unknown
The wider flicker on 8-bit displays is still unfixed. Coverage on 2 September 2026 reported NVIDIA testing a fix. Six WHQL drivers have shipped since - 616.92, 617.14, 617.42, 621.01, 621.14 and 621.24 of 12 November - and none claims it. Both 621.14 and 621.24 were read in full on 16 November 2026: neither mentions flicker, dark flashes, colour depth or bug 6673430, and both read 'N/A' under Open Issues. Flicker reports continue on both, with no NVIDIA reply resolving them.
Affects 616.56, 616.64, 616.86, 616.92, 617.14, 617.42, 621.01, 621.14, 621.24 · Status: workaround only
Separately from the flickering, 616.56 broke virtual displays used by second-screen software, with black screens and crashes. The 616.86 hotfix fixed it and Game Ready 616.92 now carries that fix too [6674464]. Before either, reverting to a 610-branch driver resolved it.
Affects 616.56, 616.64 · Status: fixed
Remote Desktop Protocol sessions displaying a black screen after updating to 616.56 is also fixed, in the 616.86 hotfix and then in Game Ready 616.92 [6687328]. That regression was never listed in the 616.56 or 616.64 release notes at all.
Affects 616.56, 616.64 · Status: fixed
Both game regressions from the same 616.56 driver have since been fixed, in later drivers rather than by anything on this page: Judgement, Lost Judgement and Virtua Fighter 5 R.E.V.O. failing to launch [6681537] in 617.14 of 22 September 2026, and Assassin's Creed Shadows crashing to desktop after extended gameplay [6685219] in 617.42 of 6 October 2026. Neither is a flicker, so neither was resolved by the drivers this page recommends.
Affects 616.56, 616.64, 616.92, Judgement fixed in 617.14, Assassin's Creed Shadows fixed in 617.42 · Status: fixed
Do not confuse this with the DxO PhotoLab and PureRAW failure. 616.56 also broke AI-powered exports in DxO's Windows apps; DxO shipped PhotoLab 10.0.1 and 9.12.1 on 4 September 2026 to fix it, and says rolling back the driver is no longer necessary for PhotoLab. DxO states NVIDIA's separate system-level issues in 616.56 are independent of DxO software and are not addressed by that update — so a PhotoLab update will not stop your screen flickering.
Affects 616.56, DxO PhotoLab 10.0.1 and 9.12.1, DxO PureRAW · Status: fixed
Windows Automatic Colour Management, the other workaround suggested for this flicker, has a cost of its own on the R620 branch. A reporter on NVIDIA's 621.14 thread using an 8 bpc RGB-full HDMI monitor found that with ACM off the screen washes out as soon as a Chromium browser opens, and with ACM on any fullscreen app washes out whenever the mouse stops moving. That is a colour fault rather than a flicker, so treat ACM as a trade-off and prefer 10 bpc where the display supports it.
Affects 621.01, 621.14 · Status: open
If none of this worked
If the flicker predates 616.56, the driver is not your problem. Check the DisplayPort or HDMI cable first, since a marginal cable at high refresh rates produces exactly this symptom. Monitor overdrive and variable-refresh settings cause their own brightness flicker on some panels, usually only in games and usually when the frame rate swings. And if a single game flashes black while the desktop is fine, look at the game's fullscreen mode and any overlay software before touching the driver. If you are on a QHD monitor at 360 Hz, check the 360 Hz step on this page first - NVIDIA documented that flash separately and fixed it in 621.01. And if the number you are watching is the frame rate rather than the brightness - 360 FPS dropping to a locked 320 - that is a different confirmed bug with its own page, also fixed in 621.01. Two look-alikes worth separating, both reported on 621.14 and 621.24 at 8 bpc: blacks sitting a level too high only while a display calibration is loaded is a gamma-ramp bug present on 610.88 too, so rolling back will not help; and a washed-out picture rather than a flashing one is the note below.
Common questions
- Is my monitor dying?
- Almost certainly not, if the flicker started the day you installed 616.56 or 616.64. NVIDIA has confirmed the bug exists in this driver branch and lists it as an open issue, so the driver is the first thing to rule out. The test that settles it is changing the driver.
- Will updating to 616.64 fix it?
- No. 616.64, released 3 September 2026, lists N/A under both Fixed Gaming Bugs and Fixed General Bugs — it fixes nothing — and it still carries the flicker in its own list of open issues. Update to 616.92 or later instead.
- Has NVIDIA fixed this?
- Partly, and the split matters. The browser flicker NVIDIA actually documented is fixed: it was listed as an open issue in 616.64, cleared in the 616.86 hotfix, and carried into WHQL 616.92 under Fixed General Bugs. The wider flicker on 8-bit desktop output was never in any release notes, and nothing through 621.24 of 12 November 2026 claims to fix it - so for that variant the answer is still no. The separate 360 Hz QHD black flash, bug 4846825, has been fixed since 621.01.
- Do I still need the 616.86 hotfix?
- No. It was the only route for a few days, and NVIDIA labels hotfix releases beta, optional and provided as-is with a much abbreviated QA process. Game Ready 616.92 carries the same flicker fix with full WHQL certification, so there is no longer a reason to run the beta driver for this.
- Does 10 bpc cost me anything?
- On a monitor that genuinely supports it, no. At very high resolutions and refresh rates the extra bandwidth may not fit, in which case the option will not be offered or the display will drop to a lower refresh rate.
- I updated DxO PhotoLab and the flickering is still there. Why?
- Because those are two different bugs. Driver 616.56 broke AI-powered exports in DxO PhotoLab and PureRAW, and DxO fixed that in PhotoLab 10.0.1 and 9.12.1 on 4 September 2026 by adapting its own software. DxO says plainly that NVIDIA is separately working on other issues in 616.56 that affect Windows and applications outside DxO, and that those are not addressed by the PhotoLab update. The display flickering is one of those. Update PhotoLab for the export problem, but use the steps on this page for the flickering.
- My screen only flashes black at 360 Hz on a QHD monitor. Same bug?
- No - that one NVIDIA documented separately, as bug 4846825, and it is now fixed. Game Ready 621.01 of 21 October 2026 lists it under Fixed General Bugs, so updating is the whole answer; the 617.70 hotfix that carried the fix first is no longer worth installing. If a QHD 360 Hz panel still flashes once you are on 621.01, treat it as the undocumented 8-bit flicker this page is mainly about and work through the 10 bpc step.
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 pageRelated problems
- Game Stuttering After an NVIDIA Driver Update
- Game Shows a Black Screen on Launch but the Audio Plays
- "Prefer maximum performance" does nothing on NVIDIA 610.88 through 617.42
- FPS locked at 320 on a 360 Hz G-SYNC Pulsar monitor
- NVIDIA driver writes to the SSD constantly (NVDisplay.Container.exe, nvlog.nvlgstg)
- No Sound Over HDMI or DisplayPort on an AMD Graphics Card After a Windows 11 Update
Sources
NVIDIA · Release notes · checked Nov 16, 2026
- 617.14, dated September 22, 2026, is the WHQL release following 616.92
- The Fixed Issues in Version 617.14 WHQL cover the Judgement/Virtua Fighter 5 launch failure, the Samsung Odyssey G95NC HDMI blank screen and DisplayPort monitors failing to wake from sleep — no flicker entry appears
- No flicker issue appears under Open Issues in Version 617.14 WHQL, whose only entry is the Assassin's Creed Shadows crash
NVIDIA · Release notes · checked Nov 16, 2026
- NVIDIA documents the flicker in its own release notes: "Intermittent flicker may be observed in browsers when navigating to certain websites [6673430]" is listed under Open Issues in Version 616.64 WHQL.
- 616.64 WHQL lists N/A under both Fixed Gaming Bugs and Fixed General Bugs, so it fixes nothing and does not resolve the flicker.
- 616.64 is a Release 615 driver, the same branch as 616.56.
- The only other open issue carried in 616.64 is that "Prefer Maximum Performance" Power Management Mode may not be applied correctly [6007998].
NVIDIA · Release notes · checked Nov 16, 2026
- 616.56 WHQL is a Release 615 driver and the release notes list changes made since version 610.88.
- Display flickering is not listed anywhere in the 616.56 release notes. The word flicker appears once, in an unrelated fixed Outer Worlds texture-flicker entry [6238668], so 616.64 is the first release in which NVIDIA documented the browser flicker.
- NVIDIA documents the output colour depth control as NVIDIA Control Panel -> Change Resolution -> "Use NVIDIA color settings" -> Output color depth.
NVIDIA · Support page · checked Nov 16, 2026
- GeForce Hotfix Display Driver version 616.86, released 4 September 2026 and based on Game Ready Driver 616.64, lists three fixes: intermittent flicker in browsers when navigating to certain websites, virtual displays that could not be created after updating to driver 616.56, and Remote Desktop Protocol sessions displaying a black screen after updating to driver 616.56.
- The hotfix does not list any fix for display flickering on 8-bit colour output.
- NVIDIA states that hotfix drivers are beta, optional and provided as-is, produced through a much abbreviated QA process, and that the safest option is to wait for the next WHQL certified driver.
NVIDIA · Release notes · checked Nov 16, 2026
- Game Ready driver 616.92, released 9 September 2026, lists "Intermittent flicker may be observed in browsers when navigating to certain websites [6673430]" under Fixed General Bugs, putting that fix in a WHQL driver for the first time.
- 616.92 also fixes virtual displays that could not be created after updating to 616.56 [6674464] and Remote Desktop Protocol sessions displaying a black screen [6687328].
- Flicker of any kind no longer appears in the 616.92 open-issues list, which names only the Prefer Maximum Performance bug [6007998], an Assassin's Creed Shadows crash [6685219], and Judgement/Lost Judgement/Virtua Fighter 5 R.E.V.O. failing to launch [6681537].
- Re-checked on 16 September 2026: 616.92 remains the newest Game Ready driver and makes no mention of flicker on 8-bit output.
NVIDIA · Release notes · checked Nov 16, 2026
- 617.42 WHQL lists "Assassin's Creed Shadows may crash to desktop after extended gameplay after updating to driver 616.56. [6685219]" under Fixed Gaming Bugs.
- 617.42 WHQL lists N/A under Fixed General Bugs.
- The only entry under Open Issues in Version 617.42 WHQL is "Prefer Maximum Performance Power Management Mode may not be applied correctly. [6007998]".
- 617.42 WHQL lists changes made since driver version 617.14.
- Pulsar Hotfix DriverOfficial
NVIDIA GeForce Forums · Forum · checked Nov 16, 2026
- NVIDIA Staff announcing hotfix 617.70, the bug ID 4846825 for occasional black flashes on a QHD monitor at 360 Hz, that the hotfix fixes some but not all cases, and the Prefer Maximum Performance workaround requiring a reboot
NVIDIA GeForce Forums · Forum · checked Nov 16, 2026
- NVIDIA's stickied changelog repeating bug 4846825 and the Prefer Maximum Performance workaround, and stating the hotfix fixes will not be in the main driver until more extensive QA
NVIDIA · Release notes · checked Nov 16, 2026
- GeForce Game Ready Driver 621.01 WHQL is dated 21 October 2026 and is a Release 620 branch driver
- 621.01 lists "QHD monitor running at 360 Hz may have occasional black flash during gameplay. [4846825]" under Fixed General Bugs
- 621.01 lists "When gaming on a 360Hz G-SYNC Pulsar monitor, FPS may drop to 320FPS. [6408986]" under Fixed General Bugs
- The Open Issues in Version 621.01 WHQL section lists no entries - it reads "N/A"
- 621.01 lists no fix for desktop or browser flicker on 8-bit output, and names no such issue either way
NVIDIA · Release notes · checked Nov 16, 2026
- RN-08399-621.14_v01, dated 4 November 2026.
- Fixed Gaming Bugs lists only Call of Duty: Modern Warfare 4 incorrect visual colors [6972531]; Fixed General Bugs lists only the video playback freeze or black screen on some GeForce RTX 50 Series GPUs/RTX Spark after updating to GRD 621.01 [6979343].
- Open Issues in Version 621.14 WHQL reads 'N/A'.
- Read in full on 16 November 2026: the document does not mention flicker, dark flashes, bug 6673430 or bug 6007998 anywhere, so it neither fixes nor lists the 8-bit desktop flicker.
NVIDIA · Release notes · checked Nov 16, 2026
- RN-08399-621.24_v01, dated 12 November 2026 - the current Game Ready release.
- Fixed Gaming Bugs reads 'N/A'; Fixed General Bugs lists only the Chaos Vantage OptiX Denoiser failure at high resolutions [6953474] and incorrect colors with DJI D-Log H.265 playback in Windows Photos/Media Player [6996250].
- Open Issues in Version 621.24 WHQL reads 'N/A'.
- Read in full on 16 November 2026: the document does not mention flicker, dark flashes, bug 6673430 or bug 6007998 anywhere, so the 8-bit desktop flicker remains neither fixed nor acknowledged in the current driver.
Club386 · News · checked Nov 16, 2026
- Reported on 2 September 2026 that NVIDIA staff acknowledged the flickering in the official 616.56 feedback thread, with staffer Manuel@Nvidia saying the firm is "testing a fix for this".
- The flickering is described as affecting displays running 8-bit colour output.
- A full fix was expected no earlier than 10 September 2026 in a subsequent Game Ready driver, and the driver released on 3 September was not expected to contain it.
- The workarounds described are switching from 8-bit to 10-bit colour, enabling Windows Automatic Colour Management, and rolling back to 610.88.
- Re-checked on 16 September 2026: the page is unchanged, still carries the 10 September estimate, and mentions neither the 616.86 hotfix nor 616.92.
- Re-checked on 16 November 2026: still dated 2 September 2026 with no update or correction note, still carrying the 10 September estimate, and still mentioning neither the 616.86 hotfix nor 616.92.
DxO Forum · Forum · checked Nov 16, 2026
- DxO warned its users on 28 August 2026 not to install 616.56, describing display flickering, brief black screens and colour shifts in browsers, Discord and video playback.
- The advisory states the problems are not specific to DxO applications and affect RTX 30, 40 and 50 series desktops and laptops.
- It recommends rolling back to 610.88 from NVIDIA's driver archive using the clean installation option.
- The thread was retitled and updated on 4 September 2026: DxO PhotoLab 10.0.1 and 9.12.1 resolve the DxO-specific export failure, which DxO traced with NVIDIA to a change in 616.56 affecting an NVIDIA component used for AI processing, and rolling back the driver is no longer necessary for PhotoLab.
- DxO states that NVIDIA is separately working on other issues in driver 616.56 that affect Windows and applications outside DxO, and that those system-level issues are not addressed by the PhotoLab update.
- Forum members using Studio driver 616.92 report no PhotoLab export problems on 11 and 14 September 2026.
Steam Community · Forum · checked Nov 16, 2026
- A user reported on 29 August 2026 getting blank black screens between games after installing 616.56, with audio still audible.
- Rolling back to 610.88 is reported in the thread to have stopped the black screens.
- Nvidia Driver 616.56 issues Not workingCommunity report
spacedesk by datronicsoft · Forum · checked Nov 16, 2026
- A user reported on 27 August 2026 that 616.56 broke spacedesk virtual displays over IP and USB, with the display showing as connected but off, and that going back to driver 610.88 fixed it.
- The same user reported on 28 August 2026 that the display could not be extended or duplicated and that reverting to an older GPU driver was the only fix.
- GeForce GRD 621.14 Feedback Thread (Released 11/4/26)Community report
NVIDIA GeForce Forums · Forum · checked Nov 16, 2026
- Read on 16 November 2026. One reporter on an RTX 4080 Super states '621.14 make MH wilds flickering problem. I have to reversion to 610.88', an in-game flicker resolved by going back to 610.88.
- A reporter running an 8 bpc RGB-full HDMI monitor on an RTX 4060 laptop describes the external monitor washing out under 621.01 and 621.14: with Windows Automatic Colour Management off the whole monitor lifts as soon as a Chromium browser opens, and with it on any fullscreen app lifts whenever the mouse stops moving, matched with PresentMon to frames presented as 'Hardware: Independent Flip'.
- A separate reporter on 8 bpc RGB full documents blacks raised one to two levels while a display calibration is loaded, naming 591.74 as the last good driver and noting the effect is also present on 610.88 and 621.01 - a different fault from this flicker.
- GeForce GRD 621.24 Feedback Thread (Released 11/12/26)Community report
NVIDIA GeForce Forums · Forum · checked Nov 16, 2026
- Read on 16 November 2026. Display complaints continue on the current driver and 610.88 is still the version reporters go back to: one says 'The RTX 5090 Palit GameRock OC issue with black screens in the browser still hasn't been resolved; I think I'll stick with driver 610.88 for a while longer.'
- A consolidated report lists black screens, display initialisation failures, fullscreen failures, forced windowed mode, HDR instability and wake problems across releases after 610.88, and states 'In multiple independent cases, including my own, rolling back to 610.88 restores normal behavior.'
- A further reporter on an RTX 5090 with three 4K OLED displays states NVIDIA Surround loses signal on 616.92, 617.14, 617.42 and 621.24, and that '610.88 is the last version that works correctly' - a different symptom, but the same rollback target.
- The 8 bpc display-calibration reporter repeats the A/B test and records 'Bad: 621.24 and 621.14 (full A/B tests, identical results)'.
- No NVIDIA staff reply in the thread resolves the flicker reports.