Sim crashes on NTDLL.DLL in areas like Washington D.C. and Las Vegas

User Support Hub Crashes (CTDs)
1

Not sure what to say. I’ve been using the sim since it came out in 2020. The past few months I’ve been experiencing crashes each time I try to fly in Washington D.C. or try landing in KLAS from the side of the buildings. I’m on a PC and it’s very annoying and irritating. I’ve tried basically everything to eliminate the problem short of uninstalling and reinstalling. I’ve cleared the rolling cache files, I set my graphics rendering to medium or low, turned off any AI traffic, changed the Anti-Aliasing to all different settings, and even rolled back my graphics driver, though, now I can’t use that and it needs to be the latest. It’s frustrating as heck.

I can recreate it by flying over Washington DC mall towards the capitol building and when I get to the building the program will stop. It happens all the time.

My system is as follows:
Intel i7-12700 not overclocked
32 GB Corsair RAM
Nvidia 3090ti with the latest driver 536.40
Sandisk 980 2TB drive with over 1TB free.
Windows 11 with all the latest patches
Using MS Defender as the virus protector

My global MS settings are low and medium from high. Monitor setting is 1920x1080 @ 60Hz

Event Log:
Application
Application Error
Event ID: 1000
Level: Error
OPCode: Info
Logged 7/7/2023 12:58:04 PM
Task Catagory: Application Crashing Events

Faulting application name: FlightSimulator.exe, version: 1.33.8.0, time stamp: 0x00000000
Faulting module name: ntdll.dll, version: 10.0.22621.1848, time stamp: 0x48d14984
Exception code: 0xc0000005
Fault offset: 0x000000000001e20e
Faulting process id: 0x0x1E40
Faulting application start time: 0x0x1D9B10C25470DA0
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.33.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: f1a8196a-6bf7-408c-ac23-1adbef42f821
Faulting package full name: Microsoft.FlightSimulator_1.33.8.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

It used to say it was in the .net 4.0 but that seemed to have gone away.

The exact error:
FlightSimulator.exe

FlightSimulator.exe has stopped working
A problem caused the program to stop working correctly.
Windows will close the program and notify you if a solution is available
Close program

This is every single time in a flight, night or day, doesn’t matter what the aircraft type.

UGH
UGH1913×1077 180 KB

2

All aircraft or just a particular one?

Community folder empty to test?

Any thrid party airports or scenery, vehicles, landscape, land meshes or poi’s for those areas?

3

Hello @watsdamattau,

Thank you for your post! Your topic has been moved to a subcategory of General Discussion & Community Support. The General Discussion category is meant for discussions that fall outside of our other sub-categories.

Please check out these other categories for your future posts:

  • Aircraft
    is where you discuss current or future planes coming to MSFS.
  • World
    is where you discuss scenery, airports, and weather.
  • Aviate, Navigate, Communicate
    is where you ask for help with flying.
  • Tech Talk
    is where you discuss installation, graphics, drivers, performance, CTDs, and hardware.
  • Menus & Activities
    is where you discuss activities (landing challenges, bush trips, etc), plus anything accessed by the menus including the Marketplace, settings, logbook, cameras, etc.
4

Looking at your picture, your right. Your graphics are not tuned. Do you need photoimagry? I don’t use it. I have a 3080 and get superb results in most places. Of course every YouTuber has the “Silver Bullet” solution. But what I would recommend is start with default graphic settings after doing a clean install of the driver. Test in those two problem airports. Then increase settings. You can always make a test Community folder too. Only what you need in it to fly your test. Rename original to _Community nd create an new folder and copy only what you nned to test into to it.

5

Sorry, I should have put down in the original message was that I use the premium and the default planes. I only purchased the P40, F-14, AIG planes, and Rex accuseason. That’s basically it. Everything else is default.

6

Thanks. I’ll rename that folder and see what happens. As I just posted my sim is basically default except for a couple planes and Rex accuseason. I have AIG planes too.

7

I renamed the Community folder and tried again and the error message came back when I was about to get to the Capitol building, as before. I think it might be the Nvidia driver because when I downgraded to one back in February it worked. Now that I can’t use the old driver though, I might need to just avoid Las Vegas and Washington D.C.

8

Just an update that it still crashes going towards the Capitol building. The .Net error reared its ugly head again.

Faulting application name: FlightSimulator.exe, version: 1.33.8.0, time stamp: 0x00000000
Faulting module name: clr.dll, version: 4.8.9166.0, time stamp: 0x64532ee7
Exception code: 0xc0000005
Fault offset: 0x00000000005f8960
Faulting process id: 0x0x28A0
Faulting application start time: 0x0x1D9B1B477C1ABA6
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.33.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: 4bf321d9-1342-42fa-9705-8fa3b3ced6c2
Faulting package full name: Microsoft.FlightSimulator_1.33.8.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

9

Are you sure Windows & MS Store is up-to-date?
Or tried uninstalling the .NET framework and reinstall it?

1 Like
10

I have an AMD GPU. I don’t fly around DC. But Las Vegas is a stutter fest for me when landing. I have never had a CTD but it stutters really bad. I use Rex Weather most of the time. With default weather it’s less of a stutter fest but the clouds all look like thunderstorms so I try to use Rex.

1 Like
11

Have you checked your memory for errors lately? Something like Memtest86+ works well.

1 Like
12

You can use the driver that didn’t give errors, it just gives a nagging message that you need to update to the specific driver to run the sim. It will still load and fly.

13

Yeah. I tried uninstalling and reinstalling the .net but was unsuccessful.

1 Like
14

Two years ago there was a similar issue near Andrews AFB (KADW).

It was pinned down by conducting multiple flight towards the area from different direction, at the same altitude, while plotting the tracks with LNM.

After sufficient CTD points were found (end of LNM tracks), it was then possible to construct a circle, passing through all points, ad the center of the circle was the location of the scenery object that was causing the CTD, and the use of ProcMon identified the exact file that was being loaded at the point of CTD.

KADW-Clear_Zone

see

1 Like
15

Wow. Nice job.

16

I just ran the Memtest86 as you suggested. I had no idea it would take almost 3 hours. Luckily I had a few things to do to while the way. Anyway, everything passed.

IMG_4947
IMG_49471920×1440 189 KB

17

Good news. I never would have guess the Bermuda triangle.

18

It’s still going on. No matter what I try it just crashes. It’s such a pity.

19

I think I finally got this problem fixed after all the updates, deletions, moves, reinstalls, etc. The NTDLL.DLL and CLR.DLL from the pesky Framework64\v4.0.30319. The fix was to rename the dll file in Capture One \Program Files\Capture One\Capture One 22\WIC\WIC64\P1.WIC.NativeComWrapper.dll . Apparently that was causing the problem.

While researching I saw that someone a few years ago came to the same resolution. So it’s not the NVidia, memory, motherboard, or anything like that.

20

The Capture One software is on the troubleshooting list for CTDs: