Forum Discussion

New Rookie

Re: Crashing to Blue Screen During Match

Since the last update ~2 days ago.

Fix your [removed].

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.

(cm edited format)

10 Replies

Agrikaan
New Rookie
22 days ago
Using XTU to underclock PC seems to mitigate the BSODs for me (core tuning down to x50), as a temporary fix until they get the stuff solved.
---
Given your earlier dump (eaanticheat.sys 0xA IRQL fault):
EAAC is triggering a kernel-level race condition
your previous CPU boost behavior was likely:
too aggressive (rapid frequency/voltage transitions)
or too spiky under load changes (menu → match → simulation load)
XTU underclock reduced that instability envelope
lKovack
Seasoned Newcomer
22 days ago
Thank you for the in depth explanation. I seen your response on another post and came to this link. I assumed it was directly tied to the anti cheat but you breaking it down for us less technically inclined folk was nice of you. I also have underclocked down to x50 instead of 57 for my 14900k for the time being since bf6 is the only issue game.

hopefully this will get escalated and resolved within the coming weeks
Agrikaan
New Rookie
22 days ago
Another INTEL i9 14900k then.
"I see dead patterns".
The bug does seem to be tied to "speed"...
KingxDespair
Rising Newcomer
22 days ago
I also have a intel i9 14900kf. The may 22nd update has made my game unplayable. If im in the menu it hard reboots my pc within 5 minutes but if im in a game it can take up to 20 minutes before happening. No other game does this and as i said it didnt start until after the may 22nd update
dpieske
New Rookie
22 days ago
Same here.....tired of this crashing my computer.....can't play the game!
dpieske
New Rookie
22 days ago
I'm not screwing up my bleeping computer for any game!!!
Tata_9715
Seasoned Newcomer
18 days ago
Hi, still dealing with the same issue but wanted to share some progress.
This time I launched the game without being connected to EA, then signed in from within the game itself to reach the main menu. From there I decided to test the campaign first — and it worked fine.
However, when I went back to the main menu and tried to join an online match, the game crashed right before it could find a game. It never actually matched me — it just closed at that point every single time.
Has anyone else experienced this or found a fix?
CorkingTheDog
Seasoned Newcomer
15 days ago
I've exhausted myself, arriving at BF6 → EA AntiCheat kernel driver → invalid memory access → BSOD (0xA). Happens quickly after joining a match. Does not occur otherwise. Does not occur with any other games. Crashes so violently, rig reboots.
ChrisHabis
New Rookie
15 days ago
In my case I was able to play 4 hours yesterday for the first time in days. I aggressively underclocked my CPU from within the BIOS. Went from 54x to 47x and 0 crashes. The original post mentions that underclocking reduces BSODs so maybe there is some truth to that.
I am running an ASUS Z690-P Prime WIFI motherboard and an intel i7-13700KF.
I will try to play more in the coming days to confirm if this is something we can at least rely on until EA gets their act together.
Agrikaan
New Rookie
5 days ago
In case EA even bothers to read these forums, this is still a thing, 3 weeks later. Not solved.
Plenty of time to get your **bleep** solved, and if you just aren't able or willing to, give us an option to play without your anti-cheat then. We who suffer from this incompetence, would rather play the game WE PAID FOR against the potential threat of a cheater or two, than not being able to play it at all.