Share via

BSD crashes - Code 139

Matthew Boyd-Gambling 0 Reputation points
2026-05-25T15:29:38.6833333+00:00

Hi,

PC has crashed quite a few times in the last 2 weeks,User's image

done the typical google of the code, cleaned PC and tried to check a few drivers but honestly not sure how to do it in bulk

wondered if someone could help me diagnose the problem via the .dmp file?

Thanks,

Windows for home | Windows 11 | Devices and drivers

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. David-M 115.2K Reputation points Independent Advisor
    2026-05-25T16:02:24.2333333+00:00

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

    Please share the 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-05-25T15:30:00.51+00:00

    Stop code 0x139 (KERNEL_SECURITY_CHECK_FAILURE) indicates that a kernel component has corrupted a critical data structure, often due to a faulty driver, system service, or hardware issue. The .dmp file is required to identify the exact cause, but there are supported steps to narrow it down on Windows 11.

    1. Apply general bug check troubleshooting
      • Remove or update any device drivers or system services that were added or updated in the last two weeks (when the crashes started). Use Device Manager to roll back or update drivers where possible.
      • Open Device Manager and look for any devices marked with an exclamation point (!). For each such device, review the Events tab in its properties and update or disable the related driver.
      • If any new hardware was added recently, temporarily remove or replace it and check with the manufacturer for firmware or driver updates.
      • Run the hardware diagnostics provided by the PC or motherboard manufacturer to rule out hardware faults.
      • Run a full antivirus scan, including a check of the Master Boot Record, to rule out disk/boot corruption.
    2. Configure and collect memory dumps
      • In the taskbar search box, type Advanced system settings and press Enter.
      • On the Advanced tab, under Startup and Recovery, select Settings.
      • Under Write debugging information, select Automatic memory dump, then select OK and restart.
      • After the next crash, confirm that %SystemRoot%\MEMORY.DMP or files in %SystemRoot%\Minidump are created.
    3. Analyze the crash dumps
      • On another stable PC, install the Windows 10/11 SDK and select Debugging Tools for Windows (WinDbg).
      • Start WinDbg, set the symbol path to https://msdl.microsoft.com/download/symbols.
      • Use File → Open Crash Dump to open the MEMORY.DMP or a minidump.
      • Run the !analyze -v command to see which driver or module is reported as the probable cause.
      • If multiple dumps show the same driver or pattern, update, roll back, or uninstall that driver or related software.
    4. Use Driver Verifier if the cause is still unclear
      • Because many stop errors are caused by drivers, enable Driver Verifier to stress non‑Microsoft drivers and force them to fail in a controlled way so that future dumps point to the faulty driver.
      • At an elevated command prompt, run verifier and configure it to verify only non‑Microsoft drivers, as described in the documentation for Driver Verifier.
      • After enabling it, use the PC normally until it crashes a few times and generates new dumps, then analyze those with WinDbg as above.
      • When finished, disable Driver Verifier with verifier /reset from an elevated command prompt.
    5. Additional checks
      • Run Windows Memory Diagnostics from Control Panel (search for “Memory” → Diagnose your computer’s memory problems) and review the results in Event Viewer under MemoryDiagnostics-Results.
      • In Event Viewer → Windows Logs → System, look for critical errors or BugCheck events that coincide with the crashes to correlate with specific drivers or services.

    These steps will let the crash dumps clearly identify whether a third‑party driver, system service, or hardware component is causing the 0x139 bug checks so that the offending component can be updated, removed, or replaced.

    References:

    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.