This has been happening my MSFS installation for several weeks now - purchased and installed 27th August this year.  For a month it worked flawlessly, then after a break of some weeks I played the game and this problem occurred.  I have no add-ons installed (Community is empty), and everything is up to date.  I have fully reinstalled twice since this happened to double check.  I have rolled back my GPU drivers to see if a recent update was the problem.  This is not a CTD problem, but a FlightSimulato.exe 'Freeze'.

Today, after weeks of research, I carried out this possible fix

All versions - Stuck on a black loading screen

 

Sadly it had zero effect for me, but might help others with similar problems.  For those few of us here who are not having much luck with MSFS2020, please add your thoughts here, as I'd really like once again to run Flight Simulator without having to exit using CTRL-ALT-DEL having not left the ground:-)

Another possible fix that I am no working on from the MS website is this:

 

Sim freezes or crashes before loading fully

 

I haven't got round to changing the game service yet, but have disabled all virus and other security software, checked firewall rules and rebooted.

Problem persists.

I have now tried many more tweaks by reading through Youtube and other forums, and still nothing works.  This is the latest I found on Microsoft forum, and is a recent thread there

 

MSFS 2020 v.1.18.13.0 - Freezes and Crashes after 27/07/2021 update

 

I have tried the advice given, in particular that of Nick Cooper

 

Microsoft Flight Simulator please try this first before asking for product support

 

but still no luck.  I am clearly not alone here, just on this forum it seems, since no one has replied to this thread and mostly seem to be flying without difficulty.  I would appreciate some input if anyone finds the time or hears something I have not covered so far.

Still pursuing this problem - and there is so much out there it's a mine field.  Anyhow I have continued trying more suggestions out, including a Windows update that was supposed to rectify errors caused by a previous update that conflicted with Nvidia drivers

 

Still no luck, but took a Windump this time and found the following.  If anyone has suggestions from it please let me know.  The MicrosoftGeospatialTiles.dll!error_destruct sounds a little final:-)

 

*** WARNING: Unable to verify checksum for offensive initials not allowed.dll
*** WARNING: Unable to verify checksum for XPlatCppWindows.dll

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 12405

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 64182

    Key  : Analysis.Init.CPU.mSec
    Value: 1046

    Key  : Analysis.Init.Elapsed.mSec
    Value: 20180

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 137

    Key  : Timeline.OS.Boot.DeltaSec
    Value: 769

    Key  : Timeline.Process.Start.DeltaSec
    Value: 492

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1

    Key  : WER.Process.Version
    Value: 1.20.6.0


NTGLOBALFLAG:  0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

APPLICATION_VERIFIER_FLAGS:  0

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 0000000000000000
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 0

FAULTING_THREAD:  00003898

PROCESS_NAME:  FlightSimulator.exe

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION}  Breakpoint  A breakpoint has been reached.

EXCEPTION_CODE_STR:  80000003

