BF6 BSOD on Launch

This doesn't fully solve it, however. I know I'm being obnoxious with this, but the issue can't be just with the memory. I have the latest BIOS, which purportedly fixes memory issues (B660M DS3H, version F35a) and it still crashes: Battlefield 6 BSOD 0x50 in eaanticheat.sys | EA Forums - 13474083.

SQuiD-FPV​ That is great news! It's also feedback we can send over to the team as well. The BIOS is called out often, so hopefully this helps other players as well.

Thanks!

I uninstalled and then ran the installer with admin privileges. It still crashes.

Here's some of the WinDbg analysis output:

    IMAGE_NAME:         eaanticheat.sys
    MODULE_NAME:        eaanticheat
    PROCESS_NAME:       bf6.exe
    FAILURE_BUCKET_ID:  AV_eaanticheat!unknown_function
    FAILURE_ID_HASH:    {d544cf09-4735-e698-77c3-5df5924e5448}

Dump analyzed
-------------
Dump file:
    C:\WINDOWS\Minidump\062126-16828-01.dmp

Debug session time:
    Sun Jun 21 16:22:46.943 2026 (UTC + 2:00)

System uptime at crash:
    0 days 7:20:21.636

Windows kernel:
    Windows Kernel Version 26100 MP (24 processors) x64
    ntkrnlmp.exe file version: 10.0.26100.8655

Bugcheck
--------
WinDbg command:
    !analyze -v

Bugcheck:
    PAGE_FAULT_IN_NONPAGED_AREA (50)

Bugcheck arguments:
    Arg1: ffffe480cb703000    memory referenced
    Arg2: 0000000000000000    read access
    Arg3: fffff805563ee6de    instruction address that referenced bad memory
    Arg4: 0000000000000000    reserved

WinDbg key fields:
    AV.PTE:                        Invalid
    AV.Type:                       Read
    Failure.Bucket:                AV_eaanticheat!unknown_function
    Failure.Exception.IP.Address:  0xfffff805563ee6de
    Failure.Exception.IP.Module:   eaanticheat
    Failure.Exception.IP.Offset:   0x188e6de
    Failure.Hash:                  {d544cf09-4735-e698-77c3-5df5924e5448}

Primary WinDbg classification:
    BUGCHECK_CODE:       50
    BUGCHECK_P1:         ffffe480cb703000
    BUGCHECK_P2:         0
    BUGCHECK_P3:         fffff805563ee6de
    BUGCHECK_P4:         0
    PROCESS_NAME:        bf6.exe
    IP_IN_PAGED_CODE:    eaanticheat+188e6de
    SYMBOL_NAME:         eaanticheat+188e6de
    MODULE_NAME:         eaanticheat
    IMAGE_NAME:          eaanticheat.sys
    FAILURE_BUCKET_ID:   AV_eaanticheat!unknown_function
    FAILURE_ID_HASH:     {d544cf09-4735-e698-77c3-5df5924e5448}

Faulting instruction
--------------------
WinDbg command:
    u fffff805563ee6de L20

