Repeated CTD's 1.18.14.0 & 1.18.15.0

So they broke the game for more than 4000 users (reddit source of people who wrote about ctd) and they can’t play UNTIL SU6?
Asobo is kidding us, probably tomorrow they’ll release a fix or rollback to SU4

1 Like

I cannot comment of the performance issues or any of the parameters after Sim Update 5, as I cannot get past the FLY stage…where it does the CTD evry bloomin time.

So its a total HALT since 28th JULY…when I was thrilled to get the Sim Update loaded!!

I now have an issue (and reported via Zendesk yesterday) where my MSFS is a fresh install, no market place content installed, no community folder content installed.

About 3 out of 5 times I get a CTD when I start a second flight, i.e.

  1. select plane, livery, airport and stand to start cold and dark
  2. start setting up for flight or just have a look with camera/views on plane and scenery…whatever
  3. ESC and back to main menu
  4. repeat step 1 with same or different plane, livery or airport.

On step 4 (after cancelling first flight as per step 4) I now end up with a CTD while the progress bar on the loading screen keeps advancing more often. This hardly ever happened to me prior to SU5 with heaps of community folder and market place content installed.

1 Like

CTD/Views and Group ONLY: This may or may not help some people. I have a mid range system. I have over 960 flight hours and recently with the CTD I have been doing some experimenting. I ALWAYS fly with Live weather and time. I always fly below 180 altitude. I have been avoiding CTDs by flying Group Only (that still gives me Live traffic) but reduces the amount of ATC activity. I always fly VFR AND I reduced (eliminated any views outside the cockpit), and guess what NO CTDs. I am NOT stating that this is a solution but it works for me. I have Rex Global Airport Textures in my Community folder.

I am currently experiencing a CTD at the start of every flight from the World Map. I don’t even get to the click to fly page. Most of my Community folders have been removed. I’m now thinking the new Market Place G1000 package may be at fault.

Uninstalling that will be my next attempt at a fix.

1 Like

Okay! That seemed to be the fix for me. Once I deleted the G1000 NXI, I was able to start a flight without a CTD.

Up to six today alone; decided to make a mark on a paper for each one. Running out of ink. Would not run more than 15 minutes without crashing. No matter where I started. No matter if I had a full flight plan in or just left from a runway with nothing entered in the FMS.

1 Like

Wow, if that’s really the issue, I’ll be amazed.

I haven’t been able to fly since they released SU5 (~ a week ago) FeelsBadMan

Happy flying, good luck, lemme know how it works out!

I’m also one who gets continues CTD. Mostly on short final Approach when I fly online on VATSIM. Here the last one, which I just Encouted.
FlightSimulator.exe
0.0.0.0
00000000
clr.dll
4.8.4390.0
609c45bd
c0000005
0000000000669d70
526c
01d7895f108f919a
C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
912abf30-d150-447c-a14a-43fb45140eda
Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe
App

Before the Update the FS was stable no CTD encounted but no, horrible 10 CTD today…

lg Rainer

2 Likes

I also have deleted the A320Neo upgrade both Marketplace and self install versions. There may be a newer version at FlyByWire, but I seemed to have problems with both sources.

For what it’s worth, given all the variables that may cause CTD, this particular memory settings adjustment solved all my CTD and sim is running much better!
Hope it helps someone!

