Battlefield 6 launched its long-awaited Season 4 naval warfare expansion on July 21, 2026, but for many PC players the first day on the new Tsuru Reef map ended not with a victory, but with a DirectX crash. EA has now confirmed that GeForce RTX 50 Series owners on Nvidia’s latest Game Ready driver—version 610.74—are running into GPU hang errors specifically on maps with large bodies of water, and the publisher’s official workaround is a driver downgrade to the older 596.49 release.
The crash: what’s actually happening
Players load into Tsuru Reef, Battlefield 6’s sprawling Pacific island chain, and within minutes the screen freezes, the game throws a DXGI_ERROR_DEVICE_HUNG message, and Windows resets the graphics driver. The problem isn’t universal: some RTX 50 cards sail through matches, while others fail repeatedly. EA says telemetry shows reports are concentrated on Nvidia hardware, with the heaviest cluster among RTX 5070 Ti, 5080, and 5090 users—but scattered reports from older GeForce owners mean the RTX 50 label is a concentration, not a hard boundary.
The common thread is water. Tsuru Reef’s new wave simulation, combined with the 610.74 driver branch, appears to be generating a workload that the driver or the Frostbite engine can’t process in time, leading Windows to reset the GPU. Developers have not yet pinned the failure to a single rendering feature, but the pattern—water-heavy maps, new driver, RTX 50—points to a compatibility regression rather than a hardware defect.
What it means for you
If you’re running an RTX 50 Series card and planned to dive into Season 4’s naval combat, you’re effectively blocked from playing the headline map unless you roll back your driver. And rolling back isn’t a one-click affair: you’ll be stepping away from any optimizations, security updates, and fixes that the 610 branch delivered for other games. Frame generation, DLSS improvements, and new title support that came with 610.74 may regress.
For everyday Windows gamers, this is a nuisance with a clear fix path. But if you use the same PC for work—3D rendering, video editing, or AI workloads that depend on a specific driver—you’ll have to weigh the inconvenience of skipping Tsuru Reef against potential disruptions elsewhere. The older 596.49 driver, released in May 2026, lacks any fixes or features that shipped since then, so treat this rollback as temporary.
Power users who manage multiple gaming rigs or oversee an esports lounge should validate the rollback on a single system first, keep installation files for both drivers, and document the process so you can reverse it when a permanent fix lands.
Why this happened
Battlefield 6’s Season 4 isn’t just another map pack. It reintroduces naval warfare as a pillar of the combined-arms formula, and the centerpiece Tsuru Reef—larger than Railway to Golmud—uses real-time wave simulation to turn open water into a dynamic battlefield. That rendering workload is uniquely taxing: real-time water can demand geometry displacement, screen-space reflections, refraction, foam, and particle effects across huge visible distances. It’s the kind of stress that can expose a latent driver or engine bug that remains hidden on landlocked maps.
Nvidia’s GeForce driver 610.74 arrived ahead of Season 4 with the usual Game Ready promise, but the gap between the 596 and 610 branches is wide enough to suggest deeper internal changes—shader compilation, memory management, or command scheduling—that interacted poorly with Frostbite’s new water code. And when thousands of players hit a live map simultaneously, small incompatibilities can become widespread failure. The DXGI_ERROR_DEVICE_HUNG message, a familiar ghost across Battlefield titles, is Windows’ way of resetting a stalled GPU; it doesn’t mean your card is dying, just that the driver and game are no longer on speaking terms.
What to do now
EA’s official guidance is to install driver 596.49. Here’s how to do it safely:
- Confirm your current driver version. Open the Nvidia app, Nvidia Control Panel, or Device Manager and verify you’re on 610.74.
- Download driver 596.49 from Nvidia’s website. Make sure you select the correct variant for your GPU model and Windows edition. Notebook users should check if a laptop-specific package is required.
- Close everything. Exit Battlefield 6, game launchers (Steam, EA app), monitoring tools like MSI Afterburner, and any overlays. These can interfere with driver installation.
- Create a system restore point. Type “create a restore point” in Windows search, open System Properties, and click Create. This is a safety net if things go sideways.
- Run the 596.49 installer. Choose the “Custom (Advanced)” option and check the box for Perform a clean installation. This wipes old profiles and settings that might carry over from the 610 branch.
- Restart your PC. Even if not prompted, reboot to flush old driver modules.
- Verify the version and test. After rebooting, confirm that Windows is actually using 596.49 (the Nvidia app or Control Panel will show the version). Launch Battlefield 6 and try Tsuru Reef without immediately restoring any GPU overclocks or third-party overlays. Testing on a clean baseline tells you if the rollback worked.
If the rollback doesn’t solve the crashes, or if you encounter instability in other applications, don’t start modifying the Windows TDR registry setting or blindly underclock your card. Instead, rebuild a controlled environment: disable frame generation and any DLSS or ray tracing options one at a time, remove overlays like RivaTuner, check that your GPU is at stock clocks, and verify the game files. Then record exactly what happens—GPU model, driver, Windows build number (type winver), the exact error message, the map, how long you played before crashing, and whether the same test passed on 596.49. EA has asked for these details to help engineers isolate the fault.
To prevent Windows Update or the Nvidia app from sneakily reinstalling 610.74, look for an option to pause driver updates in the Nvidia app’s settings, or use the “Show or hide updates” troubleshooter from Microsoft. Keep an eye on EA’s support channels and Nvidia’s driver release notes for confirmation that a fix has shipped before updating again.
Outlook: a fix before Wake Island?
The next milestone is whether the fix comes from EA or Nvidia first. A rapid Nvidia hotfix would indicate the driver team spotted a regression and applied a safe game-specific workaround; a Battlefield update would suggest DICE tweaked a shader or rendering path. The two companies are reportedly collaborating, and yesterday’s acknowledgment from EA—specific to driver 610.74 and water maps—is a good sign that reproduction is underway.
Wake Island, the most iconic naval map in Battlefield history, is slated to arrive later in Season 4. If the root cause remains unpatched, that release could trigger a repeat crisis. For now, the rollback to 596.49 is a bandage, not a cure, but it’s a bandage that works for a significant number of affected players. The fastest way to get back into the action on Tsuru Reef is to follow the steps above and wait for the all-clear from EA or Nvidia.