NVIDIA released GeForce Hotfix Driver 617.70 as an out-of-band patch built on 617.42 WHQL that addresses two high-refresh-rate display bugs. The first fixes an unintended 320 FPS cap on 360Hz G-SYNC Pulsar monitors, while the second only partially resolves black flashes on 360Hz QHD displays (Bug IDs 6408986 and 4846825). It doesn't touch a third problem, G-SYNC disappearing after a monitor wakes from sleep, and can't be installed through the NVIDIA App. NVIDIA says only affected users should install it, and offers a "Prefer Maximum Performance" workaround for the remaining black flashes.

NVIDIA Pushes GeForce Hotfix Driver 617.70 to Kill (Some) 360Hz Display Bugs

If you've got a 360Hz G-SYNC Pulsar monitor and a genuine hatred for black screens, NVIDIA just handed you something to install, and something to shrug about.

The company released GeForce Hotfix Display Driver 617.70 , a targeted out-of-band patch built on top of the 617.42 WHQL Game Ready Driver. It aims at two high-refresh-rate display bugs that have nagged a vocal subset of PC gamers running GeForce cards on Windows 10 and Windows 11.

There's a catch. The black-flash problem gets only a partial fix. And a third issue entirely, G-SYNC dropping out after your monitor wakes from sleep, is left alone. If you're in the affected crowd, this one's worth a look. If not, keep reading before you waste a download.

What 617.70 Actually Fixes

The first headline bug is Bug ID 6408986, which covers games on 360Hz G-SYNC Pulsar monitors dropping to roughly 320 FPS. Users also noticed input latency creeping in whenever that cap engaged. NVIDIA had already found the cause, and 617.70 delivers the driver-side remedy. This is a correction to broken behavior, not a speed boost, so don't expect it to squeeze extra frames out of your games. It just removes an unwanted ceiling that was otherwise-capable panels stuck at around 320 FPS.

The second fix, Bug ID 4846825, targets the flashes themselves. These occur on QHD (2560×1440) monitors running at 360Hz. Earlier reports tied the issue to RTX 30 and RTX 40 series GPUs, with the display briefly dropping its image while the game kept running underneath. NVIDIA described it as about a two-second black screen where the display momentarily lost its video signal.

Here's the part worth underlining. NVIDIA says 617.70 only fixes some cases of the flash. The rest are still being investigated, with no estimated release date for a broader fix. NVIDIA framed it the way it always frames hotfixes, saying in its official note that these drivers "are basically the same as the [previous released driver]" and exist to get fixes out faster. The two had been slated for standard releases but "missed multiple release dates," per VideoCardz, which is why they got pushed separately while broader QA runs. It's arguably better to ship a partial fix you can name than to silently ship nothing, but NVIDIA could at least tell people what fraction of cases actually clears.

Spec-wise, 617.70 is a 64-bit DCH installer for Windows 10 and Windows 11, built on 617.42 WHQL. The file, 617.70-desktop-notebook-win10-win11-64bit-international-dch.hf.exe, runs about 634 MB. You grab it standalone from NVIDIA's servers. And no, you can't pull it from the NVIDIA App, GeForce Experience, or the auto-update feed. Hotfixes ride a different attestation certificate than full WHQL releases, so they sit outside that database. Expect the NVIDIA App to keep showing your last published WHQL date after installing.

A Workaround for Remaining Black Flashes

Some users will install 617.70 and still see flashes. NVIDIA's answer is to pin your GPU's clocks so it stops bouncing between power states.

Open NVIDIA Control Panel (on Windows 11, pick "Show more options" off the desktop right-click menu). Expand 3D Settings, then Manage 3D settings. Under Global Settings or Program Settings, find Power management mode and flip it from Normal to Prefer Maximum Performance. Apply it. Then reboot your PC, because a full restart is required for the change to stick.

The reasoning is sound. Aggressive clock-state transitions, the P-states, can destabilize high-bandwidth display links when the card briefly downclocks during quieter scenes or menu screens. Pinning the GPU at maximum keeps those transitions from happening. The trade-off is real though. You'll burn more power at idle and run a bit hotter, so applying it per-game and reverting once a real WHQL fix lands is the move for your electricity bill.

What Stays Broken (and Why Pulsar Is So Tricky)

Beyond the two headline fixes, the changelog documents one issue that 617.70 doesn't touch. G-SYNC, and G-SYNC Pulsar specifically, becomes unavailable after the monitor enters sleep mode. NVIDIA has reproduced this sleep-wake bug internally but offers no date for a fix. Status is officially "ETA TBD." Monitor firmware version 1.1.8 was floated as a partial mitigation but didn't clear it across every setup, so until a proper driver fix arrives, you're stuck cycling your monitor's power or reinitializing the connection when you wake the PC.

This is where the hardware gets interesting. First-gen 27-inch 1440p 360Hz Pulsar monitors, built with MediaTek, ditched NVIDIA's legacy hardware blueprint by baking G-SYNC Pulsar directly into the display scaler rather than using a separate module. Pulsar combines variable refresh rate, variable overdrive, and backlight strobing (ULMB 2) for what NVIDIA and ASUS market as up to 4x motion clarity over a normal LCD, phrased as "faster than OLED."

That's a lot to sync at 360Hz, where each frame gets only about 2.77 milliseconds. The GPU driver, the DisplayPort or HDMI pipeline, and the MediaTek scaler firmware have to stay locked together within tight microsecond windows. A single power-state hiccup or timing drift can trigger exactly these edge cases. A 320 FPS drop or a two-second black flash is basically the signature of a display pipeline miscounting blanking intervals under load. Known panels include the ASUS ROG Strix XG27AQNGV and ROG Swift PG27AQNR, plus MSI and AOC variants.

The firmware layer runs parallel to these driver bugs. In March 2026, NVIDIA shipped a browser-based firmware tool using the monitors' Micro-B USB port to clear low-FPS visual artifacts, which kicked off a line of updates. Firmware 1.1.6 improved G-SYNC Pulsar operation in the 100 to 180 FPS range and fixed EDID white-point and input auto-detection. 1.1.8 added lower 240Hz input lag and served as a partial-but-incomplete fix for the sleep-wake issue. 1.1.10 targets sub-1ms motion persistence while reducing cases where Pulsar disengages during visually dense scenes. Oddly enough, that firmware doesn't fix the 320 FPS or input-lag bug that 617.70 handles on the host side. The fixes live in the GeForce driver stack, not the monitor, so a firmware update alone can't clear these problems.

Who Should Install and Where to Get It

Do install 617.70 if you game on a 360Hz G-SYNC Pulsar monitor that won't push past roughly 320 FPS, or if your 360Hz QHD panel is throwing random black flashes. This patch is built for exactly those rigs.

Skip it if you're on a 144Hz ultrawide, a 240Hz OLED, or just a standard panel. For everyone else, staying on 617.42 WHQL and waiting for these to graduate into the next mainline Game Ready Driver is the safer call. One heads-up on anti-cheat, though. Kernel-level anti-cheat systems in competitive shooters can take a day or two to whitelist a freshly issued hotfix, since these use different testing certificates than full WHQL builds. If a game balks at launching right after install, a clean rollback with Display Driver Uninstaller, aka DDU, is the recommended route.

Head here to the download.