Crash on dual-GPU laptops with NVIDIA GPU (cannot reach WPF Loaded event)

[Intsuho]

Hi, I'm encountering a crash when running the application on a dual-GPU laptop. Here are the system details:

• CPU: Intel Core7 240H

• Integrated GPU driver version: 32.0.101.5972 (Released: 2024-08-19)

• Discrete GPU: NVIDIA (Optimus enabled)

Issue Description:
When the application is launched using the integrated GPU, it crashes very early—before even reaching the WPF Loaded event. The crash stack includes the following key point:

Workarounds That Helped:

• Updating the Intel GPU driver to version 32.0.101.5972 resolved the issue.

• Forcing the app to launch with the discrete NVIDIA GPU via the NVIDIA Control Panel (Optimus settings) also resolved the problem.

Questions:

From the behavior, it seems the app launches using the integrated GPU, but the crash occurs in DXRegisterObjectNV, which appears related to the NVIDIA GPU. Why would launching with the iGPU trigger an NVIDIA-related error?

Is there any recommended way to force the app to always launch with the discrete GPU? (e.g., via code, configuration, or manifest)

Thanks for your work, and I appreciate any insights you can provide!

[NogginBops]

wglDXRegisterObjectNV is actually not an Nvidia specific function, it comes from the NV_DX_interop extension that Nvidia, AMD, and intel drivers all support. The NV prefix is because Nvidia wrote the extension specification.

I think this issue is likely closely related to #149 which was fixed with an intel driver update as you said.

On the topic of preferring discrete GPUs, there are a few options. You can select your preferred gpu in the windows settings, but I do not know a programmatic way of enabling this but there might be a way. Could be worth looking into.

There is the NvOptimusEnablement dll export that you can export like this:
https://gist.github.com/deccer/0c605e015da653a12090e0b386eeb09b
https://gist.github.com/deccer/306712187936efcd378188929729b2e2
There is an equivalent AMD flag that can be exported aswell. But this requires a dll rewrite step that complicates build systems.

[Intsuho]

@NogginBops Thanks for the suggestion! I'll give it a try.