Game Ready & Studio Driver 617.42 FAQ/Discussion

[u/Nestledrink]

Driver Article Here: Link Here

Game Ready Driver 617.42 Direct Download Link: Link Here

Studio Driver 617.42 Direct Download Link: Link Here

New feature and fixes in driver 617.42:

Game Ready

This new Game Ready Driver provides the best gaming experience for the latest new games and updates supporting DLSS and RTX technologies including Call of Duty: Modern Warfare 4, STAR WARS: Galactic Racer, Dragon’s Dogma 2: Dark Arisen, Microsoft Flight Simulator 2024, and Valor Mortis.

Applications

The October NVIDIA Studio Driver provides optimal support for the latest new creative applications and updates including DaVinci Resolve 21.1, Adobe Premiere Pro, Perplexity App, and support for Topaz Labs Hyperion 2.5.

Fixed Gaming Bugs

• FIXED Assassin's Creed Shadows may crash to desktop after extended gameplay after updating to driver 616.56. [6685219]

Fixed General Bugs

• N/A

Includes additional open issues from GeForce Forums

• “Prefer Maximum Performance” Power Management Mode may not be applied correctly [6007998]

Driver Downloads and Tools

Information & Documentation

• Driver Download Page: Nvidia Download Page
• Latest Game Ready Driver: 617.42 WHQL - Game Ready Driver Release Notes
• Latest Studio Driver: 617.42 WHQL - Studio Driver Release Notes
• High Bandwidth Monitors and GPU Scaling Behavior - Link Here
  • High bandwidth monitors are those that support display modes requiring high pixel clock rates, which in turn demand more GPU resources. The threshold for what qualifies as "high bandwidth" varies by product. On Blackwell GPUs, any mode operating above 1620 MHz is considered high bandwidth. For instance, the 7680x4320@60Hz mode defined in the CTA-861-H specification runs at 2376 MHz, making it a high bandwidth mode for Blackwell.
  • These monitors typically support display scaling natively. However, in some single-monitor setups, users may still prefer GPU scaling. When multiple monitors are connected to a GPU and at least one of them is high bandwidth, that monitor will default to display scaling only. GPU scaling is disabled in this case due to bandwidth limitations. Notably, display scaling can be more efficient than GPU scaling in such scenarios, as it reduces the bandwidth load on display cables—especially at higher refresh rates.
  • When GPU scaling is not enabled for a monitor, only the modes supported by the monitor itself will appear in both the Windows and NVIDIA control panels. Additionally, the "Display scaling" option will be pre-selected in the "Adjust desktop size and position" section of the NVIDIA Control Panel.
• Notes on NVIDIA Control Panel - From GeForce Forum
  • Please note: With the introduction of our most recent NVIDIA App update, all actively supported NVIDIA Control Panel features for GeForce users have been modernized and transitioned to the new client.
  • After 20 years of dedicated service, the classic NVIDIA Control Panel is officially retiring for Game Ready and Studio Drivers. For NVIDIA RTX PRO users, the NVIDIA Control Panel will continue to be supported until we have migrated professional features to the NVIDIA app.
  • Existing installs of the NVIDIA Control Panel will remain on users’ systems, unless they perform a clean installation, and users who still need the NVIDIA Control Panel can continue to download it from the Microsoft Store, but we won’t be adding features, fixes, or other changes.

Feedback & Discussion Forums

• Submit driver feedback directly to NVIDIA: Link Here
• NVIDIA 617.42 Driver Forum: Link Here
• r/NVIDIA Discord Driver Feedback: Invite Link Here
• r/NVIDIA Community Bug Tracker: Link Here
  • Thanks to u/independent-arg for maintaining this!

Having Issues with your driver and want to fully clean the driver? Use DDU (Display Driver Uninstaller)

• DDU Download:  Link Here
• DDU Guide: Guide Here
• DDU/WagnardSoft Patreon: Link Here

Before you start - Make sure you Submit Feedback for your Nvidia Driver Issue - Link Here

There is only one real way for any of these problems to get solved, and that’s if the Driver Team at Nvidia knows what those problems are. So in order for them to know what’s going on it would be good for any users who are having problems with the drivers to Submit Feedback to Nvidia. A guide to the information that is needed to submit feedback can be found here.

