Performance Issue Fortnite

Fortnite DX12 Stuttering & 100ms Frametime Spikes - Fix Guide

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

🎯 Quick Answer

Disable Intel Arc GPU's Adaptive Sync and set the Shader Cache Size to Unlimited in the graphics driver control panel to eliminate DirectX 12 frametime spikes.

SECTION 1: OVERVIEW

The error is defined as severe, periodic frametime spikes reaching approximately 100 milliseconds during Fortnite gameplay, causing perceptible stuttering and frame delivery inconsistency. This issue is isolated to the Windows platform running the DirectX 12 rendering API. The problem manifests across all recent versions of Fortnite that support DirectX 12. Based on available data, this is a rare issue specific to certain hardware configurations. The severity is high, as consistent 100ms spikes constitute a game-breaking performance degradation that severely impacts playability, despite the average framerate potentially remaining high. No explicit error codes are generated; the failure mode is purely performance-based, observable through frametime monitoring tools. The condition is reproducible and persistent under the DirectX 12 renderer, independent of in-game graphical settings.

SECTION 2: SYMPTOMS

The primary symptom is a consistent, periodic frametime spike of approximately 100 milliseconds, recorded by performance monitoring software like CapFrameX or MSI Afterburner. These spikes occur at regular intervals during standard gameplay and in-match lobbies. The application continues running without crashing, but video output exhibits severe, momentary freezing or stuttering. The issue is exclusive to the DirectX 12 rendering pipeline; switching to Performance Mode or DirectX 11 eliminates the spikes. The problem is present across all graphical preset combinations, from Low to Epic settings, indicating independence from standard GPU load.

SECTION 3: COMMON CAUSES

Category: Hardware/Driver Issue Specific technical explanation: Intel Arc GPU driver power management or Adaptive Sync (Variable Refresh Rate) implementation conflicting with Fortnite's DX12 presentation model. Why this causes the problem: The driver's attempt to dynamically manage refresh rates or power states can introduce significant scheduling delays, manifesting as exact, repeatable frametime spikes when the game engine submits a frame. Category: Software Conflict Specific technical explanation: Outdated or corrupted Microsoft DirectX 12 runtime components or Visual C++ Redistributables. Why this causes the problem: Fortnite's DX12 implementation relies on specific API calls that may fall back to slower, compatibility paths if core runtime files are missing or damaged, causing intermittent processing stalls. Category: Configuration Error Specific technical explanation: Incorrect or suboptimal Shader Cache size setting within the Intel Graphics Command Center. Why this causes the problem: An insufficient or disabled shader cache forces the GPU to compile shaders in real-time during gameplay. On DX12, this compilation can block the rendering thread, causing massive frametime spikes until completion. Category: Game Bug Specific technical explanation: A memory management or asset streaming bug in Fortnite's DirectX 12 backend specific to Intel Arc GPU architecture. Why this causes the problem: The game engine may incorrectly handle texture or geometry streaming for Arc's tile-based rendering architecture, causing the GPU to wait for data that is not optimally prepared, resulting in a pipeline stall. Category: Hardware Issue Specific technical explanation: System Memory (RAM) instability despite XMP/EXPO profile operation. Why this causes the problem: The Ryzen 7000 series Infinity Fabric is tied to memory clock. Even stable-seeming RAM can cause subtle errors that force memory controller retries, leading to periodic delays perceived as frametime spikes, exacerbated by DX12's lower-level memory management. Category: Configuration Error Specific technical explanation: Windows Power Plan or AMD Ryzen Power Plan set to a balanced or power-saving mode. Why this causes the problem: These plans allow the CPU (Ryzen 7600X) to rapidly change clock speeds and sleep states. A delay in waking cores or ramping up frequency to handle a DX12 draw call can introduce a direct frametime spike. Category: Software Conflict Specific technical explanation: Overlay software from Discord, Xbox Game Bar, or other utilities hooking into the DirectX 12 swap chain. Why this causes the problem: These overlays use present-time interception which can conflict with Intel's DX12 presentation path, adding a fixed overhead that manifests as a periodic spike when the overlay updates.

