[FIXED] CTD Exception code 0xc0000005 Crash to Desktop

[WidowsSon 135]

Really hope this can resolve at least a few of your guys issues. I couldn’t log a single flight since it started and have lost close to 20 hours from Crashing to Desktop in flight or when trying to exit to the menu.

FlightSimulator.exe had Exception code 0xc0000005 in Event Viewer as many have posted.

This is how I fixed it:

 

[Dillon 2,197]

Going to try this.  AI might need a patch from Asobo.

[edmondhk 0]

At lease you remind me to look at the event viewer. I got the 0xc0000005 too

[LarrySinNJ 1]

Didn't help me.  Still get CTD consistenly, usually when flying, occasionally when going from setup to flight.  Pretty much always due to ucrtbase.dll

Here's the error I get:

Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5f467af2
Faulting module name: ucrtbase.dll, version: 10.0.19041.488, time stamp: 0x0d8057d8
Exception code: 0xc0000409
Fault offset: 0x0000000000071218
Faulting process id: 0x584c
Faulting application start time: 0x01d688525f40f8a4
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.7.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 36eb593f-ee95-4733-9fdf-f43f3a878d2b
Faulting package full name: Microsoft.FlightSimulator_1.7.14.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

[CarlosF 1,239]

20 minutes ago, Lrscpa said:

Still get CTD consistenly

Are you OC your video card?

I don't know if this will help, but I too had CTD consistently while flying, sometimes during approach/landing, other times while changing settings, found out that the OC settings (MSI Afterburner)  were a bit too high for MSFS, same settings worked fine for XP, I guess MSFS is more demanding, anyway once I set settings back to default, no more CTD.

 

 

[LarrySinNJ 1]

1 hour ago, CarlosF said:

Are you OC your video card?

I don't know if this will help, but I too had CTD consistently while flying, sometimes during approach/landing, other times while changing settings, found out that the OC settings (MSI Afterburner)  were a bit too high for MSFS, same settings worked fine for XP, I guess MSFS is more demanding, anyway once I set settings back to default, no more CTD.

 

 

Nope Carlos, no overclocking.  CPU or GPU...

[WidowsSon 135]

Just to be clear, the key is to make sure that the limit is not your main thread (CPU limited), not to just turn off Traffic. I'm not sure if I made this clear enough in the video.

Some have found that turning V-Sync off has removed the mainthread limitation and stopped the CTD's. This is just a way to see when you are not CPU limited anymore.

I think some are thinking the solution is to stop using Traffic. This is more a solution to find your solution which may be unique.

[Cloudpiercing 65]

4 hours ago, LarrySinNJ said:

Didn't help me.  Still get CTD consistenly, usually when flying, occasionally when going from setup to flight.  Pretty much always due to ucrtbase.dll

Here's the error I get:

Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5f467af2
Faulting module name: ucrtbase.dll, version: 10.0.19041.488, time stamp: 0x0d8057d8
Exception code: 0xc0000409
Fault offset: 0x0000000000071218
Faulting process id: 0x584c
Faulting application start time: 0x01d688525f40f8a4
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.7.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 36eb593f-ee95-4733-9fdf-f43f3a878d2b
Faulting package full name: Microsoft.FlightSimulator_1.7.14.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

LarrySinNJ, i saw that you referred to ucrtbase.dll and that make me wonder if you maybe have a outdated GPU driver?  Our if your GPU driver is recently uppdated, try a roll back.

[desbean 357]

Guess I'm lucky, MSFS crashes every time I use it, but only when I click Yes, that I want to exit the sim. "flightsimulator.exe has stopped working....sending report to Microsoft"

[andrevieira 16]

5 hours ago, LarrySinNJ said:

Didn't help me.  Still get CTD consistenly, usually when flying, occasionally when going from setup to flight.  Pretty much always due to ucrtbase.dll

Here's the error I get:

Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5f467af2
Faulting module name: ucrtbase.dll, version: 10.0.19041.488, time stamp: 0x0d8057d8
Exception code: 0xc0000409
Fault offset: 0x0000000000071218
Faulting process id: 0x584c
Faulting application start time: 0x01d688525f40f8a4
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.7.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 36eb593f-ee95-4733-9fdf-f43f3a878d2b
Faulting package full name: Microsoft.FlightSimulator_1.7.14.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Same CTD here. 

