PC Crash on Campaign Launch ONLY - c0000005 Access Violation in ntdll.dll

SUMMARY

Battlefield 6 crashes to desktop every single time I try to launch the Campaign specifically. The game restarts itself first (required to switch into Campaign mode), and the crash happens right after the restart, during loading. Multiplayer works completely fine on the same install with the same settings - this issue is isolated to the Campaign launch path. I have collected 5 crash dumps across multiple attempts and troubleshooting steps, and the exception is byte-for-byte identical every time - same exception code, same relative offset in ntdll.dll, same call chain through the NVIDIA driver.

SYSTEM INFO

- GPU: NVIDIA RTX 3060ti

- OS: Windows 11 25H2

- CPU: i7-8700

- Game path: F:\Battlefield 6\bf6.exe

CRASH DETAILS (consistent across all 5 dumps)

- Exception code: 0xC0000005 (STATUS_ACCESS_VIOLATION)

- Access type: Write (parameter 0 = 0x1)

- Faulting address written to: 0x24 (near-null pointer + small offset)

- Faulting module: ntdll.dll

- Faulting offset: ntdll.dll+0x2f6a3 (identical in every single dump, including after a full driver reinstall which changed the module's base address via ASLR - only the relative offset stayed constant)

- Call chain leading to the crash (from heuristic stack analysis): bf6.exe -> nvwgf2umx.dll (NVIDIA D3D12 UMD) -> D3D12Core.dll -> ntdll.dll heap functions

- Pattern is consistent with heap corruption triggered during shader/pipeline creation while loading Campaign-specific assets.

SCOPE: CAMPAIGN ONLY, EVERY ATTEMPT, FROM A FRESH START

- Multiplayer launches and runs with no crashes on the exact same install/config.

- Every single attempt was a brand new Campaign playthrough (no carried-over save file), so this is not tied to a corrupted save - it crashes on the very first mission load, every time, from a clean start.

- Confirmed via Task Manager that the old bf6.exe process fully exits (no lingering/zombie process) before the new process starts during the Campaign restart.

- Tested at minimum graphics/texture settings (lowest VRAM footprint possible) - identical crash.

- Checked Windows Event Viewer (System log) at the time of the crash - no WHEA-Logger or Kernel-Power (Event ID 41) hardware error entries. Only a normal, clean load and unload of the anti-cheat component is logged.

TROUBLESHOOTING ALREADY COMPLETED (no change in crash signature after any of these)

1. Verified/repaired game files via launcher
2. Fully updated NVIDIA driver to latest Game Ready
3. Disabled all overlays (GeForce Experience, Discord, RTSS, Game Bar)
4. Disabled DLSS and Frame Generation entirely in-game settings
5. Disabled FSR (Frame Generation and upscaling) in-game settings
6. Cleared NVIDIA shader cache and DirectX shader cache (D3DSCache)
7. Disabled Windows compatibility mode settings on bf6.exe and launcher
8. Added game folders to Windows Defender exclusions
9. Switched display mode from Exclusive Fullscreen to Borderless Windowed (edited GstRender.FullscreenMode / GstRender.FullscreenEnabled in PROFSAVE_profile)
10. Full clean driver wipe and reinstall using DDU in Safe Mode, followed by fresh driver install - crash signature (exact same offset) remained identical afterward
11. Disabled Memory Integrity / Core Isolation (HVCI) and checked for conflicting third-party kernel-level drivers (RGB/OC software) - no change
12. Confirmed via Task Manager that no lingering/zombie bf6.exe process exists during the Campaign restart before the new process launches
13. Tested at minimum graphics/texture settings - no change
14. Checked Windows Event Viewer for hardware errors (WHEA/Kernel-Power) at time of crash - none found; anti-cheat logs show normal clean load/unload
15. Reset the entire local profile/config folder (Documents\Battlefield 6) to rule out a corrupted settings file - no change

NOT YET TESTED

- RAM stability test (MemTest86) - don't currently have the ability to run this

WHY I BELIEVE THIS IS REPRODUCIBLE/USEFUL DATA

Across 5 separate crash dumps, taken before and after a complete GPU driver wipe/reinstall, the crash always lands on the exact same relative offset (ntdll.dll+0x2f6a3) via the same call chain through the NVIDIA D3D12 driver, and it is isolated specifically to the Campaign launch path (Multiplayer is unaffected). The fact that the offset didn't shift even after the driver reinstall (which changed all module base addresses due to ASLR) strongly suggests this is a deterministic code-path bug in the Campaign-specific loading/initialization code, rather than random memory/hardware instability or a general driver problem.

CRASH DUMPS

https://drive.google.com/drive/folders/1T7n0FBUMeYxvz_0sfR8z6oOC_MMmoMTf?usp=sharing

Happy to provide additional dumps, DxDiag, or test any suggested workaround. Let me know if there's any other diagnostic info that would help track this down.