Faulting instruction:
    eaanticheat+0x188e6de:
    fffff805`563ee6de 448b4c0308  mov r9d,dword ptr [rbx+rax+8]

Surrounding disassembly:
    fffff805`563ee6d7 4c8b0403        mov     r8,qword ptr [rbx+rax]
    fffff805`563ee6db 4931c8          xor     r8,rcx
    fffff805`563ee6de 448b4c0308      mov     r9d,dword ptr [rbx+rax+8]
    fffff805`563ee6e3 4131d1          xor     r9d,edx
    fffff805`563ee6e6 4d09c1          or      r9,r8
    fffff805`563ee6e9 0f8544ffffff    jne     eaanticheat+0x188e633

Faulting memory address / PTE
-----------------------------
WinDbg command:
    !pte ffffe480cb703000

Result:
    VA ffffe480cb703000

    PTE contains:
        00007A7000000000

    Status:
        not valid
        Page has been freed

This is consistent with a read from invalid/freed memory at the faulting instruction inside eaanticheat.sys.

Stack excerpt
-------------
WinDbg command:
    kv

Relevant stack:
    nt!KeBugCheckEx
    nt!MiSystemFault+0x78d
    nt!MmAccessFault+0x646
    nt!KiPageFault+0x38b
    eaanticheat+0x188e6de

Full relevant stack excerpt:

    ffffaf84`b1425de8 fffff805`a0b131dd : 00000000`00000050 ffffe480`cb703000 00000000`00000000 ffffaf84`b1426050 : nt!KeBugCheckEx
    ffffaf84`b1425df0 fffff805`a0abe9e6 : 00000000`00000000 ffff8000`00000000 ffffe480`cb703000 0000007f`fffffff8 : nt!MiSystemFault+0x78d
    ffffaf84`b1425ee0 fffff805`a0eb85cb : ffff9f81`944dc8e0 fffff805`3238be68 ffffe480`cdafd000 ffffaf84`b1421001 : nt!MmAccessFault+0x646
    ffffaf84`b1426050 fffff805`563ee6de : 00000000`00000001 27ab0d34`dab9a830 ffffaf84`b142662f e4609729`c98bcf9c : nt!KiPageFault+0x38b
    ffffaf84`b14261e0 00000000`00000001 : 27ab0d34`dab9a830 ffffaf84`b142662f e4609729`c98bcf9c ffffaf84`b1426310 : eaanticheat+0x188e6de

Thread / process
----------------
WinDbg command:
    !thread

Relevant fields:
    THREAD:          ffff9f81941cb080
    Owning process:  ffff9f8178e1c080
    Image:           bf6.exe
    State:           RUNNING on processor 14

EA AntiCheat module information
-------------------------------
WinDbg command:
    lmvm eaanticheat

Result:
    start:       fffff805`54b60000
    end:         fffff805`59bbe000
    module:      eaanticheat
    image file:  eaanticheat.sys
    timestamp:   Thu Jun 11 00:50:01 2026 (6A29EA19)
    checksum:    037890F5
    image size:  0505E000
    symbols:     no private symbols loaded

Relevant loaded-driver context
------------------------------
The faulting stack shown above is nt -> page fault handling -> eaanticheat.sys. The stack does not show NVIDIA, Defender, Code Integrity, NordVPN, WireGuard, OpenVPN, ASUS/MSIO, or other third-party drivers as the executing faulting frame.

Some other loaded modules observed in the dump, for completeness:

    nvlddmkm.sys       loaded; not present in the faulting stack
    CI.dll             loaded; not present in the faulting stack
    WdFilter.sys       loaded; not present in the faulting stack
    WdNisDrv.sys       loaded; not present in the faulting stack
    NDivert.sys        loaded; not present in the faulting stack
    nordlwf.sys        loaded; not present in the faulting stack
    tapnordvpn.sys     loaded; not present in the faulting stack
    wireguard.sys      loaded; not present in the faulting stack
    ovpn-dco.sys       loaded; not present in the faulting stack
    MsIo64.sys         loaded; not present in the faulting stack
    AsIO2.sys          loaded; not present in the faulting stack
    AsIO3.sys          loaded; not present in the faulting stack

Notes
-----
1. The crash still occurs after reinstalling EA AntiCheat / Javelin as administrator.
2. The active process at the crash is bf6.exe.
3. The faulting instruction pointer is inside eaanticheat.sys.
4. The access type is read.
5. The referenced page is invalid and marked as freed by !pte.
6. The failure hash is stable:
       {d544cf09-4735-e698-77c3-5df5924e5448}

I went to try BF6 again during the free trial after previously playing before during beta and the previous free weekend or whatever it was and it worked fine. This time I got the BSODs. What I noticed is that the BF6 installer corrupts the EA anti cheat (the installer becomes completely broken) every time. It also affected BF2042 which was working 100% fine prior to installing BF6.

I was able to fix it for 2042 by uninstalling EA AC from it's installer, and letting BF2042 repair it while running the EA app as admin. I then attempted to try the same thing for BF6 to see if it fixed it. I was able to play for about 1 minute before the BSOD came anyways. BF2042 was affected again but this time it could not be repaired. My crashdumps seem to point to the same thing as yours.

EA AC seems to have completely destroyed itself with the installation of BF6...

(Solved for my case, check my latest reply)*****

I have this as well.. BSOD. I played it 3 ish weeks ago. after months of waiting for updates to make it actually Battlefield. It finally looks decent to play..

Updated it, now it BSOD for 3 days. Can't fix it. Requested a refund in steam. Cbf with it(refund denied lol. 200hrs)

XIO-X2​ Hey, if the Javelin driver was the issue, have you run the Javelin updater as admin by chance or at all? If so, did the crash dump logs give the same errors?

Happens for me as well. I inspected the crash dump with WinDbg and Javelin driver was the culprit. I tried disabling any potential conflicting drivers and anything that was doing screen overlays and it still crashes. They need to fix the drivers.

I'm having the same issue. I was able to determine the exact offset where a bad read is causing the BSOD: 0x80BA2C. 

A single instruction in EA's anti-cheat does a read through a pointer, and that pointer holds a different invalid value every crash. The code is constant; the data it loads is garbage. That is the classic signature of a software defect — an uninitialized, stale, or use-after-free pointer — not a hardware defect.