KERNEL_SECURITY_CHECK_FAILURE (139)

Question

Getting this annoying error since September last year. Absolutely tearing my hair out with this. Thought I had successfully resolved issue at the start of this month and computer has been running without crashing for nearly four weeks but got another of the following error today:

************* 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.203 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 43

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

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

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 26100 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff800`82200000 PsLoadedModuleList = 0xfffff800`830f47a0
Debug session time: Tue Mar 25 15:03:59.934 2025 (UTC + 0:00)
System Uptime: 5 days 3:47:52.485
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......................................................
Loading User Symbols

Loading unloaded module list
......................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`826b7ce0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff880`b251eeb0=0000000000000139
5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: fffff880b251f1d0, Address of the trap frame for the exception that caused the BugCheck
Arg3: fffff880b251f128, 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: 1093

    Key  : Analysis.Elapsed.mSec
    Value: 4593

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27793.1000

    Key  : Analysis.Version.Description
    Value: 10.2410.02.02 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2410.2.2

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x139

    Key  : Bugcheck.Code.TargetModel
    Value: 0x139

    Key  : Dump.Attributes.AsUlong
    Value: 0x21808

    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  : FailFast.Name
    Value: CORRUPT_LIST_ENTRY

    Key  : FailFast.Type
    Value: 3

    Key  : Failure.Bucket
    Value: 0x139_3_CORRUPT_LIST_ENTRY_nt!KiFastFailDispatch

    Key  : Failure.Exception.Code
    Value: 0xffffffffc0000409

    Key  : Failure.Exception.Record
    Value: 0xfffff880b251f128

    Key  : Failure.Hash
    Value: {3aede96a-54dd-40d6-d4cb-2a161a843851}

    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: 3

BUGCHECK_P2: fffff880b251f1d0

BUGCHECK_P3: fffff880b251f128

BUGCHECK_P4: 0

FILE_IN_CAB:  032525-18265-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b

DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffb306d5f31040

