A reproducible CTD has been introduced with the release of SU16 and the updated NZ POI database. Loading in over the South Island near Christchurch I have a consistent CTD when flying around for less than a minute. Uninstalling the POI eliminates the CTD. Below is a map of the area I load into.
Hi
I cam report the same issue A CTD when flying from or around the top of New Zealand’s south Island. This is with a empty community folder. I can also prevent the CTD by uninstalling the points of interest for world update12 NZ.
Best wishhes.
Bob
Remember to vote the issue as well
@SaffaJake812, I’m having the same problem. I notice the bug template that usually appears by default in this forum is missing, but I’ll try to reproduce it here so all the technical questions required by the mods and devs can be answered.
Description of the issue:
Getting a consistent CTD when starting a flight or shortly into a flight originating from several airports in New Zealand’s South Island with WU12 installed, eg NZTL. This is a new occurrence. I was part of the SU16 beta, and just 5 days ago I flew from NZTL in the 1.39.9.0 beta version without any problems. Trying to do this now in the final SU16 version leads to an almost immediate CTD.
The problem does not occur if the Points of Interest component is selectively removed from the installed WU12 package. The CTD returns if this POI component is reinstalled.
Additionally, the CTD only occurs when using DirectX version DX12. If you switch to DX11 and leave the POI installed, the CTD does not happen.
It happens with both the Nvidia App installed or uninstalled.
In my case, when the CTD occurs, there is a simultaneous “Resource-Exhaustion-Detector” event visible in Event Viewer, even though I can start from an airport on the North Island (eg Wellington) with the same hardware configuration, and look around and fly without any memory exhaustion issues.
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
This indicates a possible memory leak issue in one or more POI elements on the South Island that have been updated or changed after the beta in how they are accessed or rendered while in DX12 mode.
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Source
FlightSimulator.exe
Summary
Stopped working
Date
‎7/‎08/‎2025 6:16 PM
Status
Report sent
Description
Faulting Application Path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.39.9.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Problem signature
Problem Event Name: MoAppCrash
Package Full Name: Microsoft.FlightSimulator_1.39.9.0_x64__8wekyb3d8bbwe
Application Name: praid:App
Application Version: 1.39.9.0
Application Timestamp: 00000000
Fault Module Name: FlightSimulator.exe
Fault Module Version: 1.39.9.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 0000000001e6c1b9
OS Version: 10.0.26100.2.0.0.768.101
Locale ID: 3081
Additional Information 1: 8215
Additional Information 2: 8215bdf875a5b4312e2132802dc72c18
Additional Information 3: f1eb
Additional Information 4: f1eb9ef0894cb3a37650f5d09419a8bf
Extra information about the problem
Bucket ID: b394d8316fee3d5b90dca183f6273b37 (1215023587625745207)
If applicable, which aircraft is experiencing this issue:
Any aircraft
[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
Yes
How often does this occur for you (Example: Just once, every time on sim load, intermittently)? Consistently reproducible by following the same steps
Please list clear steps you took in order to help our test team reproduce the same issue:
What peripherals are you using, if relevant:
Not relevant
[PC Only] Are you using Developer Mode or have you made any changes to it?
No
[PC Only] What GPU (Graphics Card) do you use?
RTX 3060 Ti, Nvidia driver version 576.88, DX12 (beta)
[PC Only] What other relevant PC specs can you share?
AMD Ryzen 5 5600H 3.30Ghz, 24GB RAM, Windows 11 24H2, “FS2020 - 40 year anniversary” installed via Microsoft Store running SU16 v1.39.9.0
Do you have the same issue if you follow the OP’s steps to reproduce it?
•
Provide extra information to complete the original description of the issue:
•
If relevant, provide additional screenshots/video:
•
Thanks - I thought it was strange not seeing the bug template when I created the post. I assume the issue is on my side or I clicked the wrong button.
I can confirm, instant CTD when loading into flight near Christchurch.
Edit: On Steam
It looks like the bug template was broken for a while. I reported this and it is now fixed.
I wonder if this problem is affecting MS Store users only (I’m on Steam) and/or users that had the SU16 Beta (I didn’t). I’ve done several flights around the south island during the last couple of days, around Nelson as well as Christchurch, and I’m not getting CTDs. Also, I use PG OFF.
That is interesting. I am on the store version but was not enrolled in the beta. Can you confirm if you have updated the NZ POI install post the SU16 release?
Edit: just noting that we have Steam users experiencing this as well.
Yep, all my WUs are up to date, including the NZ POI.
So the key here is to understand what differs with our setup. I now wonder if it is possible that I do not have something installed that the sim expects to be there. I do run a pretty lean setup and I uninstall all airports, liveries I don’t use, so could it be that there is a file being called that does not exist and would that cause a CTD.
I’m the opposite. Pretty much everything is installed.
Yes, it’s curious. How much RAM do you have, @gue63? On my system the CTD occurs when a VRAM resource exhaustion event is triggered. If you have a high amount of RAM and/or an “automatically manage” setting for your paging file, it’s possible that your system never hits the resource exhaustion point that triggers the CTD.
I currently have 24GB RAM installed in my gaming laptop, and my paging file limited to 12GB. This works fine for a flight in any other area, but for some reason still triggers an almost instant “resource exhaustion” and CTD when starting at NZTL.
Also are you on DX11 or DX12 (Beta)? I wonder if that makes a difference. I’m on DX12 (beta) at the moment. I wonder if switching to DX11 stops the CTD from happening.
I have 128GB of RAM lol (I occasionally need to run several VMs, non-FS related). Otherwise it’s a mid-spec machine i7-9700K, RX6700XT. And I’m on DX11.
I tried installing the full NZ world update but the issue remains. I struggle to see how this is hardware related when removing the POI pack or commenting out the objects.bgl file in the layout.json prevent the CTD.
@SaffaJake812, check your DX version. If you’re also on DX12, that might be an additional factor in this CTD. I’ll try switching to DX11 to see if that makes a difference.
Tried it now but my sim does not want to load with DX11
Okay, I’ve just switched to DX11 and restarted the computer, started up FS2020, and clicked “ready to fly” at NZTL. No CTD this time. So it looks like the DX version along with the POI being installed are the key factors that cause this CTD.
I am updating my “reproduction steps” and @SaffaJake812, I also recommend you update the title to include “in DX12” for clarity.
Okay, confirmed. Switching back to DX12 and the CTD again occurs. Happened to catch the moment in my resource monitor too.
Source
FlightSimulator.exe
Summary
Stopped working
Date
‎8/‎08/‎2025 4:46 PM
Status
Report sent
Description
Faulting Application Path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.39.9.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Problem signature
Problem Event Name: MoAppCrash
Package Full Name: Microsoft.FlightSimulator_1.39.9.0_x64__8wekyb3d8bbwe
Application Name: praid:App
Application Version: 1.39.9.0
Application Timestamp: 00000000
Fault Module Name: FlightSimulator.exe
Fault Module Version: 1.39.9.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 0000000001e6c1b9
OS Version: 10.0.26100.2.0.0.768.101
Locale ID: 3081
Additional Information 1: 8215
Additional Information 2: 8215bdf875a5b4312e2132802dc72c18
Additional Information 3: f1eb
Additional Information 4: f1eb9ef0894cb3a37650f5d09419a8bf
Extra information about the problem
Bucket ID: b394d8316fee3d5b90dca183f6273b37 (1215023587625745207)
I’m the same as you, the sim wont run for me when using DX11.
I’m also experiencing instant CTD when flying towards the South Island. I didn’t have this issue prior to SU16. I have been trying to fly NZWN to NZCH. When I turn towards the South Island and reach roughly FL160, instant CTD on every try.
