Re: PC Constantly Blue-Screening Randomly During Gameplay

Hey,
I played BF6 and my pc crashed. When I looked into the dump file and saw it caused by eaanticheat.sys memory fault

I cannot upload the .dmp file so here is the analyze of the file:

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true
   EnableRedirectToChakraJsProvider : false

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.187 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 45

Microsoft (R) Windows Debugger Version 10.0.27920.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\101025-8000-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 26100 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff806`e6a00000 PsLoadedModuleList = 0xfffff806`e78f4e70
Debug session time: Fri Oct 10 20:16:41.099 2025 (UTC + 3:00)
System Uptime: 0 days 0:45:28.714
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
................................................................
......................................
Loading User Symbols

Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`e6ef9280 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffc880`caf27bf0=000000000000000a
10: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......................................
Loading User Symbols

Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000400, memory referenced
Arg2: 000000000000000e, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff806e6df673d, address which referenced memory

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for eaanticheat.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1078

    Key  : Analysis.Elapsed.mSec
    Value: 8489

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 24

    Key  : Analysis.Init.CPU.mSec
    Value: 875

    Key  : Analysis.Init.Elapsed.mSec
    Value: 30169

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 109

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27920.1001

    Key  : Analysis.Version.Description
    Value: 10.2506.23.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2506.23.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xa

    Key  : Bugcheck.Code.TargetModel
    Value: 0xa

    Key  : Dump.Attributes.AsUlong
    Value: 0x21008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: AV_eaanticheat!unknown_function

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff806e6df673d

    Key  : Failure.Exception.IP.Module
    Value: nt

    Key  : Failure.Exception.IP.Offset
    Value: 0x3f673d

    Key  : Failure.Hash
    Value: {d544cf09-4735-e698-77c3-5df5924e5448}

    Key  : Stack.Pointer
    Value: ISR

    Key  : WER.System.BIOSRevision
    Value: 5.35.0.0

BUGCHECK_CODE:  a

BUGCHECK_P1: 400

BUGCHECK_P2: e

BUGCHECK_P3: 0

BUGCHECK_P4: fffff806e6df673d

FILE_IN_CAB:  101025-8000-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffff938f1a895280

READ_ADDRESS: fffff806e79c44c0: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 0000000000000400 

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1 (!blackboxwinlogon)

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffc880`caf27be8 fffff806`e70b39e9     : 00000000`0000000a 00000000`00000400 00000000`0000000e 00000000`00000000 : nt!KeBugCheckEx
ffffc880`caf27bf0 fffff806`e70aeca8     : ffff938f`1aeafb14 fffff806`00000002 ffffc880`caf0b180 ffff938f`1aeaf000 : nt!KiBugCheckDispatch+0x69
ffffc880`caf27d30 fffff806`e6df673d     : 00000000`000001a8 ffffffff`ffffffff ffff938f`3dc62080 ffffc880`cb4ac470 : nt!KiPageFault+0x468
ffffc880`caf27ec0 fffff806`e70a76f0     : fffff806`e79cef80 fffffc02`f776f3a0 00000000`00000000 00000000`00000000 : nt!KiIpiProcessRequests+0xed
ffffc880`caf27fb0 fffff806`e70a730a     : ffff1cd2`14286363 ffff1cd2`14286033 00000000`00000000 00000000`00000000 : nt!KiIpiInterruptSubDispatch+0x40
fffffc02`f776f320 fffff806`d24a3f99     : 00000000`00000004 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIpiInterrupt+0x39a
fffffc02`f776f4b0 00000000`00000004     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : eaanticheat+0x783f99
fffffc02`f776f4b8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x4

SYMBOL_NAME:  eaanticheat+783f99

MODULE_NAME: eaanticheat

IMAGE_NAME:  eaanticheat.sys

STACK_COMMAND: .process /r /p 0xfffff806e79cef80; .thread 0xffff938f1a895280 ; kb

BUCKET_ID_FUNC_OFFSET:  783f99

FAILURE_BUCKET_ID:  AV_eaanticheat!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {d544cf09-4735-e698-77c3-5df5924e5448}

Followup:     MachineOwner
---------