Windows 10: Cortana BSOD my PC: KERNEL_SECURITY_CHECK_FAILURE

[COLOR=rgba30, 30, 30, 1]Microsoft R Windows Debugger Version 10.0.21306.1007 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\WINDOWS\MEMORY.DMP]Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.************* Path validation summary **************Response Time ms LocationDeferred srv*DBGHELP: Symbol Search Path: cache*;SRV*https://msdl.microsoft.com/download/symbolsSymbol search path is: srv*Executable search path is: DBGHELP: Symbol Search Path: cache*;SRV*https://msdl.microsoft.com/download/symbolsSYMSRV: BYINDEX: 0x1 C:\ProgramData\Dbg\sym ntoskrnl.exe D3F646971046000SYMSRV: PATH: C:\ProgramData\Dbg\sym\ntoskrnl.exe\D3F646971046000\ntoskrnl.exeSYMSRV: RESULT: 0x00000000DBGHELP: C:\ProgramData\Dbg\sym\ntoskrnl.exe\D3F646971046000\ntoskrnl.exe - OKDBGENG: C:\ProgramData\Dbg\sym\ntoskrnl.exe\D3F646971046000\ntoskrnl.exe - Mapped image memorySYMSRV: BYINDEX: 0x2 C:\ProgramData\Dbg\sym ntkrnlmp.pdb 3FCC539FF307DD2D9C509206D352B9AA1SYMSRV: PATH: C:\ProgramData\Dbg\sym\ntkrnlmp.pdb\3FCC539FF307DD2D9C509206D352B9AA1\ntkrnlmp.pdbSYMSRV: RESULT: 0x00000000DBGHELP: nt - public symbols C:\ProgramData\Dbg\sym\ntkrnlmp.pdb\3FCC539FF307DD2D9C509206D352B9AA1\ntkrnlmp.pdbWindows 10 Kernel Version 19041 MP 8 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTSEdition build lab: 19041.1.amd64fre.vb_release.191206-1406Machine Name:Kernel base = 0xfffff806`5b200000 PsLoadedModuleList = 0xfffff806`5be2a490Debug session time: Mon Mar 15 20:16:40.412 2021 UTC - 4:00System Uptime: 1 days 10:50:57.065SYMSRV: BYINDEX: 0x3 C:\ProgramData\Dbg\sym ntoskrnl.exe D3F646971046000SYMSRV: PATH: C:\ProgramData\Dbg\sym\ntoskrnl.exe\D3F646971046000\ntoskrnl.exeSYMSRV: RESULT: 0x00000000DBGHELP: C:\ProgramData\Dbg\sym\ntoskrnl.exe\D3F646971046000\ntoskrnl.exe - OKDBGENG: C:\ProgramData\Dbg\sym\ntoskrnl.exe\D3F646971046000\ntoskrnl.exe - Mapped image memorySYMSRV: BYINDEX: 0x4 C:\ProgramData\Dbg\sym ntkrnlmp.pdb 3FCC539FF307DD2D9C509206D352B9AA1SYMSRV: PATH: C:\ProgramData\Dbg\sym\ntkrnlmp.pdb\3FCC539FF307DD2D9C509206D352B9AA1\ntkrnlmp.pdbSYMSRV: RESULT: 0x00000000DBGHELP: nt - public symbols C:\ProgramData\Dbg\sym\ntkrnlmp.pdb\3FCC539FF307DD2D9C509206D352B9AA1\ntkrnlmp.pdbLoading Kernel Symbols.........................................................................................................................................................................................................................Loading User SymbolsPEB is paged out Peb.Ldr = 000000d2`a5a94018. Type ".hh dbgerr001" for detailsLoading unloaded module list.................................................For analysis of this file, run [/COLOR][COLOR=rgba0, 0, 255, 1]!analyze -v[/COLOR][COLOR=rgba30, 30, 30, 1]nt!KeBugCheckEx:fffff806`5b5f5c50 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff988`05eadb10=00000000000001390: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************KERNEL_SECURITY_CHECK_FAILURE 139A kernel component has corrupted a critical data structure. The corruptioncould potentially allow a malicious user to gain control of this machine.Arguments:Arg1: 000000000000000e, Type of memory safety violationArg2: fffff98805eade30, Address of the trap frame for the exception that caused the bugcheckArg3: fffff98805eadd88, Address of the exception record for the exception that caused the bugcheckArg4: 0000000000000000, ReservedDebugging Details:------------------SYMSRV: BYINDEX: 0x9 C:\ProgramData\Dbg\sym win32k.sys E87370BB9a000SYMSRV: PATH: C:\ProgramData\Dbg\sym\win32k.sys\E87370BB9a000\win32k.sysSYMSRV: RESULT: 0x00000000DBGHELP: C:\ProgramData\Dbg\sym\win32k.sys\E87370BB9a000\win32k.sys - OKDBGENG: C:\ProgramData\Dbg\sym\win32k.sys\E87370BB9a000\win32k.sys - Mapped image memorySYMSRV: BYINDEX: 0xA C:\ProgramData\Dbg\sym win32k.pdb ED706A38659240A066E6FB19B994BAAA1SYMSRV: PATH: C:\ProgramData\Dbg\sym\win32k.pdb\ED706A38659240A066E6FB19B994BAAA1\win32k.pdbSYMSRV: RESULT: 0x00000000DBGHELP: win32k - public symbols C:\ProgramData\Dbg\sym\win32k.pdb\ED706A38659240A066E6FB19B994BAAA1\win32k.pdbKEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 4312 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 4446 Key : Analysis.Init.CPU.mSec Value: 499 Key : Analysis.Init.Elapsed.mSec Value: 3940 Key : Analysis.Memory.CommitPeak.Mb Value: 78 Key : FailFast.Name Value: INVALID_REFERENCE_COUNT Key : FailFast.Type Value: 14 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.1BUGCHECK_CODE: 139BUGCHECK_P1: eBUGCHECK_P2: fffff98805eade30BUGCHECK_P3: fffff98805eadd88BUGCHECK_P4: 0TRAP_FRAME: fffff98805eade30 -- [/COLOR][COLOR=rgba0, 0, 255, 1].trap 0xfffff98805eade30[/COLOR][COLOR=rgba30, 30, 30, 1]NOTE: The trap frame does not contain all registers.[/COLOR][COLOR=rgba0, 0, 255, 1]Some register values may be zeroed or incorrect.[/COLOR][COLOR=rgba30, 30, 30, 1]rax=ffffa20802655050 rbx=0000000000000000 rcx=000000000000000erdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000rip=fffff80660731df4 rsp=fffff98805eadfc8 rbp=ffffdc0beebd2040 r8=ffffdc0c0c04b9d0 r9=fffff98805eae980 r10=0000000000000000r11=fffff98805eadf60 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei ng nz na po ncLXCORE!LxpSyscall_SCHED_SETSCHEDULER+0x94:fffff806`60731df4 cd29 int 29hResetting default scopeEXCEPTION_RECORD: fffff98805eadd88 -- [/COLOR][COLOR=rgba0, 0, 255, 1].exr 0xfffff98805eadd88[/COLOR][COLOR=rgba30, 30, 30, 1]ExceptionAddress: fffff80660731df4 LXCORE!LxpSyscall_SCHED_SETSCHEDULER+0x0000000000000094 ExceptionCode: c0000409 Security check failure or stack buffer overrun ExceptionFlags: 00000001NumberParameters: 1 Parameter[0]: 000000000000000eSubcode: 0xe FAST_FAIL_INVALID_REFERENCE_COUNT BLACKBOXBSD: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxbsd[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXNTFS: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxntfs[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXPNP: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxpnp[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXWINLOGON: 1PROCESS_NAME: backgroundTaskHost.exeERROR_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: c0000409EXCEPTION_PARAMETER1: 000000000000000eEXCEPTION_STR: 0xc0000409STACK_TEXT: fffff988`05eadb08 fffff806`5b607b69 : 00000000`00000139 00000000`0000000e fffff988`05eade30 fffff988`05eadd88 : nt!KeBugCheckExfffff988`05eadb10 fffff806`5b607f90 : fffff988`05eae130 fffff988`05eae11c ffffdc0b`fedc6880 ffffdc0b`ff8c7a68 : nt!KiBugCheckDispatch+0x69fffff988`05eadc50 fffff806`5b606323 : 00000000`00000000 fffff988`05ea9000 00000000`00000000 00000000`00000000 : nt!KiFastFailDispatch+0xd0fffff988`05eade30 fffff806`60731df4 : fffff806`61004b68 ffffa208`03bb971c ffffa208`02655050 ffffa207`fa6c9c01 : nt!KiRaiseSecurityCheckFailure+0x323fffff988`05eadfc8 fffff988`05eae0d0 : fffff988`05eae0d0 00000000`00000000 00000000`00000000 00000000`00000000 : LXCORE!LxpSyscall_SCHED_SETSCHEDULER+0x94fffff988`05eae0d8 fffff988`05eae0d0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff988`05eae0d0fffff988`05eae0e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff988`05eae0d0SYMBOL_NAME: LXCORE!LxpSyscall_SCHED_SETSCHEDULER+94MODULE_NAME: [/COLOR][COLOR=rgba0, 0, 255, 1]LXCORE[/COLOR][COLOR=rgba30, 30, 30, 1]IMAGE_NAME: LXCORE.SYSSTACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 94FAILURE_BUCKET_ID: 0x139_e_INVALID_REFERENCE_COUNT_LXCORE!LxpSyscall_SCHED_SETSCHEDULEROS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {7914fe9b-3019-bfb1-077f-959440cca2a2}Followup: MachineOwner---------[/COLOR]

