kernel security failure 0x139

Frank Pinterics 0 Reputation points
2026-09-17T14:56:09.8666667+00:00

I was working with tech support case # 7108859034 and the problem of kernel security failure 0x139 is still affecting the performance of my computer. I need talk to the tech support

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

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. David-M 126.2K Reputation points Independent Advisor
    2026-09-17T15:30:00.9466667+00:00

    Hi. I'm David, and I'm happy to help you.

    I can help you investigate and resolve this problem right here.

    Please see if your computer created minidump files.

    These files are in C:\Windows\Minidump.

    (If you don't have a Minidump folder, check if it is in the plural Minidumps.)

    Copy any files you have to your desktop and store them in a ZIP file. Then, upload the ZIP file to the cloud (OneDrive), choose to share it, and get the link.

    Then, post the link to the ZIP file here so I can have a look.

    Looking forward to your reply.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-09-17T14:56:26.6766667+00:00

    For direct Microsoft support, use live chat support:

    1. Open https://support.microsoft.com/home/contact
    2. Type Contact Support.
    3. Select Sign in to contact support and sign in with the Microsoft account, or select Contact Support if already signed in.
    4. For Product and services, select Windows.
    5. For Category, select Technical support.
    6. Select Chat with a support agent in your web browser.

    For the 0x139 stop code itself, KERNEL_SECURITY_CHECK_FAILURE means the kernel detected corruption of a critical data structure. General troubleshooting steps supported in the documentation are:

    1. Check Event Viewer and review the System Log for critical errors around the same time as the blue screen.
    2. Open Device Manager and look for devices with an exclamation mark; review the driver events and update the related driver.
    3. If hardware was added recently, remove or replace it, or check with the manufacturer for patches.
    4. If new drivers or system services were added recently, remove or update them.
    5. Run a virus scan, including a check of the Master Boot Record.
    6. If the crashes continue, examine multiple dump files with WinDbg because determining the exact cause often requires debugger analysis.
    AI-generated content may be incorrect. Read our transparency notes for more information.

    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.