I was a bit out of line. My apologies, sir. Hopefully we can all get back to flying today. Take care.
5 Likes
Works fine for the first flight with DA40. After changing to another airplane it ends to CTD.
Every new start ends in a CTD, even after rebooting the PC.
POOR quallity control and never had this before!
1 Like
1.18.14.0 Still the same CTD
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001124a00
Faulting process id: 0x2ea0
Faulting application start time: 0x01d78422b5ea406a
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 7a876000-e9f6-4f29-a493-9c29034b4e07
Faulting package full name: Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Mine now as follows:
Problem signature
Problem Event Name: APPCRASH
Application Name: FlightSimulator.exe
Application Version: 1.18.14.0
Application Timestamp: 00000000
Fault Module Name: FlightSimulator.exe
Fault Module Version: 1.18.14.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 0000000000777b0a
OS Version: 10.0.19043.2.0.0.768.101
Locale ID: 2057
Additional Information 1: b403
Additional Information 2: b4034a13398cd20520afe9699b2b7735
Additional Information 3: 2a73
Additional Information 4: 2a737e53e698c0d6ae698dac37086995
Extra information about the problem
Bucket ID: 207924fada7fb5a853938fccc898aa63 (1410629217998645859)
1 Like
Everywhere i look i see exceptioncode0xc0000005
Mine is 0x80000003
Naam van toepassing met fout: FlightSimulator.exe, versie: 0.0.0.0, tijdstempel: 0x00000000
Naam van module met fout: FlightSimulator.exe, versie: 0.0.0.0, tijdstempel: 0x00000000
Uitzonderingscode: 0x80000003
Foutmarge: 0x00000000007d5f21
Id van proces met fout: 0x72c
Starttijd van toepassing met fout: 0x01d785333f2b8e8e
Pad naar toepassing met fout: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pad naar module met fout: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Rapport-id: 42cadc8c-c562-48d3-baa7-2e5949b87a3b
Volledige pakketnaam met fout: Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe
Relatieve toepassings-id van pakket met fout: App
I have no idea what all this means, but perhaps there is somebody smarter than me somewhere on this forum. (Should not be difficult if i believe my wife 
)
1 Like
Hi BlackSanta,
It’s OK. I really do appreciate you apologising in public, some people would not apologise at all. That’s a brave thing to do so in public. 
I think this CTD business has worn us all down a bit. I have just returned to the forum and people are talking about a hot-fix? I did have a CTD problem but managed to fix it, it’s been easier for me than a majority of people who have had no luck at all with fixing their CTD’s.
Kudos to Asobo if they have released a hot-fix so quickly.
As I said in a private message to someone today, I think Microsoft have been very brave with this release. Asobo have been very innovative and know we ‘simmers’ are quite demanding.
It’s a tall order to write software that simulates something as complicated as flight and to simulate the atmosphere and scenery to a degree, (especially with the scenery where it looks so real). Asobo have been very brave and brought some new and innovative development ideas to the table in this simulator. They keep on chipping away at it even with intense criticism and some insults throw at them as well. The developers must have very ‘thick skins’ and the pressures must be intense on them. This high level of innovative development obviously comes with some caveats, given the huge diverse number of different PC’s all configured differently and with different software and FS add-ons, they have an unenviable task of trying to satisfy us all and fix everyone’s CTD problems in such an extreme software environment. They must have a huge amount of data to process and they still manage to continue the development of the simulator. I take my ‘hat off’ to them…
Take care.
BRGDS
Charles.
4 Likes
Same problem after the Update today MFS CTD
Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 0.0.0.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: FlightSimulator.exe, Version: 0.0.0.0, Zeitstempel: 0x00000000
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000001a123c7
ID des fehlerhaften Prozesses: 0x7e1c
Startzeit der fehlerhaften Anwendung: 0x01d785600db1c013
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Berichtskennung: 3aa71a31-592c-40bb-9014-969fe663ca56
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App
2 Likes
Hi Quasyboy,
Welcome to the forum. Look forward to hearing more from you…
Ausnahmecode: 0xc0000005
A search of this code on the internet suggests that there is a possibility of the simulator conflicting with some other software on your system. I am not a great authority on these problems however you could try this general recommendation for this particular error which applies to any type of software that has a problem in Windows. I have posted a link further up the page, no one has come back yet and said they tried the ‘clean boot’ method and it worked or did not work, (at this time). Are you a Steam user too?
The link is here …
And here…
Charles.
Continuous CTD even after this so called “HOT FIX”. Such a shame. This simulator is now a game and is a waste of our time. Cant even do a realistic flight anymore, graphics are horrendous, and cant even lift off the ground before a CTD. Trees loading in when you look left or right, its just completely un playable anymore. Seriously considering XP11 at this point… ASOBO and MS need to get it together and realize this update was not an update, but a downgrade.
1 Like
1 sec before MFS CTD, the display driver “nvlddmkm” stops responding and is then restored.
Before I installed the MSFS Sim Update 5 there were no problems with MSFS
- System
|||- Provider
| [ Name] Display |
|---|
|||- EventID 4101
| [ Qualifiers] 0 |
|---|
Version 0
Level 3
Task 0
Opcode 0
Keywords 0x80000000000000
|||- TimeCreated
| [ SystemTime] 2021-07-30T16:57:00.7444063Z |
|---|
EventRecordID 146741
Correlation
|||- Execution
[ ProcessID] 0
| [ ThreadID] 0 |
|---|
Channel System
Computer **********
Security
- EventData
nvlddmkm
1 Like
Driver conflict perhaps? Try updating your display driver if you have not already done so. I am wondering if Nvidia might need a new hot-fix driver to support this new version of MSFS? Someone with more experience than I might have some views on this. If so it’s just a part of the evolution of this simulator.
We might need to make Nvidia aware using their bug reporting web page so they can investigate this problem too.
Charles.
Honestly I’m not sure why that was MS’s response. We call them “0c5” errors and they’re gross memory violations. They arise in C/C++ when you’re attempting to reference memory that has been freed or not allocated yet. If they’re handled, the faulting module would be MSVCRT which is the C-Runtime. Indicates to me that this is an unhandled exception due to memory mismanagement in the code.
You never want to see these in production software.
3 Likes
They were the only type of CTD I ever saw, randomly for months on end, due to the GNS530 addons airspace messages. Once that issue was identified, for the most part they stopped.
1 Like
Hi qpHalcy0n1,
That all sounds very scary to me and I have to admit, it’s ‘gone over my head’. Way too complicated for me to understand. My approach is quite simple, just ‘Google’ the error and see what comes back.
Do you think there would be any value in trying a clean boot in this instance given what you have said?
I am now wondering if there are some issues with the current Nvidia driver?
BRGDS.
Charles.
No, there’d be no point in trying to make a diagnosis because the type of behavior that leads to a 0c5 could be anything. Referencing a texture that didn’t load, maybe some asset never loaded, something over the network expected to be there was referenced but it wasn’t there, some game object went out of scope and they still have a reference to it and are trying to use it. Could be anything, but that’s the end behavior. In general it’s just poor memory sanitation.
It’s complex software for sure, but these sorts of things can and should be caught. Particularly for memory errors of this type, they’re generally easy to trap…but hard if they’re popping up everywhere.
5 Likes
gpHalcy0n1,
It appears to me that a great deal of Steam users are effected?
I don’t want to ‘rub it in’ but I am as ‘happy as Larry’ because every thing is working well for me on my ‘dinosaur’ 2012 PC.
Charles.
Naam van toepassing met fout: FlightSimulator.exe, versie: 1.18.14.0, tijdstempel: 0x00000000
Naam van module met fout: clr.dll, versie: 4.8.4390.0, tijdstempel: 0x609c45bd
Uitzonderingscode: 0xc0000005
Foutmarge: 0x0000000000669d70
Id van proces met fout: 0x7634
Starttijd van toepassing met fout: 0x01d7855c7684ecb6
Pad naar toepassing met fout: H:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Pad naar module met fout: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Rapport-id: 52564bbe-f674-4a44-98af-af68652a569e
Volledige pakketnaam met fout:
Relatieve toepassings-id van pakket met fout:
After hotfix.
1 Like
Lost of Microsoft store reporting the same CTDs, so it has nothing to do with Steam.
2 Likes
Does anyone with knowledge and experience, think that this could be a display driver issue based upon the system errors posted in this thread? If so, I guess we would all be effected then?
Would there be any value in reporting this in the Nvidia forums, if not already done so by someone?
Charles.
Jep! Same as before with MS Store
2 Likes