EA Javelin anticheat - Error 95

I have same ıssue . not solved . reınstall game and re ınstall antı cheat . please fıx ıt . before antı cheat update game was smooth

+I fear your update bricked new things in the anticheat on other machines...

My game had yesterday first connection issues with an unkown error. (Probably unrelated)

Then on restart and rejoin in a Nightfall match I was thrown out of the match (maybe due to inactivity or connection - there was no info) and the game crashed without an error.

I of course restart the game and very shortly after a text appears on my screen that my pc needs to be restarted.

It triggers memory retraining with a boot for like 69s. And I can find out afterwards that I had a bluescreen. Windebug points directly to eaanticheat.sys.

Start of the windebug:

"IRQL_NOT_LESS_OR_EQUAL (a)

An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses.

If a kernel debugger is available get the stack backtrace."

First mention of ea anticheat follows shortly

"Debugging Details:

------------------

*** WARNING: Unable to verify timestamp for eaanticheat.sys"

It also appears in the stacm trace which I ommitted here. I'm acutally unsure if it would be clever to post it publicly. However, it ends with identifying the following names. (My pc is running Win11 I don't know why windebug thinks it is win10)

"SYMBOL_NAME: eaanticheat+c4e856

MODULE_NAME: eaanticheat

IMAGE_NAME: eaanticheat.sys

STACK_COMMAND: .process /r /p 0xffff95836057a040; .thread 0xffff958394309080 ; kb

BUCKET_ID_FUNC_OFFSET: c4e856

FAILURE_BUCKET_ID: AV_eaanticheat!unknown_function

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

Followup: MachineOwner

---------"

Bf is the only game that has ever bluescreened or hardcrashed my current pc in general. In the past it caused 2 unrelated nvidia driver tdr crashes but that's at least partially the fault of Nvidia's drivers but partially also your game's fault as it loved/sometimes still loves to throw "directX device hung" errors that seemingly very rarely make the driver hardcrash.

Edit: my crash feels related to the crash of the person reporting a hardcrash in this thread a few days ago. However, it happened today at 1:30 at central european time, so after your update.

I tried to repair the anticheat, which maybe worked, the software feels a bit off, as it is not really well communcating. I played one round on Hagental Base afterwards without new issues. However, I don't think that it's fully solved.

I really hope you can fix this.. 

Can someone hell me if this will get me banned? It has only happened once and I have been playing just fine since but if there is a chance to get banned then I will stop until it’s fixed. 

Sc0tch_Whiskey​ I doubt that this can get anyone banned. It's clearly a bug or even a bunch of bugs of EA's Anticheat. (Nearly as if it wasn't clever that every major dev creates their own kernel level anticheat with its own bugs)