Re: DXGI_ERROR_DEVICE_REMOVED or DXGI_ERROR_DEVICE_HUNG
While playing Battlefield 6 on Ultra settings with FPS capped at 140, I encountered repeated DXGI_DEVICE_HUNG and D3D11: Removing Device. errors. After extensive diagnostics, I’ve traced the root cause to invalid AV1 encoder calls originating from Edge WebView2, which appears to be used by EA’s in-game overlay or telemetry components.
System Details:
- GPU: RX 9070XT
- Driver Version: AMD Adrenalin 25.20.x (latest)
- Game: Battlefield 6 (DX12)
- OS: Windows 11 x64
- Monitoring Tools Used: DebugView, PIX, ProcMon
Observed Errors:
AMF_INVALID_ARG: Property=Av1Level
HRESULT(0x80070057)
AMFAsyncEncoderMF::OnCheckOutputType failed
D3D11: Removing Device.
DXGI_ERROR_DEVICE_HUNG
What I Did to Diagnose the Issue:
- Enabled DX12 debug layer and GPU-based validation
- Captured logs using DebugView and PIX
- Used ProcMon to trace DLL loads and encoder activity
- Confirmed that Battlefield 6 itself was not calling the AV1 encoder
- Identified msedgewebview2.exe as the process triggering encoder calls
- Located in:
C:\Program Files (x86)\Microsoft\EdgeWebView\Application\...\msedgewebview2.exe
- This Chromium-based WebView attempted to initialize AMD’s AV1 and H.264 encoders with invalid parameters
- These calls consistently preceded GPU device removal and DXGI_DEVICE_HUNG errors
Steps Taken to Resolve the Issue:
- Disabled AV1, Instant Replay, and Anti-Lag+ in AMD Adrenalin
- Disabled EA App’s In-Game Overlay
- Renamed the Edge WebView2 runtime folder to block encoder calls
- Battlefield 6 now runs cleanly at Ultra settings and 140 FPS with no device removals
Request:
Please investigate whether Battlefield 6 or the EA App is invoking AV1 or H.264 encoders via WebView2, and whether the in-game overlay or telemetry system is responsible. These encoder calls appear to be misconfigured and are triggering GPU device removal on AMD systems.
I can provide logs, PIX traces, and minidumps if needed.
