Question BSOD Kernel security check failure when alt+Tab while gaming

May 29, 2022
3
0
10
0
Hello,

when I play and I do an alt tab, windows sends me back to my desktop but it is impossible for me to return to the game.
I have to close the game, then at that moment impossible to restart any game, they all crash.
Then follows a BSOD with the message "Kernel security check failure".

Searching on the net I saw that it could be a compatibility problem between the drivers and the windows update.
So I updated all my drivers but the problem is still there.

My config:
Intel Core i7 7700K
ASUS ROG Z270 Maximum IX Code
x2 Gskill 8Go 3200Mhz
Nvidia Geforce 1070
Samsung SSD 850EVO 1 Tb
Kingstone SSD 480Gb

Here is my Minidump
https://www.mediafire.com/file/iob1wi9pd3v23i7/Minidump.rar/file

Thanks for anyone reading/helping
 
first bugcheck was in the nvidia graphics driver.
you have various out of date drivers installed.

bios update: ROG MAXIMUS IX CODE | ROG Maximus | Gaming Motherboards|ROG - Republic of Gamers|ROG Global (asus.com)

motherboard vendor did not supply proper driver updates, most likely because of the age of the motherboard. (old network drivers, old sound drivers) the old sound driver had a bug that would crash gpu driver sound support. look for update for:
\SystemRoot\system32\drivers\RTKVHD64.sys Thu Feb 8 03:07:31 2018

I would download autoruns from here:
Autoruns for Windows - Windows Sysinternals | Microsoft Docs
and disable the intel overclock utility
C:\Program Files (x86)\Intel\Intel(R) Extreme Tuning Utility\Drivers\IocDriver\64bit\iocbios2.sys Fri Sep 15 03:22:21 2017.

you should also start cmd.exe as an admin then run
dism.exe /online /cleanup-image /restorehealth

(your machine had 3 modified windows core files)
-------------
will take a quick look at the older bugcheck
looks like kernel heap corruption while
easyanticheat driver was running. can not figure out the cause from a minidump, would need a kernel dump to check the heap data structure.
work on removing the overclock driver, and update bios and retest for failure
 
Last edited:
May 29, 2022
3
0
10
0
first bugcheck was in the nvidia graphics driver.
you have various out of date drivers installed.

bios update: ROG MAXIMUS IX CODE | ROG Maximus | Gaming Motherboards|ROG - Republic of Gamers|ROG Global (asus.com)

motherboard vendor did not supply proper driver updates, most likely because of the age of the motherboard. (old network drivers, old sound drivers) the old sound driver had a bug that would crash gpu driver sound support. look for update for:
\SystemRoot\system32\drivers\RTKVHD64.sys Thu Feb 8 03:07:31 2018

I would download autoruns from here:
Autoruns for Windows - Windows Sysinternals | Microsoft Docs
and disable the intel overclock utility
C:\Program Files (x86)\Intel\Intel(R) Extreme Tuning Utility\Drivers\IocDriver\64bit\iocbios2.sys Fri Sep 15 03:22:21 2017.

you should also start cmd.exe as an admin then run
dism.exe /online /cleanup-image /restorehealth

(your machine had 3 modified windows core files)
-------------
will take a quick look at the older bugcheck
looks like kernel heap corruption while
easyanticheat driver was running. can not figure out the cause from a minidump, would need a kernel dump to check the heap data structure.
work on removing the overclock driver, and update bios and retest for failure
Here is the kernel dump

Code:
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: fffff80580a6ee30, Address of the trap frame for the exception that caused the BugCheck
Arg3: fffff80580a6ed88, 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: 3702

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 4560

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

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

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

    Key  : Bugcheck.DumpVsMemoryMatch
    Value: True

    Key  : FailFast.Name
    Value: CORRUPT_LIST_ENTRY

    Key  : FailFast.Type
    Value: 3

    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:  MEMORY.DMP

BUGCHECK_CODE:  139

BUGCHECK_P1: 3

BUGCHECK_P2: fffff80580a6ee30

BUGCHECK_P3: fffff80580a6ed88

BUGCHECK_P4: 0

