PC freezing after 10 minutes of playing since 4/16

Battlefield 6 reproducible crash when enabling DLSS Frame Generation — dump evidence points to NVIDIA Streamline / DLSSG / D3D12 device state path

Hello EA / Battlefield Engineering Team,

I am reporting a reproducible Battlefield 6 crash that appears specifically tied to DLSS Frame Generation, not general DLSS Super Resolution or system instability.

1. Reproduction summary

The crash is reproducible with the following behavior:

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

System: AMD Ryzen 7 9700X/32GB DDR5 Dual 6000c26/SK Hynix P41 2TB SSD/Gigabyte Gaming OC Geforce RTX 5070 Ti/MSI Tomahawk B850 WIFI/Windows 11 Pro

I have also tested with BIOS fully reset to default:

BIOS: fully default EXPO: disabled PBO: disabled Curve Optimizer: disabled CPU/RAM overclocking: disabled GPU overclock/undervolt: disabled

The game does not crash when DLSS Frame Generation is disabled.
The crash happens after enabling DLSS Frame Generation.

This makes CPU Curve Optimizer, EXPO, PBO, and general RAM overclocking unlikely as the primary trigger.

2. System / GPU context

GPU: NVIDIA GeForce RTX 5070 Ti NVIDIA driver shown by the game error dialog: 61062 NVIDIA driver module version in dumps: 32.0.16.1062 Game: Battlefield 6 / bf6.exe Observed game version in latest dump: 1.0.426.51287 API path: D3D12

NVIDIA driver was cleanly removed using DDU in Safe Mode and then reinstalled. The issue still reproduced afterward.

3. In-game error dialog

The Battlefield error dialog reports:

DirectX function "GetDeviceRemovedReason" failed DXGI_ERROR_DEVICE_HUNG GPU: NVIDIA GeForce RTX 5070 Ti Driver: 61062

This matches one of the crash dump results below.

4. Dump 1 — CrashDump_2026.06.27_21.54.35.667.mdmp

This dump showed an illegal instruction in the NVIDIA user-mode D3D driver while the DLSS Frame Generation thread was active.

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

Relevant loaded modules included:

nvwgf2umx.dll nvngx_dlssg.dll nvngx_dlss.dll sl.dlss_g.dll sl.dlss.dll sl.common.dll sl.interposer.dll D3D12Core.dll dxgi.dll nvspcap64.dll gameoverlayrenderer64.dll

Interpretation:

Battlefield 6 → D3D12 → NVIDIA Streamline / DLSSG → NVIDIA user-mode driver nvwgf2umx.dll → Illegal Instruction crash

The important part is that the active crash thread was sl.dlssg, strongly suggesting the DLSS Frame Generation path was involved.

5. Dump 2 — CrashDump_2026.06.27_22.18.48.712.mdmp

This dump directly matched the in-game DirectX error:

ExceptionCode: 0x887A0006 Meaning: DXGI_ERROR_DEVICE_HUNG Crash path: D3D12 / NVIDIA user-mode driver / NVIDIA Streamline / DLSS

Relevant NVIDIA / Streamline / DLSS modules observed:

sl.interposer.dll 2.10.3.0 sl.common.dll sl.dlss.dll 2.10.3.0 sl.dlss_g.dll 2.10.3.0 sl.reflex.dll nvngx_dlss.dll 310.5.2.0 nvngx_dlssg.dll 310.5.2.0 nvngx_dlssd.dll 310.5.2.0 nvwgf2umx.dll 32.0.16.1062 nvapi64.dll 32.0.16.1062 nvldumdx.dll nvgpucomp64.dll D3D12Core.dll dxgi.dll

Relevant thread names observed:

sl.dlssg sl.pacer D3D Background Thread 0 D3D Background Thread 1 D3D Background Thread 2 D3D Background Thread 3

The D3D background threads repeatedly involved:

D3D12Core.dll nvwgf2umx.dll

The dump also contained a Frostbite GPU breadcrumb:

