Forum Discussion

Seasoned Novice

26 days ago

Solved

javelin anticheat is causing my PC to hard reboot

I've managed to play a little bit of the closed beta so far and while playing my PC would randomly reboot only while playing bf6. There's no BSOD, no warning. It just suddenly reboots and will only do so when playing bf6.

I've done numerous stress testing and diagnosing of my system. I know it's not my components nor is it any of them overheating or failing since they all work for numerous other games and software much more demanding than this game.

This is a similar issue when another anti cheat; the Vanguard anti cheat by riot is active as well. After a unknown period of time, the program will cause my PC to hard reboot.

After checking event viewer and diagnosing the windows dumpfile generated after the hard reboot, I have come to the conclusion that it must be the anti cheat. The windows debugging tool indicates as such:

SYMBOL_NAME: eaanticheat+2d6f589 MODULE_NAME: eaanticheat IMAGE_NAME: eaanticheat.sys STACK_COMMAND: .process /r /p 0xffffd18759ba6080; .thread 0xffffd1874e1e5080 ; kb BUCKET_ID_FUNC_OFFSET: 2d6f589 FAILURE_BUCKET_ID: AV_R_eaanticheat!unknown_function OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {100f1e0a-abcf-3860-2e0c-3546be52e55a} Followup: MachineOwner

I highly recommend looking into this issue since there will soon be many, many more players who will potentially run into this problem and have no idea how to check or try to make sense of this problem.

bug

crashing

ea app

asas621
19 days ago
Nothing in here indicates or alludes any cheating at all. If the first thought you had at seeing super scary debug code is that I must be cheating; I'm sorry to say but you're genuinely a sped. It might look really scary but all it's doing is indicating where in the pipe line is causing the kernel level system crash.
Anyways let me move onto a fix that solved my problem so others can try and actually play the game. Might wanna look away since it clearly frightens you.
I believe I've managed to resolve the issue since I've managed to play three games in a row without a reboot or forced restart. I've updated my drivers to the latest version while also booting CMD as administrator and running:
While not required it's always safe to run "sfc /scannow"
I then ran these two commands "DISM /Online /Cleanup-Image /ScanHealth" followed by "DISM /Online /Cleanup-Image /RestoreHealth"
Once both commands have ran through to the end (it might take some time as it depends on your internet and system) I then was able to boot the game and run without any problems so far. I still have my memory integrity disabled as per the first attempted fix but I'm unsure if that's required so feel free to experiment.
From my understanding the dism command will just go through one by one and replace windows files which should fix any errors caused by missing or corrupted windows files.

6 Replies

asas621
Seasoned Novice
26 days ago
following the solution provided by Battlefield 2042 / EA Anticheat BSOD Bug | EA Forums - 12359060 is a fix for now however this should be resolved as quick as possible due to the amount of tech illiterate users that will soon be having the same issue.

EDIT: not a fix.
asas621
Seasoned Novice
23 days ago
I take it back. This was a temporary fix and the issue still persists.
_Silent1uM_
22 days ago
i've faced similar issue, but my pc isn't rebooting, it goes to sleep mode. I'm playing on laptop and when i turned on monitoring of the system while playing - i noticed, that my cpu is always at 100% and eating a lot of power, temperatures are about 85. I researched this behavior and detected that this is some kind of self defence mechanism of my laptop from overheating. Then i tried to limit the power for the cpu - the problem with sleep mode is gone, temperatures are around 70, and i didn't (!) lost performance in game.
Try to enable monitoring of the power consumption when next weekend start, maybe you'll see something similar. And if you can limit power package for you hardware - you can try it
I'm sure that it's not ok that the game punch the cpu so hard
asas621
Seasoned Novice
20 days ago
The second beta has launched and the issue still persists. It still has the same bucket ID offset however, the failure bucket id has changed.
SYMBOL_NAME: eaanticheat+2d6f589 MODULE_NAME: eaanticheat IMAGE_NAME: eaanticheat.sys STACK_COMMAND: .process /r /p 0xffffd585425ca080; .thread 0xffffd5850cda2080 ; kb BUCKET_ID_FUNC_OFFSET: 2d6f589 FAILURE_BUCKET_ID: 0xF7_MISSING_GSFRAME_eaanticheat!unknown_function OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {481c4c76-a7d7-4788-afc1-fb485413496d} Followup: MachineOwner
Solo_Dozen
New Novice
20 days ago
Love how cheaters are complaining about not being able to play the game if it's anticheat its because it detects it on your system so delete whatever mod or cheating system you have and you should be able to play
asas621
Seasoned Novice
19 days ago
Nothing in here indicates or alludes any cheating at all. If the first thought you had at seeing super scary debug code is that I must be cheating; I'm sorry to say but you're genuinely a sped. It might look really scary but all it's doing is indicating where in the pipe line is causing the kernel level system crash.
Anyways let me move onto a fix that solved my problem so others can try and actually play the game. Might wanna look away since it clearly frightens you.
I believe I've managed to resolve the issue since I've managed to play three games in a row without a reboot or forced restart. I've updated my drivers to the latest version while also booting CMD as administrator and running:
While not required it's always safe to run "sfc /scannow"
I then ran these two commands "DISM /Online /Cleanup-Image /ScanHealth" followed by "DISM /Online /Cleanup-Image /RestoreHealth"
Once both commands have ran through to the end (it might take some time as it depends on your internet and system) I then was able to boot the game and run without any problems so far. I still have my memory integrity disabled as per the first attempted fix but I'm unsure if that's required so feel free to experiment.
From my understanding the dism command will just go through one by one and replace windows files which should fix any errors caused by missing or corrupted windows files.