ARC Raiders DXGI_DEVICE_REMOVED crashes: Fixes

The UE-PioneerGame CurrentQueue.Fence.D3DFence->GetCompletedValue() error in ARC Raiders is a DirectX 12 GPU crash. The full message usually ends with DXGI_ERROR_DEVICE_REMOVED and a reason of DXGI_ERROR_DEVICE_HUNG. In plain terms, Unreal Engine 5 is issuing work that your graphics driver gives up on, so Windows resets the driver and the game dies.

Despite how dramatic the wording looks, it almost never means your GPU is physically failing. It is typically a mix of aggressive UE5 features, unstable drivers, and marginal overclocks. The fixes fall into a few clear buckets: settings inside ARC Raiders, GPU clocks and drivers, DirectX mode, and cache / file integrity.

What triggers the ARC Raiders CurrentQueue.Fence.D3DFence error

The error always points to Direct3D 12 and Unreal Engine’s D3D12 backend:

CurrentQueue.Fence.D3DFence->GetCompletedValue() failed
... with error DXGI_ERROR_DEVICE_REMOVED with Reason: DXGI_ERROR_DEVICE_HUNG

Players see it in different render passes:

• Scene > BasePass > BasePassParallel
• Scene > Lights > DirectLighting > DistanceFieldShadows
• Scene > PostProcessing > HistogramEyeAdaptation

That variety matters: it shows the crash is not tied to a single asset, but to heavy GPU work in general. Common contributing factors:

• Overclocked or undervolted GPUs (including “factory OC”) falling over under UE5’s lighting and shadows.
• Fragile GPU drivers, especially after a recent update.
• DirectX 12 instability on certain GPU / driver combinations.
• Expensive UE5 features such as dynamic global illumination and ray tracing.
• Corrupted shader or DirectX cache.

Quick triage: what to try first

Fix 1: Tame ARC Raiders’ lighting (Global Illumination and ray tracing)

Many crash logs point into lighting and distance field shadows, and players consistently report fewer crashes after dialing back global illumination and ray tracing.

Inside ARC Raiders:

• Open Settings > Graphics.
• Locate Global Illumination (sometimes labelled RTX GI / GI).
• Change it from any dynamic/RTX mode to Static or Low.
• If there are separate toggles, set:
  • Lumen GI: Off
  • Lumen Reflections: Off
  • Ray Tracing: Off
  • Virtual Shadow Maps: Off

On some setups, lowering overall preset from Epic to High or Medium temporarily helps, but crashes come back. Changing the specific GI / ray tracing options is far more effective than generic presets.

Note: Several players also avoid crashes by briefly switching RTX GI to a non-Static mode in the hub, then back to Static after loading into a raid. That workaround is worth trying if the crash occurs every few matches despite conservative settings.

AarohanTechSol • youtube.com

Starts at: 00:50

Fix 2: Remove GPU overclocking, including “mild” memory OCs

DXGI_ERROR_DEVICE_REMOVED with DEVICE_HUNG is very often a symptom of an unstable GPU clock, not a dead card. ARC Raiders and UE5 are more sensitive to marginal overclocks than many other games and synthetic benchmarks.

Do the following:

• If you use tools like MSI Afterburner, ASUS GPU Tweak, EVGA Precision, AMD Adrenalin tuning, Intel XTU, Ryzen Master, etc., reset everything to default.
• Disable:
  • Core overclocks
  • Memory overclocks (VRAM MHz)
  • Undervolts
  • Automatic “OC” or “Boost” profiles
• Close these tools completely, not just minimize them, before launching ARC Raiders.

If crashes keep happening but thermals and power look fine, a very small underclock can help stabilize borderline silicon:

• Lower core clock by ~50 MHz.
• Return memory clock to 0 offset if it is not already.

Players on both NVIDIA RTX (4070 Ti Super, 5080) and AMD RX 7000 cards report ARC Raiders becoming stable the moment VRAM overclocks are removed, even when those OCs ran for months in other games without issues.

Fix 3: Clean-install or roll back GPU drivers

Driver updates are a common turning point: the game runs flawlessly for tens of hours, then starts crashing “every raid” after a new release. A clean install, or in some cases a rollback to a known-stable branch, often fixes that.

A robust approach:

1. Download the appropriate driver installer from NVIDIA’s driver page or AMD’s support page, but don’t run it yet.
2. Boot into Windows Safe Mode.
3. Use Display Driver Uninstaller (DDU) to fully remove existing GPU drivers.
4. Reboot normally and run the new driver installer.
   • On NVIDIA, choose Custom and check Perform a clean installation.
   • On AMD, enable Factory Reset inside the Adrenalin installer.
   • Reboot once more before testing ARC Raiders.

For AMD users who rolled back to 24.5.1 to stabilize ARC Raiders: modern Frostbite games like Battlefield 6 do not require the very newest Adrenalin versions to run correctly. Frostbite targets remain compatible with solid WHQL branches such as 24.5.1.