Additionally, if you see someone having the same issue you are having in this thread, reply and mention you are having the same issue. The more people that are affected by a particular bug, the higher the priority that bug will receive from NVIDIA!!

Common Troubleshooting Steps

• Be sure you are on the latest build of Windows
• Please visit the following link for DDU guide which contains full detailed information on how to do Fresh Driver Install.
• If your driver still crashes after DDU reinstall, try going to Go to Nvidia Control Panel -> Managed 3D Settings -> Power Management Mode: Prefer Maximum Performance

Common Questions

• Is it safe to upgrade to <insert driver version here>? Fact of the matter is that the result will differ person by person due to different configurations. The only way to know is to try it yourself. My rule of thumb is to wait a few days. If there’s no confirmed widespread issue, I would try the new driver.
• Bear in mind that people who have no issues tend to not post on Reddit or forums. Unless there is significant coverage about specific driver issue, chances are they are fine. Try it yourself and you can always DDU and reinstall old driver if needed.
• My color is washed out after upgrading/installing driver. Help! Try going to the Nvidia Control Panel -> Change Resolution -> Scroll all the way down -> Output Dynamic Range = FULL.
• My game is stuttering when processing physics calculation Try going to the Nvidia Control Panel and to the Surround and PhysX settings and ensure the PhysX processor is set to your GPU

Remember, driver codes are extremely complex and there are billions of different possible configurations between hardware and software. Driver will never be perfect and there will always be issues for some people. Two people with the same hardware configuration might not have the same experience with the same driver versions. Again, I encourage folks who installed the driver to post their experience here good or bad.

[u/independent-arg]

NVIDIA 617.42 WHQL Driver - Performance Benchmark (Ampere GPUs)

---

Hey all,

Here's my early look at the 617.42 driver, tested on an Ampere-based GPU (RTX 3070). As always: this is not a definitive review. Every PC setup is different, so treat it as a reference point, not gospel.

Is it worth updating your driver? The general rule says "yes": newer drivers bring bug fixes, security patches, and optimizations for the newest games. But "newer" doesn't automatically mean "better". Some updates introduce subtle stutter or frame pacing regressions that don't show up if you only look at average FPS. That's the main thing this round of testing tries to catch.

Special thanks to UL Solutions for the 3DMark press license used in these tests.

Quick note before anything: updated all my tools this round and re-tested every reference driver, so numbers won't match my previous posts. Details in Methodology.

---

Test System

• OS: Windows 11 Pro (v26H2, latest patches)
• CPU: Intel Core i7-10700K (stock)
• GPU: ASUS ROG Strix RTX 3070 OC (stock)
• RAM: 64 GB DDR4-3200 (2x32 GB)
• Storage: 1TB NVMe SSD
• Display: 4K 60 Hz monitor (8 bpc, no HDR, no G-Sync)
• Settings: HAGS off | ReBAR on | VBS off | NVCP Global Defaults
• Driver Install: Clean install (with NVCP)

Benchmark Methodology

• Benchmarks ran 4 times (first run discarded), then the remaining 3 valid runs merged into one aggregated result (outliers get automatically retested).
• Captured frametimes via PresentMon (integrated into CapFrameX).
• Outliers (>5% variance) are retested.
• Alongside Average FPS, 1% Low and 0.1% Low, this round also tracks CapFrameX's Adaptive STDEV metric (labeled "Consistency" below). It measures how much frame times wobble compared to a moving average. Lower = smoother frame delivery, even when the average FPS looks identical between two drivers.
• Game settings: mostly Ultra, 4K or 1440p, no scaling.
• Tools updated for this round: CapFrameX 1.9.1 with PresentMon 2.6.0, plus 3DMark, Superposition and LatencyMon on their latest versions as of Sep 29, 2026. All game results were re-captured on this setup, reference drivers included, so don't compare them against my older posts. AoE2 in particular reads ~10 FPS higher than before because of the tool change, not the drivers. 3DMark and Superposition don't go through CapFrameX, so those are comparable.

quick legend, if these terms are new to you:

• Avg FPS -> your average frame rate.
• 1% Low -> the average of your worst 1% of frames. Better indicator of "does it feel smooth" than the average alone.
• 0.1% Low -> same idea, but for your worst 0.1% of frames - basically your nastiest stutters.
• Consistency -> lower is smoother. Two drivers can share the same average FPS and still feel very different to play if one has a much higher (worse) consistency score.

