Re: BF6 Crashing to BSOD on Launch

Apparently, [removed] doesn't care about this issue. Battlefield 2042 crashes with the same errors, so I basically have two unplayable games on my PC which cannot be refunded.

Here's the info from the last crash (I can provide the full dump file, if necessary, but this should be enough to figure out the issue):

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}

(cm edit removed mass tag)

Battlefield 6 consistently causes a Windows BSOD on launch after reinstalling EA AntiCheat / Javelin as administrator.

This is not a normal user-mode game crash. The latest minidump points to EA AntiCheat / Javelin as the faulting kernel module.

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

Bugcheck:
PAGE_FAULT_IN_NONPAGED_AREA (0x50)

Bugcheck arguments:
Arg1: ffffe480cb703000
Arg2: 0000000000000000
Arg3: fffff805563ee6de
Arg4: 0000000000000000

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

Faulting instruction:
eaanticheat+0x188e6de:
mov r9d,dword ptr [rbx+rax+8]

The referenced address is invalid. WinDbg !pte reports that the page has been freed.

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

EA AntiCheat module:
eaanticheat.sys
Timestamp: Thu Jun 11 00:50:01 2026
Checksum: 037890F5
Image size: 0505E000

Already tried:

• Reinstalled EA AntiCheat / Javelin as administrator
• Reinstalled EA AntiCheat / Javelin multiple times before that
• Cleared EA App, Battlefield, and shader caches
• Reinstalled NVIDIA drivers
• Disabled Discord and NVIDIA overlays
• Updated motherboard BIOS
• Disabled MSIO / Asusgio2 / Asusgio3 kernel drivers
• Tested CPU ratio cap workaround
• Verified TPM and Secure Boot

The crash still reproduces.

I can provide the full minidump, full WinDbg output, msinfo32, DxDiag, and event logs privately to EA staff.

Please escalate this failure hash to the EA AntiCheat / Javelin engineering team:
{d544cf09-4735-e698-77c3-5df5924e5448}

Have same problems with BSOD crashes in 3rd season, idk why they cant fix it in first week *facepalm*

Happened at 3rd season for me too. First thing I tried updating the BIOS, but it didn't help (it helped some others, though, so worth trying).

didnt help me 2

Yeah I have the same issue however im on Ryzen

Tried literally everything 
Tried updating BIOS
nothing worked 
It is 100% Javelin issue
And it has been persistent for a month

It's been there since the start of Season 3 and I haven't been able to play that season at all. Crashes every time. It's definitely a Javelin issue.

I have now compared your minidump details to mine and they are exactly the same.
I cant play since late may which I believe have been an extra update, however I have been playing Golmud when it released.

Im on build 26200 and Ryzen so its not platform specific either.

PROCESS_NAME:  bf6.exe

IP_IN_PAGED_CODE: 
eaanticheat+188e6de
fffff803`7e37e6de 448b4c0308      mov     r9d,dword ptr [rbx+rax+8]

STACK_TEXT:  
fffffd88`e27c5e68 fffff803`d23131dd     : 00000000`00000050 ffff8086`d8e93000 00000000`00000000 fffffd88`e27c60d0 : nt!KeBugCheckEx
fffffd88`e27c5e70 fffff803`d22be9e6     : 00000000`00000000 ffff8000`00000000 ffff8086`d8e93000 0000007f`fffffff8 : nt!MiSystemFault+0x78d
fffffd88`e27c5f60 fffff803`d26b85cb     : ffffa709`d35cd050 fffff803`63b7be68 ffff8086`ccfff000 fffffd88`e27c1001 : nt!MmAccessFault+0x646
fffffd88`e27c60d0 fffff803`7e37e6de     : 00000000`00000001 27ab0d34`dab9a830 fffffd88`e27c66af e4609729`c98bcf9c : nt!KiPageFault+0x38b
fffffd88`e27c6260 00000000`00000001     : 27ab0d34`dab9a830 fffffd88`e27c66af e4609729`c98bcf9c fffffd88`e27c6390 : eaanticheat+0x188e6de
fffffd88`e27c6268 27ab0d34`dab9a830     : fffffd88`e27c66af e4609729`c98bcf9c fffffd88`e27c6390 ffff8086`d8e91070 : 0x1
fffffd88`e27c6270 fffffd88`e27c66af     : e4609729`c98bcf9c fffffd88`e27c6390 ffff8086`d8e91070 00000000`0000000e : 0x27ab0d34`dab9a830
fffffd88`e27c6278 e4609729`c98bcf9c     : fffffd88`e27c6390 ffff8086`d8e91070 00000000`0000000e fffffd88`e27c6318 : 0xfffffd88`e27c66af
fffffd88`e27c6280 fffffd88`e27c6390     : ffff8086`d8e91070 00000000`0000000e fffffd88`e27c6318 00000000`00000000 : 0xe4609729`c98bcf9c
fffffd88`e27c6288 ffff8086`d8e91070     : 00000000`0000000e fffffd88`e27c6318 00000000`00000000 00000000`00000070 : 0xfffffd88`e27c6390
fffffd88`e27c6290 00000000`0000000e     : fffffd88`e27c6318 00000000`00000000 00000000`00000070 5a4d0101`00000218 : 0xffff8086`d8e91070
fffffd88`e27c6298 fffffd88`e27c6318     : 00000000`00000000 00000000`00000070 5a4d0101`00000218 ffffffff`80005f1c : 0xe
fffffd88`e27c62a0 00000000`00000000     : 00000000`00000070 5a4d0101`00000218 ffffffff`80005f1c ffffa709`cf8f2850 : 0xfffffd88`e27c6318


SYMBOL_NAME:  eaanticheat+188e6de

MODULE_NAME: eaanticheat

IMAGE_NAME:  eaanticheat.sys

STACK_COMMAND: .process /r /p 0xffffa709ca771080; .thread /r /p 0xffffa709c90a90c0 ; kb

BUCKET_ID_FUNC_OFFSET:  188e6de

FAILURE_BUCKET_ID:  AV_eaanticheat!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {d544cf09-4735-e698-77c3-5df5924e5448}

I merged your thread with a larger thread with similar issues from the community.

I have a full dump, WER files, logs, DxDiag and SysInfo32 outputs all packaged, if someone wants to look at it.

XIO-X2​ Hey,

Yes. Please upload them here so that we can review them.

Thanks

EA_Shepard​ Hi,

I sent you a direct message with the link to the full package, because I don't want to post specific system details on a public thread.

Thank you for taking the time to look into this.