Crash to desktop without error message

My birds are grounded since the last update, before it was working fine.
My exemption code is 0xc0000005

Here is my full error message:

Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.15.8.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.19041.962, Zeitstempel: 0xbd2c3c23
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000000063416
ID des fehlerhaften Prozesses: 0x25f0
Startzeit der fehlerhaften Anwendung: 0x01d738e9c43bb3f5
Pfad der fehlerhaften Anwendung: D:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\ntdll.dll
Berichtskennung: e3a93522-3096-45f9-93a6-c746636eb9e2
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

1 Like

I just had the same CTD also :frowning:

Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x60783c14
Faulting module name: ntdll.dll, version: 10.0.19041.844, time stamp: 0x60a6ca36
Exception code: 0xc0000005
Fault offset: 0x0000000000063416
Faulting process id: 0x2744
Faulting application start time: 0x01d738eadd702f11
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.15.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 0a6deb44-59c4-49bd-b7dc-f8dd3e3d7979
Faulting package full name: Microsoft.FlightSimulator_1.15.8.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
1 Like

The problem is, these CTD “EVENTS” do not really tell very much about what is going on.

Even a full CTD “REPORT” like the 0ne below, while providing much more information, is not oreally sufficient.

This is a CTD, cause by plugging in a Particular Thrustmaster FFB USB Joystick, that MSFS is “having an issue with”.

The report clearly show what instruction is causing the issue, in which exact module, but without a symbol library and the source, knowing exactly in what context and where in the code this took place is not easy !!

If this (100% repeatable CTD) had been caused when the software was running in a debugger at ASOBO, the problem would be identifiable and possibly fixed quicker than it has taken me to type this post.

============================================================

Microsoft (R) Windows Debugger Version 10.0.21306.1007 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\ms\AppData\Local\CrashDumps\FlightSimulator.exe.13512.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available

************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Version 19042 MP (8 procs) Free x64
Product: WinNt, suite: SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Debug session time: Wed Apr 21 18:53:02.000 2021 (UTC - 4:00)
System Uptime: not available
Process Uptime: 0 days 0:25:53.000




Loading unloaded module list

