SU6 - Sim CTD near EDDS (Stuttgart)

ISSUE DESCRIPTION

When flying near EDDS the sim crashes to desktop with Exception code: 0xc0000005
In this example, I was descending into EDDF just passed waypoint NELLI when the crash occured.

More instances here:

FREQUENCY OF ISSUE

Lets just say I dont go even NEAR Stuttgart anymore.

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Fly near EDDS

  2. Crash

  3. Anger

[PC ONLY] FAULT BUCKET ID

None available, just this:

Faulting application name: FlightSimulator2024.exe, version: 1.8.14.0, time stamp: 0x00000000
Faulting module name: FlightSimulator2024.exe, version: 1.8.14.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000031f3194
Faulting process id: 0x14D8
Faulting application start time: 0x1DD2C047E76978F
Faulting application path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.8.14.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.8.14.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Report Id: ca1124dc-06ae-405e-95f4-6a21c3b5a100
Faulting package full name: Microsoft.Limitless_1.8.14.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

YOUR SETTINGS

Irrelevant

MEDIA

So I may have found something to report here as I was able to replicate the issue and find the potential cause.

Using the Vision jet I spawned into RW 25 and simply began to taxi following the path in the chart below. At one point the sim crashed. I repeated the same test and it crashed again at exactly the same spot.

I then changed the upscaling from FSR 4.1 (I have the RX9070XT) to TAA . I then repeated the test taxiing around twice and there was no crash.

I then changed the upscaling back to FSR and it crashed again in the very same spot.

Seems this might be related to the Upscaling. Perhaps with all the testing Asobo was doing in SU6 beta with FSR4 and reverting back, they may have missed something.

It would be interesting to see if others can replicate this.

I use TAA and AMD Fluid Motion Frames.

Ok, the upscaling was just a theory but please see if you can get it to crash in the same spot by simply taxiing.

ok, I tried what you suggested. I loaded into a piston airplane and used the drone camera to fly around EDDS a bit and… nothing.

since i havent flown this plane in a while, I started up the engine, turned on the avionics (wanted to play around a bit, you know..) and BOOM! - CTD. Again at EDDS. And this after I successfully finished a flight from LEPA to LSGG in the Fenix A320 on VATSIM.

There definitely is an oddity in EDDS. This is the STOCK airport, btw. No add-on.

Default airport trying the WT 707 CTD at EDDS, I will try a different airport, hopefully it is just this area?

Quick thing… was browsing event viewer… found this a one second before the CTD, in the System logs:

one second later:

Maybe it’s not related. Worth checking for similar logs?

I’m thinking this is related, maybe. Check for similar logs.

Here the crash from yesterday. CTD at 16:54:07

Windows increasing virtual memory just 1 second earlier:

Same â– â– â– â–  thing.

ok, i’ve manually set page file size to 32000MB for now. will have to mess with EDDS again later.

BTW… I repeated the same test as my earlier post, this time disabling both the Community folder and the exe.xml file, and the CTD occurred again at exactly the same spot. This issue is not add-on related.

(post deleted by author)

I do not have the virtual memory error in my logs. I wouldn’t expect to since I have 64 GB memory. My pagefile never grows.

I mean, it makes sense… if Windows is increasing paging file size, which causes memory requests to some applications to be denied (in this case the sim), it can/will crash with this 0xc0000005 exception code.

Why this happens at EDDS, if really related, would be up to Asobo to figure out.

I have the same issue around EDDS, also with messages about increasing the pagefile size in event viewer even though I have 64 GB of RAM.

Interesting… also maybe try setting a fixed page file size so that Windows doesnt increase it dynamically.

The question is, what is it about being in or around EDDS that’s causing Windows to suddenly run out of virtual memory (if this is actually really the cause of the CTD), and for Asobo to fix it.

Since this is heavily depending on your addons and settings, you are the only one who can answer this.

And I’m absolutely convinced this is not only an EDDS issue.

FYI, increasing the page file size (virtual memory) may help prevent CTDs. Also, setting a fixed size can reduce unnecessary writes, extending SSD lifespan.

Source https://forums.flightsimulator.com/t/2024-after-new-install-and-changing-to-win11-ctd-when-setting-up-controles/704798/27?u=tenpatrol

I personally have 64GB of virtual memory (pagefile) set.

Someone will probably say, “Why do you need that much?” Well, I have a large fast nvme and I simply want to be on the safe side when playing different games without worrying about CTDs, even though I have 64GB of physical RAM.

The terrain around EDDS is quite demanding on the PC if you’re running higher settings. Even if that weren’t the case, virtual memory is a very important part of the system and even more so when you’re running a flight simulator, which needs considerably more than a calculator to run properly.

Back in the Windows XP days, the recommendation was to set the virtual memory to twice the size of the physical memory. Perhaps that still applies.