Intel drivers crashing with GSX Pro, a MSFS 2020/2024 add-on

[virtualisoftware]

I'm the developer of that add-on, and I already posted about this in February, but we haven't heard back from anybody from Intel support after this post:

community.intel.com/t5/Developing-Games-on-Intel/GSX-Pro-on-Microsoft-Flight-Simulator-crashing-repeatedly-when-I/m-p/1678737#M2655 

Somebody said since this is a game mod, it should have been redirected here, so let's try again.

I'm one of the developers of the GSX Pro program, please provide me a way to contact somebody at Intel who might be able to help. I'll give your some details about our application:

• It's not a graphic application, it doesn't call into any graphic APIs like Direct/OpenGl, etc.
• It's standard win64 C++ unmanaged app, no .NET
• It's a custom Stackless Python interpreter that interfaces with MSFS 2020 or 2024 only through the standard Simconnect API which is part of the MSFS SDK, no undocumented calls, no direct access to any related to the screen.
• In some parts of the program, we use standard wxPython 4.2 library for the UI, that's the only thing "graphic" we do.
• Some users reported the version before November worked with Intel ARC. Checking our changes, the only change was to rebuild the program using the then current MSFS 2024 SDK, which comes as a C++ Static Library. According to users reports, this is where the 2024 version stopped working, but the MSFS 2020 version was still working, because we didn't updated it back then.
• We released an update in January for both versions, with the only change that can be possibly related to graphic, was to always subscribing to the "VISUAL FRAME" Simconnect event, instead of a mix of both "VISUAL FRAME" and "SIM FRAME" events, because sometimes the "SIM FRAME" event stops working. Both are callbacks in the MSFS Simconnect API, which our app just subscribes to, we don't have any control over what happens inside the sim but, it suggests the problem might be related to the screen refresh event. However, we used it a lot before, the only change we now use it in all places where we previously used "SIM FRAME" instead.
• We tried to replicate the problem with two different PC with both Intel integrated graphics and a discrete graphic as well, by forcing the PC to always use the Intel graphic adapter. MSFS 2020 and 2024 both worked, very slow, and both issued a warning the PC didn't meet the minimum requirements. However, no crashes has been observed, suggesting the problem doesn't happen with the default Intel drivers supplied with Windows, so it might be a problem that only happens when installing dedicated Intel drivers.
• Some users with Hybrid graphic as well, who ended up in a situation where the OS for some reason decided to assign the Intel integrated graphic to our application, reported that setting the name of our .exe in the nVidia app, fixed their issue.
• In the latest version we released today, we added the following exports, to help nVidia or AMD drivers to use the right card:

extern "C" {
// http://developer.download.nvidia.com/devzone/devcenter/gamegraphics/files/OptimusRenderingPolicies.pdf
__declspec(dllexport) DWORD NvOptimusEnablement = 0x00000001;
​
// https://gpuopen.com/learn/amdpowerxpressrequesthighperformance/
__declspec(dllexport) int AmdPowerXpressRequestHighPerformance = 1;

However, this would only help users with a discrete nVidia or AMD card, not those with an Intel ARC as their main card. The crash, as indicated above, happens in this .dll

igd12um64xeh.dll

A couple of users who initially reported this on the other section of the forum "fixed" the problem by simply buying an nVidia or AMD card, but that's clearly not a solution that can work for everybody so, please, if anybody at Intel can provide some hints about what might cause this, considering we don't do any graphic calls or interactions with DirectX (they are not even allowed in MSFS), and searching online for past events related to crashes in igd12um64xeh.dll, it was always fixed by a driver update.

[xaseallo]

Update for this?

[virtualisoftware]

I would also like to get some answers, as I've said, I'm one of the developers of the GSX Pro application, and I posted this in another part of the forum back in February, with no reply, but since somebody suggested to post it in this section, I posted it again in June. Now, a month passed, and still nobody from Intel replied.

I think I have provided all possible information about this, since it's very puzzling that a non-graphic application that just uses the official MSFS SDK, would cause a driver crash, but this is what seems to be happening.

While it seems the official Intel attitude is that, because this is a "game mod", it's doesn't warrant attention, I would like to point out the uniqueness of the MSFS add-on market, which is different than most games. There's an official SDK, and an official Marketplace, and we are Microsoft partners as well, and have been working with them for almost 20 years, and some of these add-ons (ours included) have a larger user base that many stand-alone games, so I suggest to at least try to have a look at this, because the MSFS user community are very good customers compared to your average gamer.

If you need extra information about our app, contact me either by PM or at the email support address for FSDT here:

<removed> 

[xaseallo]

I was able to revert my graphics driver back to 31.0.101.5122 released January 2024 and was able to get GSX working again.

I did attempt to upgrade from there to 32.0.101.6325 which was released December 2024 but the issue returned.

[Kuroedov]

This is happening to me as well. Here are the logs:

OS: Windows 11

CPU: AMD Ryzen 7 5700X

Faulting application name: couatl64_MSFS2024.exe, version: 5.0.0.5984, time stamp: 0x687a8d8d Faulting module name: igd12um64xeh.dll, version: 32.0.101.6972, time stamp: 0x687ab8fc Exception code: 0xc0000409 Fault offset: 0x0000000000f27578 Faulting process id: 0x19C8 Faulting application start time: 0x1DBFF41045391CA Faulting application path: C:\Program Files (x86)\Addon Manager\couatl64\couatl64_MSFS2024.exe Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_204ba96c6f0b3e1c\igd12um64xeh.dll Report Id: 447bed3f-f0fd-478e-9b99-a941c4a96842 Faulting package full name: Faulting package-relative application ID:

We would really like this resolved.