How to resolve 0x00000139 Kernel Security Check Failure Blue Screen in Windows 10?

WOW that was exciting. I almost rendered my computer useless.

I was able to get you several minidumps, however. I set up a recovery point and started the verifier like stated on the page you linked. Upon restarting my computer bluescreened within maybe 30 seconds after logging in. It was the same "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED". It restarted and the exact same thing happened. I got another BSOD with the same log message around 20-30 seconds after logging in. This repeated two more times until I managed to disable the verifier.

(then it booted in recovery mode and I realized I FORGOT MY PASSWORD hahaha. Luckily i was able to speed run the disable and restart after logging in)

Here is a google drive folder with the 4 minidumps created from the 4 BSODs. They are labeled with the time the dumps were created. https://drive.google.com/drive/folders/15KwOqkFNsoth2u0yU0WbjV0P_SHCOjnM?usp=sharing

Hopefully this provides a little more information.

Thanks for the help!

Hey again Paul,

That's unfortunate to hear. I have not yet had a chance to run the verifier you recommended, however, I just received another bluescreen.

This time it was "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED". Again, I'm not sure if this is related, but I was playing a video game at the time.

Here's the bugcheck report:

The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff8053ac06d67, 0xfffffe8810866d28, 0xfffff80537d39920). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 80573f8c-7363-4092-b74b-bf0baa02c1e5.

Here's a link to the minidump created: https://drive.google.com/file/d/11AvDbTW-UoSdV9OLwFv7a1TiW3yVhpvJ/view?usp=sharing

Thanks again for helping me out. I will take a look at that driver verifier in the mean time

The minidump files still point to "ntkrnlmp.exe".

I recommend that you run Driver Verifier to find any misbehaving, corrupted, or outdated driver.

Follow the instructions from this article.

https://www.tenforums.com/tutorials/5470-enable...

Reminders:

=> Disable Driver Verifier after 48 hours or after receiving a BSOD.

=> Create a Restore Point before running Driver Verifier.

Share the minidump file once you receive a BSOD error.

Standard Disclaimer: There are links to non-Microsoft websites.

The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.

Hi Paul,

Thanks for the quick response.

I only have two other minidump files. Both of which are from 11/8 (last wednesday). I can not remember whether this was the same issue, but it is very possible.

Here is one from earlier in the evening on the eighth https://drive.google.com/file/d/1jwuLZDSrbQXTTv3bolZxjb5ZvCH9qjvy/view?usp=sharing

And the second from an hour and a half later that evening https://drive.google.com/file/d/1PYBBGFZBDFX-ZkmHHHR4bm-O1kyPtGqo/view?usp=sharing

I appreciate you taking the time to take a look at these!

Hi AyhanEyikan,

I'm Paul and I'm here to help you with your concern.

The minidump file only indicated a system kernel driver "ntkrnlmp.exe". Since it's a system file it means something else drove it into a fault. It could be hardware, software, or driver.

We need further analysis.

Can you share other minidump files that you have so that I can also analyze them?

Thanks.