:)

 

Kernel_security_check_failure bsod


A few months back I built my first PC, since then I've intermittently been experiencing BSOD crashes.

My computer crashes to a BSOD with the KERNEL_SECURITY_CHECK_FAILURE error message but I've also rarely had the following BSODs:

• DRIVER_VERIFIER_DETECTED_VIOLATION
• MEMORY_MANAGEMENT
• SPECIAL_POOL_DETECTED_MEMORY

That being said it's nearly always the KERNEL_SECURITY_CHECK_FAILURE error; the other messages haven't happened more than once or twice each.

I've attached the DM Log but I'm fairly new at this so please let me know if there is any other information that would help fix this.

Help me Ten Forums, you're my only help.

Attachment 52025

 

Cortana

Hi,

Thank you for posting your question in the Microsoft Community.

Appreciate your efforts to work on this issue.

This issue can occur if some of the system files are not working as expected.

Suggest you to follow the steps from this article to
troubleshoot Cortana on the PC.

Note: Do not go with the ‘Reset PC’ option for now.

Method 1: Follow these steps to disable Cortana:

1. Sign-in to the PC with your Microsoft account.
   
2. In the search box at the bottom, type Disable Cortana.
   
3. Once the suggestions appear in the list, click Cortana & Search settings.
   
4. From the right section of the Settings pane, move the top button to ‘Off’ to disable Cortana from Windows 10.
   

Method 2: Follow these steps to check if that helps.

1. Launch Cortana from the search bar on the taskbar.
   
2. Then, from the left pane click the settings button.
   
3. Under "Cortana" (the first option) and slide the pill switch to the ‘Off’ position.
   

Method 3: Launch the Settings app and click on Privacy. Navigate to Speech, inking, & typing, and click Stop getting to know me. These steps will disable Cortana.

Hope this helps.

Let us know if you got the help you needed.

Regards,

Srimadhwa B

Microsoft Community-Moderator

 

BSOD kernel_security_check_failure - Windows 10

I started getting kernel_security_check_failure BSOD every time I turn on my computer and letting it run. I managed to get a log text and a dump file. I checked on different sites and tried many solutions: running sfc scannow, defragging, memory error check, hard drive error check but it still happens. I read that the problem may be some drivers I had before the update. I had W7 -> W8 -> W7 -> W10. Between the OS changes I started from zero, meaning no programs or drivers installed from the old version, except for W7 to W10. Any ideas would be appreciated.

UPDATE: Here are the files i managed to get from my last BSOD crash. The PC turns on and then crashes with the BSOD. I managed to get the files after rebooting the PC for a few times until it didn't crash.here are the files I got