KERNEL_SECURITY_CHECK_FAILURE (139) windows10

vgogh

Prominent
May 7, 2017
10
0
510
Hello.
I got some BSOD these days "kernel security check failure".
I googled this BSOD problem and tried something I could do.

1)update sound, graphic, bios
2)driver verifier
3)visiting service center (RAM, M/B)
4)windbg

1),2) done and seems fine I guess. 3) They didn't find problem with mine.
Finally I try to analyzing my dump file, and it says

Probably caused by : ntkrnlmp.exe ( nt!guard_icall_bugcheck+1b )

But I can't figuring it out clear solution.

Here's my dump files adress (5mini dump+meory dump)
https://1drv.ms/u/s!AkYCtVvVpgjgah4oy1OmqfVxbsg

*my system spec
cpu : intel i5 6600
m/b : asrock p150m pro4
ram : ddr4 16gb(8+4+4)
graphic : gtx970
power : 600w

Have a nice weekend friends.
 
Solution
\
you have windows build:
Built by: 15063.0.amd64fre.rs2_release.170317-1834

apply the windows updates to get to build 15063.250

it looks like the bad memory dumps are coming from peoples machines that are about 150 builds behind

(a few weeks)

-------------------
start by removing
\SystemRoot\system32\DRIVERS\AsrAppCharger.sys Tue May 10 01:28:46 2011

or update it to a current version. the old version will not work on a BIOS after 2012
your bios is from 2016.

the memory dump is corrupted but I can see if i can figure something out. The corruption means I can not trust the debugger.
I might try to update the debugger again, microsoft might have changed how memory dumps are being made in
the current build: Built by...
\
you have windows build:
Built by: 15063.0.amd64fre.rs2_release.170317-1834

apply the windows updates to get to build 15063.250

it looks like the bad memory dumps are coming from peoples machines that are about 150 builds behind

(a few weeks)

-------------------
start by removing
\SystemRoot\system32\DRIVERS\AsrAppCharger.sys Tue May 10 01:28:46 2011

or update it to a current version. the old version will not work on a BIOS after 2012
your bios is from 2016.

the memory dump is corrupted but I can see if i can figure something out. The corruption means I can not trust the debugger.
I might try to update the debugger again, microsoft might have changed how memory dumps are being made in
the current build: Built by: 15063.0.amd64fre.rs2_release.170317-1834

most of the driver table in the memory dump is corrupted (all of the dates are invalid) so i can not tell if you have applied all of the various driver updates for your motherboard> http://www.asrock.com/mb/Intel/B150M%20Pro4/?cat=Download&os=Win1064


the actual bugcheck was a stack overflow in a graphic buffer.
most of the time when I see that it is caused by a motherboard sound driver corrupting the video card sound drivers data.
and the fix is to install a updated motherboard sound driver from the motherboard vendors website.

you might also be able to disable sound devices in control panel device manager. (disable high def sound devices that do not have a speaker connected to them) Best to get updates to your motherboard sound drivers and not use the default ones provided by windows.

in your case it looks like the driver has been updated. you might also consider going into BIOS and resetting it to defaults or change any setting and change it back. This will force the BIOS to reassign all of the hardware resources and rebuild the database of hardware settings that it sends to windows. Windows uses the database from the bios so it knows what it is free to use as a setting.

I will try to update the debugger, I did it a few days ago but still had the same issues reading some peoples memory dumps on the current build of windows. (it could be a bug in the debugger, or a bug in the new versions of windows, or a bug in a one some common component used on many systems)



 
Solution
Thanks for your comment johnbl.
I did immediately(remove AsrAppCharger.sys, disabled audio driver provided by window)

I will reinstalling latest version of debugger like WDK, SDK, Visual studio2015 provided by window, and see if I can read every dump file without interruption.
reinstalling every driver in official Asrock website you linked.
Maybe the last thing to do is reset bios (remove battery from M/B and place it in M/B again)

After I finish all above that I'll let you know wheter it's worked or not.
Thanks again, and it helps a lot to me.
 
after you update, do run powershell and run the command
winver
it will display the windows version and the minor build number.
I am seeing my debugger just not working correctly on certain minor builds. (of the current major build)

on my machine winver shows
version 1703 (os build 15063.250)

I have seen a lot of memory dumps that would not work correctly with build 15063.0 or .16

here is the list of fixes in the minor build updates:
https://support.microsoft.com/en-us/help/4016240/windows-10-update-kb4016240

16063.250 is the current recommended build.




 
I checked my version and it says 15063.250, and updated 2017/May/1.
I use WDK, SDK, Visual studio for debugging. Is there more necessary programs for debugging?

After I posted this and installing WDK, found WDK install title was 15063.0.
WDK,SDK, visual studio from this site : https://developer.microsoft.com/ko-kr/windows/hardware/windows-driver-kit
Is it wrong version for me or do I need another proper version for these?


 
I have another question about "write debugging information". There are many options "mini, total, kernel, auto".
I selected "kernel memory dump". Should I change this to another one or keep it this way?

This is my current status about Start and restoration / System error section
Write debugging information : Kernel memory dump
file location : %SystemRoot%\MEMORY.DMP
overwrite to already existed file checked