topic Re: Recurring KERNEL_SECURITY_CHECK_FAILURE (0x139) on Intel UHD Graphics 770 in Graphics

Recurring KERNEL_SECURITY_CHECK_FAILURE (0x139) on Intel UHD Graphics 770

SensorM — Sat, 14 Mar 2026 10:12:37 GMT

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.

Re:Recurring KERNEL_SECURITY_CHECK_FAILURE (0x139) on Intel UHD Graphics 770

Mahammad_Intel — Mon, 16 Mar 2026 13:21:36 GMT

Hello SensorM,

Thank you for posting on the Intel Community Forum.

To further assist you, could you please provide more details about the issue you are experiencing? Understanding the specifics will help us support you more effectively.

Please kindly provide the following information:

IPDT Result

Could you please share the IPDT result? (Please refer to the below IPDT tool.)

https://www.intel.com/content/www/us/en/download/15951/intel-processor-diagnostic-tool.html

Mini Dump / Crash Dump Files

Could you please share your mini dump or crash dump files related to the issue?

Update or Reinstall Intel Graphics Driver

please perform a clean installation using DDU. Refer to the article below for guidance. Once you have uninstalled the graphics drivers, please proceed to install the new drivers.

Please refer the below article:

https://www.intel.com/content/www/us/en/support/articles/000091878/graphics.html

Kindly note that we have requested additional details via email to further investigate the issue. Please check the inbox of your registered email address and revert at your earliest convenience.

Thank you for your cooperation. Please feel free to reach out if you need any assistance with these steps.

Best regards,

Mahammad

Intel Customer Support Technician

Re: Recurring KERNEL_SECURITY_CHECK_FAILURE (0x139) on Intel UHD Graphics 770

SensorM — Mon, 16 Mar 2026 21:35:07 GMT

Hello Mahammad,
Thank you for your assistance. I have gathered all the requested diagnostic data.
I have attached a ZIP file containing the following documents:
- Intel SSU Log: intel_snapshot.txt (System Support Utility results).
- IPDT Result: test_intel_processor_diagnostic.txt (Intel Processor Diagnostic Tool results, which passed).
- Mini Dump File: 031626-11500-01.dmp (The crash dump generated during the KERNEL_SECURITY_CHECK_FAILURE).
- Windows Event Logs: application_event.evtx, security_events.evtx, and dump_system_events.evtx (Application, Security, and System event logs from around the time of the crash).
Please let me know if you need any further information to investigate the issue.
Looking forward to your analysis.
Best regards,
SensorM

Re: Recurring KERNEL_SECURITY_CHECK_FAILURE (0x139) on Intel UHD Graphics 770

SensorM — Tue, 17 Mar 2026 08:46:06 GMT

Sorry, I sent you an empty dump. Here, there is the right one.

Best regards,
SensorM

Re: Recurring KERNEL_SECURITY_CHECK_FAILURE (0x139) on Intel UHD Graphics 770

SensorM — Wed, 18 Mar 2026 08:27:41 GMT

Hello,

I would like to provide an update on this issue.

Unfortunately, the situation is getting worse. We are seeing the problem more frequently, and the impact on system stability and usability is increasing.

To help with the analysis, I am attaching information from another kit that is showing the same behavior. The attached material includes the additional data/logs/details collected from this unit, which may help you compare the cases and better identify the root cause.

At this stage, the issue is no longer isolated and appears to be reproducible across multiple kits, which increases our concern.

Please review the newly attached information and let us know your assessment. If useful, we can also provide further details or perform additional tests on our side.

Best regards,
Salvatore - SensorM

Re: Recurring KERNEL_SECURITY_CHECK_FAILURE (0x139) on Intel UHD Graphics 770

Mahammad_Intel — Thu, 19 Mar 2026 11:41:16 GMT

Hello SensorM,

Thank you for posting on the Intel Community Forum.

Thank you for providing detailed information about the issue and the troubleshooting steps you have already performed. We understand the impact this is having on your production environment and appreciate your efforts in isolating the problem.

Based on our review, we noticed that the system is currently using an older graphics driver version, which could be contributing to the issue. We recommend trying the following steps:

Update the Graphics Driver

Please install the latest available driver for Intel UHD Graphics 770 from the Intel website and restart the system after installation.

