GeForce RTX 50 GPUs reportedly crash on Battlefield 6 maps with large bodies of water

EA recommends older NVIDIA driver after Battlefield 6 Season 4 crashes

EA and Battlefield Studios have confirmed that some PC players are experiencing NVIDIA GPU driver crashes in Battlefield 6. Reports are more common among users with GeForce RTX 50 Series graphics cards, although the problem does not affect every system.

The crashes reportedly occur on maps containing large bodies of water. EA specifically names Tsuru Reef, the new map introduced with the Battlefield 6 Season 4 update on July 21. The map includes naval combat, large open-water areas and a new dynamic wave system.

© DICE

EA has not confirmed whether the problem originates in Battlefield 6 or NVIDIA’s driver. The studio says it is working with NVIDIA to identify the cause and prepare a fix.

Players experiencing repeated crashes are advised to temporarily roll back to GeForce driver 596.49 . NVIDIA released this version on May 12, while the current Game Ready driver 610.74 was released on July 7. EA does not specifically identify version 610.74 as the faulty driver.

Known Issue: NVIDIA GPU Driver Crashes on Certain Maps

We’re investigating an issue on PC where some players may experience a GPU driver crash when playing on maps with large bodies of water, including Tsuru Reef.

Based on our current data, the issue appears to affect NVIDIA…

— Battlefield Comms (@BattlefieldComm) July 21, 2026

Driver 610.74 was released with Game Ready support for DOOM: The Dark Ages | Revelations and Assassin’s Creed Black Flag Resynced. Its published known issues do not mention Battlefield 6 or crashes on GeForce RTX 50 graphics cards.

EA asks players who continue to experience crashes after installing 596.49 to submit their GPU model, driver version, affected map and crash-report details through the Battlefield 6 Technical Issues forum. The company will provide another update after it gathers more information.

If the issue is indeed caused by the driver, NVIDIA will most likely release a hotfix. Some users have already found a working link for a new hotfix (610.82), but based on the comments on Reddit, it may not resolve this particular issue.

Sources: Battlefield Comms