WPF 3D App crashes without exception on Intel UHD770

[ToxicToxine]

• .NET Core Version: 6
• Windows version: 21H2 (Build 22000.556)
• Does the bug reproduce also in WPF for .NET Framework 4.8?: Yes

Problem description:
I created a simple Testapplication using WPF 3D Media. It only Contains a Viewport3D and a simple MeshGeometry.
Evertime i execute this on my Machine (Intel I9-12900K and Intel UHD770) the program crashes without any Exception or error in the Output.

Actual behavior:
Only Crashes, no Exceptions etc.
Expected behavior:
Rendering of Window with Geometry
Minimal repro:
Win11TestApp3d.zip

[lindexi]

@ToxicToxine Could you use ProcDump tool to collect the dump file of your process when it crashes

[AsgardXIV]

Also encountering the same issue (or similar issue) and have several users reporting it as well.

I reported to Intel and have a support ticket open with them, but not making a lot of progress. Intel Community Link.

I'm fairly certain it's a driver issue, as there was an issue with WPF apps on 11th gen Intel as well, though this one seems to effect 12th gen. Not clear to me if this issue is a regression for 12th gen, if the above fix wasn't enough or it's a totally new issue.

It seems pretty nasty overall, as 12th gen becomes more common in the wild it seems like a lot more people will run into this.

The most I can see is:

UCEERR_RENDERTHREADFAILURE (0x88980406)
System.Runtime.InteropServices.COMException (0x88980406): UCEERR_RENDERTHREADFAILURE (0x88980406)
   at System.Windows.Media.Composition.DUCE.Channel.SyncFlush()
   at System.Windows.Interop.HwndTarget.UpdateWindowSettings(Boolean enableRenderTarget, Nullable`1 channelSet)
   at System.Windows.Interop.HwndTarget.UpdateWindowPos(IntPtr lParam)
   at System.Windows.Interop.HwndTarget.HandleMessage(WindowMessage msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

If I run ProcDump, I don't actually get a dump, just get

[13:53:58] Exception: E06D7363.?AV_com_error@@
[13:54:08] Exception: E0434352.CLR
[13:54:08] Exception: E0434352.CLR
[13:54:08] Exception: E0434352.CLR
[13:54:08] Exception: E0434352.CLR
[13:54:08] Exception: C00000FD.STACK_OVERFLOW
[13:54:08] The process has exited.
[13:54:08] Dump count not reached.

My setup is slightly different as I have a discrete 3090 as well, so the monitor the app runs on is important.

I've attached 3 videos using a demo app. The configuration is that the monitor on the left is using my NVidia Discrete GPU and the monitor on the right is using Intel Integrated. This covers the 3 different behaviors I see, and which one I get appears to be random.

1. The application just crashes as soon as it's moved to the integrated monitor (this happens 100% of the time if ran from Visual Studio) Here .
2. The application doesn't crash but the performance rendering a simple cube visibly impacts the window redraw speed. Here.
3. When launched directly on the intel graphics it renders nothing for a while with terrible performance, then it finally appears and the performance remains low. Here.

[lindexi]

@AsgardXIV Could you see #3817 ?

[AsgardXIV]

I'm currently running 30.0.101.1631 (latest for 12th gen as of today) and the issue does occur there.
I did try with previous versions last week, and as far as I have been able to test, there is no driver where this works on 12th gen.

It DOES work if I set RenderOptions.ProcessRenderMode = System.Windows.Interop.RenderMode.SoftwareOnly but then obviously performance is terrible for 3d. Definitely seems like a driver issue.

[AsgardXIV]

The behavior has changed for me with either a Windows Update or an Intel Driver update. Not sure exactly when it changed, and both had updates.

It no longer crashes but the rendering is corrupt/incorrect when connected to a monitor on the Intel graphics.

In the attached videos:
Video 1: Launched on the Intel connected monitor, immediately corrupt.
Video 2: Launched on the NVidia connected monitor and it's correct, the moment it touches the intel connect monitor it corrupts.

Versions
Intel Driver: 30.0.101.1660
Windows 11: Version 10.0.22000 Build 22000
DotNet: 5.0.15
NVidia Driver: 30.0.15.1215

[ToxicToxine]

@AsgardXIV we, in the comapany i work for, have exactly the same result.
The new part is this Exception thrown, when changing Monitors.

[AsgardXIV]

I got a response from Intel to say they reproduced the issue and that it's fixed in an internal driver build. No timeline on a release yet.