Kindly refer to the below link to download and install the latest graphics driver:

https://www.intel.com/content/www/us/en/download/864990/intel-11th-14th-gen-processor-graphics-wind…

Disable Hardware Acceleration

In applications such as Chrome or Edge, navigate to Settings → System and turn OFF “Use hardware acceleration when available.” This has been known to help in similar scenarios.

Disable Hyper-V (if enabled)
- Open Command Prompt as Administrator
- Run the following command:

bcdedit /set hypervisorlaunchtype off

Restart the system

Perform a Clean Driver Reinstallation (if issue persists)

Use Display Driver Uninstaller (DDU) to completely remove the current graphics driver, and then reinstall the latest Intel graphics driver.

Kindly refer to the article below for guidance:

https://www.intel.com/content/www/us/en/support/articles/000091878/graphics.html

Check Recent Windows Updates

If the issue started after recent updates, you may test by uninstalling the latest Windows update from Settings → Windows Update → Update History (if feasible in your environment).

Additionally, please note that your system is an HP OEM platform. In such cases, OEM-customized drivers may sometimes differ from Intel generic drivers. If the issue persists with the latest Intel driver, we recommend testing with the graphics driver provided by HP for your specific system model.

If the issue continues after performing the above steps, please feel free to share minidumps and system reports, and we will be glad to assist you further.

Thank you for your patience and cooperation.

Best regards,

Mahammad

Intel Customer Support Technician

Re: Recurring KERNEL_SECURITY_CHECK_FAILURE (0x139) on Intel UHD Graphics 770

SensorM — Fri, 20 Mar 2026 23:25:26 GMT

Hello Mahammad,

Thank you for the follow-up.

I reviewed the issue again using the same criteria across multiple affected systems, and the deeper analysis points to a more stable pattern than just a generic graphics BSOD.

The stable recurring signature is:

- Stop code: `KERNEL_SECURITY_CHECK_FAILURE (0x139)`

- Parameter 1: always `0x3`

- Meaning of Parameter 1: `LIST_ENTRY` corruption / double remove

- Consistent process in analyzed dumps: `System`

- Recurrent WinDbg symbol: `dxgmms2!CVirtualAddressAllocator::RemoveVaRangeFromVad+201`

- Recurrent module/image: `dxgmms2.sys`

- Recurrent failure bucket: `0x139_3_CORRUPT_LIST_ENTRY_dxgmms2!CVirtualAddressAllocator::RemoveVaRangeFromVad`

So, after reviewing the available dumps, the most stable result is specifically `0x139 / Param1=3 / dxgmms2 virtual address allocator list corruption`.

I reorganized the affected systems into simple A/B-style test sets:

- Set A:

HP Pro SFF 400 G9, `i5-13500`, non-clean-install, Windows 11 25H2 build `26200.8037`, last KB `KB5079473` on March 11, 2026, Intel graphics driver `32.0.101.7077`.

Result: `15` unique `0x139` WER bugcheck events from March 12 to March 18, 2026. The analyzed dump matches the same `dxgmms2` bucket listed above.

- Set B:

Same physical machine as Set A, same general image state, Windows still at `26200.8037` / `KB5079473`, but Intel graphics driver changed to `32.0.101.7085`.

Result: the same `0x139` bugcheck still occurs after the driver change. I can confirm new crashes on March 19, 2026 at `11:42`, `11:46`, `15:17`, and `17:04`, while the system was already reporting driver `7085`.

- Set C:

HP Pro SFF 400 G9, `i5-14500`, non-clean-install, Windows 11 25H2 build `26200.7922`, last KB `KB5077241` on March 9, 2026, Intel graphics driver `32.0.101.7084`.

Result: `3` unique `0x139` bugchecks from March 16 to March 18, 2026. The analyzed dump matches the same `dxgmms2` bucket.

- Set 😧

HP Pro SFF 400 G9, `i5-14500`, clean install, Windows 11 25H2 build `26200.7922`, last KB `KB5077241` on March 9, 2026, Intel graphics driver `32.0.101.7084`.

Result: `3` unique `0x139` bugchecks from March 17 to March 18, 2026. The analyzed dump matches the same `dxgmms2` bucket.

- Set E:

