P3D v4.4 Crash to Desktop: possibly GSX related

[bradl]

I just read over on the P3D forums about the number of people getting CTDs with P3D v4.4. There are a few threads there in which it is happening at various places, but one in particular is happening on shutdown of P3D. The are saying over there that it is related to using GSX and Windows 7.

I'm using both of those and am getting CTDs after shutting down. I don't know if it truly is relative to GSX (yet; I'm asking over there if they can confirm that), but wanted to know if anyone heard of any problems with v4.4 GSX/GSX2, and CTDs.

If needed, I can add in the crash data.

BL.

[virtuali]

Yes, of course you should add any crash data. Do you use Windows 7 too ?

[bradl]

Yes, of course you should add any crash data. Do you use Windows 7 too ?

Yep! Windows 7 Enterprise Edition. Here are the last few CTDs I have:

Code: [Select]

Faulting application name: Prepar3D.exe, version: 4.4.16.27077, time stamp: 0x5bfdbb35
Faulting module name: KERNELBASE.dll, version: 6.1.7601.24308, time stamp: 0x5be86052
Exception code: 0xc0020001
Fault offset: 0x000000000000bded
Faulting process id: 0x49c0
Faulting application start time: 0x01d49271f4de0bba
Faulting application path: E:\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 082e578f-fe66-11e8-b8cf-902b345eb598

Faulting application name: Prepar3D.exe, version: 4.4.16.27077, time stamp: 0x5bfdbb35
Faulting module name: KERNELBASE.dll, version: 6.1.7601.24291, time stamp: 0x5be785b6
Exception code: 0xc0020001
Fault offset: 0x000000000000bded
Faulting process id: 0x3814
Faulting application start time: 0x01d4911e5b06dd3c
Faulting application path: E:\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 7fea518a-fd12-11e8-a750-902b345eb598

The exception code is always the same from what I see in the event log. If you'd like the XML for this, I can provide it. Apparently over on the P3D forums, they say that FSDT is aware of this, and there is a thread here regarding it.

BL.

[virtuali]

Apparently over on the P3D forums, they say that FSDT is aware of this, and there is a thread here regarding it.

Try to check the "Disable RTT" option in the Addon Manager settings, and restart the sim. Doing this will result losing the Jetway numbers, which use that feature so, it's up to you if you prefer an entirely harmless crash on exit (the simulator has closed correctly), or losing the Jetway numbers.

The problem, of course, it's not a fault of our software, which is a perfectly safe and fully documented way to use the new Render To Texture feature to draw on textures with DX11 at run time (which allows for lots of things not possible before), but it seems that, due to the different behavior of both DirectX itself and drivers, this causes that problem with Windows 7 ONLY.

Since Windows 7 mainstream support ended in 2015, and it will fall back to be entirely unsupported in 2020, we are not going to investigate this further, so we put that workaround in place.

[bradl]

Apparently over on the P3D forums, they say that FSDT is aware of this, and there is a thread here regarding it.

Try to check the "Disable RTT" option in the Addon Manager settings, and restart the sim. Doing this will result losing the Jetway numbers, which use that feature so, it's up to you if you prefer an entirely harmless crash on exit (the simulator has closed correctly), or losing the Jetway numbers.

The problem, of course, it's not a fault of our software, which is a perfectly safe and fully documented way to use the new Render To Texture feature to draw on textures with DX11 at run time (which allows for lots of things not possible before), but it seems that, due to the different behavior of both DirectX itself and drivers, this causes that problem with Windows 7 ONLY.

Since Windows 7 mainstream support ended in 2015, and it will fall back to be entirely unsupported in 2020, we are not going to investigate this further, so we put that workaround in place.

Thanks, Umberto. That actually makes a lot of sense. At this point it isn't a fault of the software on either end, but a problem with the underlying OS. And since W7 is a minimum requirement for P3D v4, and technically it would work, the software requirement for GSX to function properly would be Windows 10. That would be the driving requirement at this point.

I'll report this back to the P3D forums, and then go about the slow upgrade to W10.

Thanks!

BL.

[alphalimaindia]

when updated gsx . after 30 minute crash to windows . i uninstall gsx problem solved . why ?

[virtuali]

when updated gsx . after 30 minute crash to windows . i uninstall gsx problem solved . why ?

It's not possible to help you without more information. What you were doing during those 30 minutes ? Sitting on an airport of flying ?

While flying over 10K feet, for example, GSX is disabled and doesn't do anything, other than checking if you are maybe flying lower than 10K, so it would time to reactivate itself. And even under 10K feet, it won't do much, other than checking which airports are around, in case you'll need to pre-select a gate in flight.

[alphalimaindia]

sorry you right . today another fly and ... crash to desktop without GSX . it seems to another program.