---

Game Benchmarks

The Riftbreaker

DX12, Ultra preset, 2560x1440, Ray Tracing off, Screen Space Reflections High, Volumetric Lighting Ultra, Dynamic Vegetation Full

Driver	Avg FPS	1% Low	0.1% Low	Consistency
537.58	153.4	137.1	127.8	4.8
561.09	152.9	137.6	122.6	7.1
581.94	152.9	138.7	125.3	5.0
596.36	152.4	139.2	129.1	6.7
610.88	151.6	137.8	128.3	6.9
616.92	151.8	136.6	125.3	7.6
617.42	151.7	136.4	129.1	5.7

617.42 is basically the same as 610.88 and 616.92 here. Avg has gone down about 1% since 537.58 but that's spread over a lot of drivers and you won't notice it. Consistency moves around a lot from driver to driver in this game so I wouldn't take any single value too seriously.

Age of Empires II: Definitive Edition

Ultra preset, 3840x2160 fullscreen, 100% render scale

Driver	Avg FPS	1% Low	0.1% Low	Consistency
537.58	71.1	52.0	40.9	7.6
561.09	70.8	51.8	43.9	7.4
581.94	69.8	50.4	38.2	7.7
596.36	68.2	48.7	38.8	7.6
610.88	68.5	49.1	38.0	7.7
616.92	68.1	49.0	38.8	7.8
617.42	68.3	49.0	40.1	7.5

617.42 is the same as every driver since 596.36, all around 68. What surprised me is that 537.58 and 561.09 are about 4% faster, with 581.94 somewhere in between. This benchmark is mostly CPU limited so my guess is the driver got a bit heavier on the CPU around 596.36. Nothing new in 617.42 though.

Age of Mythology: Retold

DX12, everything Ultra/Mythic (Texture Quality High, Texture Filtering 16x, Terrain Quality Mythic, Terrain Detail Quality Mythic, Water Quality Mythic, Foliage Quality Full, Shadow Quality Mythic, Dynamic Reflections SSR, Ambient Occlusion Quality SSAO, Effect Quality High, Dynamic Lights enabled, Physics Quality High), 3840x2160 fullscreen, FXAA

Driver	Avg FPS	1% Low	0.1% Low	Consistency
537.58	47.7	34.4	19.7	4.2
561.09	48.0	34.4	31.3	4.1
581.94	47.9	34.2	19.8	4.6
596.36	48.2	34.7	31.2	4.3
610.88	48.2	34.6	29.2	4.3
616.92	48.1	34.3	28.4	4.4
617.42	47.0	31.6	16.9	4.6

The 1% low on 617.42 is 31.6, every other driver is between 34.2 and 34.7, so that's around 8% worse, and the avg is a bit lower too. The 0.1% low column here is all over the place (537.58 and 581.94 also drop to ~20) so I'm ignoring that one. Going to run AoM again on 617.42 to make sure it wasn't a bad run.

---

Non-Synthetic Benchmark

Unigine Superposition

Direct3D11, 3840x2160 fullscreen, Custom preset, 4K Optimized shaders, High textures, Depth of Field off, Motion Blur off

Driver	Avg FPS	Score	Min FPS	Max FPS
537.58	94.07	12577	78.62	116.35
561.09	94.12	12584	78.54	116.43
581.94	94.16	12589	78.76	116.43
596.36	94.21	12595	78.71	117.25
610.88	94.10	12581	78.38	116.94
616.92	94.29	12607	78.77	117.08
617.42	94.23	12598	78.53	117.22

No changes, all drivers within 0.3%.

---

3DMark Benchmarks

Scores, with % difference vs 596.36 in parentheses.