HP Pro SFF 400 G9, `i5-14500`, second clean-install validation set, Windows 11 25H2 build `26200.7922`, last KB `KB5077241` on March 9, 2026, Intel graphics driver `32.0.101.7084`.

Result: `2` unique `0x139` bugchecks on March 17, 2026. The analyzed dump matches the same `dxgmms2` bucket.

- Set F:

HP Pro SFF 400 G9, `i5-14500`, non-clean-install, minidump-focused set, Windows 11 25H2 build `26200.7922`, last KB `KB5077241` on March 9, 2026, Intel graphics driver `32.0.101.7084`.

Result: `3` unique `0x139` bugchecks from March 17 to March 19, 2026. This set is minidump/WER-based, but it still shows the same `0x139` / first-parameter `0x3` pattern.

What changes between these sets but does not remove the issue:

- clean install vs non-clean-install

- Intel graphics driver `32.0.101.7077` vs `32.0.101.7084` vs `32.0.101.7085`

- Windows 11 25H2 build `26200.7922` vs `26200.8037`

- `i5-13500` vs `i5-14500`

- full/kernel dump cases vs minidump/WER-only cases

What stays constant across the affected sets:

- same platform family: `HP Pro SFF 400 G9 Desktop PC`

- same iGPU family: `Intel UHD Graphics 770`

- same BIOS family/version: `HP U03 Ver. 02.20.00`

- `Intel UHD Graphics 770` status is reported as `OK` in the system reports on all affected sets

- Intel Processor Diagnostic Tool returns `Pass` on the tested systems

- `dxgmms2.sys` and `dxgkrnl.sys` are both reported as version `10.0.26100.7920`

This point is especially important from the Intel side:

- on the same physical machine, the issue existed with Intel graphics driver `32.0.101.7077`

- after changing that same machine to Intel graphics driver `32.0.101.7085`, the same `0x139` bugcheck still continued

So at this stage, the problem does not appear to be resolved simply by moving from `7077` or `7084` to `7085`.

My current interpretation from the A/B comparison is:

- This does not look like a single corrupted installation

- This does not look limited to one Intel driver version

- This does not look isolated to one CPU stepping

- the most stable common denominator is the `dxgmms2` list-corruption signature itself, on the same HP / Intel UHD 770 platform family

Additional observations:

- Some affected systems show VBS / Hyper-V-related boot entries and components, but I am not treating that as a proven root cause because the same `0x139 / Param1=3` pattern also appears across the other affected sets

- The adapter reports `OK`, and IPDT is `Pass`, so the current evidence does not point to a simple device-detection or basic hardware-failure scenario

Mitigations already tested on our side, without resolving the issue:

- clean OS install on affected validation sets

- clean graphics driver reinstallation

- changing Intel graphics driver versions across `32.0.101.7077`, `32.0.101.7084`, and `32.0.101.7085`

- testing both Intel generic and HP OEM graphics driver paths

- disabling hardware acceleration in the affected application path

- disabling Hyper-V / VBS for validation purposes

- checking the timing against recent Windows servicing changes and validating both March 9, 2026 and March 11, 2026 servicing states

Unfortunately, none of these mitigations removed the recurring BSOD pattern.

To support the investigation, I can attach the following items from multiple affected systems:

- Intel SSU logs

- IPDT results

- system reports

- WinDbg text analysis

- Windows event logs

- minidumps were available

The full `MEMORY.DMP` files are also available, but some of them are too large for a standard forum attachment. If Intel needs the full dump set, I can provide it through an alternate upload method.

Given this matrix, I would like to avoid repeating the same validation cycle again and instead understand the next Intel-side diagnostic step.

Could you please clarify:

1. Does Intel recognise this specific `0x139 / Arg1=3 / dxgmms2!CVirtualAddressAllocator::RemoveVaRangeFromVad` pattern on Intel UHD Graphics 770?

2. Since the same issue is still present on `32.0.101.7085`, what exact next Intel graphics package or debug path do you want us to validate?

3. For this HP OEM platform, do you want us to prioritise a specific Intel generic package, a specific HP OEM package, or a known stable driver branch?

4. If Intel wants deeper escalation, which additional artefacts are most useful beyond SSU, IPDT, event logs, minidumps, and WinDbg text output?

This issue is affecting multiple production medical systems, and is getting worse every day, so if Intel has a known stable baseline, mitigation path, or escalation procedure for this pattern, that information would be very important for us.

