Crash/Freeze Fortnite

Fortnite Random Crashes with EXCEPTION_ACCESS_VIOLATION - Game Fix Guide

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

🎯 Quick Answer

Disable the Windows Game Bar and Game Mode services, as the DCOM timeout error for `PresenceWriter` indicates a conflict with these background services causing the access violation crash.

SECTION 1: OVERVIEW

This error constitutes a fatal application crash in Fortnite on the Windows platform, specifically the FortniteClient-Win64-Shipping.exe process. The crash is triggered by an unhandled EXCEPTION_ACCESS_VIOLATION at memory address 0x000002992dd0e620, indicating an attempt to read from or write to an invalid memory location. Concurrent system logs show a Distributed Component Object Model (DCOM) timeout error for the Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter server. This error occurs across recent game versions following Epic Games updates that interact with Windows gaming features. The frequency is classified as occasional but persistent among affected systems. The severity is game-breaking, resulting in immediate and unpredictable termination of the game client, often during gameplay or lobby navigation. The exact error messages are "Fatal error!" and "Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x000002992dd0e620".

SECTION 2: SYMPTOMS

The Fortnite client terminates abruptly without warning. The application displays a crash reporter dialog containing the text "Fatal error!" and the EXCEPTION_ACCESS_VIOLATION call stack. This termination occurs at random intervals during gameplay, in the lobby, or when loading into a match. No in-game error message precedes the crash. The Windows Event Viewer records an Error event from the DCOM source with Event ID 10010, stating: "The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout." The game process exits with a non-zero code, and the Epic Games Launcher may prompt to send crash diagnostics.

SECTION 3: COMMON CAUSES

Category: Software Conflict Specific technical explanation: The Windows Game Bar and Game Mode services (GameBarPresenceWriter.exe) fail to initialize or communicate with Fortnite via DCOM within the mandated timeout period. This failure corrupts memory handles or interrupts a critical game thread, leading to the access violation. Why this causes the problem: Fortnite attempts to call a gaming service API that is unresponsive. The subsequent timeout leaves a dangling pointer or invalid memory reference, which the game later attempts to access. Category: Configuration Error Specific technical explanation: Incorrect or corrupted DCOM security permissions for the Game Bar components prevent the PresenceWriter server from launching successfully. Why this causes the problem: The system blocks the required inter-process communication, causing the registration timeout. The game receives an error state it cannot handle gracefully. Category: Software Conflict Specific technical explanation: Outdated or buggy GPU drivers, particularly for AMD Radeon RX 7000 series cards, contain memory management faults that interact poorly with the Game Bar's screen capture hooks. Why this causes the problem: The driver and the Game Bar compete for or corrupt shared video memory regions that Fortnite is actively using, resulting in an invalid memory address access. Category: Game Bug Specific technical explanation: A race condition in the Fortnite client between its internal state management and external Windows gaming service queries. Why this causes the problem: The game accesses a resource or memory location before the Game Bar service has fully initialized it, leading to a read from a null or freed pointer. Category: Configuration Error Specific technical explanation: Overclocked or EXPO/XMP-enabled system memory (DDR5-6800) operating at an unstable frequency or timing for the AMD Ryzen 7800X3D's integrated memory controller. Why this causes the problem: Memory instability causes bit flips or corruption in the game's address space. The EXCEPTION_ACCESS_VIOLATION occurs when the CPU tries to read an address that has become invalid due to this corruption. Category: Software Conflict Specific technical explanation: Third-party overlay software (Discord, MSI Afterburner, Xbox Game Bar) injects DLLs that conflict with Fortnite's anti-cheat (Easy Anti-Cheat) or the Game Bar's own injection. Why this causes the problem: Multiple hooks into the same DirectX or Windows API calls cause a stack overflow or heap corruption, manifesting as an access violation.

SECTION 4: SOLUTIONS

Solution 1: Disable Windows Game Bar and Game Mode

Difficulty: Easy Time Required: 5 minutes Success Rate: High Prerequisites: Windows administrative rights Steps:

Press Windows Key + I to open Windows Settings.
Navigate to Gaming > Game Bar.
Toggle the switch for "Record game clips, screenshots, and broadcast using Game Bar" to Off.
Return to the Gaming menu and select Game Mode.
Toggle the switch for "Game Mode" to Off.
Press Windows Key + R, type services.msc, and press Enter.
In the Services window, locate "GameDVR and Broadcast User Service".
Right-click it, select Properties, set Startup type to Disabled, click Stop if the service is running, then click Apply and OK.
Restart the computer and launch Fortnite.

Technical Explanation: This solution prevents the GameBarPresenceWriter.exe process from loading, eliminating the DCOM timeout error at its source and removing the conflicting service that leads to memory access violations. Verification: The Windows Event Viewer no longer shows DCOM error 10010 for PresenceWriter after a system restart. Fortnite launches and runs without the fatal error crash.

Solution 2: Perform a Clean Reinstallation of GPU Drivers

Difficulty: Medium Time Required: 15 minutes Success Rate: High Prerequisites: Internet connection for driver download, administrative rights Steps:

Download the latest AMD Radeon Adrenalin driver package from AMD's official website for the Radeon RX 7900 XTX.
Download the Display Driver Uninstaller (DDU) utility from https://www.guru3d.com/download/display-driver-uninstaller-download/.
Boot Windows into Safe Mode. Press Windows Key + R, type msconfig, go to the Boot tab, check Safe boot with Minimal selected, click OK, and restart.
In Safe Mode, run DDU. Select AMD as the device type and click "Clean and restart".
After the system restarts normally, install the previously downloaded AMD driver package. Select the "Factory Reset" or "Clean Install" option during the installation wizard.
Complete the installation and restart the system as prompted.

