DLSS Frame Generation causes DXGI device removed/hung and NVIDIA driver crash

Hello EA / Battlefield Engineering Team,

Here is an updated summary of today’s findings after the latest Battlefield 6 update.

1. Reproduction status

The issue is still reproducible with DLSS Frame Generation enabled.

Current observed behavior:

DLSS Super Resolution only: stable DLSS Frame Generation disabled: stable DLSS Frame Generation enabled: crash

The system has also been tested with BIOS defaults previously:

EXPO disabled PBO disabled Curve Optimizer disabled CPU/RAM tuning disabled GPU overclock/undervolt disabled

This continues to suggest that the primary trigger is not CPU/RAM instability, but the Battlefield 6 + NVIDIA DLSS Frame Generation / Streamline / D3D12 path.

2. Application and environment

Game path: D:\SteamLibrary\steamapps\common\Battlefield 6\bf6.exe Application: bf6.exe Application version: 1.0.426.51287 Application timestamp: 6a2884d7 GPU: NVIDIA GeForce RTX 5070 Ti NVIDIA driver shown by previous error dialog: 61062 NVIDIA driver module version in records: 32.0.16.1062 OS version: 10.0.26200.2.0.0.256.48

3. New Windows Reliability / AutoVerifierV2 records

Record A — DXGI_ERROR_DEVICE_HUNG

Problem Event Name: AutoVerifierV2 Faulting application: bf6.exe Faulting module: KERNELBASE.dll Faulting module version: 10.0.26100.8655 Exception code: 0x887A0006 Fault offset: 0x00000000000c1b6a Status code: 1 Bucket ID: c8659c48474aeaf21d8e32734e5b77ab

Interpretation:

0x887A0006 = DXGI_ERROR_DEVICE_HUNG

This matches the previous in-game DirectX error dialog:

DirectX function GetDeviceRemovedReason failed DXGI_ERROR_DEVICE_HUNG

Record B — DXGI_ERROR_DEVICE_REMOVED

Problem Event Name: AutoVerifierV2 Faulting application: bf6.exe Faulting module: KERNELBASE.dll Faulting module version: 10.0.26100.8655 Exception code: 0x887A0005 Fault offset: 0x00000000000c1b6a Status code: 1 Bucket ID: b2177097ce884baafd28a5b9273c1662

Interpretation:

0x887A0005 = DXGI_ERROR_DEVICE_REMOVED

This is closely related to the previous DXGI_ERROR_DEVICE_HUNG event. Both indicate a D3D/DXGI device-loss condition while running Battlefield 6.

Record C — NVIDIA user-mode D3D driver illegal instruction

Problem Event Name: AutoVerifierV2 Faulting application: bf6.exe Faulting module: nvwgf2umx.dll Faulting module version: 32.0.16.1062 Faulting module timestamp: 6a2b0e0f Exception code: 0xC000001D Fault offset: 0x0000000000963d00 Status code: 1 Bucket ID: f0781fa4c849ae195e2ddd7fde85ce05

Interpretation:

0xC000001D = Illegal Instruction nvwgf2umx.dll = NVIDIA user-mode Direct3D driver

This matches an earlier crash dump where the active crash thread was:

sl.dlssg

and the faulting location was:

nvwgf2umx.dll + 0x963d00

Record D — BF6 access violation

Problem Event Name: AutoVerifierV2 Faulting application: bf6.exe Faulting module: bf6.exe Application version: 1.0.426.51287 Exception code: 0xC0000005 Fault offset: 0x00000000047c6edf Status code: 2 Bucket ID: d4f71cffd3a1dbd5d423bf0f7f7c1505

Interpretation:

0xC0000005 = Access Violation

This may be a secondary failure after the renderer / D3D12 device / DLSS Frame Generation state becomes invalid. It may indicate that bf6.exe later dereferences an invalid or null renderer/frame-generation-related object after a device removed/hung condition.

4. Relation to previous crash dumps

Previous BF6 crash dumps showed NVIDIA Streamline / DLSS Frame Generation components active, including:

sl.dlssg sl.pacer sl.dlss_g.dll sl.dlss.dll sl.common.dll sl.interposer.dll nvngx_dlssg.dll nvngx_dlss.dll D3D12Core.dll dxgi.dll nvwgf2umx.dll nvapi64.dll nvgpucomp64.dll

One previous dump showed:

ExceptionCode: 0x887A0006 Meaning: DXGI_ERROR_DEVICE_HUNG

Another showed:

ExceptionCode: 0xC000001D Crash thread: sl.dlssg Faulting module/address: nvwgf2umx.dll + 0x963d00 NVIDIA module version: 32.0.16.1062

The latest crash dump also showed:

ExceptionCode: 0xC0000005 Faulting module: bf6.exe Access type: read Read address: 0x0

5. Current failure pattern

Today’s records show four related failure modes:

1. 0x887A0006 / DXGI_ERROR_DEVICE_HUNG Fault module: KERNELBASE.dll 2. 0x887A0005 / DXGI_ERROR_DEVICE_REMOVED Fault module: KERNELBASE.dll 3. 0xC000001D / Illegal Instruction Fault module: nvwgf2umx.dll Offset: nvwgf2umx.dll + 0x963d00 4. 0xC0000005 / Access Violation Fault module: bf6.exe Offset: bf6.exe + 0x47c6edf

These appear to be different manifestations of the same underlying issue:

Battlefield 6 → D3D12 renderer → NVIDIA Streamline → DLSS Frame Generation / DLSSG → NVIDIA user-mode D3D driver / DXGI device state → Device hung / device removed / driver illegal instruction / BF6 invalid state access

6. Debug areas suggested by the evidence

Please investigate the Battlefield 6 DLSS Frame Generation integration, especially:

1. NVIDIA Streamline / DLSSG enable path 2. sl.dlssg and sl.pacer frame pacing behavior 3. D3D12 device removed / device hung handling 4. Swapchain / Present / frame generation interaction 5. Renderer object lifetime after device loss 6. Null or invalid state handling near: bf6.exe + 0x47c6edf 7. NVIDIA driver crash point: nvwgf2umx.dll 32.0.16.1062 + 0x963d00 8. Interaction with RTX 5070 Ti and NVIDIA driver 61062 / 32.0.16.1062

7. Final conclusion

After today’s update and additional Windows reliability records, the evidence still points strongly to a Battlefield 6 + NVIDIA DLSS Frame Generation / Streamline / D3D12 device-state issue.

The key reproducible trigger remains:

DLSS Frame Generation enabled = crash DLSS Frame Generation disabled = stable

The new records add stronger evidence that the issue is not just a generic application crash:

- Windows records DXGI_ERROR_DEVICE_HUNG - Windows records DXGI_ERROR_DEVICE_REMOVED - NVIDIA user-mode D3D driver nvwgf2umx.dll throws 0xC000001D at +0x963d00 - bf6.exe later throws 0xC0000005 access violation at +0x47c6edf

Please focus debugging on DLSS Frame Generation / Streamline integration, D3D12 device loss handling, and the NVIDIA user-mode driver path rather than general CPU/RAM/system instability.