Best regards,

Salvatore

Re: Recurring KERNEL_SECURITY_CHECK_FAILURE (0x139) on Intel UHD Graphics 770

SensorM — Fri, 20 Mar 2026 23:52:22 GMT

Here there are some logs.

Re:Recurring KERNEL_SECURITY_CHECK_FAILURE (0x139) on Intel UHD Graphics 770

Mahammad_Intel — Tue, 24 Mar 2026 11:30:12 GMT

Hello SensorM,

Thank you for posting on the Intel Community Forum.

Thank you for sharing the test details with us.

Could you please provide the replication steps — the process you followed to identify the issue? This information will help us troubleshoot the problem more effectively.

We appreciate your cooperation and look forward to your reply.

Best regards,

Mahammad

Intel Customer Support Technician

Re: Recurring KERNEL_SECURITY_CHECK_FAILURE (0x139) on Intel UHD Graphics 770

SensorM — Wed, 25 Mar 2026 14:45:33 GMT

Hello Mahammad,

Thank you for your reply and for your continued support.

Regarding the replication steps, unfortunately, there is no precise user action sequence that triggers the crash. The issue can be reproduced simply by leaving our software open in the 3D view, even while the system is idle and no user interaction is performed.

What we can add, however, is an important technical detail regarding the application path involved:

- the issue appears after our software is using its 3D rendering path, also in different pages;
- our software uses HelixToolkit;
- we have observed the issue with both rendering paths we use internally: the WPF engine and the SharpDX engine.

So, from our side, the recurring factor is not a specific UI action, but the use of the 3D graphics path on affected systems running on Intel integrated graphics, specifically Intel UHD 770.

At the moment, we have identified only two practical mitigations in the field:

1. Moving the rendering workload away from the Intel integrated GPU by installing and using an NVIDIA discrete graphics card.

2. Keeping the system on a very specific combination of Windows build, update level, and Intel graphics driver version, namely:

- OS: Microsoft Windows 11 Pro
- Build: 26100 (UBR 3323)
- DisplayVersion: 24H2
- GPU driver: Intel Corporation 32.0.101.5973
- KB5045934 @ 2025-12-26

However, this second mitigation is not a practical long-term solution for us, because in real deployments it effectively forces us to reformat affected PCs in order to return them to that exact software combination.

At present, we still have approximately 50 PCs that are not operational because of this issue, so the impact remains significant for us.

For completeness, we would also like to point out that this does not appear to be an isolated software-only symptom. We found several publicly documented reports on Intel Community, GitHub, and other public development channels describing very similar WPF / Viewport3D / HelixToolkit behavior on Intel integrated graphics.

What is particularly concerning is that, among the public references most closely matching our scenario, we have not found a confirmed root-cause fix that applies to our case. Most of them point only to mitigations or workarounds, such as disabling hardware acceleration, forcing the application onto a discrete GPU, or avoiding the Intel integrated graphics path entirely. We have already tried every practical path currently available to us, including the recommended troubleshooting and mitigation steps, but so far none has produced a genuine fix.

Relevant references:
- Intel Community: Crash with UHD 770 in WPF applications using Viewport3D
- Intel Community: Graphics failure with WPF 3D content and Iris XE
- dotnet/wpf issue #6312: WPF 3D App crashes without exception on Intel UHD770
- dotnet/wpf issue #7076: Rendering issue with WPF 3D content on Intel Iris XE
- microsoft/D3D9On12 issue #52: WPF 3D content not working on Intel Iris XE
- imchillin/Anamnesis issue #888: Crash or Visual Corruption when running on 12th Gen Intel Graphics

To help your investigation more efficiently, we already have a test system available where the issue is present and ready for analysis. RustDesk is installed and enabled. If you would like to access it remotely, please let us know and we will provide the credentials privately.

If useful, we can also provide a short video showing that the system crashes while the software is simply left idle in the 3D view.

I will allow myself one final personal note: I truly hope Intel is taking cases like this seriously, because at this rate, this issue is becoming not only a technical problem, but a very real business and professional problem for us.

We look forward to your feedback.

Best regards,
Salvatore
SensorM

Re:Recurring KERNEL_SECURITY_CHECK_FAILURE (0x139) on Intel UHD Graphics 770

