Windows 11 25H2 recurring KERNEL_SECURITY_CHECK_FAILURE (0x139) with dxgmms2/dxgkrnl on HP Pro SFF 400 G9 / Intel UHD 770

Question

Hello,

We are seeing recurring BSODs on multiple Windows 11 systems with the following common pattern:

• HP Pro SFF 400 G9 Desktop PC

Intel UHD Graphics 770

Windows 11 Pro 25H2

Build 26200

Intel graphics driver 32.0.101.7084

Observed crash pattern:

KERNEL_SECURITY_CHECK_FAILURE (0x139)

recurring modules in the crash context:

dxgmms2.sys

  dxgkrnl.sys

  
     dwm.exe

     
        Intel graphics driver path

We also noticed a timing correlation with recent Windows servicing, especially in the KB5079473 / KB5077181 timeframe.

Question: Is Microsoft aware of any current Windows 11 25H2 issue involving 0x139 crashes in the dxgmms2/dxgkrnl graphics path on Intel UHD 770 systems, and if so, is there a recommended diagnostic or mitigation path?

We have already compared affected and unaffected systems and can provide minidumps and system details if needed.

Thank you.

Answer 1

Microsoft documentation and public Windows 11 25H2 release-health notes in the provided context do not list a specific known issue for Windows 11 25H2 where KERNEL_SECURITY_CHECK_FAILURE (0x139) is attributed to dxgmms2.sys/dxgkrnl.sys on Intel UHD 770.

However, the 0x139 bug check is documented as kernel detection of corruption of a critical data structure, and the guidance focuses on driver and system changes as likely causes. For graphics-path crashes, this typically means treating the graphics stack (GPU driver, DirectX components, and any recent updates) as primary suspects.

Based on the documented guidance for 0x139 and stop errors, a recommended diagnostic/mitigation path is:

1. Collect and analyze crash dumps
   • Ensure systems are configured to generate kernel or full memory dumps.
   • Use WinDbg and !analyze -v on multiple dumps to confirm that 0x139 is consistent and that dxgmms2.sys/dxgkrnl.sys are always on the stack.
   • Use the 0x139 parameter table to see what type of corruption is being detected (Parameter 1). This can help distinguish stack cookie violations, LIST_ENTRY corruption, invalid parameters, etc.
   • If Parameter 1 is 3 (LIST_ENTRY corruption), follow the specific guidance for list corruption (for example, suspect drivers mismanaging internal lists or synchronization objects).
2. Correlate with recent changes (updates, drivers, services)
   • Use Event Viewer → System log to correlate the bug checks with Windows updates or driver installations, as recommended for 0x139 and general stop errors.
   • Specifically look for critical errors and driver updates in the same time window as the BSODs.
3. Driver and device validation
   • In Device Manager, check for any devices with warning icons and review the Events tab for the display adapter to see if there are related driver issues.
   • Update or roll back the Intel graphics driver on a test system to see if the issue is driver-version-specific.
   • If the issue started after a particular update, test temporarily reverting that update on a subset of systems (as already done in similar Insider/preview scenarios in the context) to validate correlation.
4. Use Driver Verifier and special pool (for driver-related corruption)
   • For suspected driver corruption (including graphics drivers), enable Driver Verifier with appropriate settings (including special pool) for third-party drivers to try to catch the corruption closer to the source, as suggested for 0x139 LIST_ENTRY and synchronization-object issues.
5. General stop-error troubleshooting
   • Follow the general Windows 11 stop-error guidance: treat unexpected restarts and BSODs as potentially caused by hardware, drivers, or software; use the stop code and module information to narrow down the cause.
6. Escalation to Microsoft with data
   • Since minidumps and system details are available, use:
     • Feedback Hub to submit a report including crash dumps and a clear description of the hardware model, Windows build, driver version, and correlation with KBs.
     • For organizational environments, use Windows release health in the Microsoft 365 admin center and/or open a support case via Support for business to provide dumps and detailed repro information.

This path aligns with the documented handling of KERNEL_SECURITY_CHECK_FAILURE (0x139) and Windows 11 stop errors, and it is the recommended way to determine whether the crashes are due to a graphics driver issue, a Windows kernel/graphics stack regression, or another third-party driver.

---

References:

• Bug Check 0x139: KERNEL_SECURITY_CHECK_FAILURE
• Troubleshooting Windows unexpected restarts and stop code errors
• Windows 11, version 25H2 known issues and notifications
• Resolved issues in Windows 11, version 25H2