BUG REPORT – EasyAntiCheat_EOS.sys Kernel Scan Loop

Additional technical clarification:

This issue previously affected Fortnite and VRChat on the same system and was resolved for both games after updates.

The problem now persists only in Apex Legends, which strongly suggests an Apex-specific Easy Anti-Cheat EOS regression, not a system or configuration issue.

i think i have the same issue but the game crashes when trying to play any mode except firing range it started with the merry mayhem drop "Apex keeps crashing with a DXGI_ERROR_DEVICE_HUNG error or an 0x8000001 integrity error whenever I hover over certain legends (like Mirage or using seer's alt) in the locker. The models load slowly, sometimes show up as white placeholders, and then the game crashes." from my post earlier

 i tried reinstalling drivers and downgrading windows too but nothing works

I have the same issue except EasyAntiCheat_EOS driver fails to terminate when the game and EasyAntiCheat processes close. It also doesn't respond to sc stop. It will fully utilize my CPU until it finishes, typically taking more than 30 minutes, or if I just restart my system.

I'm experiencing the exact same thing now. Even though I closed the game, the system continues to consume 20-25% of the CPU.

I don't have any antivirus softwares but i actually have Core Isolation disabled in Windows by default. I am going to definitely try this right now. 

I can't belive i'm saying this but i think enabling Core Isolation fixed the issue so far...40 minutes in and it's fine. I'm speechles lol.

I think that this is how they improve the fight against cheaters, so that **bleep** with DMA cards don't have access to memory interception, and that soon enabling core isolation will be a prerequisite for playing Apex, like it was in the case of BF6, where they made the presence of a secure boot mandatory... and that's great.

I found the deeper solution for blocking the anti-cheat in the ntoskrnl process, in my case it was related to the cumulative windows update KB5071546, which is aimed at improving the firewall, perhaps the update was installed crookedly via windows update, because when trying to uninstall it, the system wrote that "not all update components were removed." Therefore, I downloaded this cumulative package from the Microsoft repository

https://www.catalog.update.microsoft.com/Home.aspx

find in search KB5071546

and downloadig for my version of the OS (W10 LTSB 21H2), and reinstalled it, and then reset the firewall to default settings by running the <netsh advfirewall reset> command in the console; turned off core isolation and rebooted the PC; after that, launched the EA app, granted connection permissions and that's it...2-3 sessions of 20-40 minutes, a total of 2-3 matches, and no problems, Apex closes as instantly as with core isolation enabled; I'm most likely assuming that the update screwed up some of the connection permissions for EAC itself, which is why after the end of the game session, EAC didn't received a resolve from the server.How did I end up like this? It was just a coincidence that I updated just as the second split was about to begin: I installed both the cumulative update and updated my antivirus, and then I started noticing that I wasn't the only one having these problems. The catch is, I'm on Windows 10, and people were reporting the problem starting on November 25th with Windows 11... so I don't know what cumulative update from microsoft sent them at the end of november😁

P.S. So, regarding the EAC, there's a joke about it: don't shoot the pianist, he plays as best he can... and is not guilty of anything

P.P.S. Viva la microsoft...threw a puzzle 🤪