EXCEPTION_ACCESS_VIOLATION_READ Crashes in igd9trinity32

paul2k25 — Mon, 09 Dec 2024 15:16:30 GMT

We’ve been encountering crashes with some customers using our software. The software is a mixed (native/managed) application with some WPF screens. The issue occurs when users try to open a WPF screen, triggering an EXCEPTION_ACCESS_VIOLATION_READ error in igd9trinity32.dll after a CreateDeviceLHDDI call.

Observed Behavior:

The crashes appear to occur during graphics initialisation in WPF.
All affected systems have Intel integrated graphics, including the following GPUs:
- UHD 730
- UHD 770
- Intel Arc
- Iris® Xe Graphics

Affected Driver Versions:

We’ve confirmed the crash occurs on the following driver versions:

31.0.101.5590
31.0.101.5522
32.0.101.5972
31.0.101.5382
31.0.101.4887
32.0.101.5763
31.0.101.5388

Affected Windows Versions:

Windows 10.0.22631
Windows 10.0.26100
Windows 10.0.19045
Windows 10.0.22621

Stack Trace:

Below is the stack trace for the crash:

OS Version: Windows 10.0.26100 (2454)
Report Version: 104

Crashed Thread: 11544

Application Specific Information:
Fatal Error: EXCEPTION_ACCESS_VIOLATION_READ / 0x0

Thread 11544 Crashed:
0 <unknown> 0x0 <unknown>
1 igd9trinity32.dll 0x4344655f <unknown>
2 igd9trinity32.dll 0x43445c2a <unknown>
3 igd9trinity32.dll 0x433f0298 <unknown>
4 igd9trinity32.dll 0x433f0f37 <unknown>
5 igdumdim32.dll 0x3257aa71 <unknown>
6 igdumdim32.dll 0x32579772 <unknown>
7 d3d9.dll 0x597c3e86 CreateDeviceLHDDI
8 d3d9.dll 0x597c3962 D3D9CreateDirectDrawObject
9 d3d9.dll 0x597c03e5 FetchDirectDrawData
10 d3d9.dll 0x597c758c InternalDirectDrawCreate
11 d3d9.dll 0x597c8807 CEnum::CEnum
12 d3d9.dll 0x597c92e6 Direct3DCreate9Impl
13 d3d9.dll 0x597cab06 Direct3DCreate9Ex
14 wpfgfx_v0400.dll 0x7acacc91 CD3DModuleLoaderInternal::CreateD3DObjects
15 wpfgfx_v0400.dll 0x7acacd29 CD3DModuleLoader::CreateD3DObjects
16 <unknown> 0x9bee74c <unknown>
17 wpfgfx_v0400.dll 0x7acaca21 CDisplayManager::CreateNewDisplaySet
18 wpfgfx_v0400.dll 0x7acacac9 CDisplayManager::DangerousGetLatestDisplaySet
19 wpfgfx_v0400.dll 0x7acacbbe CDisplayManager::DangerousGetLatestDisplaySet
20 wpfgfx_v0400.dll 0x7ac7341c CMILFactory::UpdateDisplayState
21 wpfgfx_v0400.dll 0x7ac734bf CComposition::ProcessComposition
22 wpfgfx_v0400.dll 0x7ac73614 CComposition::Compose
23 wpfgfx_v0400.dll 0x7ac73656 CPartitionThread::RenderPartition
24 wpfgfx_v0400.dll 0x7ac7329e CPartitionThread::Run
25 wpfgfx_v0400.dll 0x7aca541e CPartitionThread::ThreadMain
26 KERNEL32.DLL 0x76d15d48 BaseThreadInitThunk
27 ntdll.dll 0x77bdceba __RtlUserThreadStart
28 ntdll.dll 0x77bdce40 _RtlUserThreadStart

The EIP register is 0x0.

Disabling the Intel graphics driver prevents the crash, but doing so disables external display functionality, which is not a viable workaround for our customers.

Thank you for your assistance. Please let us know if crash dumps or further diagnostic details are needed.

Re: EXCEPTION_ACCESS_VIOLATION_READ Crashes in igd9trinity32

paul2k25 — Wed, 11 Dec 2024 16:40:56 GMT