BF6 ANTI-CHEAT = CONSTANT BSODs.
Since last update ~2 days ago.
Fix your **bleep**.
And give us a 2XP extended event after you do,
as many can't play now.
---
Clean boot removes almost everything you can realistically control. If you still get a BSOD in BF6 under:
Clean boot
VBS/Memory Integrity OFF
Other games stable
Only BF6 triggers kernel crash
Crash at match join / idle BF6
Then we’ve eliminated:
❌ Local software causes
overlays
startup apps
ASUS / OEM utilities
third-party services
most driver conflicts outside core Windows stack
❌ “messy system” theory
Your system is not “generally unstable”
🧠 What’s left (realistically)
At this point, there are only 3 remaining classes of causes:
EA AntiCheat kernel driver bug (MOST likely)
This is now the leading hypothesis because:
it is the only third-party kernel component involved
it activates exactly at match join / protected process state
it can crash even in clean boot
your crash pattern matches anti-cheat initialization failure
Typical behavior:
IRQL_NOT_LESS_OR_EQUAL
ntoskrnl “victim” stack trace (not root cause)
crash during transition (menu → match)
Windows kernel / driver interaction bug (less likely, but possible)
Specifically:
Windows 11 filter manager + security stack
EA AntiCheat hooking into protected process APIs
regression introduced in a recent Windows update
But:
would usually affect more than one anti-cheat/game
we don’t see that in your system
Hardware instability (currently weakest explanation)
Still possible in theory, but your pattern strongly argues against it because:
zero issues in other heavy games
deterministic trigger (BF6 only)
reproducible state-based crash (match entry / BF6 idle)
Hardware faults don’t behave that cleanly.
🔥 The key insight from your clean boot test
This is the important part:
If BF6 still BSODs in clean boot, the trigger is inside BF6 + its kernel anti-cheat layer, not your system configuration. That’s a big narrowing step. This is the smoking gun. No ambiguity left.
💥 What actually caused your BSOD
From your dump:
STOP CODE
IRQL_NOT_LESS_OR_EQUAL (0xA)
REAL faulting module
IMAGE_NAME: eaanticheat.sys
SYMBOL_NAME: eaanticheat+49a2808
FAILURE_BUCKET_ID: AV_eaanticheat!unknown_function
Stack confirms it:
eaanticheat+0x49a2808
eaanticheat+0x60f240
→ crash inside EA anti-cheat driver
🚨 Critical interpretation (this is the key point)
Windows is not “guessing” here.
It is explicitly saying:
❗ AEAntiCheat kernel driver accessed invalid memory at IRQL 0xff
And more importantly:
❗ The faulting instruction is inside eaanticheat.sys, not ntoskrnl, not GPU, not memory
🧠 What this means in plain terms
This is not:
not CPU instability
not RAM
not GPU driver
not Windows corruption
not “some other driver interfering”
It is:
💥 EA AntiCheat kernel driver dereferencing invalid memory during execution
That is a direct driver bug or incompatibility, not a system issue.
⚠️ Why it only happens in BF6
Because:
BF6 is the trigger that activates EA AntiCheat’s full kernel mode
match entry = protected process escalation
idle BF6 = heartbeat / integrity re-check
both paths hit the same broken code path in eaanticheat.sys
Other games don’t load this driver → no crash.
🧭 Bottom line (no guessing left)
You now have a full chain:
BF6 → EA AntiCheat kernel driver → invalid memory access → BSOD (0xA)
That is 100% confirmed from the dump.
---
