Gsx ctd

iMT4168 · August 20, 2022, 9:31pm

Ever since I bought GSX on the night of release I haven’t been able to complete a single flight without CTD. It happens during boarding, fueling, pushback, mid-flight, or even during deboarding at the destination. I tried singling it down to only GSX to see if it has anything to do with other mods, so I emptied my community folder and only left GSX Pro and GSX World of Jetways. Still had a CTD.

Here’s the weird thing. When I did the GSX-only test, I got a CTD with no event viewer.
Whenever I try with other mods I either get event viewer or not, I can’t tell what causes this.
Here are the 2 event viewer logs I got (out of at least 5 CTDs):

Log Name: Application Source: Application Error Date: 20.08.2022 23:34:24 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: Falcon Description: Faulting application name: FlightSimulator.exe, version: 1.26.5.0, time stamp: 0x00000000 Faulting module name: d3d11.dll, version: 10.0.19041.1865, time stamp: 0x8ff19571 Exception code: 0xc0000005 Fault offset: 0x000000000012e9a0 Faulting process id: 0x52d8 Faulting application start time: 0x01d8b4bb0519827b Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Faulting module path: C:\Windows\SYSTEM32\d3d11.dll Report Id: 40cc4d1b-d4c0-48fc-9d13-13a94f104113 Faulting package full name: Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2022-08-20T20:34:24.9312608Z" /> <EventRecordID>236497</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>Falcon</Computer> <Security /> </System> <EventData> <Data>FlightSimulator.exe</Data> <Data>1.26.5.0</Data> <Data>00000000</Data> <Data>d3d11.dll</Data> <Data>10.0.19041.1865</Data> <Data>8ff19571</Data> <Data>c0000005</Data> <Data>000000000012e9a0</Data> <Data>52d8</Data> <Data>01d8b4bb0519827b</Data> <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data> <Data>C:\Windows\SYSTEM32\d3d11.dll</Data> <Data>40cc4d1b-d4c0-48fc-9d13-13a94f104113</Data> <Data>Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe</Data> <Data>App</Data> </EventData> </Event>

Log Name: Application Source: Application Error Date: 19.08.2022 23:20:27 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: Falcon Description: Faulting application name: FlightSimulator.exe, version: 1.26.5.0, time stamp: 0x00000000 Faulting module name: FlightSimulator.exe, version: 1.26.5.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x0000000002145a03 Faulting process id: 0x21e8 Faulting application start time: 0x01d8b402c87e413d Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Report Id: 5ee72d39-356d-46bf-be35-a55e5f851cc8 Faulting package full name: Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2022-08-19T20:20:27.9549085Z" /> <EventRecordID>235965</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>Falcon</Computer> <Security /> </System> <EventData> <Data>FlightSimulator.exe</Data> <Data>1.26.5.0</Data> <Data>00000000</Data> <Data>FlightSimulator.exe</Data> <Data>1.26.5.0</Data> <Data>00000000</Data> <Data>c0000005</Data> <Data>0000000002145a03</Data> <Data>21e8</Data> <Data>01d8b402c87e413d</Data> <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data> <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data> <Data>5ee72d39-356d-46bf-be35-a55e5f851cc8</Data> <Data>Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe</Data> <Data>App</Data> </EventData> </Event>

At this point it’s either GSX or MSFS crashing the sim, as I don’t see what else could cause a crash if my community folder is empty except for GSX and no video driver issues were detected (e.g black screen, flicker, all program windows turn black), which is usually the cause of my CTDs.

Xelli7500 · August 21, 2022, 1:24am

GSX is not responsible for crashing the simulator. many people have CTDs right now including myself. This is due to some server problem I think …

TaubeKelch78866 · August 21, 2022, 5:21am

It’s in fact not entirely correct. I have uninstalled GSX and haven’t CTD. The Issue is GSX and not any Server.

BossRaccoon7630 · August 21, 2022, 6:08am

I have GSX and have been flying for over 6 hours now, no CTD. I am on SU10 Beta 5, Steam version and in West Coast USA. I don’t think the issue is from GSX, I think it’s the server issues with MSFS/Asobo but it’s localized so not everyone is experiencing them but a lot of people are.

OnkelpuhGER6895 · August 21, 2022, 6:50am

It has always been the case up to now, when new SUs are pending, the number of CTDs increases and right now it is clear when many changes are pending to improve performance etc. Asobo will again try out changes on the servers which will then be tested by the beta testers

iam2sober · August 21, 2022, 4:15pm

Same problem here CTD with Exception Code: c0000005 in flight

iMT4168 · August 21, 2022, 4:25pm

I have uninstalled GSX and still had a CTD, so for now I am leaning as well to think that it’s actually MSFS causing the crashes. I will try a flight without online services and with GSX installed to see if they are the ones causing issues, and I will keep this topic updated.

iMT4168 · August 22, 2022, 3:03am

Turning online services off didn’t help me, as I got another CTD even with them on. However, after clearing the page file, creating custom page files on my Windows drive and the drive I have MSFS installed on, then clearing them again, fixed my CTDs.

So for a quick tutorial on how I did this:

Clearing page file

Open start menu, search for regedit, open

Find this path: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

Change ClearPageFileAtShutdown’s value to 1

Restart PC (might take longer due to the page file being cleared)

Set the value back to 0

Making custom page file (repeat this on the drive you have Windows installed and MSFS installed)

Open start menu, search for Advanced system settings

Open the View advanced system settings option

Go to Advanced tab, and under performance click on Settings…

Go to Advanced tab in the new window and under Virtual memory click Change…

Uncheck Automatically manage paging file size for all drives

Find the drive you need and enable Custom size

Now here you need to do some calculations. In the Initial size tab you need to enter your memory size in MB multiplied by 1.5. In the Maximum size tab you need to enter your memory size in MB multiplied by 3. In my case I have 16GB of RAM, so I did the following calculations: 16 x 1024 x 1.5 = 24576, which I put in the Initial size tab. Then I calculated 16 x 1024 x 3 = 49152 which I put this in the Maximum size tab.

After this make sure to click on Set (!!!)

Repeat per drives as required

OK out of everything, applying when necessary

Repeat step 1

Hope this helps some other people!!! Enjoy your flights

Edit: spelling
Edit 2: spelling (lol)

BachFrosch85590 · August 22, 2022, 3:59pm

I just tried out what you suggested. No luck here. Ctd when launching the app with memory error message. All weekend’s ctds were midflight.

FiftyEagle07429 · August 22, 2022, 5:33pm

Since some day ago I had repeated CTD during any kind of flight; reaidng the posts above, I understand that may this is caused by the MSFS server under pressure because of Beta tests. Let’s hope this is the reason, since I didn’ t make any single change in my options and settings.

MagicManASK · August 22, 2022, 6:51pm

The page file would have nothing do with this, purely coincidence/placebo.
And please, that 1.5x your installed RAM ‘advice’ dates back 20 years or more.
Set your page file to system managed and forget about it.

mlider3288 · November 5, 2023, 4:42am

Here i have CTD ALL FLIGHTS if gsx is in my community folder, if i dont use it and i remove gsx from community folder i dont have any CTD