Incomplete breadcrumb found on device 0 hardware queue: Main frameIndex: 116516 last renderPass: LodFadeStencilMask last bound pipeline: ShaderProgram_GpuMeshScatteringCull_IndirectDraw last Opcode: Dispatch 5 x 1 x 1

Interpretation:

The GPU appears to hang while executing a D3D12 workload. The breadcrumb suggests the last incomplete GPU work was around:

LodFadeStencilMask ShaderProgram_GpuMeshScatteringCull_IndirectDraw Dispatch 5 x 1 x 1

Because this only reproduces when DLSS Frame Generation is enabled, this may indicate an interaction between the Frostbite render graph / async compute / indirect draw / LOD or stencil pass and NVIDIA Streamline DLSSG frame generation.

6. Dump 3 — CrashDump_2026.06.29_23.20.41.551.mdmp

The latest dump changed from a direct DXGI device-hung error to a game-process access violation:

Process: bf6.exe Game version: 1.0.426.51287 ExceptionCode: 0xC0000005 Meaning: Access Violation Faulting module: bf6.exe Fault offset: bf6.exe + 0x53bf390 Access type: read Read address: 0x0

This appears to be a null pointer read inside the game executable.

However, this crash is still only reproducible when DLSS Frame Generation is enabled. The dump still had NVIDIA Streamline / DLSS Frame Generation components active:

sl.interposer.dll sl.common.dll sl.dlss.dll sl.dlss_g.dll sl.reflex.dll nvngx_dlss.dll nvngx_dlssg.dll nvngx_dlssd.dll D3D12.dll D3D12Core.dll dxgi.dll nvwgf2umx.dll nvapi64.dll nvgpucomp64.dll

Relevant threads:

sl.pacer sl.dlssg D3D Background Thread 0 D3D Background Thread 1 D3D Background Thread 2 D3D Background Thread 3

NVIDIA driver module version remained:

32.0.16.1062 / 61062

Interpretation:

This latest crash may be a secondary failure after the renderer / frame generation / device state becomes invalid. Instead of surfacing as DXGI_ERROR_DEVICE_HUNG, the game later reads a null or invalid renderer/frame-generation-related object and crashes inside bf6.exe.

7. Common pattern across all crashes

Across all collected dumps and the in-game error dialog, the common pattern is:

Trigger: DLSS Frame Generation enabled Stable condition: DLSS Frame Generation disabled API: D3D12 NVIDIA path: Streamline / DLSSG / user-mode driver Threads/modules: sl.dlssg, sl.pacer, sl.dlss_g.dll, nvngx_dlssg.dll, nvwgf2umx.dll, D3D12Core.dll Observed failure types: - 0xC000001D Illegal Instruction in nvwgf2umx.dll while sl.dlssg was active - 0x887A0006 DXGI_ERROR_DEVICE_HUNG / GetDeviceRemovedReason failed - 0xC0000005 null read inside bf6.exe while DLSSG modules were active

This suggests the issue is not generic DLSS Super Resolution. It appears specific to:

Battlefield 6 → D3D12 renderer → NVIDIA Streamline → DLSS Frame Generation / DLSSG → NVIDIA user-mode driver / GPU device state

8. Suspected debug area

Please investigate the Battlefield 6 integration around NVIDIA Streamline / DLSS Frame Generation, especially:

1. DLSS Frame Generation enable/disable state handling 2. Streamline interposer / sl.dlss_g.dll / nvngx_dlssg.dll integration 3. D3D12 device removed / device hung handling 4. Renderer object lifetime after device-hung or DLSSG state changes 5. Swapchain / frame pacing / present path interaction with sl.pacer 6. Async compute / indirect dispatch work submitted while DLSSG is active 7. Frostbite GPU breadcrumb location: - LodFadeStencilMask - ShaderProgram_GpuMeshScatteringCull_IndirectDraw - Dispatch 5 x 1 x 1 8. Potential null renderer/frame-generation state dereference near: - bf6.exe + 0x53bf390

