Crash/Freeze Fortnite

Fortnite PC - Crash to Desktop at "Connecting" Screen Fix Guide

📅 Published: 2026-02-05 🔄 Updated: 2026-02-05 👥 Reports: 2 ⚡ Severity: 🟢 Low

🎯 Quick Answer

Delete the corrupted DirectX 12 Shader Pipeline Cache file located at `C:\Users\[USERNAME]\AppData\Local\FortniteGame\Saved\FortniteGame_PCD3D_SM6.upipelinecache`.

SECTION 1: OVERVIEW

This error constitutes a fatal application crash during the Fortnite client initialization sequence on the Windows platform. The failure occurs specifically during the creation of a Direct3D 12 (D3D12) Ray Tracing state object, which is a required data structure for the game's graphics pipeline. The crash manifests immediately after the game completes its supervised settings download and JSON data synchronization, at the point where the "Connecting" screen is displayed. The primary error code is E_INVALIDARG (0x80070057), indicating an invalid parameter was passed to the ID3D12Device5::CreateStateObject API call. This issue is classified as an occasional but game-breaking failure, as it prevents the application from launching entirely. The error is documented in game log files with the exact signature: RayTracingDevice->CreateStateObject(...) failed at D:\build\++Fortnite\Sync\Engine\Source\Runtime\D3D12RHI\Private\D3D12RayTracing.cpp:663 with error E_INVALIDARG.

SECTION 2: SYMPTOMS

The application launches normally and proceeds through the initial "Downloading Supervised Settings" phase. Upon completion of this phase, the final "Connecting" screen appears. The application then terminates abruptly, typically within 1-3 seconds. The system presents the standard Epic Games crash reporter dialog with the message "Fortnite has crashed! Send Crash Report?". No in-game menus or environments are loaded. Examination of the game's log file (FortniteGame.log) confirms the crash occurs after the log entry "Sparks catalog updated" and is immediately followed by the D3D12 state object creation error. The process FortniteClient-Win64-Shipping.exe exits with a non-zero code.

SECTION 3: COMMON CAUSES

Category: Configuration Error Specific technical explanation: A corrupted or invalidated DirectX 12 Shader Pipeline Cache file (FortniteGame_PCD3D_SM6.upipelinecache). This file contains pre-compiled shader state objects. If this cache becomes desynchronized from the current game version or GPU driver, the engine attempts to load invalid data, resulting in the E_INVALIDARG error during state object creation. Category: Software Conflict Specific technical explanation: Incompatible or corrupted Microsoft DirectX 12 runtime components. The D3D12 runtime is responsible for managing GPU resources. Missing or damaged system-level DLLs (e.g., d3d12.dll, dxil.dll) cause the underlying API calls to fail. Category: Game Bug Specific technical explanation: A game update introducing a change to the ray tracing or shader compilation pipeline that is incompatible with cached shader data from a previous version. The engine fails to properly invalidate the old cache, leading to a crash on load. Category: Hardware Issue Specific technical explanation: GPU hardware or driver that does not fully support the specific DirectX 12_2 feature level or ray tracing tier required by the game's current configuration, despite previous successful operation. A driver update may have altered feature reporting. Category: Configuration Error Specific technical explanation: Incorrect or corrupted game user settings within the GameUserSettings.ini file, specifically the r.D3D12.RayTracing or related graphics settings that force an incompatible rendering path on launch. Category: Software Conflict Specific technical explanation: Third-party application interference, such as overlay software (Discord, Xbox Game Bar), screen recording tools, or GPU utilities that hook into the DirectX API, injecting code that modifies the parameters of the CreateStateObject call.

SECTION 4: SOLUTIONS

Solution 1: Delete Corrupted Pipeline Cache

Difficulty: Easy Time Required: 2 minutes Success Rate: High Prerequisites: None Steps: Technical Explanation: This action forces the game's rendering engine to rebuild its DirectX 12 Shader Pipeline Cache from scratch. The new cache will be compiled against the current game version and GPU driver, ensuring all state object parameters are valid and eliminating the E_INVALIDARG error. Verification: The game progresses past the "Connecting" screen and successfully loads the lobby. A new FortniteGame_PCD3D_SM6.upipelinecache file will be created in the Saved directory with a recent timestamp.

