Recurring KERNEL_SECURITY_CHECK_FAILURE (0x139) on Intel UHD Graphics 770

[SensorM]

Hello Intel Support,
We are seeing a recurring BSOD issue on multiple production systems and would like to understand whether Intel is aware of a known problem involving Intel UHD Graphics 770 under recent Windows 11 builds.
Representative affected system:
HP Pro SFF 400 G9 Desktop PC
13th Gen Intel Core i5-13500
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 graphics-related context involving:
dxgkrnl.sys
dxgmms2.sys
dwm.exe
Intel graphics driver path (igdkmdn64.sys in dump analysis)
This is not limited to a single device. We manage about 400 systems, and around 20 are currently affected by the same pattern.
These systems are used as medical devices / medical equipment in production, so this issue is becoming increasingly serious for us.
We also noticed a timing correlation with recent Windows 11 servicing, especially around:
KB5079473
KB5077181
We have already tried the usual mitigation path, including:
driver alignment / reinstall
rollback and stabilization attempts
comparison between affected and unaffected systems
Unfortunately, the issue appears to be getting worse over time, and we are no longer able to stabilize it internally with standard remediation steps.
Question:
Is Intel aware of any current issue involving Intel UHD Graphics 770, driver 32.0.101.7084, and repeated 0x139 / dxgmms2 / dxgkrnl / dwm crashes on Windows 11, and if so, what is the recommended stable driver baseline or mitigation path for enterprise environments?
We can provide minidumps, system reports, and affected/unaffected comparisons if needed.
Thank you.

[xycross]

I Have the same issue, would be happy to know what is the underlying cause of this

[xycross]

The device is HP Victus 16 R0777TX

[CZFF]

Hello there,

thanks to you SensorM for all your detailed information already.

At our company we also have the exact similar behaviour in countless systems (talking about 200+) which were delievered over the last few years. It all started with the Windows Update KB5074109.

We recently found that for older systems the Intel Driver v31.0.101.3302 is stable. Nevertheless this is not a permanent solution since from Windows updates there is automatically installed a newer version (which we would block for now). 

I want to bump this topic and get an reaction from Intel about this topic.

Also please don´t ask again for minidumps, system reports. Those are exactly similar to the one SensorM was providing already. We investigated and compared it already with several developers.

Thank you and hopeing to get an answer/update from Intel side.

CZFF 

[Blackwaters]

Also having this issue on 3 ThinkCentre M70s Gen 3. All 3 having reboots related to 

FAILURE_BUCKET_ID:  0x139_3_CORRUPT_LIST_ENTRY_dxgmms2!

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.26100.7920

 Have also tried different newer and older intel drivers, shutting off hardware acceleration, uninstalling windows updates, etc etc. Nothing has worked so far.

[Tharun_Intel]

Hello SensorM,

I hope you are doing well.

Thank you for reaching out to us and for your patience while we work on your case.

We wanted to follow up as we are currently in the process of replicating the issue you have reported. We kindly ask you to refer to the private email we had previously sent you, which contains further details regarding this request.

Exact Application/Software Version – The version of the application or software in use when the issue occurred.

Step-by-Step Reproduction Steps (with Video) – A detailed walkthrough of the steps that lead to the issue, along with a screen recording if possible.

Crash Dump Files – Any crash or error dump files generated at the time of the issue.

System Settings Screenshots – Screenshots of the relevant system configuration or settings.

Sample/Test Data – Any sample or test data that may be used to reproduce the issue on our end.

Once we receive the above details, we will be able to move forward promptly and keep you updated on our progress.

Please do not hesitate to reach out if you have any questions or need assistance in gathering this information — we are happy to help.

Tharun

Intel Customer Support Technician.

[Resolutions404]

Hi @SensorM ,

I’ve been tracking the reports regarding the KERNEL_SECURITY_CHECK_FAILURE (0x139) affecting the Intel UHD 770 on recent Windows 11 builds (24H2/25H2). Looking at the stack traces provided, this isn't a standard "corrupt install" issue; it appears to be a LIST_ENTRY corruption within the Kernel-Mode Driver (igdkmdn64.sys) when interacting with the DirectX Graphics Kernel (dxgkrnl.sys).

Since standard DDU wipes and IPDT tests aren't providing permanent relief for enterprise fleets, here is a technical approach to stabilize these units while we wait for a microcode or driver branch update:

