As reported by VideoCardz and detailed in NVIDIA's official Customer Care and GeForce forum disclosures, this optional driver package (617.70-desktop-notebook-win10-win11-64bit-international-dch.hf.exe) is built directly atop the recent GeForce 617.42 WHQL release. If you do not own a 360Hz display exhibiting these exact symptoms, you can safely skip this download—internally, it is identical to 617.42 WHQL in every other respect. For competitive players who have been watching their frame counters mysteriously stall out or their monitors blink mid-firefight, however, 617.70 is a long-awaited relief valve, even if it comes with a few important caveats attached.
What GeForce Hotfix 617.70 Actually Fixes
NVIDIA's engineering teams typically reserve hotfix releases for bugs that are too disruptive to wait for the next full WHQL certification cycle, or that require targeted field validation before being merged into the mainline Game Ready branch. According to NVIDIA's QHD 360Hz Pulsar Monitors Changelog on the GeForce forums, the fixes in 617.70 had previously been targeted for standard driver releases before slipping past scheduled windows, prompting the company to push them out as a standalone hotfix while broader quality assurance continues.
The update targets two specific bug IDs:
- G-SYNC Pulsar 320 FPS Drop (Bug ID 6408986): When gaming on a 360Hz G-SYNC Pulsar monitor, frame rates could inexplicably drop and hover around approximately 320 FPS. Alongside the lost headroom, affected users reported a noticeable uptick in input latency when the cap engaged. NVIDIA previously confirmed it had found the root cause of the behavior, and 617.70 delivers the driver-side remediation.
- QHD 360Hz Gameplay Black Flashes (Bug ID 4846825): Gamers running QHD (2560×1440) monitors at 360Hz experienced occasional, brief black screen flashes during active gameplay. Earlier entries in NVIDIA's Pulsar forum changelog characterized this issue as a roughly two-second black screen occurring on GeForce RTX 30-series and RTX 40-series graphics cards at 360Hz, where the display momentarily lost video signal while the game continued running underneath. While the official 617.70 release notes broaden the description to QHD monitors running at 360Hz without specifying GPU generations, the fix directly targets that signal-dropout behavior.
Section Summary: GeForce Hotfix 617.70 branches off the 617.42 WHQL codebase exclusively to resolve bug 6408986 (a ~320 FPS drop on 360Hz G-SYNC Pulsar displays) and bug 4846825 (momentary black screen flashes during gameplay on 360Hz QHD monitors).
Understanding the Hardware Context: Why G-SYNC Pulsar Is Different
To understand why these bugs have been so thorny to untangle, it helps to look at how G-SYNC Pulsar monitors are architected compared to traditional variable refresh rate (VRR) displays. First-generation 27-inch 1440p 360Hz Pulsar monitors—developed in partnership with MediaTek—departed from NVIDIA's legacy hardware blueprint by integrating G-SYNC Pulsar technologies directly into the display scaler rather than relying on a separate, dedicated G-SYNC hardware module.
Pulsar itself is a dual-discipline timing trick: it combines variable refresh rate synchronization with variable overdrive and advanced backlight strobing to deliver simultaneous motion clarity and tear-free rendering. Because the GPU driver, the display pipeline over DisplayPort or HDMI, and the MediaTek scaler firmware must stay in lockstep within tight microsecond windows at 360Hz (where each frame budget is roughly 2.77 milliseconds), any power-state hiccup or timing drift in the Windows display driver can trigger weird edge cases. A sudden drop from 360 FPS to 320 FPS—or a momentary loss of display sync resulting in a two-second black flash—is the classic signature of a display pipeline miscalculating blanking intervals or clock states under load.
Back in March 2026, NVIDIA rolled out a web-based firmware update tool (utilizing the monitors' Micro-B USB port) to resolve low-FPS visual artifacts on these displays. The issues tackled in 617.70, however, lived on the host PC side inside the GeForce display driver stack.
Section Summary: G-SYNC Pulsar relies on tight coordination between the Windows GPU driver and scaler-integrated synchronization hardware to manage simultaneous VRR and backlight strobing at 360Hz, making driver-level timing and power-state bugs particularly noticeable.
The Catch: Black Screens Aren't Dead Yet (Plus a Step-by-Step Workaround)
In a welcome bit of transparency, NVIDIA is not claiming total victory over the 360Hz black-screen phenomenon just yet. In its official hotfix notes, the company explicitly cautions that driver 617.70 resolves some, but not all, cases of the black-screen flashing issue. NVIDIA's driver engineers are still investigating the remaining edge cases for a comprehensive fix in a future release.
If you install 617.70 and your 360Hz QHD display still occasionally blinks out mid-match, why is that happening? General industry knowledge of high-refresh display pipelines points to aggressive GPU clock-state transitions (P-states): when a modern GeForce card briefly downclocks during a less demanding scene or menu transition, the sudden voltage and frequency shift can momentarily destabilize high-bandwidth display links.
To combat this, NVIDIA recommends a specific temporary workaround for users who still experience black flashes after installing 617.70:
- Right-click on an empty area of your Windows 10 or Windows 11 desktop and open the NVIDIA Control Panel (under Show more options on Windows 11 if using the default context menu).
- In the left-hand navigation pane, expand 3D Settings and click on Manage 3D settings.
- Under the Global Settings tab (or the Program Settings tab if you prefer to isolate the change to specific games), scroll down the feature list to locate Power management mode.
- Change the setting from Normal to Prefer maximum performance.
- Click Apply in the bottom-right corner of the window.
- Restart your PC. NVIDIA explicitly notes that a full system reboot is required for this workaround to take proper effect against the black-screen bug.
Keep in mind that setting Prefer maximum performance globally will prevent your GPU from dropping into its lowest idle power states on the Windows desktop, which increases idle power draw and baseline heat output. If you only experience black flashes in one or two specific competitive titles, applying that setting via per-game profiles—or remembering to revert it once a future WHQL driver permanently resolves bug 4846825—is the smart play for your electric bill.
Section Summary: Hotfix 617.70 only partially resolves the 360Hz QHD black-screen bug. Users who still encounter black flashes should set Power management mode to Prefer maximum performance in the NVIDIA Control Panel and reboot their system.
The Unresolved Sleep Bug and What to Watch Out For
Before you rush to install 617.70 expecting every G-SYNC Pulsar quirk to vanish, there is one major known issue that remains completely untouched by this release.
According to NVIDIA's QHD 360Hz Pulsar changelog, a separate bug persists where G-SYNC (and consequently G-SYNC Pulsar) becomes unavailable after the monitor enters sleep mode. NVIDIA has confirmed that its engineers have reproduced this sleep-wake defect internally, and while monitor firmware version 1.1.8 was previously floated as a partial mitigation, it did not resolve the problem across all configurations. Right now, a permanent driver-side fix for the monitor sleep bug carries an official status of "ETA TBD". Until that patch materializes, users whose Pulsar toggles vanish after walking away from their desks will still need to rely on cycling the monitor's power or reinitializing the display connection when waking their PCs.
There are also a couple of practical housekeeping details for Windows users considering the 617.70 package:
- Not in the NVIDIA App: Because this is a beta-track hotfix, it will not show up in the automatic update feed inside the NVIDIA App. You must grab the 64-bit DCH installer directly through NVIDIA's Customer Care support portal or official GeForce forum release thread. Furthermore, as noted in community discussions tracking the release, installing the hotfix may cause the NVIDIA App to display an older driver publication date because hotfix releases are not indexed in the app's standard WHQL database.
- Anti-Cheat Whitelisting: As documented in GeForce community driver advisories, kernel-level anti-cheat systems in competitive multiplayer games occasionally take a day or two to whitelist newly issued hotfix driver components, as hotfixes use different attestation and testing certificate signatures than full WHQL releases. If your favorite shooter balks at launching immediately after installing 617.70, rolling back to 617.42 WHQL is quick and painless.
| Issue / Attribute | Status in GeForce Hotfix 617.70 | Official Guidance / Notes |
|---|---|---|
| Base Driver Version | Based on GeForce 617.42 WHQL | Identical to 617.42 outside of the two targeted 360Hz fixes. |
| Supported OS | Windows 10 & Windows 11 (64-bit DCH) | Single combined installer for desktop and notebook GPUs. |
| Bug 6408986 (320 FPS drop on 360Hz Pulsar) | Fixed | Resolves frame-rate drop to ~320 FPS during Pulsar gameplay. |
| Bug 4846825 (Black flashes on 360Hz QHD) | Partially Fixed | Fixes some cases; remaining cases require Control Panel power workaround + reboot. |
| G-SYNC / Pulsar lost after monitor sleep | Unresolved (ETA TBD) | Reproduced internally by NVIDIA; not addressed in 617.70. |
Should You Install It?
Our advice on hotfix drivers at WindowsForum.com never wavers: treat them like prescription medication. If you are gaming on a 360Hz G-SYNC Pulsar display that refuses to push past 320 FPS, or if your 360Hz QHD monitor is treating you to random two-second blackouts, GeForce Hotfix 617.70 is made specifically for your rig and is well worth the manual download. Everybody else—whether you are running a 144Hz ultrawide, a 240Hz OLED, or a standard 60Hz office panel—should stay put on GeForce 617.42 WHQL and wait for these patches to graduate into the next mainline WHQL Game Ready Driver after NVIDIA wraps up its extended QA testing.
Have you been fighting the 320 FPS cap or the dreaded 360Hz black flash on your setup, and did 617.70 finally smooth things out for you? Drop your GPU model, monitor firmware version, and Windows build into our Graphics Cards and Display Drivers discussion threads here on WindowsForum.com to let fellow builders know how the hotfix is holding up.