KERNEL_SECURITY_CHECK_FAILURE

Question

KERNEL_SECURITY_CHECK_FAILURE

Anonymous

041224-21281-01.dmp

Microsoft (R) Windows Debugger Version 10.0.22621.3233 AMD64

Loading Dump File [C:\Windows\Minidump\041224-21281-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 22621 MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Machine Name:

Kernel base = 0xfffff8046d400000 PsLoadedModuleList = 0xfffff8046e013110

Debug session time: Fri Apr 12 14:57:28.992 2024 (UTC + 8:00)

System Uptime: 1 days 7:54:56.949

Loading Kernel Symbols

...............................................................

................................................................

....

Loading User Symbols

Loading unloaded module list

..................................................

For analysis of this file, run !analyze -v

1: 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: 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: 2686 

Key  : Analysis.DebugAnalysisManager 

Value: Create 

Key  : Analysis.Elapsed.mSec 

Value: 3138 

Key  : Analysis.Init.CPU.mSec 

Value: 1281 

Key  : Analysis.Init.Elapsed.mSec 

Value: 20872 

Key  : Analysis.Memory.CommitPeak.Mb 

Value: 112

FILE_IN_CAB: 041224-21281-01.dmp

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

DUMP_FILE_ATTRIBUTES: 0x1808

Kernel Generated Triage Dump

BUGCHECK_CODE: 139

BUGCHECK_P1: a

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

TRAP_FRAME: 0000000000000000 -- (.trap 0x0)

EXCEPTION_RECORD: 0000000000000000 -- (.exr 0x0)

Cannot read Exception record @ 0000000000000000

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:

ffffa80712ff7298 fffff8046d82350e : 0000000000000139 000000000000000a 0000000000000000 0000000000000000 : nt!KeBugCheckEx

ffffa80712ff72a0 fffff80493c9e774 : ffffe502214dbde0 000064dde985bbe5 ffffe502214dbd00 000000000000000e : nt!guard_icall_bugcheck+0x1e

ffffa80712ff72d0 fffff80493ca7a45 : ffffe502214dbde0 ffffe5020bfc0250 ffffe502214dbde0 ffffe5020bfc0250 : rfcomm!BrbpConnect+0xbc

ffffa80712ff7360 fffff80493ca9c3b : ffffe502214dbde0 ffffe5020bfc0250 0000000000000000 0000000000000000 : rfcomm!SessionConnect+0xc1

ffffa80712ff73b0 fffff80493c9796d : ffffe5020bfc0201 0000000000000001 0000000000000000 ffffe50213702c10 : rfcomm!ChannelConnect+0x66f

ffffa80712ff7440 fffff80493c97b4b : ffffe5020bfc0250 ffffe50213702c10 ffffe5020bfc0250 0000000000000000 : rfcomm!TdiConnectToPort+0x1b1

ffffa80712ff74b0 fffff80493c9b13f : ffffe5020bfc0250 7f868150e515b205 ffffe5020bfc0280 ffffe502129f7260 : rfcomm!TdiConnectToPortWithPolicy+0x17f

ffffa80712ff7510 fffff80493cabf60 : ffffe5021278e2c0 ffffa80712ff75c0 0000000000000013 fffff80493cb21d8 : rfcomm!TdiServiceClassIdCallback+0xaf

ffffa80712ff7560 fffff80493cab97c : ffffe5022c957960 fffff80493cbd000 0000000000000000 ffffe5022c957960 : rfcomm!SdppIdToPortNextAttribute+0x180

ffffa80712ff75f0 fffff8046d7334b4 : 0000000000000000 ffffa80712ff76a9 ffffe5022c957f8b 0000000000000000 : rfcomm!SdppAttributeSearchCompletionRoutine+0xbc

ffffa80712ff7630 fffff8046d733367 : ffffe5022c957960 ffffa80712ff7708 0000000000000000 0000000000000000 : nt!IopfCompleteRequest+0x134

ffffa80712ff7710 fffff80490ea957b : ffffe5022c957960 0000000000000000 0000000000000000 0000000000000000 : nt!IofCompleteRequest+0x17

ffffa80712ff7740 fffff80490f255e0 : ffffe50221590650 0000000000000000 0000000000000000 0000000000000040 : BTHport!BthCompleteRequest+0x1b7

ffffa80712ff77b0 fffff80490fb6b29 : ffffe5021bba0920 ffffa80712ff7850 ffffe50221590650 fffff8046d6924fd : BTHport!SdpL2cap_CompleteClientRequest+0xb0

ffffa80712ff77f0 fffff8046d65bbe0 : 000000000a1f2f40 ffffe5020b2bfb00 0000000016000105 000000000000001b : BTHport!SdpL2cap_ReadWorkItemWorker+0x249

ffffa80712ff7890 fffff8046d6d6fd5 : ffffe502038abc50 ffffe50222c0d040 ffffa80712ff7a00 ffffe50200000000 : nt!IopProcessWorkItem+0x100

ffffa80712ff7900 fffff8046d76db37 : ffffe50222c0d040 000000000000072a ffffe50222c0d040 fffff8046d6d6e80 : nt!ExpWorkerThread+0x155

ffffa80712ff7af0 fffff8046d81d554 : fffff8046a77e180 ffffe50222c0d040 fffff8046d76dae0 0000000000000246 : nt!PspSystemThreadStartup+0x57

ffffa80712ff7b40 0000000000000000 : ffffa80712ff8000 ffffa80712ff1000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x34

SYMBOL_NAME: rfcomm!BrbpConnect+bc

MODULE_NAME: rfcomm

IMAGE_NAME: rfcomm.sys

IMAGE_VERSION: 10.0.22621.3209

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: bc

FAILURE_BUCKET_ID: 0x139_a_GUARD_ICALL_CHECK_FAILURE_rfcomm!BrbpConnect

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ea7976f7-259a-f064-f54b-3af0593bd68a}

Followup: MachineOwner

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

2 answers

Answer 1

Anonymous

Thank you for your response. I will update the driver and check if the issue continues.

0 comments

Answer 2

Hello, LinweiZheng

Welcome to the Microsoft community.

Thank you for your feedback. Based on the analysis you provided, the problem seems to point to rfcomm.sys, which is usually associated with Bluetooth drivers. We suggest you to update the corresponding driver on the website of your Bluetooth device to see if it can solve your problem.

If the problem continues, please provide me with the dmp file and I will be ready to help you.

Please let me know if you have any other questions or if I haven't explained something clearly.

Best Regards,

Aaron- MSFT | Microsoft Community Support Specialist

Share via

KERNEL_SECURITY_CHECK_FAILURE

2 answers