Hardware Issues
Ongoing coverage on Hardware Issues.
Latest coverage
Before you buy a used GameCube, check for this common issue
This guide advises potential buyers of used GameCube consoles to be aware of a common issue that may prevent them from playing certain games. It offers advice on what to look for before purchasing to ensure full game compatibility.
Battlefield 6 PC Players With Nvidia RTX 50-Series GPUs Face Crashes on Maps With Lots of Water
Electronic Arts is investigating a GPU driver crash issue affecting Battlefield 6 players on PC who use Nvidia's RTX 50-series graphics cards with the latest drivers, particularly on maps with large bodies of water like Tsuru Reef. The company advises affected players to temporarily roll back to driver version 596.49 while a fix is developed. This issue emerged shortly after the launch of Season 4, which introduced the Tsuru Reef map focused on naval warfare.
Morning Tech Bits
Valve has clarified that the 'Red Line of Death' on Steam Machines indicates a memory training issue rather than GPU failure. The company has released drivers and notes to assist users experiencing this problem on Windows.
Evening Metaverse
Some users are experiencing issues with their Chromecast with Google TV remotes. Separately, Google's Gemini AI is rolling out to Chrome users in Latin America, Africa, and the Middle East.
Control Issues
A peculiar rumble issue with the Steam Controller is rendering it unusable in certain games. This hardware problem is affecting the controller's functionality, particularly in titles like Control.
The Steam Controller Has A Strange Rumble Issue That’s Making It Unusable In Some Games
The Steam Controller is experiencing a widespread rumble issue that renders it unusable in certain games, despite its advanced features and integration with Steam. This problem, potentially caused by a recent firmware update, affects games like 007 First Light and Forza Horizon 6, while titles such as Hollow Knight: Silksong and Metro Exodus function correctly. Valve's support suggests developer implementation as the cause, but the inconsistency points to a potential flaw within the controller's own firmware.