Treyarch has issued a new update for Black Ops 4 recently but seems like it has done more bad than good for Xbox One players. Players around the globe are reporting that after updating their game, Blackout keeps crashing at random points for them and currently there is no fix in sight.
The latest update was released back on December 18 which introduced the special Black Ops 4 Absolute Zero event for players on Xbox One. This update was supposed to bring a new update filled with content but along with the bonus content, it came with an annoying bug which is causing trouble for a lot of players.
Players who are playing the game on Xbox One X are reporting around the globe that when they are playing Blackout, the game crashes at random points. The game runs fine in the early stages but as the match nears the ending, the game seems to crash forcing players to restart the game or in worst scenarios restart the console.
The most common crash point for most players is when the match reaches the 15 player point down from 100 players. The crash starts with a freeze and then eventually crashes. This is a game breaking bug specially for players who reach the top of the match because the game is crashing after a lot of progression in the match.
Treyarch is being lazy on the fix and as of now there has been no fix for the game considering the fact that it has now been 10 days since the patch was released. However, all hope is not lost as Treyarch has acknowledged that they are aware of the game breaking bug and a fix is on its way. Their official tweet states
We are aware that Xbox One X players are experiencing an intermittent freeze during late-game play in Blackout. We are actively investigating and will deploy an update as soon as we have a resolution to the issue.
This bug has definitely ruined the game for a lot of players in their holiday season but at least Treyarch is now working to fix it as soon as possible.
Are you one of the players affected by this game-breaking bug? Let us know if anything has worked for you on fixing this annoying bug in the comments section below.