• Disable Hardware-Accelerated GPU Scheduling (HAGS): This is the most likely culprit for 0x139 race conditions.

  • Path: Settings > System > Display > Graphics > Change default graphics settings.

  • Why: Turning this OFF forces Windows to handle the memory buffer scheduling instead of the Intel driver, bypassing the specific code path that is likely tripping the security check.

• Check for Conflicts with "Memory Integrity" (HVCI): * Go to Windows Security > Device Security > Core Isolation. If "Memory Integrity" is ON, try toggling it OFF on one of the failing test units. The 0x139 error is a security check; HVCI adds a layer of virtualization that often clashes with Intel's kernel-mode memory addresses during high-frequency interrupts.

• Power Management Regression: * In Power Options, set the "PCI Express Link State Power Management" to Off. Sometimes the driver crashes during a "D3" power state transition when the GPU tries to wake up to handle a kernel request.

• Wait for the "BETA" Branch: * Historically, the Intel Graphics Beta Drivers (look for the .7000+ branch) often contain the specific "KMD" stability fixes before they hit the WHQL (General Release) branch.

To the Intel Team Moderator @Mahammad_Intel @Nikhil_Intel  : Can we confirm if Engineering is looking at potential TLB (Translation Lookaside Buffer) issues or race conditions specifically related to the 13th Gen's efficiency-core scheduling on these newer Windows 11 kernels? I mean just a suggestion or you could say I am just curious about it.

[iridevtwins]

Hi @SensorM 

I reported a similar issue on 3-25 in this thread:  Re:Intel UHD Graphics 770 with BSOD Bug Check 139 with Drivers Version beyond 31.0.101.4255 in Win11 - Intel Community.  As a workaround, try downgrading or rolling back to driver version 31.0.101.4255 or older.  This is our standing workaround.  Intel had me work with Lenovo and closed my case, but no one's been able to identify the root cause yet.  Good luck.

[basti01985]

Thanks for this.

We have downgraded the driver of the Intel UHD 770 to the version 31.0.101.3302

With this we have had no crash in the last 4 days, it seems to work.

[Mahammad_Intel]

Hello SensorM,

Thank you for your continued patience as we work to resolve your issue.

We've sent a detailed email requesting additional information that will help our technical team better understand the problem you're experiencing. Could you please check your registered email inbox and provide the requested details at your earliest convenience?

Once we receive this information, we'll be able to expedite our investigation and work toward a swift resolution.

We appreciate your cooperation and look forward to your response.

Best regards,

Mahammad

Intel Customer Support Technician

[SensorM]

Hello Mahammad,

Thank you for the follow-up.

Apologies for the delayed reply. I have been travelling recently, including to install NVIDIA cards on multiple affected systems, since at the moment that seems to be the only practical workaround we have found.

I have now replied by email with the requested details.

I must say, though, that much of this information had already been shared earlier, both here in the thread and in the email case.

In any case, I have resent the requested details privately so the investigation can move forward.

At this stage, what we really need is progress toward root cause analysis and a real fix, as the issue is still affecting a significant number of production systems, albeit less so on systems where we have installed NVIDIA cards.

Best regards,
SensorM

[Tharun_Intel]

Hello Sensor M,

I hope this message finds you well.

We wanted to let you know that we have sent you a private email regarding your query, and we are currently awaiting your response to move forward.

If you haven't received it, we kindly ask that you check your spam or junk folder as well.

Please don't hesitate to reach out if you need any assistance.

Thank you for your support and co-operation.

Tharun

Intel Customer Support Technician.

[basti01985]

Good Morning,

is it possible to give us others also an update regarding this matter/issue?

There are some insights that are known meanwhile:

- UHD 770: downgrading the driver version to "v31.0.101.3302" works for us

- Intel N97 pcs: disabling "RC6 Render Standby" in BIOS works as for us 

Did this help on your end to narrow the issue down?

Do you have any updates if you have found the reason for the black screen to happen?

Is there perhaps already any ETA for a possible fix for this?

[NeBula_1]

How were you able to obtain the older version for the UHD 770, i have tried to look for older version on the intel download page and im able to find it

[iridevtwins]

Hi NeBula_1,

For us, we had systems that still ran a working older driver (31.0.101.4255), so we were able to retrieve the driver from its DriverStore\FileRepository and install it on the crashing ones.