From Singapore: When you pay upward of A$5,500 for a graphics card, the reasonable expectation is that a routine software update will not put the hardware at risk. That expectation took a hit this week when Nvidia pulled its freshly released GeForce Game Ready Driver 595.59 after a wave of user reports revealed the update was breaking fan control systems across a broad range of its own products.
Released on 26 February 2026 with day-one optimisations for path tracing, DLSS 4 multi-frame generation, and DLSS ray reconstruction, the 595.59 package was pulled by Nvidia within hours after users reported serious fan-control, clocking, and stability regressions across a range of GeForce hardware. The release was explicitly positioned as the Game Ready package for Resident Evil: Requiem, including support for path tracing, DLSS 4 with Multi-Frame Generation, and other modern RTX features. The timing could hardly have been worse.
Multiple users across forums and social platforms reported that hardware monitoring tools and vendor utilities suddenly displayed only one fan sensor, that manual fan profiles stopped being applied correctly, and in some cases one or more physical fans did not spin when expected, an issue that increases the risk of thermal runaway under load. A second group of complaints pointed to reduced boost behaviour after the update, with users reporting lower peak clocks and suggesting the driver limits GPU voltage to around 0.95V, which caps frequency on cards such as the GeForce RTX 5080 and RTX 5090.
Stability reports also appeared across separate threads, including black screens, VIDEO_TDR_FAILURE, nvlddmkm Event ID 153 crashes, freezes, and hard restarts, with one report describing idle desktop reboots with Kernel-Power Event ID 41 and BugcheckCode 270. These are not cosmetic annoyances. Fan control and thermal sensor reporting are among the most safety-critical functions a GPU driver performs.
Nvidia's GeForce team posted on its forum: "We have discovered a bug in the Game Ready and Studio 595.59 WHQL drivers and have removed the downloads temporarily while our team investigates. For users that have already installed this driver and are experiencing issues with fan control, please roll back to 591.86 WHQL." Nvidia acknowledged the bug, removed the downloads, and instructed users experiencing fan-control issues to roll back to 591.86 WHQL, explaining how to reinstall the previous driver via the Nvidia App by clicking the three dots in the Drivers tab, and recommending users post detailed reports to the Driver Feedback Forum if they continued to experience problems.
The thread responses and tests indicate the bug affected boards from Founders Edition to many third-party designs, spanning the RTX 3000 through RTX 5000 families. That is a remarkable breadth of exposure for a single driver release, and it raises a pointed institutional question: how did a WHQL-certified driver ship with faults this severe?
The crucial question is how a WHQL-certified driver with such a wide range of errors could go live in the first place. Internal QA, beta feedback, and telemetry should prevent precisely such scenarios. The symptom set varied by combination of GPU, motherboard, BIOS, and third-party utilities, suggesting the regression interacts with multiple driver subsystems: sensor enumeration, fan subsystem hooks, and possibly new power and voltage handling code. That complexity does not absolve Nvidia of accountability, but it does illustrate why GPU software is genuinely hard to test across millions of hardware configurations.
Defenders of Nvidia's approach would fairly point out that the company identified and responded to the problem within hours. AMD and Nvidia generally release drivers whenever a new major game drops to ensure that the new title will play well with their GPUs. That competitive pressure creates real incentives to ship fast, and the sheer variety of PC hardware combinations means some failures will only surface at scale. Driver development for a platform as diverse as the Windows ecosystem is not a problem any company has fully solved. Nvidia's willingness to publicly acknowledge the bug and issue clear rollback instructions is a better outcome than silence or delay.
Even so, this is not an isolated incident. RTX 30 and 40-series GPUs ran into BSODs, system instability, and game-breaking bugs in March 2025 when the company dropped new drivers that were seemingly built for the new RTX 50-series GPUs. Nvidia also released an emergency fix in November 2025 after Microsoft's KB5066835 update affected gaming performance on several titles on Windows 11 25H2 and 24H2 PCs. Three significant driver quality events in roughly 12 months is a pattern, not an anomaly, and it warrants genuine scrutiny of how the company structures its release cadence and testing.
For Australian consumers, the stakes are higher than they used to be. In January 2026, average prices for entry-level variants of the RTX 5080 had already climbed to A$1,899, while the cheapest RTX 5090 cards rose 15.2% in just two months, from A$4,832 in November 2025 to A$5,566. Buyers committing that kind of capital to a GPU are entitled to expect that a routine driver update will not leave their investment at risk of thermal damage. Consumer protection obligations under the Australian Consumer Law are clear that products, including the software required to operate them, must be fit for purpose. Whether a faulty driver update triggers those guarantees is a question worth monitoring if Nvidia does not resolve the issue cleanly.
The incident is particularly damaging at a time when software features such as DLSS are increasingly being sold as a key differentiating factor for Nvidia hardware. Whether 595.59 goes down as a one-off outlier or a symptom of accelerated release cycles remains to be seen. The answer will depend less on what Nvidia says and more on whether the replacement driver ships with the kind of cross-platform testing rigour that should have been applied the first time. Reasonable people can debate how much pressure the game-launch cadence puts on driver teams, but the bottom line for consumers is straightforward: a company charging premium prices for premium hardware must hold its software to the same standard.
If you have already installed driver 595.59, the recommended path is to open the Nvidia App, select the Drivers tab, click the three dots, and choose Roll Back Driver. If that option is greyed out, the driver can be removed via Windows Device Manager before reinstalling 591.86 WHQL directly from Nvidia's website.