Nikhil_Intel — Sat, 28 Mar 2026 15:23:41 GMT

Hello SensorM,

Thank you for posting on the Intel Community Forum.

Thank you for sharing the detailed analysis and additional data. I understand the impact this issue is having on your environment.

I would like to inform you that we are currently reviewing the information provided and actively investigating the issue.

We will get back to you shortly with further update.

Thank you for your patience and cooperation.

Re: Recurring KERNEL_SECURITY_CHECK_FAILURE (0x139) on Intel UHD Graphics 770

ChristianG — Tue, 31 Mar 2026 07:04:54 GMT

Hi!

Thank you SensorM the detailed troubleshooting and documentation.

We are experiencing the same issues across multiple devices (20 and counting) where we've narrowed it down to the same root cause - during 3d-visualization.

We've tried the all the mitigations listed and still experience the crashes.

Hardware where crashes occur:

HP Pro Mini 260 G9

Lenovo Thinkcentre M70q Gen 5

Lenovo Thinkcentre M70q Gen 3

HP Pro Mini 400 G9

HP EliteBook 640 G10

OS:

Windows 11 Pro 25H2

BIOS: Updated without success, seeing crashes across multiple versions.

Drivers where crashes occur:

Intel UHD Graphics 770 (v32.0.101.5973, v32.0.101.7085)

Intel UHD Graphics 730 (v31.0.101.5590, v32.0.101.7026)

Intel UHD Graphics (v32.0.101.6881, v32.0.101.7077)

Intel Iris Xe Graphics (v31.0.101.3358, v32.0.101.6651)

Intel Graphics (v32.0.101.6651, v32.0.101.6737)

Drivers without crashes:

Microsoft Basic Display Adapter (comes with limited functionality, not good enough as a workaround)

AMD Radeon Graphics

Error code:

KERNEL_SECURITY_CHECK_FAILURE (0x139) dxgmms2.sys
Failure bucket:
0x139_3_CORRUPT_LIST_ENTRY_dxgmms2!CVirtualAddressAllocator
Stack trace:
dxgmms2!VidMmWorkerThreadProc → ProcessDeferredCommand → CVirtualAddressAllocator

Correlation:

Seeing the same correlations where the issue occurs after updating Windows, first errors came with the release of KB5077181 and remains after KB5079473. KB5077181 also included an explicit fix for dxgmms2.sys.

Other actions tested:

DWM registry tuning - No change

VBS and HVCI adjustments - No change

Vulkan based Direct3D - Runs without crashes, but a minor loss in perfomance

Re: Recurring KERNEL_SECURITY_CHECK_FAILURE (0x139) on Intel UHD Graphics 770

ChristianG — Tue, 31 Mar 2026 09:00:29 GMT

Hi!

Thank you SensorM the detailed troubleshooting and documentation.

We are experiencing the same issues across multiple devices (20 and counting) where we've narrowed it down to the same root cause - during 3d-visualization.

We've tried the all the mitigations listed and still experience the crashes.

Hardware where crashes occur:

HP Pro Mini 260 G9

Lenovo Thinkcentre M70q Gen 5

Lenovo Thinkcentre M70q Gen 3

HP Pro Mini 400 G9

HP EliteBook 640 G10

OS:

Windows 11 Pro 25H2

BIOS: Updated without success, seeing crashes across multiple versions.

Drivers where crashes occur:

Intel UHD Graphics 770 (v32.0.101.5973, v32.0.101.7085)

Intel UHD Graphics 730 (v31.0.101.5590, v32.0.101.7026)

Intel UHD Graphics (v32.0.101.6881, v32.0.101.7077)

Intel Iris Xe Graphics (v31.0.101.3358, v32.0.101.6651)

Intel Graphics (v32.0.101.6651, v32.0.101.6737)

Drivers without crashes:

Microsoft Basic Display Adapter (comes with limited functionality, not good enough as a workaround)

AMD Radeon Graphics

Error code:

Correlation:

Other actions tested:

DWM registry tuning - No change

VBS and HVCI adjustments - No change

Vulkan based Direct3D - Runs without crashes, but a minor loss in perfomance

Re: Recurring KERNEL_SECURITY_CHECK_FAILURE (0x139) on Intel UHD Graphics 770