TRAP_FRAME:  fffff880b251f1d0 -- (.trap 0xfffff880b251f1d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff878142bfc038 rbx=0000000000000000 rcx=0000000000000003
rdx=ffff87811d154038 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800825757cf rsp=fffff880b251f360 rbp=ffff8781210f0000
 r8=ffff8781210f0020  r9=ffffb306d199b938 r10=0000000000000001
r11=ffffb3067a7ffd60 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac po nc
nt!EtwpAdjustSiloTraceBuffers+0xbf:
fffff800`825757cf cd29            int     29h
Resetting default scope

EXCEPTION_RECORD:  fffff880b251f128 -- (.exr 0xfffff880b251f128)
ExceptionAddress: fffff800825757cf (nt!EtwpAdjustSiloTraceBuffers+0x00000000000000bf)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000003
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY 

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE_STR:  c0000409

EXCEPTION_PARAMETER1:  0000000000000003

EXCEPTION_STR:  0xc0000409

STACK_TEXT:  
fffff880`b251eea8 fffff800`8288cee9     : 00000000`00000139 00000000`00000003 fffff880`b251f1d0 fffff880`b251f128 : nt!KeBugCheckEx
fffff880`b251eeb0 fffff800`8288d4f2     : 00000000`00000000 ffffb306`7a598c20 00000000`00000000 fffff800`826a8fc9 : nt!KiBugCheckDispatch+0x69
fffff880`b251eff0 fffff800`8288b128     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiFastFailDispatch+0xb2
fffff880`b251f1d0 fffff800`825757cf     : ffffb306`d199b900 ffffb306`7aade000 fffff880`b251f4c0 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0x368
fffff880`b251f360 fffff800`8257560c     : 00000000`00000000 00000000`00000000 fffff880`b251f4c0 ffffb306`7a605b20 : nt!EtwpAdjustSiloTraceBuffers+0xbf
fffff880`b251f390 fffff800`82517b02     : ffffb306`d5f31040 ffffb306`7a605b20 00000000`00000000 ffffb306`00000000 : nt!EtwpAdjustTraceBuffers+0x2c
fffff880`b251f3c0 fffff800`8264fd8a     : ffffb306`d5f31040 ffffb306`d5f31040 fffff800`82517950 ffffb306`7a605b20 : nt!ExpWorkerThread+0x1b2
fffff880`b251f570 fffff800`8287a024     : ffffc301`c99c0180 ffffb306`d5f31040 fffff800`8264fd30 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`b251f5c0 00000000`00000000     : fffff880`b2520000 fffff880`b2519000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34

SYMBOL_NAME:  nt!KiFastFailDispatch+b2

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.26100.3476

STACK_COMMAND:  .process /r /p 0xffffb3067a565040; .thread 0xffffb306d5f31040 ; kb

BUCKET_ID_FUNC_OFFSET:  b2

FAILURE_BUCKET_ID:  0x139_3_CORRUPT_LIST_ENTRY_nt!KiFastFailDispatch

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {3aede96a-54dd-40d6-d4cb-2a161a843851}

Followup:     MachineOwner
---------
************************** ************* ************* ************* ************* *************  **************
At time of crash, there is no blue screen. The computer simply freezes leaving image last left on the screens.

Memtest86 repeated passes show no problems with ram. 
PC manufacturer suggested total removal of graphics drivers and allow Windows update to install it's own AMD radeon driver. 
That's what I did four weeks ago. Horrified to see screen crash when it came out of standby this afternoon.

Can someone advise, if possible please? Thanks.

Answer 1

Hello,

Thanks for suggestions. Have tried most of these over the past few months (official drivers, sfc, chkdsk, etc.) but will see what, if anything, may not have been done properly.

regards,

Answer 2

Thanks for suggestion.

Problem happens so infrequently (after number of days) that it may be difficult to diagnose this way. Trying to find a way of forcing the problem to happen, which may help diagnose issue.

regards,

Answer 3

Hello, ColinoGreen

Welcome to the Microsoft Community.

Thank you for your feedback on your issue here, to follow up, did you refer to Reza Ameri's suggestion for a clean boot, and did the issue persist under a clean boot.

I will also add some other suggestions for you!

Run Windows memory diagnostics:

KERNEL_SECURITY_CHECK_FAILURE errors can be caused by faulty memory (RAM).

To run the memory diagnostic tool:

Press Windows + R to open the Run window.

Type mdsched.exe and press Enter.

Select Restart and check for problems.

If memory errors are found, the faulty memory stick may need to be replaced.

Update the drivers:

Outdated or incompatible drivers can also cause this error.

Graphics Card Drivers: Update your graphics card drivers from the official NVIDIA, AMD or Intel websites.

Other drivers: Make sure all system drivers, especially motherboard and storage drivers, are up-to-date, either through Device Manager or the motherboard's official website.

Check for corrupted system files:

Run System File Checker (SFC) to scan and repair corrupted system files:

Open a command prompt as administrator.

Type sfc /scannow and press Enter.

Wait for it to complete and follow the prompts to fix any problems found.

Check for hard disk problems:

Failed hard disks can also cause such errors. Use chkdsk to check for disk errors:

Open a command prompt as an administrator.

Type chkdsk /f and press Enter.

If necessary, reboot the computer and let the system scan to fix the disk error.

Disclaimer: Running Microsoft Safety Scanner can help you check if the system is disturbed or malicious software exists. To avoid any trouble for you, please back up all your personal files first to ensure you do not lose data.  

Disclaimer: Running chkdsk can check the file system and file system metadata of a volume for logical and physical errors. To avoid any trouble for you, do not cancel or interrupt chkdsk, and back up important data.  

More information please refer to this chkdsk | Microsoft Learn. 

Best regards

Bobhe | Microsoft Community Support Specialist

Answer 4

Hi,

Make sure report this issue using the Feedback Hub app.

Try performing Clean Boot and see if the problem persists?

Have a look at How to perform a clean boot in Windows - Microsoft Support.