When im flying and use GPS several times, the sim crash.
I try every times now, and crash ever i use GPS.

 

Nome da aplicação com falha: FlightSimulator.exe, versão: 0.0.0.0, carimbo de data/hora: 0x5f467af2
Nome do módulo com falha: ucrtbase.dll, versão: 10.0.19041.423, carimbo de data/hora: 0xccf6a09c
Código de exceção: 0xc0000005
Desvio de falha: 0x0000000000024e28
ID do processo com falha: 0x1190
Hora de início da aplicação com falha: 0x01d6888596035c29
Caminho da aplicação com falha: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.7.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Caminho do módulo com falha: C:\WINDOWS\System32\ucrtbase.dll
ID do Relatório: 09a02ab1-d40b-48ef-9081-fea4f0655725
Nome completo do pacote com falha: Microsoft.FlightSimulator_1.7.14.0_x64__8wekyb3d8bbwe
ID da aplicação relativa ao pacote com falha: App

[WidowsSon 135]

Sorry guys, was hoping this would help more people. A few have mentioned that when using this technique they notice an increase in fps from around 20 to 50 when disabling VSync. Not so much a CTD fix but worth a look if you have vsync enabled.

[Dillon 2,197]

Man I was hoping this would work but after pulling up the framerate counter I see no problem with my settings and I still get CTD's in the Longitude on longer flights... Hope this upcoming patch offers some improvements.

[united001 126]

This thread and video helped me a TON! Thank you WindowsSON! Thank you! I had no idea V-Sync was so detrimental for my system. Also, I did something that I think is underated or at least underestimated. I changed from wifi to hard-wired ethernet. I had had realized how many Gigs are streamed in with great frequency. The end result:  ~12 to 30 FPS before in the A320 clear weather external view non over urban areas to 30 - 67 FBS. Stutters drastically reduced, eliminated entirely for long stretches.

United001 

Edited September 12, 2020 by united001

[edmondhk 0]

5 hours ago, andrevieira said:

Same CTD here. 

When im flying and use GPS several times, the sim crash.
I try every times now, and crash ever i use GPS.

 

Nome da aplicação com falha: FlightSimulator.exe, versão: 0.0.0.0, carimbo de data/hora: 0x5f467af2
Nome do módulo com falha: ucrtbase.dll, versão: 10.0.19041.423, carimbo de data/hora: 0xccf6a09c
Código de exceção: 0xc0000005
Desvio de falha: 0x0000000000024e28
ID do processo com falha: 0x1190
Hora de início da aplicação com falha: 0x01d6888596035c29
Caminho da aplicação com falha: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.7.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Caminho do módulo com falha: C:\WINDOWS\System32\ucrtbase.dll
ID do Relatório: 09a02ab1-d40b-48ef-9081-fea4f0655725
Nome completo do pacote com falha: Microsoft.FlightSimulator_1.7.14.0_x64__8wekyb3d8bbwe
ID da aplicação relativa ao pacote com falha: App

Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5f467af2
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5f467af2
Exception code: 0xc0000005
Fault offset: 0x0000000001454d70
Faulting process id: 0x1f70
Faulting application start time: 0x01d6876f40e342ec
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.7.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.7.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: b9d53637-4f13-4f11-a865-0ed3e6a46b08
Faulting package full name: Microsoft.FlightSimulator_1.7.14.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

 

Seems I fail differently...which explain the fix doesn't work for me

[jcirrus 0]

On 9/11/2020 at 11:49 PM, united001 said:

This thread and video helped me a TON! Thank you WindowsSON! Thank you! I had no idea V-Sync was so detrimental for my system. Also, I did something that I think is underated or at least underestimated. I changed from wifi to hard-wired ethernet. I had had realized how many Gigs are streamed in with great frequency. The end result:  ~12 to 30 FPS before in the A320 clear weather external view non over urban areas to 30 - 67 FBS. Stutters drastically reduced, eliminated entirely for long stretches.

United001 

Hi,

 

How you change from wifi to hard-wired ethernet?

 

Many tks