ChristianG — Tue, 31 Mar 2026 12:06:56 GMT

Hi!

Thank you SensorM the detailed troubleshooting and documentation.

We are experiencing the same issues across multiple devices (20 and counting) where we've narrowed it down to the same root cause - during 3d-visualization.

We've tried the all the mitigations listed and still experience the crashes.

Hardware where crashes occur:
HP Pro Mini 260 G9
Lenovo Thinkcentre M70q Gen 5
Lenovo Thinkcentre M70q Gen 3
HP Pro Mini 400 G9
HP EliteBook 640 G10

OS:
Windows 11 Pro 25H2

BIOS: Updated without success, seeing crashes across multiple versions.

Drivers where crashes occur:
Intel UHD Graphics 770 (v32.0.101.5973, v32.0.101.7085)
Intel UHD Graphics 730 (v31.0.101.5590, v32.0.101.7026)
Intel UHD Graphics (v32.0.101.6881, v32.0.101.7077)
Intel Iris Xe Graphics (v31.0.101.3358, v32.0.101.6651)
Intel Graphics (v32.0.101.6651, v32.0.101.6737)

Drivers without crashes:
Microsoft Basic Display Adapter (comes with limited functionality, not good enough as a workaround)
AMD Radeon Graphics

Error code:
KERNEL_SECURITY_CHECK_FAILURE (0x139) dxgmms2.sys
Failure bucket:
0x139_3_CORRUPT_LIST_ENTRY_dxgmms2!CVirtualAddressAllocator
Stack trace:
dxgmms2!VidMmWorkerThreadProc → ProcessDeferredCommand → CVirtualAddressAllocator

Correlation:
Seeing the same correlations where the issue occurs after updating Windows, first errors came with the release of KB5077181 and remains after KB5079473. KB5077181 also included an explicit fix for dxgmms2.sys.

Other actions tested:
DWM registry tuning - No change
VBS and HVCI adjustments - No change
Vulkan based Direct3D - Runs without crashes, but a minor loss in perfomance

Re: Recurring KERNEL_SECURITY_CHECK_FAILURE (0x139) on Intel UHD Graphics 770

ChristianG — Tue, 31 Mar 2026 15:14:10 GMT

Re: Recurring KERNEL_SECURITY_CHECK_FAILURE (0x139) on Intel UHD Graphics 770

Grewd — Wed, 01 Apr 2026 08:30:52 GMT

Hi, thank you for raising this SensorM

We are experiencing the same KERNEL_SECURITY_CHECK_FAILURE (0x139) issue as described above and this is impacting us in a very serious way.

Our devices are Panasonic Toughbook 33 mark 4 tablets that are docked and used in Kiosk mode. We believe they only crash in this state as we are unable to replicate with a standard, undocked device.

13th Gen Intel Core i5-1345U
Intel Iris Xe Graphics - Driver Version/s 32.0.101.7085
Windows 11 Enterprise 24H2
Build 26100

If there is anything else I can provide to help support a speedy resolution , please let me know.

Re: Recurring KERNEL_SECURITY_CHECK_FAILURE (0x139) on Intel UHD Graphics 770

SensorM — Wed, 01 Apr 2026 14:37:05 GMT

I sincerely hope Intel can step in with concrete support, because this issue has now placed us in a critical situation.
It is severely affecting our work, and we urgently need a real fix, not just mitigations or temporary workarounds.
So far, none of the workarounds we have tried has proven to be genuinely practical for production use or sustainable as a long-term solution.

Re: Recurring KERNEL_SECURITY_CHECK_FAILURE (0x139) on Intel UHD Graphics 770

SensorM — Wed, 01 Apr 2026 19:04:32 GMT

ChristianG, may I ask whether the 3D engine could be involved in triggering this issue?

Re:Recurring KERNEL_SECURITY_CHECK_FAILURE (0x139) on Intel UHD Graphics 770

Mahammad_Intel — Mon, 06 Apr 2026 13:38:18 GMT

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

Re: Recurring KERNEL_SECURITY_CHECK_FAILURE (0x139) on Intel UHD Graphics 770

Grewd — Tue, 07 Apr 2026 15:15:09 GMT

@Mahammad_Intel
If there is anything I can supply from our estate to help move this forward please let me know?