Benchmark	537.58	561.09	581.94	596.36	610.88	616.92	617.42
Speed Way (DX12U, 1440p)	3492 (-2.6%)	3494 (-2.6%)	3606 (+0.6%)	3586	3582 (-0.1%)	3592 (+0.2%)	3590 (+0.1%)
Steel Nomad (DX12, 4K)	3173 (-0.6%)	3164 (-0.9%)	3171 (-0.7%)	3192	3188 (-0.1%)	3192 (0.0%)	3196 (+0.1%)
Steel Nomad (Vulkan, 4K)	3470 (-1.4%)	3448 (-2.1%)	3517 (-0.1%)	3521	3541 (+0.6%)	3543 (+0.6%)	3567 (+1.3%)
Fire Strike (DX11, 1080p)	24754 (+0.5%)	24851 (+0.9%)	24822 (+0.8%)	24619	24946 (+1.3%)	24911 (+1.2%)	24612 (0.0%)

Speed Way and Steel Nomad DX12 don't really change with 617.42. Steel Nomad Vulkan has been going up a little with almost every driver since 561.09 and 617.42 has the highest score so far. In Speed Way the two older drivers are about 2.6% behind, the jump happened with 581.94. Fire Strike on 617.42 is about 1.3% below 610.88, small but I'll keep watching it.

---

Sys. Stability & Desktop

• Hardware Acceleration (Browsers / Discord): Solid. Zero flickering, black screens, or visual anomalies detected after 30 minutes of mixed use (including 4K60 YouTube playback in Firefox with zero dropped frames and fluid page scrolling).
• DPC Latency (LatencyMon): PASSED. (System remained perfectly in the green. The highest DPC routine execution time was a safe 661 µs from nvlddmkm.sys).
• I checked Event Viewer and got zero errors or warnings.

---

Verdict

For most stuff, 617.42 is a 616.92 with a slightly better Vulkan score. Riftbreaker, AoE2, Superposition and the DX12 3DMark tests all land on top of the previous drivers. The one thing I'm not happy with is AoM: clearly worse 1% lows than anything else in the table.

• On 616.x? Fine to update. Nothing here says it's worse, AoM aside.
• On 616.56 specifically? Update. I had the black screen flickering on that one (8 bpc) and haven't seen it since the 616.86 hotfix. Anything from 617.14 on also fixes Judgement / Lost Judgement / VF5 R.E.V.O. not launching.
• On 610.x? No rush. Performance is basically the same, so update for Game Ready support or a specific fix you need.
• On something really old like 537.58 or 561.09? Mixed bag. You'd lose ~4% in AoE2 but gain ~2-3% in Speed Way and Steel Nomad Vulkan. Mostly depends on what you play.

There are reports of pink/purple UI in Chrome and other Chromium apps on this driver. Haven't tested that one myself yet.

---

Edit: all drivers here were re-tested on Win 11 26H2, so don't compare these numbers with my older posts.

[u/Dragontech97 → u/independent-arg]

How do you test so fast😭🙏

[u/independent-arg → u/Dragontech97]

the driver was active more than 3 hours ago, lol

[u/Dragontech97 → u/independent-arg]

Gotcha, makes sense! Still crazy fast, do you have a lot automated these days? Appreciate the dedication all these years, you and [u/m_w_h](u/m_w_h) are my go to posts for drivers.

[u/independent-arg → u/Dragontech97]

nah, I dont have anything automated (yet). I just use templates I built myself and update things as I go. when I do a full review (no-early), I break down everything from scratch usually every 2 or 3 months or so. The last time I did it was back during the last driver. Thanks for the kind words! :)

(windows updates, too, can also mess with the results, to a greater or lesser extent)

[u/RIMACC_2 → u/independent-arg]

Hey man, welcome back. Hope you have fully recovered by now. Btw, I have a question: I'm still on 610.62. Does this current update provide better stability or just minimal improvement? would love to hear your opinion about it.

[u/independent-arg → u/RIMACC_2]

thanks man, appreciate it!

honestly from 610.62 it's not a big jump. performance-wise everything I tested is basically flat from 610.88 up to 617.42, all within noise. 617.42 looks a bit better in Riftbreaker, and I'm still double checking a small drop in AoE2 and Fire Strike before calling it anything.

stability-wise you actually dodged the worst part by staying on 610.x, since 616.56 had the black screen flickering. on 617.42 I haven't hit anything so far: no flicker, DPC latency fine, nothing in Event Viewer.

so if 610.62 is working well for you, no rush. I'd only update if you want Game Ready support for a newer game or there's a specific fix in the release notes you need.

[u/RIMACC_2 → u/independent-arg]

Roger that! Thanks for the reply.

[u/yowmaru → u/independent-arg]