STACK_TEXT:  
000000ef`2437e5a8 00007ffd`a5fa1a8e     : 0000027c`3c64b770 00007ffd`423cbc46 0000027a`00000002 00007ffd`423ca818 : ntdll!NtWaitForSingleObject+0x14
000000ef`2437e5b0 00007ffd`42324fdf     : 000000ef`2437eb90 00007ffd`42325166 0000027c`00000000 00000000`000032bc : KERNELBASE!WaitForSingleObjectEx+0x8e
000000ef`2437e650 00007ffd`4230c0ce     : 0000027c`41712f60 0000027c`00000002 0000b7fe`d539f999 0000b7fe`00000000 : MicrosoftGeospatialTiles!error_destruct+0xfa4a4
000000ef`2437e690 00007ffd`4241a7a1     : 0000027c`41740a20 0000027c`417409b8 00007ffd`421e4951 0000001f`00000006 : MicrosoftGeospatialTiles!error_destruct+0xe1593
000000ef`2437e6c0 00007ffd`4241c0b3     : 0000027c`41740030 00007ffd`4228ad33 0000027c`0ad2ee50 00007ffd`4228b385 : MicrosoftGeospatialTiles!error_destruct+0x1efc66
000000ef`2437e790 00007ffd`4241c2ba     : 0000027c`41740030 00000000`0000000e 000000ef`00000001 000000ef`2437e848 : MicrosoftGeospatialTiles!error_destruct+0x1f1578
000000ef`2437e810 00007ffd`42443978     : 0000027c`41740030 000000ef`2437e940 00000000`00000001 000000ef`2437e8e8 : MicrosoftGeospatialTiles!error_destruct+0x1f177f
000000ef`2437e880 00007ffd`4227866e     : 0000027c`414637e0 000000ef`2437e940 000000ef`2437e8e8 000013c0`00001f7d : MicrosoftGeospatialTiles!error_destruct+0x218e3d
000000ef`2437e8b0 00007ffd`422a130a     : 0000027c`0ad2ee20 000000ef`2437e950 000000ef`2437e940 00000000`00000001 : MicrosoftGeospatialTiles!error_destruct+0x4db33
000000ef`2437e920 00007ffd`4229f448     : 000000ef`2437ea30 00007ffd`a8553241 000000ef`2437ebe9 00007ffd`a851fae2 : MicrosoftGeospatialTiles!error_destruct+0x767cf
000000ef`2437e9a0 00007ffd`4229df58     : 000000ef`2437eab0 000000ef`2437ea30 000000ef`2437ea48 000000ef`2437ea70 : MicrosoftGeospatialTiles!error_destruct+0x7490d
000000ef`2437ea10 00007ff6`46bd19c6     : 0000027c`0ad2ee20 00000000`135fb551 000000ef`2437eab0 000000ef`2437eaf0 : MicrosoftGeospatialTiles!error_destruct+0x7341d
000000ef`2437ea70 00007ff6`46bd2731     : 0000027a`95220ae0 000000ef`2437f060 00000000`0000000d 000000ef`2437ebd0 : FlightSimulator!FlightSimGetProcessId+0xe372a6
000000ef`2437eb50 00007ff6`46bcd9d2     : 00000000`00000000 0000027c`4576a1f8 0000027d`00000000 00000000`00000004 : FlightSimulator!FlightSimGetProcessId+0xe38011
000000ef`2437ec30 00007ff6`46bce000     : 000000ef`00000004 0000027c`4576a138 0000027c`4576a1f8 00000000`00000000 : FlightSimulator!FlightSimGetProcessId+0xe332b2
000000ef`2437ee50 00007ff6`46bdf04b     : 000000ef`2437f060 0000027c`4576a138 0000027c`4576a1f8 00000015`000004ef : FlightSimulator!FlightSimGetProcessId+0xe338e0
000000ef`2437efb0 00007ff6`46bca0ed     : 0000027c`4576a110 0000027a`9d8e5320 000000ef`2437f120 0000027a`9d8e5320 : FlightSimulator!FlightSimGetProcessId+0xe4492b
000000ef`2437f020 00007ff6`46e0ad54     : 0000027a`00000000 0000027a`00000001 0000027a`84c67800 00000000`00000001 : FlightSimulator!FlightSimGetProcessId+0xe2f9cd
000000ef`2437f210 00007ff6`46e0ae08     : 0000027a`81cab340 0000027a`98b93830 0000027c`45662a00 0000027c`45769c60 : FlightSimulator!FlightSimGetProcessId+0x1070634
000000ef`2437f2b0 00007ff6`46e0b97c     : 0000027a`81cab340 0000027a`98b93830 0000027c`456629e0 0000027c`456629e0 : FlightSimulator!FlightSimGetProcessId+0x10706e8
000000ef`2437f350 00007ff6`467bd85d     : 0000027a`145b0f28 00000000`00000000 00000000`00000023 00007ff6`46e0b740 : FlightSimulator!FlightSimGetProcessId+0x107125c
000000ef`2437f5a0 00007ff6`467bc2a6     : 00000000`00000080 00007ff6`462b88c5 00000000`00000000 000000ef`2437f7a0 : FlightSimulator!FlightSimGetProcessId+0xa2313d
000000ef`2437f760 00007ff6`46e0bace     : 00007ff6`49b6ee18 0000027a`81cab340 000000ef`2437f910 0000027a`83d8a1a8 : FlightSimulator!FlightSimGetProcessId+0xa21b86
000000ef`2437f7a0 00007ff6`46819a40     : 00000000`ffffffff 0000027a`83d8a1a8 00000000`00000000 00000204`8f942000 : FlightSimulator!FlightSimGetProcessId+0x10713ae
000000ef`2437f810 00007ff6`469413fd     : 00000001`bc14f172 0000027a`852120a0 00000000`00000000 00000000`00000000 : FlightSimulator!FlightSimGetProcessId+0xa7f320
000000ef`2437f960 00007ff6`46940fa0     : 00000000`00000000 00007ff6`493170a0 00000000`00000001 00000000`00000007 : FlightSimulator!FlightSimGetProcessId+0xba6cdd
000000ef`2437f9b0 00007ff6`465c14b5     : af358769`00009fe0 af358769`e4469aa8 00007ff6`465c3db0 00000000`00000000 : FlightSimulator!FlightSimGetProcessId+0xba6880
000000ef`2437f9f0 00007ff6`473d9f32     : 00000000`0000000a 00000000`00000000 00000000`00000000 01d7c73e`36909bfd : FlightSimulator!FlightSimGetProcessId+0x826d95
000000ef`2437fa30 00007ffd`a7097034     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : FlightSimulator!FlightSimGetProcessId+0x163f812
000000ef`2437fa70 00007ffd`a8542651     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
000000ef`2437faa0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21


STACK_COMMAND:  ~0s; .ecxr ; kb

SYMBOL_NAME:  microsoftgeospatialtiles!error_destruct+fa4a4

MODULE_NAME: MicrosoftGeospatialTiles

IMAGE_NAME:  MicrosoftGeospatialTiles.dll

FAILURE_BUCKET_ID:  BREAKPOINT_80000003_MicrosoftGeospatialTiles.dll!error_destruct

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

IMAGE_VERSION:  1.0.0.0

FAILURE_ID_HASH:  {4dfcd692-d99e-e2da-d601-6a32b5e403bf}

Followup:     MachineOwner
---------

 

 

 

 

I realise that many people are opening the thread and not responding, but I would appreciate comments.  This is the report from Windows 10 security and Maintenance.  The faulting module that keeps coming up is:

 

C:\WINDOWS\SYSTEM32\ntdll.dll

 

Description
Faulting application name: FlightSimulator.exe, version: 1.19.9.0, time stamp: 0x00000000
Faulting module name: ntdll.dll, version: 10.0.19041.1202, time stamp: 0x4f115fac
Exception code: 0xc0000409
Fault offset: 0x00000000000923df
Faulting process id: 0xcc0
Faulting application start time: 0x01d7c10f05318083
Faulting application path: D:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 091e6a33-e356-46f4-b65b-0028c63595db
Faulting package full name: 
Faulting package-relative application ID: 
 

 

Description
Faulting Application Path:    D:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe

Problem signature
Problem Event Name:    APPCRASH
Application Name:    FlightSimulator.exe
Application Version:    1.20.6.0
Application Timestamp:    00000000
Fault Module Name:    FlightSimulator.exe
Fault Module Version:    1.20.6.0
Fault Module Timestamp:    00000000
Exception Code:    c0000005
Exception Offset:    00000000007160b0
OS Version:    10.0.19041.2.0.0.768.101
Locale ID:    2057
Additional Information 1:    8861
Additional Information 2:    8861c3ad716830e9d5f29ddffdab30f7
Additional Information 3:    d42a
Additional Information 4:    d42a6b184a70a21c679e50ef8909d4c9

Extra information about the problem
Bucket ID:    24a3b36ab35e8c8673de6b1193c0e751 (1431699454787905361)
 

Hey man! I'm still struggling with this too. I reinstalled all my scenery last night and most times it loaded fine, but every once and a while I still got the loading indefinitely issue. I THINK it might actually be a livery issue with SU6. When I tried loading in with default liveries all was well. But when I tried with a couple of old liveries (mostly for the FBW A320NX), I started to get the loading issues again. This is a bizarre and extremely frustrating issue.

Let me give you some info on this Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll

This modules is a windows kernel module which mean is usually used when the operating system is trying to access kernel function. NTDLL is a library in windows related issue while trying to access some hardware. So the first thing you should be looking into is drivers of any devices you have on your PC. That could be anything that has a driver.  If you google how to fix NTDLL.DLL error you will come up with a ton of different solution. Let me give you the easiest one you can do. Disable any Overclocking you have on your CPU / GPU. It could be as simple as that. Everything else after that is about Windows update, replacing this file, reinstall drivers for all of your devices. It's a painful process. It's not MSFS causing this issue but your windows. It's important to understand this part.  Your windows is having trouble with this specific library. That is a core function of the operating system. 

Since the problem seems to be tending more toward the O/S and task overhead side with respect to servicing drivers etc., a very safe and relevant step to take would be to perform a clean boot of the system with minimal services loaded.  This temporarily puts the operating system in essentially the leanest, meanest default config for one boot only.  On the next reboot, it will automatically revert to your existing configuration.  So its very safe and can help you isolate any problematic background tasks or services by selectively disabling some tasks further if needed.  Nothing to install or uninstall here. 

Takes like 5 minutes to walk through it tops and is a good technique to know about. This would be the very next thing I'd be doing if it were my system (and I have).

https://support.microsoft.com/en-us/topic/how-to-perform-a-clean-boot-in-windows-da2f9573-6eec-00ad-2f8a-a97a1807f3dd

Would also get a ZenDesk ticket opened up on this if you havent already just to be on the safe side.

 

Edited October 22, 20214 yr by Stoopy

Thanks to those for chipping in.  I have now reinstalled the whole of FS again (24 hours later) and still have the issue.  Today I rolled back drivers a couple of months, uninstalled all system mechanic style software, malware progs, and loads of other stuff.  I have messed with more settings, tried unregistering and reregistering ntdll.dll

 

Nothing has made any difference.

 

I have been rendered utterly miserable by this experience, and deciding that life is too short to be spent on searching a needle in a haystack, will wait  a few years, by which time I might afford (or need) a new computer.

 

My best regards to all who have offered a sympathetic ear.