Solution 2: Verify and Repair Game Files

Difficulty: Easy Time Required: 5-15 minutes Success Rate: Medium Prerequisites: Epic Games Launcher installed Steps: Technical Explanation: This process ensures all game binaries, including the core engine files and DirectX shader libraries, are intact and match the expected version. It can replace corrupted or modified system files that contribute to the state object creation failure. Verification: The Epic Games Launcher will display a "Verified" status. Upon launch, the game should proceed without the crash. Check the FortniteGame.log file for the absence of the E_INVALIDARG error.

Solution 3: Update Graphics Drivers

Difficulty: Easy Time Required: 10 minutes Success Rate: Medium Prerequisites: Internet connection, administrator rights Steps: Technical Explanation: GPU drivers contain the compiler and runtime components for DirectX 12 state objects. An update ensures full compatibility with the game's API calls and can resolve known bugs in previous driver versions that cause invalid arguments during ray tracing initialization. Verification: The device manager shows the new driver version. Fortnite launches without error. The driver control panel (NVIDIA Control Panel, AMD Adrenalin Software) confirms the successful installation.

Solution 4: Reset Graphics Configuration to Defaults

Difficulty: Easy Time Required: 3 minutes Success Rate: Medium Prerequisites: None Steps: Technical Explanation: A corrupted GameUserSettings.ini may contain invalid or overly aggressive graphics settings (e.g., forcing Ray Tracing on an unsupported configuration) that are passed to the D3D12 initialization routine, causing the CreateStateObject call to fail. Resetting to defaults ensures a compatible baseline configuration. Verification: A new GameUserSettings.ini file is created upon launch. The game starts with default video settings, and the crash does not occur.

Solution 5: Perform a Clean Boot to Isolate Software Conflicts

Difficulty: Medium Time Required: 10 minutes Success Rate: Medium Prerequisites: Administrator access Steps: Technical Explanation: This procedure starts Windows with a minimal set of drivers and startup programs, eliminating interference from third-party applications that may hook into the graphics API or modify system libraries, thereby isolating the cause of the crash. Verification: Fortnite launches successfully in the clean boot state. Re-enabling services/software one by one and testing will identify the specific conflict.

Solution 6: Reinstall Microsoft Visual C++ Redistributables and DirectX

Difficulty: Advanced Time Required: 10 minutes Success Rate: Low Prerequisites: Administrator access, internet connection Steps: Technical Explanation: The game engine relies on these runtime libraries for core functions. Corrupted or missing DLLs within these packages can lead to undefined behavior in API calls, including passing invalid arguments to DirectX functions. Verification: The redistributables appear correctly in the installed programs list. The game's dependency on these core runtime components is satisfied, potentially resolving the crash.

SECTION 5: PREVENTION

To prevent recurrence, implement a regular maintenance routine. Before applying major game updates or GPU driver updates, manually delete the FortniteGame_PCD3D_SM6.upipelinecache file as a precautionary measure. Configure the Epic Games Launcher to verify game files automatically after each update. Maintain a disciplined GPU driver update schedule, opting for clean installations when possible. Periodically review the FortniteGame.log file after updates to check for early warning signs of rendering errors. Avoid modifying graphics configuration files manually unless necessary, and always create backups before doing so.

SECTION 6: WHEN TO CONTACT SUPPORT

Contact Epic Games Support if all documented solutions fail and the E_INVALIDARG error persists. Prior to contact, gather the following diagnostic information: the full FortniteGame.log file from C:\Users\[USERNAME]\AppData\Local\FortniteGame\Saved\Logs, your DxDiag report (dxdiag /t dxdiag.txt), and a detailed description of the steps already attempted. Provide your system specifications, including GPU model, driver version, and Windows build number. Official support channels are accessible via the Epic Games Help section at [epicgames.com/help](https://www.epicgames.com/help).