Fix 4: Reset shader and DirectX caches

Corrupt or stale GPU shader cache is a subtle cause of black screens, hitching, and fence-related GPU crashes. Clearing it forces Windows and ARC Raiders to rebuild everything.

Clear DirectX Shader Cache via Disk Cleanup

1. Press the Windows key and type Disk Cleanup, then open it.
2. Select your system drive (usually C:).
3. In the list, check DirectX Shader Cache. Optionally also select Temporary files and Recycle Bin.
4. Click OK, then confirm deletion.
5. Restart your PC.

Clear ARC Raiders / Unreal local caches

Several players regain stability after purging UE5’s local caches for this game:

• Press Win + R, type %localappdata%, press Enter.
• Open the ArcRaiders folder, then Saved, and remove its contents or rename the folder.
• In the same %localappdata% directory, open UnrealEngine > Common > DerivedDataCache and delete its contents.

Note: Removing these folders resets some in-game settings and requires ARC Raiders to recompile shaders on next launch, so expect longer initial loading and stutter during the first few matches.

Fix 5: Switch ARC Raiders to DirectX 11

The crash message explicitly references D3D12. Running ARC Raiders in DirectX 11 mode avoids that code path altogether, trading some visual features for stability.

On Steam:

1. Right-click ARC Raiders in your Library.
2. Select Properties.
3. In the General tab, find Launch Options.
4. Close the window and start the game.

Enter:

-dx11

Many players can play crash-free in DX11 at the cost of lower frame rates or heavier CPU use. Others report that DX11 removes crashes but makes it hard to hold 60fps compared to DX12 with frame generation. That trade-off is system-dependent; it is still worth trying as a diagnostic step:

• If DX11 is stable and DX12 is not, the issue is almost certainly in the DX12 driver / UE5 interaction, not your hardware.
• If both DX11 and DX12 crash, return to drivers, overclocks, and lighting settings.

Fix 6: Verify ARC Raiders’ files and, if needed, reinstall

Crashes that begin immediately after a large patch (for example, an update like 1.3) can stem from bad file installs or leftover data.

On Steam:

1. Right-click ARC Raiders in your Library.
2. Click Properties.
3. Go to the Installed Files tab.
4. Click Verify integrity of game files.
5. Wait for the scan to finish.

If Steam reports issues it cannot fix, fully uninstall ARC Raiders and reinstall it to a fast SSD. Several players also report that a full uninstall/reinstall, then leaving the default graphics preset untouched, eliminated their DX12 crashes after everything else failed.

Fix 7: Adjust Windows graphics and memory features

On some systems, Windows’ own graphics stack and memory settings can amplify instability or reduce performance when fleeing to DX11.

Set ARC Raiders to use the dedicated GPU

1. Open Windows Settings and go to System > Display > Graphics.
2. Click Browse or Add desktop app.
3. Navigate to the ARC Raiders install folder, then to PioneerGame\Binaries\Win64, and select PioneerGame.exe.
4. Once added, click it, choose Options, and set it to High performance.

Disable aggressive Windows overlays or optimizations

Some players only stabilized after disabling the first toggle under Windows’ graphics system settings, which controls optimizations for windowed games and certain overlays. If you see regular crashes in the menu or queue, experiment with:

• Turning Optimizations for windowed games off.
• Disabling overlays (Steam overlay, Discord overlay, GPU vendor overlays).

Fix 8: ARC Raiders settings for “best visuals without crashing” on modern GPUs

After the game stops crashing, it still needs to look and feel good. On a GPU in the 7900 XT / 4070 Ti class, the following configuration keeps visual quality high while avoiding the features most associated with UE5 GPU hangs:

On AMD GPUs, keep driver-side “extras” as simple as possible for ARC Raiders:

• Off: Enhanced Sync, Anti-Lag, Chill, Boost, driver overlays, Radeon sharpening.
• On: Smart Access Memory (Resizable BAR), basic Freesync if supported.
• No GPU undervolt or OC while troubleshooting.

When none of this helps

If ARC Raiders still throws CurrentQueue.Fence.D3DFence errors after:

• Disabling GI / ray tracing and Lumen.
• Removing all GPU overclocks and undervolts.
• Clean-installing or rolling back GPU drivers.
• Clearing shader and DirectX caches.
• Testing both -dx12 (default) and -dx11 launch options.
• Verifying files or reinstalling the game.

then the issue is likely tied to a very specific driver + hardware + engine edge case. At that point:

• Capture the full crash message and logs from ARC Raiders and Windows Event Viewer.
• Submit them through the game’s official support channel, including GPU model, driver version, and whether DX11 or DX12 was in use.

Occasional crashes are inevitable with a demanding UE5 game, but with conservative graphics settings, stock GPU clocks, and stable drivers, ARC Raiders should run for many hours at a time without hitting the CurrentQueue.Fence.D3DFence error.