Battlefield 2042 / EA Anticheat BSOD Bug

Question

The bug: After enabling Secure Boot on my PC post the update that made this a requirement for EA Anticheat, starting the game (and the anticheat) resulted in a BSOD with the error stating "attempted to write to read only memory".

The investigation: I updated Windows 10 to the latest version, updated my graphics card drivers and checked to see if there were any corrupted system drivers (the usual cause for this BSOD). I repaired the Anticheat using their installer and none of these things solved the problem. I went ahead and ran an analysis on the memory dump file that windows generates after a blue screen and low and behold there were no corrupted drivers causing this issue... except for eaanticheat.sys.

The solution: Enabling Settings > Windows Security > Device Security > Core Isolation Details > Memory Integrity prevents malware from inserting malicious code into high security processes, also prevents EA Anticheat from attempting to insert it's code into read only memory where it does not belong and circumvents the BSOD. (note in order to enable this setting some older drivers may need to be removed from your system if they are incompatible).

After speaking with EA Support I learned that Memory Integrity is in fact, not an official requirement for this game, so this is indeed a bug. Considering the danger of messing around with highly secure kernel layer memory EA Absolutely needs to fix this immediately.

chris_hawkner · Answer

Interesting. Did you have to do the mbr2gpt stuff to get your secure boot working? I'm wondering if maybe that had gone slightly awry.

taugie84 · Answer

