DX12/DX11-- Several CTDs on Several Planes While Spawning (Solved: 3rd Party Mods Causing CTD)

[moxiejeff]

Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

Are you using Developer Mode or made changes in it?

No

Brief description of the issue:

I can’t load into KDFW or KDAL on any plane (default or 3rd party) with DX12, DLSS Enabled (Quality) – CTD every time.

Provide Screenshot(s)/video(s) of the issue encountered:

Detailed steps to reproduce the issue encountered:

Enable DX12, restart sim, try to load into KDFW or KDAL (DLSS enabled)

PC specs and/or peripheral set up if relevant:

i9-12900k, 32gb DDR 5 RAM, 980 Pro SSD, 3080 Ti

Are you using DX12?

Yes

Are you using DLSS?

Yes

Are you using the multi monitor feature?

No

---

For anyone who wants to contribute on this issue, Click on the button below to use this template:

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:

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

[moxiejeff]

Faulting application name: FlightSimulator.exe, version: 1.27.9.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.27.9.0, time stamp: 0x00000000
Exception code: 0x80000003
Fault offset: 0x0000000001d9cf52
Faulting process id: 0x3ee8
Faulting application start time: 0x01d892e5e62ac9b1
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.27.9.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.27.9.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 30e12519-0d32-48f1-a7b3-3d3acb8dfd0a
Faulting package full name: Microsoft.FlightSimulator_1.27.9.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

[Jummivana]

Hi @moxiejeff - could you provide a few of the Fault Bucket IDs, as well as the names of the planes you tried?

How to find your Fault Bucket ID after a crash [PC]

Make sure your computer has internet connection. After the crash, make sure to ‘check for solutions’ and click on ‘send information’ buttons. Go to Start → Event Viewer Go got Windows Logs → Application Click on Event ID 1001 around the time of your crash. Look for FlightSimulator.exe. [image] In General tab you will find ‘Fault bucket’. This is Watson bucket ID generated for the crash. [image]

[anon41762679]

Do you have the same issue if you follow the OP’s steps to reproduce it?

Yes although I am using DX11. I tested with PMDG 737. The airport was Heathrow. Will try other planes

Provide extra information to complete the original description of the issue:

Faulting application name: FlightSimulator.exe, version: 1.27.9.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.27.9.0, time stamp: 0x00000000
Exception code: 0x80000003
Fault offset: 0x0000000001d9cf52
Faulting process ID: 0x25d0
Faulting application start time: 0x01d892e4677b572e
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.27.9.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.27.9.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report ID: 7df51ef1-2c8b-4b03-95ec-84f45aad59c0
Faulting package full name: Microsoft.FlightSimulator_1.27.9.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

If relevant, provide additional screenshots/video:

[moxiejeff]

Hey Jayne! Thanks for the quick response.

Here you go. The last 3 CTDs via DX12 all show this Fault bucket ID: 2289884357001141437, type 5

CM edit to remove private details

Let me know if you need anything else!

[Jummivana]

Thank you! And seeing the above user mention they are having the same issue with DX11, can you try the same repro steps on DX11 and see if it is still happening?

You also mentioned some planes, which ones did you try so we can have our testers try the same ones?

[HXArdito]

DLSS has nothing to do with the cloud.

[HXArdito]

I thing you got something wrong. AA and DLSS is something that runs native on your PC, on your CPU/GPU.

[Cahzito]

Not at all, Nvidia uses AI on that tech, but nothing is really stored on the cloud.

[moxiejeff]

Correct - this is about DX12, not DLSS.

[moxiejeff]

OK, I just tried DX11 instead of DX12… I just got a CTD when spawning the Asobo A320 (default) into KDFW. I also noticed HDR is not working on DX11 either (yes, I ensured it’s on in Windows Settings).

[Jummivana]

Okay, thank you. I’ll edit the title to reflect both.

[DensestSnail693]

I haven’t really delved into it so I guess I’m guilty of a bit of presumption… not for the first time I must admit. Jumivana feel free to expunge my posts in this thread.

[Jummivana]

@moxiejeff will you confirm this issue is happening with a clean community folder and in safe mode?

[moxiejeff]

I’m testing that now – had a few mods in my comm folder (PMDG and some 3rd party scenery); so I’ve moved all of them and restarting as we type. I’ll update shortly.

[moxiejeff]

Hey Jayne,

Sorry for the wild goose chase – I know better, sigh. I removed every addon in my comm folder and DX11 and DX12 are now spawning fine. So there’s clearly something causing the CTD in my community folder, which will take time adding them in one by one.

I’ll edit my thread title to explain it’s probably a 3rd party mod causing the issue?

** still can’t get HDR to work on either, but that’s a separate bug.

[Jummivana]

Okay, great to hear! Thanks for the update.