Share via

KERNEL_SECURITY_CHECK_FAILURE (139)

Anonymous
2023-03-02T01:48:32+00:00

After i got new internet installed and connected to my pc , after every couple of hours my pc freezes.

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

Loading Dump File [C:\Windows\Minidump\030123-16500-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 19041 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff805`4b000000 PsLoadedModuleList = 0xfffff805`4bc2a210
Debug session time: Wed Mar  1 20:28:45.709 2023 (UTC + 0:00)
System Uptime: 11 days 13:18:00.490
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`4b3fa090 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff8603`9f828d40=0000000000000139
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: 0000000000000008, A compiler-inserted array bounds check detected an illegal
array indexing operation.
Arg2: ffff86039f829060, Address of the trap frame for the exception that caused the BugCheck
Arg3: ffff86039f828fb8, Address of the exception record for the exception that caused the BugCheck
Arg4: 0000000000000000, Reserved

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 6030

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 21511

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

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

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

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x139

    Key  : Bugcheck.Code.Register
    Value: 0x139

    Key  : FailFast.Name
    Value: RANGE_CHECK_FAILURE

    Key  : FailFast.Type
    Value: 8

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1

FILE_IN_CAB:  030123-16500-01.dmp

BUGCHECK_CODE:  139

BUGCHECK_P1: 8

BUGCHECK_P2: ffff86039f829060

BUGCHECK_P3: ffff86039f828fb8

BUGCHECK_P4: 0

TRAP_FRAME:  ffff86039f829060 -- (.trap 0xffff86039f829060)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000009b rbx=0000000000000000 rcx=0000000000000008
rdx=ffffa981470a7106 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8055b4e22e5 rsp=ffff86039f8291f8 rbp=ffff898802000000
 r8=000000000000000a  r9=0000000000000000 r10=0000000000000080
r11=ffffa981470a7092 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
rtwlane01!_report_rangecheckfailure+0x5:
fffff805`5b4e22e5 cd29            int     29h
Resetting default scope

EXCEPTION_RECORD:  ffff86039f828fb8 -- (.exr 0xffff86039f828fb8)
ExceptionAddress: fffff8055b4e22e5 (rtwlane01!_report_rangecheckfailure+0x0000000000000005)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000008
Subcode: 0x8 FAST_FAIL_RANGE_CHECK_FAILURE 

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

EXCEPTION_STR:  0xc0000409

STACK_TEXT:  
ffff8603`9f828d38 fffff805`4b40e129     : 00000000`00000139 00000000`00000008 ffff8603`9f829060 ffff8603`9f828fb8 : nt!KeBugCheckEx
ffff8603`9f828d40 fffff805`4b40e690     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff8603`9f828e80 fffff805`4b40c65d     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiFastFailDispatch+0xd0
ffff8603`9f829060 fffff805`5b4e22e5     : fffff805`5b7cafc0 ffff8988`00ea64f0 ffff8988`08aa31c0 ffff8988`00ea6170 : nt!KiRaiseSecurityCheckFailure+0x31d
ffff8603`9f8291f8 fffff805`5b7cafc0     : ffff8988`00ea64f0 ffff8988`08aa31c0 ffff8988`00ea6170 ffff8988`0ff384b0 : rtwlane01!_report_rangecheckfailure+0x5
ffff8603`9f829200 fffff805`5b679489     : 00000000`00000001 ffff8603`9f829440 00000000`00000000 00000000`00000000 : rtwlane01!phydm_fw_trace_handler_8051+0x80
ffff8603`9f8292c0 fffff805`5b55a1d5     : fffff805`5b679400 ffff8603`9f8293f0 ffff8988`04f24168 00000000`00000000 : rtwlane01!RxCommandPacketHandle8192E+0x89
ffff8603`9f8292f0 fffff805`5b55a103     : fffff805`5b6807d0 fffff805`5b55b952 fffff805`5b688050 ffff8988`02000000 : rtwlane01!ProcessReceivedPacketForEachPortSpecific+0xc1
ffff8603`9f8295f0 fffff805`5b55b047     : fffff805`5b6807d0 ffff8988`04f24168 00000000`00000000 ffff8988`04f24168 : rtwlane01!ProcessReceivedPacket+0x93
ffff8603`9f829630 fffff805`5b557b32     : 00000914`5f931300 ffff8988`00964101 ffffa981`27ea0001 ffff8987`fe010000 : rtwlane01!RxHandleInterrupt+0x337
ffff8603`9f8296c0 fffff805`5b4b3411     : 00000914`5f931348 00000914`5f931348 ffff8988`02000000 ffff8603`9f829750 : rtwlane01!NicIFHandleInterrupt+0x5d2
ffff8603`9f829700 fffff805`4f2c7886     : 00000000`00000000 ffff8988`08977b10 ffff8988`003901a0 00000000`00000000 : rtwlane01!N6PciHandleInterrupt+0x121
ffff8603`9f829780 fffff805`4b29fc2e     : ffffa981`27ea4240 00000000`00000000 00000000`00000004 ffffa981`27ea1180 : ndis!ndisInterruptDpc+0x196
ffff8603`9f829860 fffff805`4b29ef14     : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e
ffff8603`9f8299d0 fffff805`4b3fe98e     : 00000000`00000000 ffffa981`27ea1180 ffffa981`27eac140 ffff8988`0bb0a480 : nt!KiRetireDpcList+0x1f4
ffff8603`9f829c60 00000000`00000000     : ffff8603`9f82a000 ffff8603`9f824000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e

SYMBOL_NAME:  rtwlane01!_report_rangecheckfailure+5

MODULE_NAME: rtwlane01

IMAGE_NAME:  rtwlane01.sys

IMAGE_VERSION:  2023.70.109.2018

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  5

FAILURE_BUCKET_ID:  0x139_8_RANGE_CHECK_FAILURE_rtwlane01!_report_rangecheckfailure

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {9bfdff00-2e77-2c49-499d-a0bfd47bb017}

Followup:     MachineOwner
---------
Windows for home | Windows 10 | Devices and drivers

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 No comments

1 answer

Sort by: Most helpful
  1. Lester Bernard Reyes 82,025 Reputation points Independent Advisor
    2023-03-02T02:19:59+00:00

    Hi and thanks for reaching out. My name is Bernard a Windows fan like you. I'll be happy to help you out today.

    I understand the issue you have, nothing to worry I am here to help, and just to confirm can you still use the affected device? if so, we need to analyze the error, can you please check if you have minidump files on the PC so that we can further examine what is the root cause of the issue?

    Press Windows key + E (To open file explorer)

    Click "This PC" > then follow the file path:

    C:\Windows\Minidump

    Copy the Minidump files and save them to another location like Desktop or Documents.

    Then please upload it to Cloud storage and please share the shareable link here.

    Let me know how it goes and I hope that helps.

    Bernard

    Was this answer helpful?

    0 comments No comments