Why Does Fortnite Keep Crashing?

Since the release of the latest season of Fortnite, many players have experienced the game crashing while they’re in the game or Lobby. This error occurs frequently when there is a new release or update in the game. Most of the time, PC players complain about Fortnite crashing, but sometimes, Xbox players also face the same problem.

Understanding the Fortnite Crashing Error

Fortnite crashes can occur for many reasons, including outdated versions, corrupted files, network errors, or outdated graphic drivers. Microsoft Support has suggested many solutions for PC players, including checking for software conflicts, verifying game files, updating your GPU driver, and reinstalling Fortnite. However, many players believe most of these methods do not resolve the problem.

How To Fix Fortnite Keep Crashing?

Change your current skin in Fortnite to stop crashing. Even though this is not a standard method, it is the best solution given by many players. Since most of the standard techniques seem to not work for this problem, let’s look at other players’ solutions.

1. Change Your Fortnite Skin

Some players say that playing with skins such as Mae, Tarr, and Eva often causes Fortnite to crash. So, if you are experiencing this error, try changing your Fortnite skin.

2. Adjust Graphics Settings and Switch to Performance Mode

This solution also comes from players who have faced similar problems and found a workaround. Here’s how you can implement this method:

1. Open the Epic Games Launcher.
2. Navigate to your Library and find Fortnite.
3. Click on the three dots next to Fortnite.
4. Select “Options.”
5. Uncheck the “High-Resolution Textures” and “DirectX 12 Shaders “options.

Also, another player has switched to the performance mode in the same option menu and fixed the error.

Amusingly, another player says streaming the game on Discord has resolved the issue. However, looking at these solutions, it seems there might also be some reasons from the game side for Fortnite to keep crashing. However, we still have not seen this error addressed on official sites.