Share via

BSOD: KERNEL_SECURITY_CHECK_FAILURE

Jeaz ‪ 0 Reputation points
2025-08-17T19:16:57.98+00:00

I have a google drive of the minidump I tried to take a look myself but am clearly not well versed enough to understand the issue to be honest, any help would be appreciated.

https://drive.google.com/drive/folders/1XATxRrIkn7aNEB5ZeYzSXfsL1QykRtEO?usp=sharing

Windows for home | Windows 11 | Performance and system failures
0 comments

12 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Igor Leyko 110.8K Reputation points Independent Advisor
    2025-08-19T19:24:26.4566667+00:00

    Seems there were some mistypes in the command. Boot to Safe mode, disable verifier by

    verifier /reset

    command and share this minidump for analysis.

    Was this answer helpful?

  2. Igor Leyko 110.8K Reputation points Independent Advisor
    2025-08-18T22:58:29.0966667+00:00

    Please use driver verifier to gather additional information. https://support.microsoft.com/en-us/help/244617/using-driver-verifier-to-identify-issues-with-windows-drivers-for-adva

    Run

    verifier /standard /all /bootmode resetonbootfail

    command, reboot PC and use it as usual (it will be slower). If blue screen happens please share memory dumps to OneDrive for analysis.

    Was this answer helpful?

  3. Jeaz ‪ 0 Reputation points
    2025-08-18T20:11:49.1166667+00:00

    PC crashed again after launching into a counter strike game so COD isn’t the issue probably, it’s currently running a memory diagnostic and i’ll send the results of that an the new dump when it’s done

    Was this answer helpful?

    0 comments
  4. Michael Taylor 61,221 Reputation points
    2025-08-18T19:55:53.26+00:00

    A quick scan of the dump files you provided indicates the following:

    • First crash was caused by corrupted memory by your graphics driver
    • Second crash was caused by corrupted memory itself
    • Last crash was caused by Call of Duty while doing something with memory

    My gut instinct is that you have bad memory. If this machine is older then the memory could be bad. Running a memory test like memtest86 would help identify this. If this is a new machine then I'd wonder about a compatibility issue between motherboard and memory or overclocking issues. If you are overclocking then reset the system to baseline and see if the issue goes away.

    If memory test doesn't find anything wrong and you aren't overclocking then the graphics driver would be next. This doesn't seem likely given the later crashes. Not sure if COD has a kernel-level anti-cheat driver or not but that is also a possibility I guess.

    Was this answer helpful?

  5. Igor Leyko 110.8K Reputation points Independent Advisor
    2025-08-17T19:57:11.7833333+00:00

    Hi,

    My name is Igor, it's a pleasure for me to help others and I'll try to help you. I am merely a fellow user trying to provide insight and information that may be helpful to others.

    This bug check indicates that the kernel has detected the corruption of a critical data structure. Determining the cause of this issues typically requires the use of the debugger to gather additional information. Multiple dump files should be examined to see if this stop code has similar characteristics.

    Try to use recommendations from Resolution section of https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x139--kernel-security-check-failure#resolution page

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.