The latest access violation suggests there may be a missing null/device-removed guard in the game code path after a DLSSG/D3D12 device-state failure.

9. Overlay note

Some dumps also showed overlay/capture related modules loaded, including:

Steam gameoverlayrenderer64.dll NVIDIA nvspcap64.dll NvTelemetryAPI64.dll NvTelemetryBridge64.dll

However, the crash is controlled by the DLSS Frame Generation toggle:

Frame Generation off: stable Frame Generation on: crash

So overlays may be a secondary amplifier, but the primary reproducible trigger is DLSS Frame Generation.

10. Final conclusion

The crash appears to be a reproducible Battlefield 6 issue in the NVIDIA DLSS Frame Generation / Streamline / D3D12 path.

The strongest evidence is:

- BIOS defaults and no CPU/RAM tuning do not prevent the crash. - DLSS Super Resolution without Frame Generation is stable. - Enabling DLSS Frame Generation reproduces the crash. - The game dialog reports DXGI_ERROR_DEVICE_HUNG. - Dumps show sl.dlssg / sl.pacer / sl.dlss_g.dll / nvngx_dlssg.dll active. - One dump faults in nvwgf2umx.dll. - One dump reports DXGI_ERROR_DEVICE_HUNG. - The latest dump faults inside bf6.exe with a null read, likely after invalid renderer/device/frame-generation state.

Please focus debugging on the DLSS Frame Generation integration and device-hung recovery/state-management path rather than general system instability.

Hi EA team and fellow players,

just wanted to drop by and express my gratitude for today’s EA App update. It’s truly impressive how effectively it manages to make Battlefield 6 completely unplayable.

After multiple reinstallations, cache wipes, and manually removing every trace of EA AntiCheat, the EA App still insists on delivering nothing but archaeological artifacts: – files from June 10th, 2026 – or, if it’s feeling extra nostalgic, even from January 26th, 2026

I didn’t know the EA App now supports time travel. Too bad it can’t find a single working, signed EAAntiCheat.sys along the way.

The installer itself is from June 23rd, 2026, but it apparently pulls its payload from a CDN graveyard that only serves outdated builds. Secure Boot says “nope”, Battlefield says “goodbye”, and the player says “seriously?”.

And honestly: There are plenty of players who don’t want to dig around in their PC systems just to make a game run that they paid money for. One would expect a AAA title to launch without BIOS acrobatics, driver voodoo, or Windows exorcism.

Maybe one day you’ll upload the correct files to your servers again. Until then, BF6 will remain a very pretty menu simulator for many of us.

Thanks for the technical masterpiece. Really.

Regards, Joerg

Sounds about right and something i considered. That is why we ask for the crash dump files and to check the WER, one may have something the other does not but if it is a temp file being created, that would be something we need to see in logs. It's good info though for sure and something we can certainly pass along.

I really appreciate you testing this out. It does help a lot and others can test it out if they like and see if they get the same or find something that was overlooked.

EA_Shepard​ 

A quick update, because your comment about the EA App cache may have been onto something.

After reading your reply, I used the EA App recovery option and cleared the application's cache. I did not change anything else on the system. No driver changes, no BIOS changes, no Windows changes, and no Anti-Cheat reinstall.

Immediately after clearing the EA App cache, I launched Battlefield 6 and was able to complete two matches without any issues. The first was already in progress when I joined, and the second was a full match lasting approximately 17 minutes. During both matches, the game was completely stable.

Most importantly, I did not see the packet-loss indicators that had previously become a common warning sign before freezes and crashes.

This obviously does not prove that the issue is solved, and I need more testing before drawing conclusions. However, considering that I had already experienced the return of the freezing problem after a period of stability, the timing is interesting enough that I wanted to report it.

As a reminder, after the full game reinstall I accumulated roughly 24 hours of gameplay with greatly improved stability. The issue then returned after I exited the game normally, left my PC running for about 20 minutes, and launched the game again without changing anything on my system. That behavior made me suspect that some type of temporary data, cache, or generated files might be involved.