Sorry to say that @MichaMMA has been our resident expert on
Virtual Memory (Win 10 Paging File").

From: How to change virtual memory size on Windows 10 | Windows Central
"On Windows 10, virtual memory (or paging file) is an essential component (hidden file) designed to remove and temporarily store less frequently use modified pages allocated in RAM (random-access memory) to the hard drive. Using this approach allows the system to prioritize faster physical memory for more frequent processes and applications, improving the overall performance and preventing the device from locking up in the event it runs out of system memory.

In addition, the paging file is important to support crash dumps during a system crash (Blue Screen of Death), as without a large enough page file, a dump with all the contents of the system memory won’t be created.

Although the system does a pretty good job managing the paging file size according to various factors automatically, sometimes, you may still need to increase the default virtual memory values manually."

You should search his Posts to see how this subject has been
a long set of Topics and Posts.

I apologize but we have already been down this discussion path.

I have 64 GB and let Windows 10 do that task for me.

Search @MichaMMA or “paging file or virtual memory” to see his Posts.

Yeah, bloody disgusting, we have to wait weeks to find out IF we can actually use the product we paid for again, and then if that doesn’t work, how long more? I’m so fed up with Asobo, this project should have gone to a different team.

4 Likes

Getting consistent CTD’s either loading into the ‘wrong’ gate at any given large airport, when departing or approaching a large airport.

The departure/approach CTD’s appear to occur ~20NM from the runway. I suspect this is either my photogrammetry LOD range, or somehow ILS info’s bugged out as this is the beginning of ILS range.

1 Like


CTD Update 1

Hey no worries guys, just a couple more weeks until World Update 6!

For a total of about one month of an entirely unplayable simulator!

:frowning:

5 Likes

I never thought about this.

I have never gotten a CTD.

I have never taken off except on the runway via the World Map
or a saved flight plan.

It’s all very vague, but there’s a new bug in the approach phase. In the Airbus the flightplan gets lost as soon as it hits the approach or when you activate it.

It jumps to heading mode and despite still seeing it in the MCDU, you can’t get the airplane to follow it anymore.

Now, unless the FBW Airbus has something new added that I missed, it didn’t used to do that in SU4.

So a crash around that time in the flight would not completely surprise me.

And in the DC-6 similar problems with the approach and the GPS.

Frankly, it takes the fun out of it if you only try to fly airliners. And past year has taught us that those bugs really are on the end of the list at Asobo. IFR never worked. And it only got worse.

1 Like

Just curious as to what can causes this CTD.
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000005d18c9
Faulting process id: 0x3308
Faulting application start time: 0x01d789717fd9263f
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: e1c43aa5-4a9b-4744-b5b2-730e874898df
Faulting package full name: Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe

Using a KVM Switch to watch a larger screen with my
ASUS - ROG Zephyrus M15 15.6" Gaming Laptop - Intel Core i7 - 16GB Memory - NVIDIA GeForce RTX 2070 Max-Q - 1TB SSD - Prism Gray

Just wondering if anyone is seeing an administrative event outside of the above just before the game crashes that says something to the effect of “disk 03 has been removed”? I’ve noticed it occurs right before the CTD and Application Error event occurs.

Now my Micrsoft Store version which I purchased a few days ago. Running fine after installation. Today its CTD!!!

Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001a123c7
Faulting process id: 0x3bfc
Faulting application start time: 0x01d789c4034a16f2
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: f8bc2bde-09df-4207-a053-9f735a67a82f
Faulting package full name: Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Fault bucket , type 0
Event Name: MoAppCrash
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 0.0.0.0
P4: 00000000
P5: FlightSimulator.exe
P6: 0.0.0.0
P7: 00000000
P8: c0000005
P9: 0000000001a123c7
P10:

Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C47.tmp.mdmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1DDE.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1DDF.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1DED.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1E0D.tmp.txt
\?\C:\Users\camov\AppData\Local\Temp\WER1EEB.tmp.appcompat.txt

These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_Microsoft.Flight_2d40d434ed8072c79d1ed17c75ae413c650db6_652e0ba4_cab_4c12615a-f985-4c89-b5a6-df694d46a764

Analysis symbol:
Rechecking for solution: 0
Report Id: f8bc2bde-09df-4207-a053-9f735a67a82f
Report Status: 4
Hashed bucket:
Cab Guid: 0

Fault bucket 1514158318975717276, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 0.0.0.0
P4: 00000000
P5: FlightSimulator.exe
P6: 0.0.0.0
P7: 00000000
P8: c0000005
P9: 0000000001a123c7
P10:

Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C47.tmp.mdmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1DDE.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1DDF.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1DED.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1E0D.tmp.txt
\?\C:\Users\camov\AppData\Local\Temp\WER1EEB.tmp.appcompat.txt

These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Flight_2d40d434ed8072c79d1ed17c75ae413c650db6_652e0ba4_4c12615a-f985-4c89-b5a6-df694d46a764

Analysis symbol:
Rechecking for solution: 0
Report Id: f8bc2bde-09df-4207-a053-9f735a67a82f
Report Status: 268435456
Hashed bucket: 7d2d5d9219c50cd875035ef800400f9c
Cab Guid: 0

Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 141
P2: ffffa6873ae24050
P3: fffff80276ac6958
P4: 0
P5: 3bfc
P6: 10_0_19043
P7: 0_0
P8: 768_1
P9:
P10:

Attached files:
\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20210805-1437.dmp
\?\C:\Windows\TEMP\WER-71506343-0.sysdata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER24C3.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER24D4.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER24D5.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER24F5.tmp.txt

These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_87baea0d67d08383492413451c7d74fec7d421_00000000_cab_759ce5f8-4131-479d-ad71-a79af00697be

Analysis symbol:
Rechecking for solution: 0
Report Id: 759ce5f8-4131-479d-ad71-a79af00697be
Report Status: 4
Hashed bucket:
Cab Guid: 0

Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing_3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 1e2b42df-8078-4cea-be85-ad8daf2ae4dc

Problem signature:
P1: 141
P2: ffffa6873ae24050
P3: fffff80276ac6958
P4: 0
P5: 3bfc
P6: 10_0_19043
P7: 0_0
P8: 768_1
P9:
P10:

Attached files:
\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20210805-1437.dmp
\?\C:\Windows\TEMP\WER-71506343-0.sysdata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER24C3.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER24D4.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER24D5.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER24F5.tmp.txt
\?\C:\Windows\Temp\WER7AD3.tmp.WERDataCollectionStatus.txt

These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_87baea0d67d08383492413451c7d74fec7d421_00000000_cab_759ce5f8-4131-479d-ad71-a79af00697be

Analysis symbol:
Rechecking for solution: 0
Report Id: 759ce5f8-4131-479d-ad71-a79af00697be
Report Status: 268435456
Hashed bucket:
Cab Guid: 0

Edit:
Forgot to mention, no mods in community folder :slight_smile:

1 Like