SECTION 4: SOLUTIONS

Solution 1: Disable Adaptive Sync & Configure Shader Cache

Difficulty: Easy Time Required: 5 minutes Success Rate: High Prerequisites: Intel Arc Graphics Driver installed Steps:

Right-click on the desktop and select Intel Graphics Command Center.
Navigate to the System tab in the bottom left.
Select Power from the system menu.
Set Adaptive Sync to Disabled.
Navigate to the Game tab in the bottom left.
Select Fortnite from your game list or add it manually by browsing to C:\Program Files\Epic Games\Fortnite\FortniteGame\Binaries\Win64\FortniteClient-Win64-Shipping.exe.
Under the Game Settings for Fortnite, find the Shader Cache Size option.
Set the Shader Cache Size to Unlimited.
Close the Intel Graphics Command Center. The settings save automatically.

Technical Explanation: Disabling Adaptive Sync prevents the driver from negotiating variable refresh rates with the monitor on a per-frame basis, eliminating a potential source of presentation queue delays. Setting the shader cache to unlimited prevents runtime compilation stalls during gameplay, which are a known source of frametime spikes in DX12 titles. Verification: Launch Fortnite, set the renderer to DirectX 12, and enter a Battle Royale match. Monitor frametimes using the in-game performance overlay (Alt+R) or a tool like CapFrameX. The consistent 100ms spikes should be eliminated, resulting in a smooth frametime graph.

Solution 2: Perform a Clean Reinstallation of Graphics Drivers

Difficulty: Medium Time Required: 10 minutes Success Rate: Medium Prerequisites: Internet connection to download DDU and latest driver Steps:

Download the latest Intel Arc B580 driver from Intel's official website.
Download Display Driver Uninstaller (DDU) from www.guru3d.com.
Boot Windows into Safe Mode. This can be done via System Configuration (msconfig.exe) under the Boot tab.
Run DDU in Safe Mode. Select Intel from the device type dropdown menu.
Click Clean and restart.
After the system restarts into normal Windows, install the previously downloaded Intel graphics driver package. Choose Custom Install and check the box for Perform clean installation.
Restart the system when prompted.

Technical Explanation: A clean installation removes all previous driver files, registry entries, and configuration profiles that may be corrupted or conflicting with Fortnite's DX12 runtime. This ensures a pure driver state and fresh shader cache. Verification: After reinstallation, reconfigure Solution 1 settings. Test in Fortnite DX12. Check that the driver version in Intel Graphics Command Center matches the newly installed version.

Solution 3: Adjust Windows & AMD CPU Power Settings

Difficulty: Easy Time Required: 3 minutes Success Rate: Medium Prerequisites: Administrator account Steps:

Press Windows Key + R, type control panel, and press Enter.
Navigate to Hardware and Sound > Power Options.
Select the High Performance power plan. If it is not visible, click Show additional plans.
Click Change plan settings next to High Performance, then Change advanced power settings.
In the Advanced settings window, expand Processor power management.
Set Minimum processor state to 100%.
Set Maximum processor state to 100%.
If present, also expand PCI Express and set Link State Power Management to Off.
Click Apply and OK.

Technical Explanation: Forcing the CPU to maintain a constant 100% processor state prevents latency-inducing transitions from idle (C-states) to active performance states (P-states). This ensures the Ryzen 7600X responds immediately to DX12 draw calls without ramp-up delay. Verification: Monitor CPU clock speeds using HWiNFO64 during gameplay. The cores should maintain a steady high clock speed instead of frequently fluctuating, correlating with the elimination of frametime spikes.

Solution 4: Repair Microsoft Visual C++ and DirectX Runtimes

Difficulty: Medium Time Required: 7 minutes Success Rate: Low Prerequisites: Internet connection Steps:

