BF6 BSOD on Launch

I posted a very similar issue in the CF27 fourm.  Tried Madden 26 and CF27.  Same Anticheat crashes for both.  

https://forums.ea.com/discussions/college-football-27-technical-issues-en/college-football-27-pc-%E2%80%93-repeated-ea-javelin-anticheat-crash--0xc0000005/13682298

Why doesn’t anticheat work you can report people blatantly hacking and nothing happens yet my mate with a raunchy name gets banned indefinitely these devs need to fix priorities seriously bunch of spuds 

Did you manage to get it working? I have had the same issue since May

Nope. And EA doesn't seem to [removed]

I tried after each update, installed/reinstalled Windows updates, every Javelin version since then, uninstalled VPN, booted without any drivers, and it still crashes.

Also, sent the full dump (with other relevant files) to EA_Shepard​ and attached dump analysis here. Reminded them multiple times. Nothing.

This affects Battlefield 2042 as well, making both games basically unusable. I don't think this is important enough for them to address. Too few people are having the issue, so they probably figure "100 people not being able to play won't cost us any reputation". And they're right. It's free money, as far as they are concerned.

(cm removed language, please be mindful of word choice)

Hey, folks

First, apologies for not getting back to those who replied to my requests. I am not sure why I never saw them.

If you are still running into the annoying BSOD, please provide me with the following

• Crash dump logs: C:\Users\<WindowsUser>\Documents\Battlefield 6\CrashDumps
• AntiCheat crash dump logs: C:\ProgramData\eaanticheat\Crashdumps
• Attach a DxDiag

I will be able to look through them and see what is happening.

Hey, EA_Shepard​,

Maybe it was a bug or just too many things in the inbox.

The crash dump logs aren't available, because the crash happens in the driver, before anything can be saved to the disk.

I'm attaching the crash dump analysis and DxDiag outputs here: Crash.zip.

I'm also resending the previous full zip file with dumps, EAAC, event logs, system info, WinDbg, WER and other logs to your inbox. Hope it doesn't get buried by other stuff again.

XIO-X2​ 

First off, huge apologies for the delay in getting back to you on your dump file. I understand how frustrating it is to sit on a high-end rig that should easily crush these games and instead end up staring at a Blue Screen every time you try to launch. The good news is your rig exceeds the specs, so no issue there.

I dug straight into your minidump (091826-19531-01.dmp) and the DxDiag you attached, and here is exactly what is happening:

Your PC specs (i9-12900KF, RTX 3080, 64 GB RAM) are far above the recommended requirements—hardware power is definitely not the problem.

The crash is a Bug Check 0x50 (PAGE_FAULT_IN_NONPAGED_AREA) occurring in eaanticheat.sys right as the Windows Filter Manager (FLTMGR) initializes. Because both Battlefield 6 and Battlefield 2042 share the same kernel anti-cheat engine, eaanticheat.sys hitting an invalid memory pointer crashes the Windows kernel before either game can boot into menus.

1. Clean Reinstall EA AntiCheat:
   • Go to C:\Program Files\EA\AC (or your game install folder).
   • Right-click EAAntiCheat.Installer.exe and select Run as Administrator.
   • Select Uninstall All.
   • Restart your PC, relaunch the EA app / Steam as Administrator, and let the game re-prompt the fresh anti-cheat install.
2. Update / Unplug the PreSonus Studio 26c Audio Driver:
   • Your DxDiag shows the PreSonus driver (PaeStudioUsbks.sys) is from September 2022. Kernel-mode USB audio drivers can clash with anti-cheat file system sweeps. Grab the latest driver update from PreSonus, or unplug the audio interface temporarily and test using regular monitor/headphone audio to see if it bypasses the BSOD.
3. Disable ASUS Armoury Crate / ROG Peripheral Helpers:
   • Your system is running ASUS background drivers (ROGMS.sys, ArmouryLiveUpdate). Background lighting and peripheral hooks in Armoury Crate are known to clash with kernel-level memory scans. Try pausing Armoury Crate services or running a clean boot to test.
4. Temporarily Disable the Meta Virtual Monitor:
   • In Device Manager under Display Adapters, right-click Meta Virtual Monitor and choose Disable device to avoid WDDM hook conflicts.

Give the EA AntiCheat reinstall and the PreSonus check a run first, and let me know if the BSOD stops or changes codes. We'll get this sorted out with you!

Also, you're on the Insider Preview - AC does not like this, so my suggestion would be to change that.