Hey! I took a closer look at your WinDbg output, and there's definitely something worth investigating here.
First of all, excellent work collecting the crash dump and providing the exception details. This is considerably more useful than a generic crash report.
Your dump confirms that eaanticheat.gameservice.exe encountered an access violation (0xC0000005), with WinDbg classifying it as an invalid pointer read.
One particularly interesting detail is the instruction at eaanticheat_gameservice_exe+0xa47279b, which attempts an indirect jump through the RAX register.
However, there are two important limitations.
First: The necessary debugging symbols for EA's anticheat weren't available, so the analysis cannot identify the exact internal function responsible.
Second: Although the dump confirms an exception in the Javelin service, it doesn't establish that this exception is responsible for the complete system reboots.
Given that you're also running an i7-14700KF, I'd still want to rule out processor instability, especially considering Intel's documented 13th/14th-generation stability issues.
There's one test I'd be particularly interested in:
Do the timestamps of your Javelin crash dumps match the exact times of your unexpected system reboots?
If they don't, we might actually be looking at two separate issues.
Also, have you found any WHEA-Logger events immediately before the reboots?
I wouldn't recommend reinstalling Windows at this stage. You've already done extensive troubleshooting, and the next step should be collecting evidence that helps distinguish an application crash from a system-level failure.
I'd strongly encourage EA's engineering team to examine your dump, particularly the failure bucket and the anticheat service version 1.0.59063.0.
You've provided enough technical information to justify a proper investigation.
Please keep us updated. I'm genuinely interested in what the additional logs reveal!
Thank you for your reply. The timestamp of the JAVELIN crash data I provided is for the new version of the updated season crashing to the desktop during the game. It can be confirmed that this timestamp is completely consistent with my crash to the system and complete restart of the computer.
As a computer novice, I reply to ISSUES by asking for various possible crashes through DEESPEEK and using AI to troubleshoot my computer's crash issues. Most of the data I report has already been screened by AI, and almost all the evidence points to Battle Eye. This hidden danger may have been buried during the S3 season update and only began to erupt in the S4 version.
This level of bug is almost fatal for a game that has already been publicly released, completely affecting normal gameplay. Therefore, while combating cheating, we also hope that EA can solve this problem as soon as possible.
As for hardware, it can be confirmed that my hardware combination runs 4K graphics of other large games, and even when the screen settings are full, there will be no sudden crash like this. On the other hand, this kind of crash is caused by my constant attention to various data during the game - whether it is GPU usage or RAM and CPU, it still crashes even when it does not exceed 80%, and this kind of crash is almost timed, no matter what I do in the game, even standing still.
Therefore, I focused on the software level as the cause of the crash.
Anyway, thank you for your reply.
Update: I have run OCCT power test (CPU+GPU 100%). At the beginning of the test, the system immediately restarts. This confirms that the system restart is caused by PSU transient power protection (OCP/OPP), but this issue only breaks through my power settings when both GPU and CPU are running at full power. In the game, it is caused by unknown peak power, which may be speculated to be a power consumption limitation issue of the game engine, combined with the issue of crashing.