This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(34c8.39f8): Access violation - code c0000005 (first/second chance not available)
For analysis of this file, run !analyze -v
ntdll!NtWaitForMultipleObjects+0x14:
00007ffd`cff4d874 c3 ret
0:095> !analyze -v

Exception Analysis

*** WARNING: Unable to verify timestamp for FlightSimulator.exe
*** WARNING: Unable to verify checksum for WwiseLibPCx64P.dll
*** WARNING: Unable to verify checksum for WTF.dll
*** WARNING: Unable to verify checksum for CoherentUIGT.dll
*** WARNING: Unable to verify checksum for XPlatCppWindows.dll
*** WARNING: Unable to verify timestamp for xgameruntime.dll

KEY_VALUES_STRING: 1

Key : AV.Fault
Value: Read

Key : Analysis.CPU.mSec
Value: 6452

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 16588

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

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

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

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

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: 3.3.39.0

NTGLOBALFLAG: 0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

APPLICATION_VERIFIER_FLAGS: 0

CONTEXT: (.ecxr)
rax=0000000000000000 rbx=0000020d52f2b3f0 rcx=00000000000010e0
rdx=00000027ffffffd8 rsi=0000000000000009 rdi=0000020cda075dc0
rip=00007ffdb1fc6805 rsp=000000e45380eee0 rbp=0000000000000000
r8=00000232b1c9ffd8 r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206
pid!PID_ReadComplete+0x185:
00007ffdb1fc6805 428b440138 mov eax,dword ptr [rcx+r8+38h] ds:00000232b1ca10f0=???
Resetting default scope

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ffdb1fc6805 (pid!PID_ReadComplete+0x0000000000000185)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000232b1ca10f0
Attempt to read from address 00000232b1ca10f0

PROCESS_NAME: FlightSimulator.exe

READ_ADDRESS: 00000232b1ca10f0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 00000232b1ca10f0

STACK_TEXT:
000000e45380eee0 00007ffdcff50a4e : 0000020d52f2b3f0 0000000000000000 0000000000000000 0000000000000000 : pid!PID_ReadComplete+0x185
000000e45380f150 00007ffdcde8a104 : 00007ffdce3d078e 0000020d52f2b3f0 0000000000000000 0000000000000020 : ntdll!KiUserApcDispatch+0x2e
000000e45380f688 00007ffdce3d078e : 0000020d52f2b3f0 0000000000000000 0000000000000020 0000000000000000 : win32u!NtUserMsgWaitForMultipleObjectsEx+0x14
000000e45380f690 00007ffdb1fc6a67 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : user32!RealMsgWaitForMultipleObjectsEx+0x1e
000000e45380f6d0 00007ffdcf857034 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : pid!PID_ThreadProc+0x87
000000e45380f750 00007ffdcff02651 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : kernel32!BaseThreadInitThunk+0x14
000000e45380f780 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : ntdll!RtlUserThreadStart+0x21

SYMBOL_NAME: pid!PID_ReadComplete+185

MODULE_NAME: pid

IMAGE_NAME: pid.dll

STACK_COMMAND: ~95s ; .ecxr ; kb

FAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_pid.dll!PID_ReadComplete

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

IMAGE_VERSION: 10.0.19041.1

FAILURE_ID_HASH: {843d278a-8462-05da-6394-aaca8615d790}

Followup: MachineOwner

0:095> .exr -1
ExceptionAddress: 00007ffdb1fc6805 (pid!PID_ReadComplete+0x0000000000000185)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000232b1ca10f0
Attempt to read from address 00000232b1ca10f0

2 Likes

I had not had CTD until the last update. The amount of CTD is horrible. Impossible to use the simulator in these conditions. Asore strokes batteries because it is a disaster to fix one thing and break 20 things

3 Likes

How did you get the details? Event viewer shows only what i posted.

welp, i fixed the problem i was facing myself apparently… as you can see from this screenshot, i was trying to get past the main menu ctd on my side by experiementing with quite a lot of different things but was constantly getting that event id 1000 with a ctd right after reaching the main menu.

1000

nothing actually worked until i tricked the sim into redownloading and reinstalling the latest update two hours later. i’m now successfully back in the main menu while still using the same mods, the same overclock, the same patch level of the os, the same vcruntimes and the same settings for my paging file. i just applied the last msfs update once again and the sim got back to life for me.

another proof that it’s not about the hardware or state of the operating system - it’s just about the game.

2 Likes

You will need to download and install WinDbg, so that you can analyze your DUMP files.
You will also have to configure your windows to produce .dmp files (if it is not already doing so)

Most, if not all the information to do the above is on the Microsoft website.

I used the WinDbg Preview

2 Likes

For my topic I found a solution - I had two problems, after 1h flight CTD always on the same route and same place. Second problem came a few days later starting a flight, when I click on the button (screen where you see your plane) to enter the game CTD.

What I did, clean my community folder, tried again and everything was fine. So I spend 3h to findout which of my addons leads to a crash and it was the airport “lgsm”. Now it works, I could complete my flight.

1 Like
1 Like

Hello guys, yesterday my simulator was opening and working normally, today (now) when trying to open, it is giving CTD, it is nothing more than the initial load screen, I have removed everything from the Community, and have not installed anything new from yesterday to today!

I dont know what to do anymore, every day a new problem! :cry:

maybe you’re facing the same issue i was tackling today after the sim refused to function properly all of a sudden today after launching the sim even though yesterday it was still all okay.

1 Like

Can you mention some system specs ( RAM, GPU, Free Disc Space on main disc, etc. ) ?
Can you show us the event log entry ?
May be check date of latest window update too.

1 Like

i’m curious, michael… if i would have shown you that the path of the faulting module was the vcruntime140.dll while facing the very same issue maglestat is facing, what would have been your advice?

that you possible joining into the thread about the vcruntime140.dll and may be you find a hint within :slight_smile: ( may be the old issues with azure are back, or you have other trouble which we mentioned within these other thread which is then “WITH an error message” ).

In generaly it is allways important to know more as “I have a CTD”.

I asked @maglestat for more infos because we have not less cases of seemingly random CTD , which comes from memory consume of msfs ( also for users which reported the vcrun…dlll error, more rare , but sometime. ).

see, that is what i’m saying… instead of randomly advising on things or fishing in the dark, i actually did fix the mentioned ctd i was facing by just reinstalling the last msfs update. your advice most likely would have been, as you’ve advised before, to uninstall / reinstall a bunch of vc++ runtime libraries, do a sfc /scannow, a dism check, downclock or tweak pagefile settings…

what i’m just saying is that searching this forums and posting links to threads that seem to be about what some issue might be, is still not helpful. nor is randomly asking people to do this or that. do as you like, michael, but as this is just my 5 cents and even though you’re just trying to do your best, i’d be cautious to listen to someone who is not and never has been facing ctd’s as you’ve been saying quite some times now.

the reason that reinstalling the latest msfs update actually did fix my main menu ctd’s after that loading screen should bother asobo. again, one could guess a filesystem corruption was happening to me while booting up my system this morning but that is rather unlikely since the only application affected by this, once again was just this sim.

it worries me how rarely you suspect that the problems peepz are facing here are actually in the sim itself. first guess for you is almost always “there must be something wrong with your system or the platform” and that is just because you never experience any ctd’s coming for the sim itself.

that’s just a faulty way of diagnosing things.

but again, all of this are just my 5 cents.

6 Likes

and I asking @maglestat about more informations that we can possible avoid that he must re-install the 170GIG again…

It is your personal opinion that my help is

. The users which can play because of my tips may have another opinion.

Still not know why you attack me if I ask @maglestat for more informations so that the community can give possible hints ! You can ignore this question and of course @maglestat can ignore the question.

i’m not attacking you - i’m just telling the truth and do reasonable questioning… feel free to put me on your ignore list if you wish… but i’m not gonna stop critizing advise that i deem not to be helpful at all. sorry.

1 Like

How did you reinstalll latest MSFS update?

had to try a couple of things, first, but it seems that getting rid of or renaming a certain core package from the sim forces the sim to redownload the latest update. i own the steam version, so the path i went to has been this:

C:\Users\xXx\AppData\Roaming\Microsoft Flight Simulator\Packages\Official\Steam

in there i renamed the folder

fs-devmode

to

fs-devmode.old

and after launching the sim, i got forced to redownload the latest update again.

there might be other ways to do this but this was indeed working for me.

the advantage of doing this obviously is that you only have to download 4gb instead of the round about 120gb of data.

Please keep this topic on assisting with CTDs and not on each other. All these CTD topics are of interest to the developers and the less bickering, the better. The more feedback as to the cause of the CTD will help the developers.

As a reminder, the purpose of the #bugs-and-issues categories is to discuss issues that affect the base simulator. Please do not discuss issues with third-party addons or modifications in this category. These should be filed via the developer’s preferred support method.

If you believe your issue may be caused by a third-party addon/mod, empty your community folder, restart the simulator and try to reproduce the error.

All issues caused by, or involving third-party addons/mods should be reported to the third-party developer. All issues related to the core simulator can be formally reported through Zendesk.