Kernel check failure BSOD when closing any game with Easy anti cheat.

Question

Here's the MiniDump. Also for some reason the minidump says my OS is 10 but I'm definitely on 11

---

•                                                                         *
  

               Bugcheck Analysis                                    *

                                                                        *
```> *******************************************************************************
> KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 000000000000000a, Indirect call guard check detected invalid control transfer.
Arg2: 0000000000000000, Address of the trap frame for the exception that caused the BugCheck
Arg3: 0000000000000000, Address of the exception record for the exception that caused the BugCheck
Arg4: 0000000000000000, Reserved
Debugging Details:
------------------
> KEY_VALUES_STRING: 1
    Key  : Analysis.CPU.mSec
    Value: 1234
    Key  : Analysis.Elapsed.mSec
    Value: 7047
    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: 656
    Key  : Analysis.Init.Elapsed.mSec
    Value: 29039
    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 90
    Key  : Analysis.Version.DbgEng
    Value: 10.0.29507.1001
    Key  : Analysis.Version.Description
    Value: 10.2511.5.1 amd64fre
    Key  : Analysis.Version.Ext
    Value: 1.2511.5.1
    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x139
    Key  : Bugcheck.Code.TargetModel
    Value: 0x139
    Key  : Dump.Attributes.AsUlong
    Value: 0x31808
    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: 0x139_a_GUARD_ICALL_CHECK_FAILURE_ANALYSIS_INCONCLUSIVE!unknown_function
    Key  : Failure.Hash
    Value: {88f6175b-0b38-033f-8093-5476c457189f}
    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7497cf94
    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1
    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1
    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0
    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0
    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0
    Key  : Hypervisor.Flags.CpuManager
    Value: 1
    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0
    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1
    Key  : Hypervisor.Flags.Epf
    Value: 0
    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1
    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1
    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0
    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0
    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0
    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1
    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1
    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0
    Key  : Hypervisor.Flags.RootScheduler
    Value: 0
    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1
    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0
    Key  : Hypervisor.Flags.Value
    Value: 38408431
    Key  : Hypervisor.Flags.ValueHex
    Value: 0x24a10ef
    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1
    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1
    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1
    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1
    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1
    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0
    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1
    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0
    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1
    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1
    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1
    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1
    Key  : Hypervisor.RootFlags.Nested
    Value: 0
    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1
    Key  : Hypervisor.RootFlags.Value
    Value: 1015
    Key  : Hypervisor.RootFlags.ValueHex
    Value: 0x3f7
> BUGCHECK_CODE:  139
> BUGCHECK_P1: a
> BUGCHECK_P2: 0
> BUGCHECK_P3: 0
> BUGCHECK_P4: 0
> FILE_IN_CAB:  012526-16468-01.dmp
> TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b
> DUMP_FILE_ATTRIBUTES: 0x31808
>   Kernel Generated Triage Dump
> FAULTING_THREAD:  ffffd20200fdc300
> TRAP_FRAME:  0000000000000000 -- (.trap 0x0)
> EXCEPTION_RECORD:  0000000000000000 -- (.exr 0x0)
> Cannot read Exception record @ 0000000000000000
> CUSTOMER_CRASH_COUNT:  1
> PROCESS_NAME:  System
> STACK_TEXT:  
> ffffb702`c3b3cd28 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
> SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE
> MODULE_NAME: Unknown_Module
> IMAGE_NAME:  Unknown_Image
> STACK_COMMAND: .cxr; .ecxr ; kb
> FAILURE_BUCKET_ID:  0x139_a_GUARD_ICALL_CHECK_FAILURE_ANALYSIS_INCONCLUSIVE!unknown_function
> OSPLATFORM_TYPE:  x64
> OSNAME:  Windows 10
> FAILURE_ID_HASH:  {88f6175b-0b38-033f-8093-5476c457189f}
> Followup:     MachineOwner
> 

Answer 1

Upon checking the dump file, it does not provide enough information and inconclusive, as no specific driver is indicated.

• Disable any overclocking, revert any changes and reset them to default

Disabled. If enabled, XMP is disabled

• Reinstall and update the Chipset and clean install the Graphics drivers.

Download their drivers directly from the manufacturer's support site and install them.

Restart your computer.

• If another crash occurs after performing the steps, please provide the most recent dump file.

Answer 2

Appreciate the information. To review further the cause of the crash, we’ll need the actual minidump file. Thank you.

Answer 3

Hi, I'm Jan and I'm happy to help you today. I'm sorry you're having this problem. Please share the latest dmp files for us to diagnose the cause of the computer crash. Thank you.

Please find this folder.

C:\Windows\Minidump

Put the files in a zip

upload files to OneDrive

Share the link here.

Thank you