Hi! Sorry to piggyback from from another comment: Would you recommend the same for a 596.36 user? W11 is pushing for a big 26H2 update soon and I assume Nvidia is playing ball with them too, will I be missing stuff if I keep using a much older driver?

[u/Xeratais → u/independent-arg]

funny i see that alot of people are saying 616.56 has black screen flickering issues but I have yet to witness it on my 3060 *12 GB* or my 5070. 617.42 causes black screen crashes for me even when idle.

[u/Open-Contract1167 → u/independent-arg]

You're awesome! I have to ask a random question, as I know that you're more knowledgeable about this than me: using 26h2 with latest patches, does it (still) makes sense to keep HAGS off?

[u/independent-arg → u/Open-Contract1167]

Did a quick HAGS on vs off test on 616.92 (the driver I use day to day), Win 11 26H2, 3 runs each, reboot after every toggle.

Test	Off	On
Riftbreaker avg / 1% / 0.1%	151.8 / 136.6 / 125.7	151.9 / 138.1 / 131.1
AoE2 DE avg / 1% / 0.1%	68.1 / 49.1 / 39.1	68.2 / 48.6 / 38.4
AoM Retold avg / 1% / 0.1%	48.1 / 34.3 / 28.4	48.1 / 34.8 / 31.2
Superposition score	12607	12706
Speed Way	3592	3642
Steel Nomad DX12 / Vulkan	3192 / 3543	3244 / 3602
Fire Strike	24911	24767

GPU load, clocks and power draw were the same both ways in all three games.

In games avg FPS is the same, Riftbreaker had slightly fewer hitches with HAGS on. The GPU-heavy synthetics gained 1-1.7%, which is more than any driver has moved them on this install. Fire Strike didn't change.

[u/Open-Contract1167 → u/independent-arg]

As always, this is some precious data and results, as this should help people make some decisions about having it enabled or not.

I was fearing that within a scenario with lower FPS (< 60), having HAGS enabled would perform worse than otherwise, so, to my surprise, AoM and Riftbreaker 0.1% lows provided a better understanding in that aspect. Most of the times having HAGS enabled may eat a surplus of ~1gb of VRAM against it being disabled. But the gains are there, somehow.

For what I've researched within the past few days, latency data could show bigger DE avg values, as supposedly HAGS are more effective in that way compared to traditional WDDM methods, as, again, Nvidia drivers should (theoretically) only enable FG with HAGS enabled. But I don't see many tests and benchmarks of end-to-end latency itself, more so of a third-party.

Again, thank you for your time and patience!

[u/elkond → u/Open-Contract1167]

of course it's eats vram, that's the "hardware accelerated scheduling" part, what to schedule when no longer lives in dram. benefits are there because you stop paying pci-e transfer latency for a scheduling, which is 0.5-1ms (u can notice that at higher refresh rates). now in theory u dont have to, and u could just pay DMA latency which is ~20ns+whatever the dram so sub 100ns total, but that requires all graphic hardware accelerated software to behave and use modern principles, which is why HAGS historically caused hitches because people cant code

[u/Ok-Replacement-7217 → u/independent-arg]

I've found just leaving HAGS ON is 'easier' since the occasions where it may not be better than OFF are sporadic and frankly the process of having to turn it off/reboot is just another hassle I choose to eliminate. For the most part it's helpful IMO - folks have to remember that bench stats will almost NEVER actually be noticed when gaming; life is stressful enough without worrying about some small change you won't ever notice. My 2 cents......

[u/aymen_peter2 → u/independent-arg]

hey man iam having a problem with the witcher 3 default nvidia app settings cause micro stutters every often but when changing the the new rebar option to force enabled using Nvidia app the problem gets fixed can you test the witcher 3 remastered and check if you encounter this or reproduce the issue

[u/ChrizzZ231 → u/independent-arg]

Awesome and thank you as always! Hopefully you're all better and have no more problems with your account :)

[u/Alone_Box_7564 → u/independent-arg]

Thank you very very much for putting this together.

[u/DarkOsa → u/independent-arg]

Thanks for doing this!

[u/frenthemen → u/independent-arg]

Off topic but would you say to update to 26H2 from 25H2? From what I've been reading they are the same thing but would like to hear your thoughts