technology

Nvidia rushes out emergency driver patch after february flop

Nvidia just dropped GeForce 595.97 WHQL at 03:00 Pacific, a silent admission that the February 595.59 package turned high-end GPUs into expensive paperweights. Clock-speed spikes, fan-detection failures, and sudden game freezes forced weekend warriors to roll back or simply stop playing.

The body count inside 595.59

Internal telemetry leaked to TechCurrent shows 1.3 million crash reports in the first ten days, with Halo Infinite texture corruption topping the chart. Frame-time graphs looked like saw blades; GPUs idled at 1,950 MHz then slammed into 95 °C in seconds. Reddit threads ballooned to 12 k comments, most ending with “rolled back to 551.86”.

The new code line-by-line: a forced 40 ms polling loop for fan RPM, tighter voltage/frequency curves for Ada and Ampere, and an explicit mutex that keeps DLSS Frame Generation from tripping over Instant Replay. Early beta testers report the combo no longer bombs to desktop after 18 minutes of Call of Duty.

What still stutters

What still stutters

Not every bullet wound is bandaged. Enshrouded terrain still vanishes in the Revelwood, and Arknights: Endfield hitches every 47 seconds on RTX 5090 cards—an esoteric bug tied to PCIe 5.0 link-state transitions, according to an Nvidia engineer I pinged on Discord. A hotfix is penciled for late May.

If you never touched those titles and your rig is humming along, skip this round—595.97 brings zero performance uplifts in synthetic benches. But if you own a 40- or 50-series card and value stability over curiosity, pull the driver straight from GeForce Experience or the official portal; third-party repacks are already injecting crypto miners under the hood.

Nvidia’s driver division is bleeding talent—three senior architects exited last quarter, lured by AI startups promising million-dollar RSUs. Until the exodus stops, gamers will keep beta-testing in production. Grab 595.97, but keep the rollback option warm; the next fire drill is already queued.