TRAP_FRAME:  fffff80580a6ee30 -- (.trap 0xfffff80580a6ee30)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe10f99e5c130 rbx=0000000000000000 rcx=0000000000000003
rdx=ffffe10f9f473360 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80593a3fe32 rsp=fffff80580a6efc0 rbp=0000000000000000
r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=ffffe10f8b660d60 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
dxgmms2!VidSchiUnwaitWaitQueuePacket+0x1ee:
fffff805`93a3fe32 cd29            int     29h
Resetting default scope

EXCEPTION_RECORD:  fffff80580a6ed88 -- (.exr 0xfffff80580a6ed88)
ExceptionAddress: fffff80593a3fe32 (dxgmms2!VidSchiUnwaitWaitQueuePacket+0x00000000000001ee)
   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

PROCESS_NAME:  System

ERROR_CODE: (NTSTATUS) 0xc0000409 - Le syst me a d tect  la saturation de la m moire tampon dans cette application. Cette saturation pourrait permettre   un utilisateur mal intentionn  de prendre le contr le de cette application.

EXCEPTION_CODE_STR:  c0000409

EXCEPTION_PARAMETER1:  0000000000000003

EXCEPTION_STR:  0xc0000409

STACK_TEXT:
fffff805`80a6eb08 fffff805`7aa09c69     : 00000000`00000139 00000000`00000003 fffff805`80a6ee30 fffff805`80a6ed88 : nt!KeBugCheckEx
fffff805`80a6eb10 fffff805`7aa0a090     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff805`80a6ec50 fffff805`7aa08423     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiFastFailDispatch+0xd0
fffff805`80a6ee30 fffff805`93a3fe32     : fffff805`80a6ef60 00000000`00000004 fffff805`80a6f040 ffffe10f`99e5c010 : nt!KiRaiseSecurityCheckFailure+0x323
fffff805`80a6efc0 fffff805`93a3be7a     : ffffe10f`98774000 fffff805`80a6f069 ffffe10f`9cdea130 ffffe10f`98774330 : dxgmms2!VidSchiUnwaitWaitQueuePacket+0x1ee
fffff805`80a6f000 fffff805`93a3b9eb     : ffffe10f`987737a8 ffffe10f`a1f16218 ffffe10f`987746b0 ffffe10f`a2c476c0 : dxgmms2!VidSchiUnwaitMonitoredFences+0x3fa
fffff805`80a6f0d0 fffff805`93a39055     : 00000000`00000000 fffff805`80a6f220 00000000`00000000 ffffe10f`a2172930 : dxgmms2!VidSchiCompleteSignalSyncObject+0x9b
fffff805`80a6f120 fffff805`93a38acc     : ffffe10f`98774602 fffff805`00000000 ffffe10f`00000000 ffffe10f`00000000 : dxgmms2!VidSchiProcessCompletedQueuePacketInternal+0x1e5
fffff805`80a6f2c0 fffff805`93a35af5     : ffffe10f`987f2202 00000000`00000001 00000000`00000001 00000000`00000001 : dxgmms2!VidSchiProcessDpcCompletedPacket+0x70c
fffff805`80a6f420 fffff805`9667d572     : fffff805`80a6f519 ffffe10f`987f23f0 fffff805`80a6fa70 00003317`d5bca495 : dxgmms2!VidSchDdiNotifyDpc+0x225
fffff805`80a6f4d0 fffff805`9c27a99b     : ffffe10f`92f27030 00000000`00000000 ffffe10f`92f27030 ffffe10f`96502000 : dxgkrnl!DxgNotifyDpcCB+0x92
fffff805`80a6f580 fffff805`9ca37d1b     : fffff805`9c27a92e ffffe10f`96502000 fffff805`80a6f860 00000000`00000000 : nvlddmkm+0x5a99b
fffff805`80a6f610 fffff805`9ca37b01     : fffff805`9ca37cb3 fffff805`7a8a27f9 ffffe10f`96502000 ffffe10f`965020e8 : nvlddmkm+0x817d1b
fffff805`80a6f6a0 fffff805`9c28a009     : ffffe10f`96502000 fffff805`80a6fa70 fffff805`80a6fa70 00000000`00000000 : nvlddmkm+0x817b01
fffff805`80a6f6d0 fffff805`7a8a181e     : fffff805`9c289f83 fffff805`761b6240 fffff805`80a6fa60 fffff805`00000002 : nvlddmkm+0x6a009
fffff805`80a6f760 fffff805`7a8a0b04     : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e
fffff805`80a6f8d0 fffff805`7a9fb8ce     : 00000000`00000000 fffff805`761b3180 fffff805`7b327a00 ffffe10f`8d639040 : nt!KiRetireDpcList+0x1f4
fffff805`80a6fb60 00000000`00000000     : fffff805`80a70000 fffff805`80a69000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME:  dxgmms2!VidSchiUnwaitWaitQueuePacket+1ee

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.19041.1620

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1ee

FAILURE_BUCKET_ID:  0x139_3_CORRUPT_LIST_ENTRY_dxgmms2!VidSchiUnwaitWaitQueuePacket

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {a5c301dd-d94c-ce51-487a-a2f93a69ccff}

Followup:     MachineOwner
 
normally for this type of problem your first fix attempt would be to remove any overclocking drivers and remove and update all of your graphics drivers. I would also suggest updating your motherboard sound drivers. And disable any sound source that you do not have a speaker connected to. for example disable high definition sound in your gpu if you do not get sound via you graphics cable to your monitor. Update motherboard sound driver since there was a version that would respond to other sound devices like the gpu sound driver and overflow the gpu stack. you can disable the motherboard sound hardware in bios if you do not use it. (sound includes unconnected microphone)

generally, I actually need the memory dump file even though it is kind of big.
memory dumps are several GB,

you should also confirm you updated the bios or went into bios and reset it to defaults.
 
May 29, 2022
3
0
10
0
normally for this type of problem your first fix attempt would be to remove any overclocking drivers and remove and update all of your graphics drivers. I would also suggest updating your motherboard sound drivers. And disable any sound source that you do not have a speaker connected to. for example disable high definition sound in your gpu if you do not get sound via you graphics cable to your monitor. Update motherboard sound driver since there was a version that would respond to other sound devices like the gpu sound driver and overflow the gpu stack. you can disable the motherboard sound hardware in bios if you do not use it. (sound includes unconnected microphone)

generally, I actually need the memory dump file even though it is kind of big.
memory dumps are several GB,

you should also confirm you updated the bios or went into bios and reset it to defaults.
Thanks for helping agin i'll try all of this.
here is the file: https://www.mediafire.com/file/q8ugckoad6grhox/MEMORY.rar/file
 
try and remove nvidia share and the old game driver and reboot and see if you still the bugcheck
problem took a few hours in the last dump.
-----------
video driver stack overflow.
I do not see a direct cause of this problem.
I would next:
disable nvidia share
remove this game driver: (if you are done with the game)
D:\Program Files\TxGameAssistant\UI\2.0.12832.123\aow_drv_x64_ev.sys Tue Sep 24 00:08:32 2019

remove this driver:
C:\Program Files (x86)\Intel\Intel(R) Extreme Tuning Utility\Drivers\IocDriver\64bit\iocbios2.sys Fri Sep 15 03:22:21 2017

you should not be running a 32 bit overclocking tool. if really want it you should install a current version.

update this driver if you can
RTKVHD64.sys Thu Feb 8 03:07:31 2018
motherboard real tek sound driver. disable the hardware in bios if you do not use. there was a bug where they would corrupt the gpu graphics driver. not sure at what date it was fixed. it responded to the gpu hd audio DMA request and would overflow the graphics stack.

microsoft autoruns can be used to delete the two drivers.

-be sure to look for updates to your logi tech sound device (including firmware)

2 very old usb driver from 2010 installed;
SiLib.sys Thu Jul 15 15:08:26 2010
SiUSBXp.sys Thu Jul 15 15:27:13 2010

driver that causes corruption:
ScpVBus.sys Sun May 5 14:31:26 2013
(2016 version should be ok if you can find or compile a copy)
(not the cause of this problem, but you should remove it and find another driver when you can)
just fyi:
you have a 2018 killer networks wireless driver.
Qcamain10x64.sys
Qualcomm Atheros Extensible Wireless LAN device driver
intel now owns the company look here for update:
https://www.intel.com/content/www/us/en/products/details/wireless/killer-series/downloads.html

note: old unpatched bios from 2017
 
Last edited:

ASK THE COMMUNITY

TRENDING THREADS