Technical Explanation: A clean install removes corrupted driver files and registry entries that cause memory leaks or conflicts with Windows gaming services, ensuring stable GPU memory management for Fortnite. Verification: Open AMD Radeon Software and confirm the driver version is current and correctly installed. Launch Fortnite and monitor for crashes; stability indicates a resolved driver conflict.

Solution 3: Test System Memory Stability and Adjust RAM Settings

Difficulty: Advanced Time Required: 30 minutes Success Rate: Medium Prerequisites: Access to system UEFI/BIOS Steps:

Download and install a memory stress testing utility such as TestMem5 (TM5) with the anta777 extreme configuration profile.
Restart the computer and enter the UEFI/BIOS setup (typically by pressing Delete or F2 during boot).
Locate the memory settings. Disable any EXPO, XMP, or DOCP profile. Manually set the memory frequency to the JEDEC standard of 4800 MHz or 5200 MHz for DDR5. Save changes and exit.
Boot into Windows and run the memory stress test for a minimum of 30 minutes to confirm baseline stability with conservative settings.
If the system is stable, re-enter the UEFI/BIOS. Re-enable the EXPO/XMP profile but manually reduce the DRAM frequency from 6800 MHz to 6000 MHz or 6200 MHz, which is more compatible with the Ryzen 7800X3D's memory controller.
Save, boot, and run the memory test again to verify stability at the new frequency.

Technical Explanation: The Ryzen 7000 series memory controller can be unstable with high-frequency DDR5 kits. Reducing the frequency prevents memory corruption that leads to invalid pointer addresses and subsequent access violations. Verification: The memory stress test completes multiple cycles without errors. Fortnite runs without the EXCEPTION_ACCESS_VIOLATION crash over an extended gaming session.

Solution 4: Repair DCOM Permissions and System Files

Difficulty: Advanced Time Required: 10 minutes Success Rate: Medium Prerequisites: Administrative command prompt access Steps:

Press Windows Key, type cmd, right-click Command Prompt, and select Run as administrator.
Execute the following commands in order, pressing Enter after each:

sfc /scannow DISM /Online /Cleanup-Image /RestoreHealth

After the scans complete, restart the computer.
Press Windows Key + R, type dcomcnfg, and press Enter to open the Component Services console.
Navigate to Component Services > Computers > My Computer.
Right-click My Computer, select Properties, then go to the COM Security tab.
Under "Launch and Activation Permissions", click Edit Limits. Ensure SYSTEM, Administrators, and your user account have "Local Launch" and "Local Activation" permissions allowed. Click OK.
Click Apply and OK to close the properties window, then close the console.
Restart the computer.

Technical Explanation: This repairs corrupted Windows system files and resets DCOM security to default, ensuring the Game Bar presence server can launch and register correctly, eliminating the timeout condition. Verification: Check the Windows Event Viewer. The absence of new DCOM 10010 errors for several days after performing these steps confirms the repair.

Solution 5: Disable All Third-Party Overlays and Perform a Clean Fortnite Launch

Difficulty: Easy Time Required: 5 minutes Success Rate: Medium Prerequisites: None Steps:

Close all non-essential applications, especially Discord, Steam, Overwolf, MSI Afterburner/RivaTuner, and any screen recording software.
For Discord, open User Settings > Overlay, and toggle "Enable in-game overlay" to off.
Press Ctrl + Shift + Esc to open Task Manager. On the Startup tab, disable any entries related to overlays or gaming utilities.
Restart the computer.
Launch the Epic Games Launcher directly, not as an administrator.
Navigate to your Library, click the three dots under Fortnite, and select "Verify". Wait for the verification process to complete.
Launch Fortnite from the launcher.

Technical Explanation: This eliminates DLL injection conflicts between multiple overlays and Fortnite's own hooks, preventing heap corruption and race conditions that result in access violations. Verification: Fortnite runs without crashing. You can monitor running processes in Task Manager to confirm no overlay processes (DiscordHook.exe, RTSSHooks.dll, etc.) are active alongside the game.

Solution 6: Configure Fortnite for DirectX 11 and Performance Mode

Difficulty: Easy Time Required: 3 minutes Success Rate: Medium Prerequisites: Ability to launch Fortnite to the settings menu before a crash occurs Steps:

Open the Epic Games Launcher and launch Fortnite.
Immediately upon reaching the lobby, press Esc to open the menu and navigate to the Settings cog icon.
Go to the Video Settings tab.
Set Rendering Mode to "DirectX 11" (instead of DirectX 12).
Scroll down to Advanced Graphics.
Set Rendering Mode to "Performance".
Apply the settings. The game will restart.
After the restart, return to Video Settings and ensure all "NVIDIA Reflex" or "AMD Anti-Lag" options are set to Off.

Technical Explanation: DirectX 11 uses a different rendering path with more mature Windows integration, bypassing DX12 features that may conflict with Game Bar. Performance Mode uses a simplified renderer, reducing GPU driver complexity and potential fault points. Verification: The game operates without crashing. The visual fidelity will be reduced, confirming the renderer is operating in the selected mode.

SECTION 5: PREVENTION

Maintain a regular schedule for GPU driver updates, performing a clean installation using Display Driver Uninstaller every 2-3 major driver revisions. Keep Windows updated, but defer major feature updates for 2-4 weeks post-release to avoid new compatibility issues. Configure the system UEFI/BIOS with stable, tested memory timings rather than aggressive XMP/EXPO profiles. Conduct a monthly