Press Windows Key + R, type appwiz.cpl, and press Enter to open Programs and Features.
In the list, uninstall all instances of Microsoft Visual C++ 2015-2022 Redistributable.
Download the latest Visual C++ Redistributable package from the official Microsoft website.
Install both the x64 and x86 versions.
Download the DirectX End-User Runtime Web Installer from Microsoft.
Run the installer (dxwebsetup.exe). It will check and update any missing or corrupted DirectX runtime files.
Restart the computer.

Technical Explanation: Fortnite, like many Unreal Engine 4 titles, depends on specific versions of these runtime libraries for low-level API calls. Corrupted files can cause functions to execute in an exception-handling or fallback mode, introducing severe stalls. Verification: The installation processes will complete without error. Fortnite will regenerate its initial configuration files upon next launch, which may indicate successful runtime dependency resolution.

Solution 5: Test for Memory Stability with EXPO Disabled

Difficulty: Advanced Time Required: 15 minutes (plus extended test time) Success Rate: Medium Prerequisites: Willingness to enter BIOS/UEFI Steps:

Restart the computer and press Delete or F2 to enter the BIOS/UEFI.
Navigate to the Ai Tweaker or Advanced CPU Settings menu.
Locate the setting for EXPO or DOCP. Set this profile to Disabled. This will revert RAM to its JEDEC standard speed (typically 4800MHz for DDR5).
Save changes and exit the BIOS (usually F10).
Boot into Windows and launch Fortnite.
Test gameplay under DirectX 12. If the frametime spikes are gone, the EXPO profile is likely unstable.
If stable, re-enter BIOS and manually set memory frequency to 5600MHz with timings 30-36-36-76 and DRAM Voltage to 1.35V, leaving EXPO disabled. Test again.

Technical Explanation: Unstable memory or Infinity Fabric clocks can cause correctable errors that the system handles with retries. DX12's explicit memory control is more sensitive to these micro-delays than DX11, causing periodic spikes that align with memory access patterns. Verification: Use a tool like TestMem5 with the Extreme1 anta777 profile to test memory stability at the EXPO settings. Any errors indicate instability. A stable system should pass 3 cycles without errors.

Solution 6: Disable Conflicting Overlays and Recording Software

Difficulty: Easy Time Required: 4 minutes Success Rate: Low Prerequisites: None Steps:

Close Discord completely via the system tray (right-click icon > Quit).
Press Windows Key + G to open Xbox Game Bar. Click the Settings cog.
Go to Gaming > Game Bar and turn off Record game clips, screenshots, and broadcast using Game Bar.
Also, under Gaming > Captures, turn off Record in the background while I'm playing a game.
If MSI Afterburner or RivaTuner Statistics Server (RTSS) is running, exit the application from the system tray.
For the Epic Games Launcher, open its Settings (click profile icon). Scroll to the bottom and disable Enable Overlay.
Restart Fortnite.

Technical Explanation: Overlay software injects itself into the game's rendering pipeline to draw its elements. This injection can conflict with Intel's DX12 presentation model, causing a frame to be held for an extra cycle while the overlay composites, resulting in a precise frametime spike. Verification: Launch Fortnite with no third-party applications running. Use the in-game performance overlay exclusively for monitoring. Check if the spike pattern changes or is eliminated.

SECTION 5: PREVENTION

Maintain the Intel Arc graphics driver at the latest stable version, checking for updates monthly. After any driver update, verify that the Adaptive Sync and Shader Cache settings in the Intel Graphics Command Center remain configured as per Solution 1. Establish a stable memory overclock using stress-testing tools like TestMem5 and y-cruncher, rather than relying solely on EXPO profiles. Set the Windows Power Plan to High Performance permanently. Conduct a quarterly clean reinstallation of graphics drivers using DDU to prevent configuration drift. Monitor system temperatures using HWiNFO64 to ensure no thermal throttling is occurring on the CPU or GPU.

SECTION 6: WHEN TO CONTACT SUPPORT

Contact Epic Games Support if all solutions fail and the issue persists exclusively in Fortnite under DirectX 12. Contact Intel Support if the frametime spikes are reproducible in other DirectX 12 titles, confirming a driver-level fault. Before contacting support, gather the following