Summary

Arma Reforger repeatedly crashes shortly after entering gameplay due to a DirectX graphics-device hang (DXGI_ERROR_DEVICE_HUNG, 0x887A0006).

The issue occurs consistently in the vanilla Tutorial mission, with no Workshop addons installed or loaded. It has also occurred in vanilla Game Master and modded multiplayer sessions.

The problem appeared following a PC platform upgrade from an AMD Ryzen 5 5600X system to an Intel Core Ultra 7 265K system. The RTX 3060 Ti and storage drives were retained from the previous system, where Reforger previously worked.

Despite extensive troubleshooting and successful independent hardware stress testing, the crashes persist.

Steps to Reproduce

1. Launch Arma Reforger on the affected PC.

2. Select the official Tutorial mission with no addons enabled.

3. Enter gameplay and begin the introductory tutorial sequence.

4. Within seconds to a few minutes, the game crashes.

Expected result: The tutorial runs without a graphics-device failure.

Actual result: The GPU device hangs, followed by an application crash and crash report.

Crash Details

Latest reproduction: 31 October 2026, 14:51:28 AEST.

Game version: 1.8.0.13

Enfusion engine version: 192142

Reported errors:

Render error (-2005270522 = 0x887A0006):
The application's device failed due to badly
formed commands sent by the application

func: m_pD3DDevice->GetDeviceRemovedReason()

enf::RendererImpl::EndFrame

Device removed, reason: DXGI_ERROR_DEVICE_HUNG

The corresponding crash log reports an access violation involving an illegal write to address 0x0.

Windows has also recorded LiveKernelEvent 141 graphics timeout events involving nvlddmkm.sys, along with NVIDIA driver Event ID 153.

GPU memory consumption at the latest crash was approximately 1,999 MB, suggesting VRAM exhaustion is unlikely.

Affected Hardware and Software

• Operating system: Windows 11 Pro, 26H2 (build 26300)

• CPU: Intel Core Ultra 7 265K

• Motherboard: Gigabyte B860M DS3H WIFI6E

• BIOS: F10, dated 11 June 2026

• RAM: 64 GB DDR5, running at 4800 MT/s

• GPU: Palit NVIDIA GeForce RTX 3060 Ti, 8 GB

• Display resolution: 2560 × 1080

• NVIDIA drivers tested: 617.14, 621.01 and 610.88

Troubleshooting Performed

The issue persists after:

• NVIDIA graphics driver updates and clean driver installations, including testing an older driver branch.

• Windows 11 in-place repair installation retaining applications and files.

• Steam game file integrity verification.

• Resetting the game's configuration/profile settings.

• Disabling hardware-accelerated GPU scheduling (HAGS).

• Disabling Steam and NVIDIA overlays.

• Running the GPU at stock settings and with an 80% power target.

• Temporarily restricting the CPU-connected PCIe slot from Gen 4 to Gen 3.

• Removing the downloaded Workshop addon directory and reproducing the crash with only the official Core and Arma Reforger packages available.

Hardware Stability Testing

Five OCCT 17.1.10 tests were completed successfully:

TestDurationErrorsGPU 3D Adaptive15 minutes0GPU VRAM15 minutes0CPU + RAM15 minutes0Dedicated Memory (42 GB allocated)30 minutes0Combined CPU/GPU Power15 minutes0

Total: 90 minutes of testing, zero errors detected. :(

Other games have not exhibited comparable graphics-device hangs.

These results do not conclusively exclude hardware faults, but a general instability has not been reproduced outside Reforger.

Additional Observations

The issue is reproducible with no Workshop addons, no multiplayer connection and no unusual VRAM consumption.

The logs also contain resource and prefab warnings during vanilla Tutorial loading, including unrecognised properties. It is unclear whether these are related to the graphics-device hang.

The recurring failure occurs in the renderer's EndFrame path across multiple NVIDIA driver versions.

Request

Could the development team investigate whether there is a known Enfusion/D3D12 compatibility issue affecting NVIDIA Ampere GPUs, particularly the RTX 3060 Ti, on newer Intel platforms?

I would also appreciate guidance on collecting more specific diagnostic information, such as DRED data or additional render debugging logs, to help isolate the underlying failure.

The latest console, error, script, crash logs and application minidump are available for investigation.

Update: Disabling Intel integrated graphics and performing a Windows clean boot did not resolve the crash. The clean-boot test survived approximately 55 seconds of gameplay before the same DXGI_ERROR_DEVICE_HUNG occurred.