Hello friend
Penguin give big thanks for the recent chat about this issue.
For clarity here is a list of what has been performed and tested:
1. Set BF6.exe and EA AntiCheat launcher to Run As administrator.
2. Checked Windows Event Viewer for crash logs. (⚠️Access violation possibly from software conflict between AMD and NVIDIA software 👉 Detected 🔔, attempted to uninstall the AMD software to ensure it's not due to that software conflict, crash still persists.)
3. Ran Windows repair Commands in CMD (Admin)
DISM /online /Cleanup-image /restoreHealth
sfc /scannow
4. Reinstalled EA AntiCheat using EAAntiCheat.installer.exe(Uninstall All 👉 Reinstall.)
5. Checked GPU drivers. (GeForce drivers updated.)
6. Cleared NVIDIA Shader cache (%localappdata%\NVIDIA cache folders)
7. Verified TPM status using tpm.msc (Confirmed ''Ready for use''
Not yet confirmed tested:👇
Update Bios and Chipset driver.
Official Asus Mother Board steps:👉 https://www.asus.com/support/faq/1012815/
Penguin recommend you only follow the steps given by your motherboards manufacturers for this, safety = key 🛡️🔑
In Penguins understanding EA AntiCheat operates at a low system level and verfifies hardware security features and driver signatures.
Outdated motherboard chipset drivers or old BIOS version can sometimes cause the anticheat to fail its integrity checks.
ASUS official website also recommends to make sure of this: ''If your system currently has Secure Boot enabled, please ensure these certificates are updated before they expire in mid-2026.''
Chipset drivers do control communication between Windows and important hardware components such as:
CPU
PCIe Devices such as👉 GPU(AMD and NVIDIA conflict may be due to this? Speculation, Penguin pinch of salt situation🐧)
TPM security module
And general system buses.
If these drivers are outdated, EA AntiCheat may incorrectly detect a driver signature or hardware validation issue occurs, which can lead to access violation crashes as seen in the Windows Event viewer log, or even the game closing itself immediately at launch. (This step has resolved some earlier cases where Penguin been involved with different community members having similar issues, primarily from Discord🐧)
At this point Penguin is running out of more suggestions to provide for this case.
And starting to suspect the game update itself is the primary culprit if the last steps don't solve it.
Many thanks for posting friend!
Penguin
