bf6.exe+0xb732xx
My game crashes on launch. I ran the dump files through Claude and received the following. I have followed all of the recommended instructions and the game still crashes. I continually get corrupt games files in Steam. Here are all the details:
On Windows, the Battlefield 6 crash logs are located here:
C:\Users\[your_username]\Documents\Battlefield 6\CrashDumps GamePressure
Just replace [your_username] with your actual Windows username. Check the timestamps on the files to find the one that matches your most recent crash. Steam Community
If you want to share them with EA for support, you can upload them to cloud storage like Google Drive and include the link when submitting a report. GamePressure
You can also check Windows Event Viewer as a secondary source — it sometimes contains additional information about crash causes. Steam Community
CrashDump_2026.05.30_16.06.30.826.mdmp
mdmp
Can you read this and tell me what is happening? My BF6 game keeps crashing.
May 30
Ran 10 commands, viewed a file
Ran 10 commands, viewed a file
Good, I now have enough to give a solid diagnosis. Here's what your crash dump reveals:
BF6 Crash Analysis — May 30, 2026
What happened
Your game crashed with an ACCESS_VIOLATION (0xC0000005) — the most common crash type in BF6. Specifically, the game tried to read from memory address 0x43e30ae8f, which was either freed or never valid at that moment. The Frostbite engine couldn't recover, so it killed the process.
The crash occurred inside bf6.exe at offset +0xb73254, only 9 seconds after the process started (7 seconds kernel time + some user time), meaning you likely crashed very early — on launch, during loading, or right as you joined a match.
Key clues from the dump
NVIDIA GPU stack is heavily involved. The memory scan shows significant references to:
nvwgf2umx.dll — NVIDIA's DirectX 12 driver (built May 5, 2026)
nvcuda64.dll — NVIDIA CUDA runtime
nvapi64.dll — the most referenced non-system module in memory (1,183 references)
Intel XeSS upscaling is loaded. Two XeSS libraries are present:
libxess.dll — built October 2025
libxess_fg.dll — built March 2026 (Frame Generation)
This is very significant. The crash pattern — an invalid pointer read deep inside the rendering thread — is consistent with the known FSR2/XeSS upscaler conflict that many players have reported with BF6's Frostbite engine.
Engine.Render.Core2.PlatformPcDx12.retail.dll is also present, confirming this is the DX12 rendering path.
Most likely cause
The crash strongly resembles the well-documented upscaling/VRAM pointer bug in BF6 where the Frostbite engine's XeSS or DLSS integration dereferences a stale GPU resource pointer during frame generation. The address it tried to read (0x43e30ae8f) is in a region that's consistent with a freed GPU resource handle.
Things to try
Disable Frame Generation in BF6 graphics settings — libxess_fg.dll being present is a red flag given this crash pattern.
Switch upscaler — try TAA or DLSS instead of XeSS if you're on NVIDIA.
Update your NVIDIA drivers — your current driver is from May 5, 2026; check if a newer one is available that addresses BF6 stability.
Disable in-game upscaling entirely and set rendering to native resolution as a test to confirm the cause.
If crashes stop with upscaling off, re-enable one option at a time to isolate the culprit.
Your hardware (16-core CPU, Windows 11 Build 26200, NVIDIA GPU) is not the problem — this is a game engine/driver interaction issue.
CrashDump_2026.05.30_16.21.41.912.mdmp
mdmp
There was a driver update and it just crashed again
May 30
Parse the second crash dump and compare with the first
Parse the second crash dump and compare with the first
The driver update didn't fix it — and this second dump makes the picture even clearer. Here's the comparison:
Second Crash — Same Root Cause, Narrowed Down
What's identical to the first crash
Same exception: ACCESS_VIOLATION (0xC0000005) — read from an invalid pointer
Exact same crash address: bf6.exe+0xb73254 — the very same instruction in Frostbite crashed both times
Same upscaling libraries loaded: libxess.dll (Oct 2025) and libxess_fg.dll (Mar 2026)
What changed with the driver update
Your NVIDIA drivers updated from May 5 → May 19, 2026:
nvwgf2umx.dll (DX12 driver): May 5 → May 19
nvcuda64.dll: May 5 → May 19
nvapi64.dll / nvapi64_impl.dll: new, dated May 19
Despite the new driver, the crash hits the same exact byte in bf6.exe. This strongly rules out the driver as the cause — it's the game engine itself, specifically that instruction at bf6.exe+0xb73254, mishandling a pointer.
The real smoking gun
In the first crash, nvapi64.dll had 1,183 memory references (the top module by far). In this crash, it's been split into nvgpucomp64.dll (923) and nvwgf2umx.dll (884) — the new driver restructured things — but the crash location didn't move at all. That tells you the bug is inside bf6.exe's own code, not inside the driver.
The invalid read address also changed (0x43e30ae8f → 0x3dcbea0f1), which is typical of a use-after-free or dangling pointer — the bad address is different each time because it depends on where memory happened to be allocated that session.
What to do next
Since the driver update didn't help, the fix needs to come from inside the game. Your best bets right now:
Disable Frame Generation (libxess_fg.dll) — this is the most likely trigger. Go to Settings → Graphics → Frame Generation and turn it off.
Switch from XeSS to DLSS or TAA — the XeSS integration in Frostbite has a known pointer management issue at exactly this kind of offset.
Report it to EA — both dumps point to bf6.exe+0xb73254 with the same Frostbite comment. That's a reproducible, reportable bug. Upload both .mdmp files to the EA Forums with this info — same address across two crashes is exactly what the devs need to find and fix it.
Where do I disable frame generation? Settings in which app?
May 30
In Battlefield 6 itself — not Windows or the EA app. Once you're in the game:
Settings → Video → (scroll down to) Upscaling / Frame Generation
The exact label may be "Frame Generation" or "XeSS Frame Generation" — just toggle it off. While you're there, also change the Upscaling Method from XeSS to either DLSS (if you have an NVIDIA card) or TAA as a fallback.
I cannot get into the game, it keeps crashing.
May 30
Good point. You'll need to edit the game's config file directly instead.
Try this:
Open File Explorer and navigate to: Documents\Battlefield 6\settings
Look for a file called something like PROFSAVE_profile or VideoSettings.ini (the exact name varies)
Open it with Notepad and search for any of these settings:
FrameGeneration
XeSSFrameGen
Upscaler or UpscaleMode
Set the Frame Generation value to 0 and the upscaler to something like TAA or 0 (native), then save.
Alternatively, you can try launching with safe video settings via the EA app:
Open the EA app → find Battlefield 6 → click the three dots (...) → look for "Repair" first, then check if there's a "Launch with default settings" or "Safe Mode" option.
If neither of those works and you can't find the config file, let me know and I can look up the exact file name and path for BF6's config — the location can differ slightly depending on whether you're on Steam or the EA app.
GstAudio.3dEnabled 0 GstAudio.Announcer_Voice 0 GstAudio.AudioLanguage 0 GstAudio.AudioQuality 1 GstAudio.CarRadio 0 GstAudio.DiegeticMusic 1 GstAudio.DiegeticRadio 1 GstAudio.Freq_Tinitus 20000.000000 GstAudio.HitIndicatorSound 0 GstAudio.InGameAnnouncer_OnOff 1 GstAudio.MenuNarration 0 GstAudio.Mi
pasted
Here are the options:
May 30
Good news — I can see your config file, and the settings are already in a safe state. Looking at the relevant lines:
GstRender.FrameGeneration 0 GstRender.NVIDIAFrameGenerationEnabled 0 GstRender.NvidiaMultiFrameGeneration 0 GstRender.AMDFrameGenerationEnabled 0 GstRender.IntelFrameGenerationEnabled 0
Frame generation is already disabled across the board. So that's not what's causing your crashes.
Looking further at your config, a couple of other things stand out that are worth changing:
GstRender.Dx12Enabled 0 — you're running DX11, but your crash dumps show the game loading DX12 drivers anyway (D3D12Core.dll, Engine.Render.Core2.PlatformPcDx12). Try flipping this to 1 to force DX12 properly, or the inverse — some people have had luck keeping it at 0 but that's inconsistent with what the engine is actually loading.
GstRender.NvidiaUpscalingTechnique 0 and GstRender.AMDIntelUpscalingTechnique 0 — these are set to 0, which may mean XeSS is still active. The exact value meanings vary, but try setting both to a higher number (typically 2 = TAA, 1 = DLSS/FSR).
Could you tell me where your config file is located? Is it in Documents\Battlefield 6\ or somewhere else? That'll help confirm which version of the game you have and what the upscaling values actually map to.
it is in \documents\battlefield 6
May 30
That matches what we'd expect. The file you shared is your PROFSAVE_profile — that's the right one.
Given that frame generation is already off and the crash is hitting the exact same spot in bf6.exe both times, this is almost certainly a bug EA needs to patch. The two things most worth trying in your config right now:
Enable DX12 properly— openDocuments\Battlefield 6\PROFSAVE_profile in Notepad and change:
GstRender.Dx12Enabled 0
to:
GstRender.Dx12Enabled 1
Change the upscaling technique— on the same lines, change:
GstRender.NvidiaUpscalingTechnique 0 GstRender.AMDIntelUpscalingTechnique 0
to 2 on both (which typically maps to TAA).
Save the file, then try launching. If it still crashes, the next step would be reporting it to EA directly with both your .mdmp files — the fact that it's the same address (bf6.exe+0xb73254) across two different driver versions is exactly the kind of reproducible data they need to find and fix it.
1780183775394_CrashDump_2026.05.30_16.28.46.207.mdmp
mdmp
It crashed again, but it went a little further this time. I saw the BF6 splash screen
May 30
Parse third crash dump and compare with previous two
Parse third crash dump and compare with previous two
This third dump tells us something new and important. Here's the full picture:
Third Crash — Different Location, Same Family of Bug
What changed
This crash hit a slightly different address — bf6.exe+0xb73296 instead of +0xb73254 from before. That's only 66 bytes apart, meaning it's crashing in the same function, just a few instructions later. Enabling DX12 got you a tiny bit further before it fell over.
The process also ran longer this time — 28 seconds of CPU time vs. 9 seconds in the first crash — which matches you seeing the splash screen.
The new clue — DX12 is now active
With Dx12Enabled 1, the dump now shows Engine.Render.Core2.PlatformPcDx12.retail.dll actively in use alongside D3D12Core.dll. The crash is happening during DX12 render initialization, right as the engine is setting up GPU resources for the first rendered frame. The read from address 0x3fac2a000 is another classic dangling/unmapped GPU buffer pointer.
What this means
The bug is in Frostbite's DX12 render initialization path at bf6.exe+0xb732xx. It's crashing whether DX12 is explicitly enabled or not, but it gets a bit further with DX12 on. Either way, this is firmly a game bug, not your hardware or drivers.
Next steps to try
Revert DX12 back to 0— it didn't fix it and the crash location shifted, suggesting DX12 mode hits the same bug differently. SetGstRender.Dx12Enabled back to 0.
Lower your graphics quality significantly in the config — change these values:
GstRender.TextureQuality 0 GstRender.MeshQuality 0 GstRender.ShadowQuality 0 GstRender.EffectsQuality 0 GstRender.LightingQuality 0 GstRender.OverallGraphicsQuality 0
Some users have found the crash is triggered by the engine trying to allocate too much VRAM upfront during init. Dropping everything to minimum reduces that initial allocation.
Report to EA— at this point you have three dumps all pointing to the same function in bf6.exe. Post on theEA Forums tech issues board with all three .mdmp files and mention the crash address bf6.exe+0xb732xx — that's the detail the devs need.
I used the steam client to verify files and it said there were 11 files that needed to be redownloaded. While it was downloading the files, it stopped and I get this error message:
7:26 AM
That's your answer right there — "CORRUPT UPDATE FILES" means Steam downloaded a patch but the files are damaged or incomplete, likely due to a bad connection or a disk issue during the download. This explains all three crashes — you've been running a corrupted install this whole time, not a driver or settings problem.
Here's what to do:
Click the retry button(the circular arrow icon on the right) to try the download again. If your connection is stable it may just work second time.
If it keeps failing, clear Steam's download cache:
Open Steam → Steam menu (top left) → Settings → Downloads → Clear Download Cache
Then try the file verification and redownload again
If it still corrupts, the issue may be your disk:
Run a quick disk check — open Command Prompt as Administrator and type:
chkdsk C: /scan
(replace C: with whatever drive BF6 is installed on)
Also check your drive's free space — Steam needs roughly double the patch size free to download and unpack safely
Last resort— fully uninstall and do a clean reinstall of BF6
The good news is your crashes were almost certainly caused by these corrupted game files hitting that specific render initialization code, not a deeper hardware or engine bug. Once the files are clean it should launch fine.
