driver power state failure and kernel security check failure

Question

driver power state failure and kernel security check failure

Sriram Cherukuri 0


Loading Dump File [C:\Windows\Minidump\060423-8703-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 22621 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff800`3b400000 PsLoadedModuleList = 0xfffff800`3c0134d0
Debug session time: Sun Jun  4 17:16:35.518 2023 (UTC + 5:30)
System Uptime: 0 days 0:00:14.217
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:
fffff800`3b82c0f0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff60f`d532eb10=0000000000000139
4: 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: fffff800953dd0f0, Reserved

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2062

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 7507

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

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

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

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x139

    Key  : Bugcheck.Code.Register
    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


FILE_IN_CAB:  060423-8703-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: fffff800953dd0f0

TRAP_FRAME:  0000000000000000 -- (.trap 0x0)

EXCEPTION_RECORD:  0000000000000000 -- (.exr 0x0)
Cannot read Exception record @ 0000000000000000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  smss.exe

STACK_TEXT:  
fffff60f`d532eb08 fffff800`3b836e2e     : 00000000`00000139 00000000`0000000a 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff60f`d532eb10 fffff800`3bab5c98     : fffff60f`d532eb80 fffff60f`d532eb80 00000000`00000001 ffff970e`d298b140 : nt!guard_icall_bugcheck+0x1e
fffff60f`d532eb40 fffff800`3baeae9c     : 00000000`00000000 00000000`00000000 00000000`00000001 ffff970e`cdfc5b60 : nt!PspCallProcessNotifyRoutines+0x204
fffff60f`d532ec10 fffff800`3bb032ae     : ffff970e`d298d140 ffff970e`d298b140 fffff60f`d532f440 fffff60f`d532f2f8 : nt!PspInsertThread+0x738
fffff60f`d532ecf0 fffff800`3b840ee8     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtCreateUserProcess+0xa2e
fffff60f`d532fa30 00007ffd`7ee70624     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000c4`49c7f508 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`7ee70624


SYMBOL_NAME:  nt!guard_icall_bugcheck+1e

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.1778

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1e

FAILURE_BUCKET_ID:  0x139_a_GUARD_ICALL_CHECK_FAILURE_nt!guard_icall_bugcheck

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {391a5384-38fb-03d6-baa8-4a74bc53c199}

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


Loading Dump File [C:\Windows\Minidump\060423-12234-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 22621 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff801`46e00000 PsLoadedModuleList = 0xfffff801`47a134d0
Debug session time: Sun Jun  4 16:45:07.977 2023 (UTC + 5:30)
System Uptime: 0 days 0:00:11.682
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:
fffff801`4722c0f0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffffb07`90f56b10=0000000000000139
2: 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: fffff80174c8d210, Reserved

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1750

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 14776

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

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

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

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x139

    Key  : Bugcheck.Code.Register
    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


FILE_IN_CAB:  060423-12234-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: fffff80174c8d210

TRAP_FRAME:  0000000000000000 -- (.trap 0x0)

EXCEPTION_RECORD:  0000000000000000 -- (.exr 0x0)
Cannot read Exception record @ 0000000000000000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  smss.exe

STACK_TEXT:  
fffffb07`90f56b08 fffff801`47236e2e     : 00000000`00000139 00000000`0000000a 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffffb07`90f56b10 fffff801`474b5c98     : fffffb07`90f56b80 fffffb07`90f56b80 00000000`00000001 fffffb07`90f57578 : nt!guard_icall_bugcheck+0x1e
fffffb07`90f56b40 fffff801`474eae9c     : 00000000`00000000 00000000`00000000 00000000`00000001 ffff9107`46b72140 : nt!PspCallProcessNotifyRoutines+0x204
fffffb07`90f56c10 fffff801`475032ae     : ffff9107`4adad140 ffff9107`4adab140 fffffb07`90f57440 fffffb07`90f572f8 : nt!PspInsertThread+0x738
fffffb07`90f56cf0 fffff801`47240ee5     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtCreateUserProcess+0xa2e
fffffb07`90f57a30 00007ffc`3ced0624     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000033`aef2f378 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`3ced0624


SYMBOL_NAME:  nt!guard_icall_bugcheck+1e

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.1778

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1e

FAILURE_BUCKET_ID:  0x139_a_GUARD_ICALL_CHECK_FAILURE_nt!guard_icall_bugcheck

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {391a5384-38fb-03d6-baa8-4a74bc53c199}

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


Loading Dump File [C:\Windows\Minidump\060423-8546-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 22621 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff803`27a00000 PsLoadedModuleList = 0xfffff803`286134d0
Debug session time: Sun Jun  4 16:39:03.688 2023 (UTC + 5:30)
System Uptime: 0 days 0:00:13.387
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:
fffff803`27e2c0f0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffd28d`6baa6b10=0000000000000139
4: 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: fffff8038969d210, Reserved

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1608

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 1899

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

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

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

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x139

    Key  : Bugcheck.Code.Register
    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


FILE_IN_CAB:  060423-8546-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: fffff8038969d210

TRAP_FRAME:  0000000000000000 -- (.trap 0x0)

EXCEPTION_RECORD:  0000000000000000 -- (.exr 0x0)
Cannot read Exception record @ 0000000000000000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  smss.exe

STACK_TEXT:  
ffffd28d`6baa6b08 fffff803`27e36e2e     : 00000000`00000139 00000000`0000000a 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffd28d`6baa6b10 fffff803`280b5c98     : ffffd28d`6baa6b80 ffffd28d`6baa6b80 00000000`00000001 ffffd505`47192140 : nt!guard_icall_bugcheck+0x1e
ffffd28d`6baa6b40 fffff803`280eae9c     : 00000000`00000000 00000000`00000000 00000000`00000001 ffffd505`41b4b4c0 : nt!PspCallProcessNotifyRoutines+0x204
ffffd28d`6baa6c10 fffff803`281032ae     : ffffd505`47194140 ffffd505`47192140 ffffd28d`6baa7440 ffffd28d`6baa72f8 : nt!PspInsertThread+0x738
ffffd28d`6baa6cf0 fffff803`27e40ee8     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtCreateUserProcess+0xa2e
ffffd28d`6baa7a30 00007ffc`c99b0624     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
0000002a`0ddcf598 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`c99b0624


SYMBOL_NAME:  nt!guard_icall_bugcheck+1e

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.1778

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1e

FAILURE_BUCKET_ID:  0x139_a_GUARD_ICALL_CHECK_FAILURE_nt!guard_icall_bugcheck

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {391a5384-38fb-03d6-baa8-4a74bc53c199}

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

Sriram Cherukuri 0 Reputation points

2023-06-08T08:04:21.91+00:00

please help, i dont understand none of that, can the cause of this problem be identified with the above information, and what else is needed if so?
Thanks a lot

2 answers

Your answer

Sriram Cherukuri 0 Reputation points

2023-06-08T08:04:21.91+00:00

please help, i dont understand none of that, can the cause of this problem be identified with the above information, and what else is needed if so?
Thanks a lot

Answer 1

hi there,

Common reasons you might get the "Kernel Security Check Failure" issue are corrupted system files, faulty hardware, or outdated drivers.

Faulty RAM (memory) or a corrupted or damaged hard disk drive could be the cause of the issue.

At the desktop, click Windows Key + R to launch the “Run” box.

In the "Run" box, type in “cmd” then press ctrl+shift+enter to run the command prompt as administrator.

Click the "Yes" button on the "User Account Control" (UAC) prompt.

Type in “chkdsk c: /f” and press enter

or

From the desktop, use the Windows + R key to open the “Run” box

In the the “Run” box, type in “cmd” then press ctrl+shift+enter to launch the command prompt with administrative privileges.

Click the "Yes" button on the "User Account Control"ss (UAC) prompt

Type “SFC /scannow” in the command prompt window and press “Enter”.

Launch the memory diagnostics tool.

Input memory or mdsched in the Windows Cortana Search box.

Click on the best match Windows Memory Diagnostic to run the tool

And see if it helps,

Thank you

--If the reply is helpful, please Upvote and Accept as answer--

Answer 2

Docs 15,761

Please run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive.

https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

https://www.elevenforum.com/t/bsod-posting-instructions.103/

.

--Please don't forget to upvote and Accept as answer if the reply is helpful--

.

Share via

driver power state failure and kernel security check failure

2 answers

Your answer