This was fixed for me with the first ASOBO fix as long as I kept my flights under 3 hours. After this latest fix I can’t even takeoff with the CJ4 (latest mod). I am able to set up the FMS and config for the flight but before I can taxi I get an unexplained CTD. This happened twice. I have the same community items that I had before this last fix. It was fine before. ASOBO what do you keep doing to us? Give us back the SU4 program and make a 2nd dumbed-down version for the kids on X-Box. We need our flight simulator back the way it was. How many complaints do you need before you admit that this is either going to be a REAL simulator or just another kids’ game? It can’t be both!!!
1 Like
Menu clicks are crashing the game for me all over the place. Main culprits are clicking Contiue in logbook, clicking return to main menu ( if you manage to get through the logbook bit without crashing 
) and if i survive those it’ll crash on exiting the game every single time,
Clearly not as bad as CTD’s in flight, but it’s really getting on my wick a bit now.
3 Likes
Still same CTD’s as before. The hotfix is just another desaster -.-
If any Moderator reads this, please forward to developers:
User Mini Dump File: Only registers, stack and portions of memory are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Version 19042 MP (24 procs) Free x64
Product: WinNt, suite: SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Debug session time: Sat Aug 7 16:47:38.000 2021 (UTC + 2:00)
System Uptime: not available
Process Uptime: 0 days 0:39:05.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.
(479c.4d20): Access violation - code c0000005 (first/second chance not available)
For analysis of this file, run !analyze -v
ntdll!NtWaitForMultipleObjects+0x14:
00007ffb`6ed8d974 c3 ret
0:126> !analyze -v
-
* -
Exception Analysis * -
*
*** WARNING: Unable to verify checksum for WwiseLibPCx64P.dll
*** WARNING: Unable to verify checksum for ■■■.dll
*** WARNING: Unable to verify checksum for CoherentUIGT.dll
*** WARNING: Unable to verify checksum for CoherentUIGTDevelopment.DLL
*** WARNING: Unable to verify checksum for XPlatCppWindows.dll
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullPtr
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 13093
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 134210
Key : Analysis.Init.CPU.mSec
Value: 406
Key : Analysis.Init.Elapsed.mSec
Value: 23101
Key : Analysis.Memory.CommitPeak.Mb
Value: 610
Key : Timeline.Process.Start.DeltaSec
Value: 2345
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.18.15.0
NTGLOBALFLAG: 0
PROCESS_BAM_CURRENT_THROTTLED: 0
PROCESS_BAM_PREVIOUS_THROTTLED: 0
APPLICATION_VERIFIER_FLAGS: 0
CONTEXT: (.ecxr)
rax=0000006b0966ab58 rbx=0000000000000000 rcx=00000261a3f1b230
rdx=0000000000000000 rsi=00000000ffffffff rdi=00000261ff669170
rip=00007ff70c362757 rsp=0000006b0966ab60 rbp=0000006b0966ac60
r8=0000000000000001 r9=0000006b0966ac60 r10=0000000000000000
r11=0000006b0966ab30 r12=0000006b0966b100 r13=00000261a3a91fe0
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
FlightSimulator!FlightSimGetProcessId+0x8959b7:
00007ff70c362757 488b03 mov rax,qword ptr [rbx] ds:0000000000000000=???
Resetting default scope
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ff70c362757 (FlightSimulator!FlightSimGetProcessId+0x00000000008959b7)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000
PROCESS_NAME: FlightSimulator.exe
READ_ADDRESS: 0000000000000000
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: 0000000000000000
STACK_TEXT:
0000006b0966ab60 00007ff70c36388b : 00000261a3a78100 00000263cff3df90 00000261ff666050 0000006b0966b100 : FlightSimulator!FlightSimGetProcessId+0x8959b7
0000006b0966ae20 00007ff70c35ddeb : 00000261a3a78100 0000006b0966b100 00000261b201ad10 0000006b00000000 : FlightSimulator!FlightSimGetProcessId+0x896aeb
0000006b0966af00 00007ff70c35c78e : 0000000000000001 0000006b0966f6d0 0000000000000000 0000000000000000 : FlightSimulator!FlightSimGetProcessId+0x89104b
0000006b0966f530 00007ff70c35bac5 : 00000261a3a78100 0000000000000000 0000000000000000 0000000000000000 : FlightSimulator!FlightSimGetProcessId+0x88f9ee
0000006b0966fab0 00007ff70ca7f881 : 00000261a3a78ad8 0000000000000000 000075cea85806b2 0000000000000000 : FlightSimulator!FlightSimGetProcessId+0x88ed25
0000006b0966fae0 00007ff70c2f6219 : 00000261a3a78ad8 0000000000000000 0000000000000000 0000000000000000 : FlightSimulator!FlightSimGetProcessId+0xfb2ae1
0000006b0966fb10 00007ffb6e0d7034 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : FlightSimulator!FlightSimGetProcessId+0x829479
0000006b0966fb40 00007ffb6ed42651 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : kernel32!BaseThreadInitThunk+0x14
0000006b0966fb70 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : ntdll!RtlUserThreadStart+0x21
SYMBOL_NAME: FlightSimulator!FlightSimGetProcessId+8959b7
MODULE_NAME: FlightSimulator
IMAGE_NAME: FlightSimulator.exe
STACK_COMMAND: ~126s ; .ecxr ; kb
FAILURE_BUCKET_ID: NULL_POINTER_READ_c0000005_FlightSimulator.exe!FlightSimGetProcessId
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
IMAGE_VERSION: 1.18.15.0
FAILURE_ID_HASH: {820ddbe2-45c5-6e4d-b094-bb260b2dc826}
Followup: MachineOwner
Sigh still getting CTD - weather has been fixed thank god! fps still good !
Never had one CTD before su5. After a month of trying to fix this on my end I have given up and am waiting for my refund(if I’ll even get it). This is absolutely ridiculous and disappointing that I can’t even use this sim anymore because a stupid update.
1 Like
Figured my latest one out. I have a payware version of KDEN from the Marketplace. Anytime I try to put it in a plan, CTD or a freeze. Asobo/MS must get the third party developers in on these updates earlier. Currently sitting on the runway at my home airport, KAUS. Fingers crossed that I make it to KMEM…
If you’re still getting CTD’s, I highly recommend opting out of Ultra settings. I am able to push to LOD 3.0 and beyond (though it starts getting choppier), no CTD with all High settings + Ultra clouds. When I bumped up texture synthesis and terrain vector data to Ultra, I’m back to CTD’s.
Also, for the life of me still can’t get FBW A320 to not crash on approach. But every stock plane works and the game looks great.
1 Like
Mine just CTD when I was descending in the FBW A32NX.Looks I will never be able to finish a flight like I used to with this mod.Annoying! Indeed everything else works great except this mod!
It’s pretty clear at this point Asobo is completely clueless when it comes to CTD’s, they just dont know what they are doing or how to fix it.
I left MSFS after purchasing it last year on its release. I wasn’t going to get frustrated trying to play it when it was obviously not fit for release. “Give them time and they will sort it” I thought.
Any way long story short, I came back after SU5, and what a wonderful, problem free game this is. Flawless graphics, beautiful game play. No CTD…
…
…
…
- gets woken up from my deep sleep *
…
…
Rats, it was just a dream
Reality is this game is going backwards. The CTD issue is unbelievably frustrating. The Hotfix has made it worse. I can no longer load a game 9 put of 10 times. It’s continuously CTD for no reason. I have reinstalled it twice, deleted and installed Community folder, have a top Spec PC at great cost to me and yet MSFS still doesn’t work.
So I will now return to Xplane 11 and give it another year and try again.
The game has great promise and a future, but ASOBO should really have not released the game in the state it was and is and really get a grip and get the game working.
I thought there were reports of the FBW A320 causing CTD after SU5 and I hadn’t seen an update for it yet? I still have it uninstalled.
As for the new CTDs for some users, I’m wondering if it is related to CPU and/or GPU overheating or undervoltage. The increased FPS of SU5 wasn’t just about reduced render distance or additional culling. I’m pretty sure the CPU and GPU are being pushed harder…and then people are turning up their settings now that they can. I’ve read some some users have solved their CTDs by backing off on their GPU overclocking. I’m wondering if other users, who aren’t overclocking, can reduce their CTDs by backing off on some of the settings that may be pushing their CPU or GPU over the limit.
Awesome man and true it is vary from one PC to another. Its so weird, its like the update was tested and running in a vanilla Windows 10. Nothing else was install. I don’t even have my norton install, my windows 10 is basic. Now I’m scared since I don’t have any other firewall and security othern than windows defender.
Was pretty stable before SU5. Not perfect, but crashing wasn’t a typical problem.
1.18.13.0. Plenty of CTDs.
1.18.14.0 NOTHING but CTDs, all but entirely unusable.
1.18.15.0 Only flew a few times in one session for about 40 minutes, no crashes so far. Just some really bad popping of scenery objects, some horrible photogrametry that used to look great. And my fps flying low over dense airports and cities, while still better than before SU5, is much slower than with 1.18.13.0 and 1.18.14.0. My higher fps over sparse scenery or at high altitudes is similar fps as 1.18.13.0 and 1.18.14.0.
2 Likes
I was not having any issues with CTDs before SU5. I had a few with version 1.18.14.0. Today I updated to version 1.18.15.0 and have and 4 CTDs.
1st - Started the sim with 4 addons in my community folder and had a CTD after clicking on “FLY NOW”
2nd - Started the sim without an empty community folder and had a CTD after clicking on “FLY NOW”
3rd - Restarted my PC and started the sim with an empty community folder. I started a flight with my plane on the runway and switched to drone mode. I went up about 11000 feet and pushed the number 5 key on my keyboard to return the drone to the aircraft and BOOM CTD.
Just a heads up for people experiencing CTDs.
I have stopped using the Icon A5 and set Vsync to 60FPS max in the game settings.
Please note I never saw more than 60 FPS when flying, only in menus (around 100 FPS) and during game initial loading (up to 600 FPS)
I still experience some CTDs but far less than initially (see report in this same thread).
So Vsync ON seems worth trying as a potential workaround.
I had been having CTDs with varying frequency since about January.
SU5 added in freezing as I entered the approach phase of IFR flights 100% of the time.
Hotfix 1 also added in CTDs when pressing Fly maybe 50% of the time
Hotfix 2 upped the CTDs to 100% of the time.
I’ve currently got a ticket actually being looked at however it relates to my freezing problem at the point of SU5. Even if they suggest a fix it will be irrelevant now due to the CTDs.
I’ve got to the stage now where I’ve stopped caring. The disappointment and frustration that gave way to rage has now settled in to indifference. The way the issues have accumulated for me makes me believe that it comes down to random luck. The software is so incredibly unstable that it can affect anyone at any time for no good reason. I’m not a “fiddler”, I had a new pc that worked perfectly for 4 months, there was nothing in my community folder that hadn’t been downloaded thousands of times by other people and I don’t mess around with settings. I was one of the unlucky ones, that all it comes down to. I guess it’s all you can expect when you entrust a heritage software title to a small console game producer unused to time constraints imposed by a multinational giant.
I’m not holding my breath for the supposed fix at the end of the month. Even if it does make the game playable for me no doubt it will get screwed up again further on down the line.
If this debacle has shown me anything it is the appalling attitude of some of those for whom aren’t affected that are effectively telling us to shut up, that we have no right to complain. It is rather like an able bodied person telling a quadriplegic that his inability to walk is in his imagination as he can walk perfectly well.
I have a very low opinion of the ability of Asobo to sort this out and an even lower opinion of society in general after all this.
2 Likes
Descripción
Ruta de acceso de la aplicación con errores: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Firma del problema
Nombre de evento de problema: MoAppCrash
Nombre completo del paquete: Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe
Nombre de la aplicación: praid:App
Versión de la aplicación: 0.0.0.0
Marca de tiempo de la aplicación: 00000000
Nombre del módulo con errores: FlightSimulator.exe
Versión del módulo con errores: 0.0.0.0
Marca de tiempo del módulo con errores: 00000000
Código de excepción: c0000005
Desplazamiento de excepción: 0000000002272700
Versión del sistema operativo: 10.0.19042.2.0.0.256.4
Id. de configuración regional: 3082
Información adicional 1: 8861
Información adicional 2: 8861c3ad716830e9d5f29ddffdab30f7
Información adicional 3: 1419
Información adicional 4: 141930c89912722894d187127694c3f6
Información adicional sobre el problema
Identificador de depósito: 9489f65cd0ea2f8ff4eb91e93b44ee59 (1507458931193343577)
You know, I kind of feel the same way that you do. From Nov 2020 until about May of 2021 everything in the sim was good. Then SU5 came out, and I started having issues with Airliner approaches would completely freeze up and you could barely fly it to the runway. At that point, I just said meh I’ll fly GA aircraft until this gets sorted out.
When SU5 came out, I tried airliners again and while the approaches were smoother I had a lot of switches that just stopped working in the aircraft. Ok, back to GA I go. Hot Fix 1 came out and I started noticing the ATC issues where they wouldn’t think I’m at the correct altitude even though I was. While annoying, not a deal breaker. Hot Fix 2 came out and now the game is unplayable.
In the last 2 days I have only been able to get a 30 minute flight in from Boston to New York. Every other attempt, the Sim has crashed. Now I’ve reached the point of indifference. It seems things go 1 step forward and 2 steps back.
Now I’m not of the camp that defiantly announces that this is the worst thing they experienced, they will never play the game again, and they want their money back. At the end of the day, this is still a game. And there are plenty of games out there that folks pay full price for that turn out to be utter rubbish (Cyberpunk 2077 comes to mind). It sucks, for sure, but it also happens.
I don’t know about you, but I’ll certainly keep an eye out for future updates to see if things become usable again, but I’m not going to get my hopes up in the near term. I got better things to do with my time than to sit around waiting on a game.
Totally agree.
1 Like