I experience frequent PC Crashes resulting in BSOD while playing Battlefield 2042 too! It's become more and frequent. Like, today It happened about 7 times and I have minidump files for 5 of them. Upon analysis of the Microsoft minidump file, it revealed the culprit being a kernel-mode exception that wasn’t handled caused by the eaanticheat.sys driver. The Exception code indicates an Access Violation, meaning the driver attempted to access memory it wasn’t allowed to. The Parameters (Arg3, Arg4) 0000000000000000 and fffffffffffffff suggest the memory address involved was invalid or out of bounds which reinforces the Access Violation Exception code. The stack shows the crash originated in eaanticheat.sys (eaanticheat+0x26da9be), followed by calls to core Windows kernel functions (nt!KiGeneralProtectionFault, nt!KiExceptionDispatch, etc.). This confirms the issue is with the anti-cheat driver triggering a general protection fault, which Windows couldn’t recover from.Below is the output of the analyzed minidump file I explained above:************* Path validation summary **************Response &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Time (ms) &nbsp; &nbsp; LocationDeferred &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; srv*C:\Symbols*https://msdl.microsoft.com/download/symbols6: kd&gt; !analyze -vLoading Kernel Symbols..........................................................................................................................................................................................................................Loading User SymbolsPEB is paged out (Peb.Ldr = 00000000`00374018). &nbsp;Type ".hh dbgerr001" for detailsLoading unloaded module list.........******************************************************************************** &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ** &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Bugcheck Analysis &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;** &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ********************************************************************************KMODE_EXCEPTION_NOT_HANDLED (1e)This is a very common BugCheck. &nbsp;Usually the exception address pinpointsthe driver/function that caused the problem. &nbsp;Always note this addressas well as the link date of the driver/image that contains this address.Arguments:Arg1: ffffffffc0000005, The exception code that was not handledArg2: fffff8067d3aa9be, The address that the exception occurred atArg3: 0000000000000000, Parameter 0 of the exceptionArg4: ffffffffffffffff, Parameter 1 of the exceptionDebugging Details:------------------*** WARNING: Unable to verify timestamp for eaanticheat.sys**************************************************************************** &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ****** &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ****** &nbsp; &nbsp;Either you specified an unqualified symbol, or your debugger &nbsp; ****** &nbsp; &nbsp;doesn't have full symbol information. &nbsp;Unqualified symbol &nbsp; &nbsp; &nbsp;****** &nbsp; &nbsp;resolution is turned off by default. Please either specify a &nbsp; ****** &nbsp; &nbsp;fully qualified symbol module!symbolname, or enable resolution ****** &nbsp; &nbsp;of unqualified symbols by typing ".symopt- 100". Note that &nbsp; &nbsp; ****** &nbsp; &nbsp;enabling unqualified symbol resolution with network symbol &nbsp; &nbsp; ****** &nbsp; &nbsp;server shares in the symbol path may cause the debugger to &nbsp; &nbsp; ****** &nbsp; &nbsp;appear to hang for long periods of time when an incorrect &nbsp; &nbsp; &nbsp;****** &nbsp; &nbsp;symbol name is typed or the network symbol server is down. &nbsp; &nbsp; ****** &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ****** &nbsp; &nbsp;For some commands to work properly, your symbol path &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ****** &nbsp; &nbsp;must point to .pdb files that have full type information. &nbsp; &nbsp; &nbsp;****** &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ****** &nbsp; &nbsp;Certain .pdb files (such as the public OS symbols) do not &nbsp; &nbsp; &nbsp;****** &nbsp; &nbsp;contain the required information. &nbsp;Contact the group that &nbsp; &nbsp; &nbsp;****** &nbsp; &nbsp;provided you with these symbols if you need this command to &nbsp; &nbsp;****** &nbsp; &nbsp;work. &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;****** &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ****** &nbsp; &nbsp;Type referenced: ExceptionRecord &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ****** &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ******************************************************************************************************************************************************** &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ****** &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ****** &nbsp; &nbsp;Either you specified an unqualified symbol, or your debugger &nbsp; ****** &nbsp; &nbsp;doesn't have full symbol information. &nbsp;Unqualified symbol &nbsp; &nbsp; &nbsp;****** &nbsp; &nbsp;resolution is turned off by default. Please either specify a &nbsp; ****** &nbsp; &nbsp;fully qualified symbol module!symbolname, or enable resolution ****** &nbsp; &nbsp;of unqualified symbols by typing ".symopt- 100". Note that &nbsp; &nbsp; ****** &nbsp; &nbsp;enabling unqualified symbol resolution with network symbol &nbsp; &nbsp; ****** &nbsp; &nbsp;server shares in the symbol path may cause the debugger to &nbsp; &nbsp; ****** &nbsp; &nbsp;appear to hang for long periods of time when an incorrect &nbsp; &nbsp; &nbsp;****** &nbsp; &nbsp;symbol name is typed or the network symbol server is down. &nbsp; &nbsp; ****** &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ****** &nbsp; &nbsp;For some commands to work properly, your symbol path &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ****** &nbsp; &nbsp;must point to .pdb files that have full type information. &nbsp; &nbsp; &nbsp;****** &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ****** &nbsp; &nbsp;Certain .pdb files (such as the public OS symbols) do not &nbsp; &nbsp; &nbsp;****** &nbsp; &nbsp;contain the required information. &nbsp;Contact the group that &nbsp; &nbsp; &nbsp;****** &nbsp; &nbsp;provided you with these symbols if you need this command to &nbsp; &nbsp;****** &nbsp; &nbsp;work. &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;****** &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ****** &nbsp; &nbsp;Type referenced: ContextRecord &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ****** &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ****************************************************************************KEY_VALUES_STRING: 1&nbsp; &nbsp; Key &nbsp;: Analysis.CPU.mSec&nbsp; &nbsp; Value: 1187&nbsp; &nbsp; Key &nbsp;: Analysis.Elapsed.mSec&nbsp; &nbsp; Value: 2897&nbsp; &nbsp; Key &nbsp;: Analysis.IO.Other.Mb&nbsp; &nbsp; Value: 10&nbsp; &nbsp; Key &nbsp;: Analysis.IO.Read.Mb&nbsp; &nbsp; Value: 1&nbsp; &nbsp; Key &nbsp;: Analysis.IO.Write.Mb&nbsp; &nbsp; Value: 47&nbsp; &nbsp; Key &nbsp;: Analysis.Init.CPU.mSec&nbsp; &nbsp; Value: 609&nbsp; &nbsp; Key &nbsp;: Analysis.Init.Elapsed.mSec&nbsp; &nbsp; Value: 412903&nbsp; &nbsp; Key &nbsp;: Analysis.Memory.CommitPeak.Mb&nbsp; &nbsp; Value: 103&nbsp; &nbsp; Key &nbsp;: Analysis.Version.DbgEng&nbsp; &nbsp; Value: 10.0.27829.1001&nbsp; &nbsp; Key &nbsp;: Analysis.Version.Description&nbsp; &nbsp; Value: 10.2503.24.01 amd64fre&nbsp; &nbsp; Key &nbsp;: Analysis.Version.Ext&nbsp; &nbsp; Value: 1.2503.24.1&nbsp; &nbsp; Key &nbsp;: Bugcheck.Code.LegacyAPI&nbsp; &nbsp; Value: 0x1e&nbsp; &nbsp; Key &nbsp;: Bugcheck.Code.TargetModel&nbsp; &nbsp; Value: 0x1e&nbsp; &nbsp; Key &nbsp;: Dump.Attributes.AsUlong&nbsp; &nbsp; Value: 0x21808&nbsp; &nbsp; Key &nbsp;: Dump.Attributes.DiagDataWrittenToHeader&nbsp; &nbsp; Value: 1&nbsp; &nbsp; Key &nbsp;: Dump.Attributes.ErrorCode&nbsp; &nbsp; Value: 0x0&nbsp; &nbsp; Key &nbsp;: Dump.Attributes.KernelGeneratedTriageDump&nbsp; &nbsp; Value: 1&nbsp; &nbsp; Key &nbsp;: Dump.Attributes.LastLine&nbsp; &nbsp; Value: Dump completed successfully.&nbsp; &nbsp; Key &nbsp;: Dump.Attributes.ProgressPercentage&nbsp; &nbsp; Value: 0&nbsp; &nbsp; Key &nbsp;: Failure.Bucket&nbsp; &nbsp; Value: AV_R_eaanticheat!unknown_function&nbsp; &nbsp; Key &nbsp;: Failure.Exception.IP.Address&nbsp; &nbsp; Value: 0xfffff8067d3aa9be&nbsp; &nbsp; Key &nbsp;: Failure.Exception.IP.Module&nbsp; &nbsp; Value: eaanticheat&nbsp; &nbsp; Key &nbsp;: Failure.Exception.IP.Offset&nbsp; &nbsp; Value: 0x26da9be&nbsp; &nbsp; Key &nbsp;: Failure.Hash&nbsp; &nbsp; Value: {100f1e0a-abcf-3860-2e0c-3546be52e55a}&nbsp; &nbsp; Key &nbsp;: Hypervisor.Enlightenments.ValueHex&nbsp; &nbsp; Value: 0x7417df84&nbsp; &nbsp; Key &nbsp;: Hypervisor.Flags.AnyHypervisorPresent&nbsp; &nbsp; Value: 1&nbsp; &nbsp; Key &nbsp;: Hypervisor.Flags.ApicEnlightened&nbsp; &nbsp; Value: 0&nbsp; &nbsp; Key &nbsp;: Hypervisor.Flags.ApicVirtualizationAvailable&nbsp; &nbsp; Value: 1&nbsp; &nbsp; Key &nbsp;: Hypervisor.Flags.AsyncMemoryHint&nbsp; &nbsp; Value: 0&nbsp; &nbsp; Key &nbsp;: Hypervisor.Flags.CoreSchedulerRequested&nbsp; &nbsp; Value: 0&nbsp; &nbsp; Key &nbsp;: Hypervisor.Flags.CpuManager&nbsp; &nbsp; Value: 1&nbsp; &nbsp; Key &nbsp;: Hypervisor.Flags.DeprecateAutoEoi&nbsp; &nbsp; Value: 1&nbsp; &nbsp; Key &nbsp;: Hypervisor.Flags.DynamicCpuDisabled&nbsp; &nbsp; Value: 1&nbsp; &nbsp; Key &nbsp;: Hypervisor.Flags.Epf&nbsp; &nbsp; Value: 0&nbsp; &nbsp; Key &nbsp;: Hypervisor.Flags.ExtendedProcessorMasks&nbsp; &nbsp; Value: 1&nbsp; &nbsp; Key &nbsp;: Hypervisor.Flags.HardwareMbecAvailable&nbsp; &nbsp; Value: 1&nbsp; &nbsp; Key &nbsp;: Hypervisor.Flags.MaxBankNumber&nbsp; &nbsp; Value: 0&nbsp; &nbsp; Key &nbsp;: Hypervisor.Flags.MemoryZeroingControl&nbsp; &nbsp; Value: 0&nbsp; &nbsp; Key &nbsp;: Hypervisor.Flags.NoExtendedRangeFlush&nbsp; &nbsp; Value: 0&nbsp; &nbsp; Key &nbsp;: Hypervisor.Flags.NoNonArchCoreSharing&nbsp; &nbsp; Value: 1&nbsp; &nbsp; Key &nbsp;: Hypervisor.Flags.Phase0InitDone&nbsp; &nbsp; Value: 1&nbsp; &nbsp; Key &nbsp;: Hypervisor.Flags.PowerSchedulerQos&nbsp; &nbsp; Value: 0&nbsp; &nbsp; Key &nbsp;: Hypervisor.Flags.RootScheduler&nbsp; &nbsp; Value: 0&nbsp; &nbsp; Key &nbsp;: Hypervisor.Flags.SynicAvailable&nbsp; &nbsp; Value: 1&nbsp; &nbsp; Key &nbsp;: Hypervisor.Flags.UseQpcBias&nbsp; &nbsp; Value: 0&nbsp; &nbsp; Key &nbsp;: Hypervisor.Flags.Value&nbsp; &nbsp; Value: 55185662&nbsp; &nbsp; Key &nbsp;: Hypervisor.Flags.ValueHex&nbsp; &nbsp; Value: 0x34a10fe&nbsp; &nbsp; Key &nbsp;: Hypervisor.Flags.VpAssistPage&nbsp; &nbsp; Value: 1&nbsp; &nbsp; Key &nbsp;: Hypervisor.Flags.VsmAvailable&nbsp; &nbsp; Value: 1&nbsp; &nbsp; Key &nbsp;: Hypervisor.RootFlags.AccessStats&nbsp; &nbsp; Value: 1&nbsp; &nbsp; Key &nbsp;: Hypervisor.RootFlags.CrashdumpEnlightened&nbsp; &nbsp; Value: 1&nbsp; &nbsp; Key &nbsp;: Hypervisor.RootFlags.CreateVirtualProcessor&nbsp; &nbsp; Value: 1&nbsp; &nbsp; Key &nbsp;: Hypervisor.RootFlags.DisableHyperthreading&nbsp; &nbsp; Value: 0&nbsp; &nbsp; Key &nbsp;: Hypervisor.RootFlags.HostTimelineSync&nbsp; &nbsp; Value: 1&nbsp; &nbsp; Key &nbsp;: Hypervisor.RootFlags.HypervisorDebuggingEnabled&nbsp; &nbsp; Value: 0&nbsp; &nbsp; Key &nbsp;: Hypervisor.RootFlags.IsHyperV&nbsp; &nbsp; Value: 1&nbsp; &nbsp; Key &nbsp;: Hypervisor.RootFlags.LivedumpEnlightened&nbsp; &nbsp; Value: 1&nbsp; &nbsp; Key &nbsp;: Hypervisor.RootFlags.MapDeviceInterrupt&nbsp; &nbsp; Value: 1&nbsp; &nbsp; Key &nbsp;: Hypervisor.RootFlags.MceEnlightened&nbsp; &nbsp; Value: 1&nbsp; &nbsp; Key &nbsp;: Hypervisor.RootFlags.Nested&nbsp; &nbsp; Value: 0&nbsp; &nbsp; Key &nbsp;: Hypervisor.RootFlags.StartLogicalProcessor&nbsp; &nbsp; Value: 1&nbsp; &nbsp; Key &nbsp;: Hypervisor.RootFlags.Value&nbsp; &nbsp; Value: 1015&nbsp; &nbsp; Key &nbsp;: Hypervisor.RootFlags.ValueHex&nbsp; &nbsp; Value: 0x3f7BUGCHECK_CODE: &nbsp;1eBUGCHECK_P1: ffffffffc0000005BUGCHECK_P2: fffff8067d3aa9beBUGCHECK_P3: 0BUGCHECK_P4: ffffffffffffffffFILE_IN_CAB: &nbsp;071925-12375-01.dmpTAG_NOT_DEFINED_202b: &nbsp;*** Unknown TAG in analysis list 202bDUMP_FILE_ATTRIBUTES: 0x21808&nbsp; Kernel Generated Triage DumpFAULTING_THREAD: &nbsp;ffff938648d92080EXCEPTION_PARAMETER1: &nbsp;0000000000000000EXCEPTION_PARAMETER2: &nbsp;ffffffffffffffffREAD_ADDRESS: fffff806c8bc44c0: Unable to get MiVisibleStateUnable to get NonPagedPoolStartUnable to get NonPagedPoolEndUnable to get PagedPoolStartUnable to get PagedPoolEndunable to get nt!MmSpecialPagesInUse&nbsp;ffffffffffffffff&nbsp;BLACKBOXBSD: 1 (!blackboxbsd)BLACKBOXNTFS: 1 (!blackboxntfs)BLACKBOXPNP: 1 (!blackboxpnp)BLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: &nbsp;1PROCESS_NAME: &nbsp;BF2042.exeSTACK_TEXT: &nbsp;fffffc8e`c7fd6168 fffff806`c7fc56cb &nbsp; &nbsp; : 00000000`0000001e ffffffff`c0000005 fffff806`7d3aa9be 00000000`00000000 : nt!KeBugCheckExfffffc8e`c7fd6170 fffff806`c82b9845 &nbsp; &nbsp; : 00006c79`b726df7f fffff806`7b50090a 00000000`7d7e8c1d 1443d9c7`1ca497ef : nt!KiDispatchException+0xb0bfffffc8e`c7fd6880 fffff806`c82b4525 &nbsp; &nbsp; : 00000371`38028b7f ffffffff`c7ffffff cbf29c84`84202220 ffffffff`ffffffff : nt!KiExceptionDispatch+0x145fffffc8e`c7fd6a60 fffff806`7d3aa9be &nbsp; &nbsp; : b2c773a1`b2c69ffa e5e65158`4ec3cdf4 7a105263`739f8279 00000001`80a1af5d : nt!KiGeneralProtectionFault+0x365fffffc8e`c7fd6bf0 b2c773a1`b2c69ffa &nbsp; &nbsp; : e5e65158`4ec3cdf4 7a105263`739f8279 00000001`80a1af5d 00000000`00000000 : eaanticheat+0x26da9befffffc8e`c7fd6bf8 e5e65158`4ec3cdf4 &nbsp; &nbsp; : 7a105263`739f8279 00000001`80a1af5d 00000000`00000000 fffffc8e`c7fd6f10 : 0xb2c773a1`b2c69ffafffffc8e`c7fd6c00 7a105263`739f8279 &nbsp; &nbsp; : 00000001`80a1af5d 00000000`00000000 fffffc8e`c7fd6f10 fffffc8e`c7fd74a8 : 0xe5e65158`4ec3cdf4fffffc8e`c7fd6c08 00000001`80a1af5d &nbsp; &nbsp; : 00000000`00000000 fffffc8e`c7fd6f10 fffffc8e`c7fd74a8 1fffff00`cf617932 : 0x7a105263`739f8279fffffc8e`c7fd6c10 00000000`00000000 &nbsp; &nbsp; : fffffc8e`c7fd6f10 fffffc8e`c7fd74a8 1fffff00`cf617932 3552f624`9c51c998 : 0x00000001`80a1af5dSYMBOL_NAME: &nbsp;eaanticheat+26da9beMODULE_NAME: eaanticheatIMAGE_NAME: &nbsp;eaanticheat.sysSTACK_COMMAND: .process /r /p 0xffff9386522df080; .thread 0xffff938648d92080 ; kbBUCKET_ID_FUNC_OFFSET: &nbsp;26da9beFAILURE_BUCKET_ID: &nbsp;AV_R_eaanticheat!unknown_functionOSPLATFORM_TYPE: &nbsp;x64OSNAME: &nbsp;Windows 10FAILURE_ID_HASH: &nbsp;{100f1e0a-abcf-3860-2e0c-3546be52e55a}Followup: &nbsp; &nbsp; MachineOwner---------

annakarava1 · Answer

for 1 second i thought was an&nbsp; a uni examination and not a game !!!!!!!!!!!! what the **bleep** you doing you&nbsp; ruin your game EA with secure boot&nbsp; ? Games is for **bleep** fun not to learn informatic !!!!!!

Forum Discussion

Battlefield 2042 / EA Anticheat BSOD Bug

3 Replies

About Battlefield 2042 Technical Issues & Bugs

Recent Discussions

Missing modes and options

Frontlines and Strike-team are no longer available in portal (22/7/25)

SecureBoot is not enabled. This is how Battlefield 2042 became unplayable.

Crash DirectX Error

Battlefield 2042– black screen and kick to lobby after match starts