BF6 PC Crash Persistent c0000005 Access Violation
Battlefield 6 consistently crashes or stalls pointing to an Access Violation (c0000005). After extensive troubleshooting and analysis of multiple Crash Dumps via WinDbg, the issue appears to be a conflict between the Windows 11 24H2 Kernel (Build 26100) and the game engine/Anti-Cheat, which triggers system-level mitigations (APPLICATION_VERIFIER_LOADED: 1) that cannot be disabled by the user.
System Specifications:
CPU: Intel Core i9-9900KF
GPU: Nvidia RTX 4060 (Latest Drivers, Clean Install via DDU)
RAM: 64GB DDR4 3200MHz
OS: Windows 11 Pro, Version 24H2 (Build 26100.1)
Storage: SSD formatted in NTFS (Clean install verified)
Technical Analysis (WinDbg): Despite a clean installation on an NTFS drive and a full registry reset (verifier /reset), every crash dump consistently reports:
Exception Code: c0000005 (Access Violation) inside ntdll.dll or bf6.exe.
Verifier Flag: APPLICATION_VERIFIER_LOADED: 1 is ALWAYS present in the dumps, even though I have manually reset Application Verifier and cleared all Image File Execution Options registry keys. This indicates the OS Kernel is enforcing it automatically.
Fault Type: INVALID_POINTER_WRITE attempting to write to address 0x00000000.
Recent Behavior: Even when the game stalls (GameStall_2026.01.17...), the underlying error remains c0000005 triggered by memory protection violations.
------------------------------------------------------------------------
Troubleshooting Steps ALREADY TAKEN (Please do not suggest these):
-Clean Install: Game uninstalled via Revo Uninstaller (Registry scrubbed) and reinstalled on a freshly formatted NTFS SSD (ruling out exFAT issues).
-Drivers: GPU drivers wiped with DDU and reinstalled.
-OS Integrity: sfc /scannow and DISM commands run (no corruption found).
-Boot Environment: Performed a Clean Boot (disabled all non-MS services).
- Registry: Manually checked Image File Execution Options, AppCompatFlags, and FTH keys. All are clean.
-Hardware: RAM tested (XMP on/off makes no difference, this is a software violation, not hardware instability).
Conclusion: The persistence of the APPLICATION_VERIFIER_LOADED flag on a clean, registry-reset system strongly suggests that Windows 11 Build 26100 (24H2) is automatically applying a compatibility shim or mitigation policy that breaks the game. I request this be escalated to the dev team to investigate compatibility with the Germanium (24H2) kernel.