For now, I will continue testing and monitoring the situation. If the game remains stable after clearing the EA App cache, that may provide another useful clue toward identifying the root cause and helping other affected players.

Thanks again for taking the time to look into this.

Thanks for the follow-up EA_Shepard​ ! 😃

To answer your questions, according to AMD Adrenalin I accumulated roughly 24 hours of Battlefield 6 gameplay after the full reinstall. During that period, the game was dramatically more stable than before. I was able to complete multiple sessions, including several lasting multiple hours. Prior to the reinstall, I was often freezing within minutes, sometimes even in the menus before reaching a match.

Regarding the packet-loss indicators, they appeared to be gone together with the freezes. During the period after the reinstall, I do not recall seeing the packet-loss warnings that had become a common warning sign before a crash.

This is why the reinstall caught my attention. The system, drivers, BIOS, and hardware remained the same. The only significant change was the game reinstall itself.

However, I do have one additional observation that may be relevant.

Last Saturday, after several hours of normal gameplay with a friend, I exited the game as I normally would. I left the PC running, stepped out for about 20 minutes to buy cigarettes, came back, had a smoke, and then launched Battlefield 6 again. I had not rebooted the PC, changed any settings, installed anything, updated anything, or modified my setup in any way.

The very next launch resulted in the exact same freeze behavior that I had been experiencing before.

That is one of the reasons I am wondering whether some kind of temporary file, cache, shader cache, EA App cache, or other data generated while closing or reopening the game may be involved. From my perspective, nothing else changed during those 20 minutes.

For reference, Battlefield 6 worked perfectly on this system from December until Season 3. The issues only started after the Season 3 update.

I will continue monitoring the situation and reporting any additional findings

MurderOne1986​ Thanks for the update. The reinstall help is interesting, since you had already gone through BIOS updates, driver rollbacks, Anti-Cheat reinstalls, system file checks, and other troubleshooting. The fact that the crashes were happening in menus and class selection before matches, then stopped after a full reinstall, is a useful data point for anyone else seeing similar behavior after the recent updates.

Since you've already covered most of the common troubleshooting, a couple of things worth checking if the issue returns are whether the EA App cache has been cleared recently, and whether the Battlefield 6 shader cache gets rebuilt after the reinstall. I am curious whether something like temp files is getting corrupted and stuck in the folders, not getting deleted.

We've also seen reports of players' stability improving after a clean reinstall, because corrupted or outdated game files survived previous patching but were removed during the full reinstall. If things remain stable over the next few days, do you happen to know roughly how many matches or hours you've played since reinstalling? Also, are you seeing the packet-loss indicators at all anymore, or have they disappeared along with the freezes?

Quick update:

After all the testing I've been doing, I decided to try something very simple: I completely reinstalled the game.

So far, this has been the only change I made recently.

Since reinstalling Battlefield 6, I have been able to play multiple matches yesterday and again today without any freezes, crashes, or system reboots.

It's still too early for me to declare the issue fully resolved, especially considering how inconsistent this problem has been, but the difference is significant enough that I wanted to report it here.

At the moment, the game is behaving normally again. I'll continue testing over the next few days and will update this thread if anything changes.

Current setup remains the same as previously reported, including Radeon Adrenalin 25.9.1 and BIOS F40.

Hopefully this information helps others and maybe provides another clue as to what is actually causing these freezes.

Thank you for sharing the detailed changes you've noticed with your device. I'm also glad to hear that the game has finally returned to a playable state for you.

I’ve not noticed any performance difference between F11 and F12, but it might be worth the update regardless. I haven’t had any issues with it so far, and it does not take long to do. :)

Moerges​ /offtopic What do you think, F12 BIOS is better than F11? I updated my board from an earlier version from 2024 to F11 because of this issue, and the difference in performance is night and day. I had no performance issues before but the system is snappier than ever before with my 9800x3d. The change in performance reminds me when I installed OS onto an SSD first time from HDD back in 2011. Board is the same as yours.