I'm experiencing BSOD with bugcheck code 139.

Question

Here is the analyze report:

****************************************************************************** * * * 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: ffffa904d5765ca0, Address of the trap frame for the exception that caused the BugCheck Arg3: ffffa904d5765bf8, Address of the exception record for the exception that caused the BugCheck Arg4: 0000000000000000, Reserved

Debugging Details:

*** WARNING: Check Image - Checksum mismatch - Dump: 0x20b809, File: 0x20b889 - C:\ProgramData\Dbg\sym\BTHport.sys\C546C699202000\BTHport.sys

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 1156

Key  : Analysis.Elapsed.mSec
Value: 1622

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

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

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

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

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

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

Key  : Bugcheck.Code.LegacyAPI
Value: 0x139

Key  : Dump.Attributes.AsUlong
Value: 1808

Key  : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key  : Dump.Attributes.ErrorCode
Value: 0

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\_KTIMER\_LIST\_CORRUPTION\_nt!KiSwapThread

Key  : Failure.Hash
Value: {364d2a10-fb5b-e8e9-9b5b-39c85a1b5a41}

Key  : Hypervisor.Enlightenments.ValueHex
Value: 1417df84

Key  : Hypervisor.Flags.AnyHypervisorPresent
Value: 1

Key  : Hypervisor.Flags.ApicEnlightened
Value: 0

Key  : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1

Key  : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key  : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key  : Hypervisor.Flags.CpuManager
Value: 1

Key  : Hypervisor.Flags.DeprecateAutoEoi
Value: 1

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

Key  : Hypervisor.Flags.ValueHex
Value: 14a10fe

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

BUGCHECK_CODE: 139

BUGCHECK_P1: 3

BUGCHECK_P2: ffffa904d5765ca0

BUGCHECK_P3: ffffa904d5765bf8

BUGCHECK_P4: 0

FILE_IN_CAB: 020524-51859-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1808 Kernel Generated Triage Dump

TRAP_FRAME: ffffa904d5765ca0 -- (.trap 0xffffa904d5765ca0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=ffffe687081375f8 rbx=0000000000000000 rcx=0000000000000003 rdx=ffffe6870705b1a0 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8052e46cd66 rsp=ffffa904d5765e30 rbp=ffffa904d5765f30 r8=0000000000000001 r9=000000000000000e r10=000000000000000e r11=fffff8052a484180 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe cy nt!KiSwapThread+0xe46: fffff805`2e46cd66 cd29 int 29h Resetting default scope

EXCEPTION_RECORD: ffffa904d5765bf8 -- (.exr 0xffffa904d5765bf8) ExceptionAddress: fffff8052e46cd66 (nt!KiSwapThread+0x0000000000000e46) 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: explorer.exe

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:
ffffa904d5765978 fffff8052e62c4e9 : 0000000000000139 0000000000000003 ffffa904d5765ca0 ffffa904d5765bf8 : nt!KeBugCheckEx ffffa904d5765980 fffff8052e62cab2 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiBugCheckDispatch+0x69 ffffa904d5765ac0 fffff8052e62a806 : ffffae8099156180 fffff8052e6203f7 ffffe686fbdd5080 ffffe6870705b990 : nt!KiFastFailDispatch+0xb2 ffffa904d5765ca0 fffff8052e46cd66 : ffffae8099156180 0000000000000000 ffffe686d3802080 0000000000000000 : nt!KiRaiseSecurityCheckFailure+0x346 ffffa904d5765e30 fffff8052e46ebb7 : ffffe6870705b080 0000000000000000 0000000000000000 0000000000000000 : nt!KiSwapThread+0xe46 ffffa904d5765f80 fffff8052e470ad6 : 0000000000000000 0000000000000001 000000000000000e 0000001c74398ab1 : nt!KiCommitThreadWait+0x137 ffffa904d5766030 fffff8052e431a63 : 00000000ffffffff ffffffffffffffff 0000000000000000 ffffe686fbdd5000 : nt!KeWaitForSingleObject+0x256 ffffa904d57663d0 fffff8053400ff52 : ffffffffffffffff ffffa904d5766750 0000000000000001 ffffffffffffffff : nt!KeWaitForMultipleObjects+0x5d3 ffffa904d5766630 fffff8d9a53fb911 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : dxgkrnl!DxgkWaitForVerticalBlankEventInternal+0x6b2 ffffa904d57676b0 fffff8d9a53fc60f : 0000000000000000 0000000000000000 ffffd68cd7902000 0000000000000000 : win32kbase!DirectComposition::CCompClockInfo::WaitForTick+0xc1 ffffa904d5767850 fffff8d9a5f5047e : 0000000000000000 000000002013a350 ffffa904d5767a38 ffffe6870705b080 : win32kbase!NtDCompositionWaitForCompositorClock+0x13f ffffa904d57679f0 fffff8052e62bbe5 : ffffe6870705b080 0000000000000000 ffffa904d5767a38 0000000000000000 : win32k!NtDCompositionWaitForCompositorClock+0x16 ffffa904d5767a20 00007ff865bc3d54 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25 0000000009fff6e8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff8`65bc3d54

SYMBOL_NAME: nt!KiSwapThread+e46

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.22621.3007

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: e46

FAILURE_BUCKET_ID: 0x139_3_CORRUPT_LIST_ENTRY_KTIMER_LIST_CORRUPTION_nt!KiSwapThread

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {364d2a10-fb5b-e8e9-9b5b-39c85a1b5a41}

Followup: MachineOwner

Answer 1

Ok. If you have any questions, don't hesitate to ask.

Answer 2

OK thanks. I've updated the BIOS to version 3101. Will monitor for a few days.

Answer 3

The minidumps do not mention any driver as causing the crashes.

I suggest doing the following:

• Go to the support area of the Asus website and search for the model of your motherboard. Then, download the latest chipset drivers and install them.
• I noticed that the motherboard BIOS is outdated. I suggest you update it by following Asus's instructions.

Then, see if the system will work stable.

Answer 4

Thanks. Here are 2 dumps : https://drive.google.com/file/d/1aoo0Lapx1K0tyVdJU107ixflDSp22YVd/view?usp=drive\_link

Answer 5

Hi. I'm David, and I'm happy to help you.

Please send the minidump files.

(Do not send the MEMORY.DMP file as it may contain personal information. Only send the minidump files.)

These files are in "C:\Windows\Minidump".

Copy any files you have to your desktop and store them in a ZIP file. Then upload the ZIP file to the cloud (OneDrive, Google Drive, Dropbox, etc...), choose to share it, and get the link.

Post the link to the ZIP file here so I can have a look.