Flying the FBW A320 from EGLL - LGAV just over northern France, the sim froze for ages (sound was still playing) and then after a few minutes crashed to fhe desktop. 

Took off from inibuilds EGLL with FSLTL and default live weather. 

First time since starting to use the sim a few months ago. Have just installed the latest SU. 

1 hour ago, BWBriscoe said:

Flying the FBW A320 from EGLL - LGAV just over northern France, the sim froze for ages (sound was still playing) and then after a few minutes crashed to fhe desktop. 

Took off from inibuilds EGLL with FSLTL and default live weather. 

First time since starting to use the sim a few months ago. Have just installed the latest SU. 

You do realise the update you mention, is not a general update. It is a Beta, and expect issues like CTD's. Its all part of testing.

5 minutes ago, Car147 said:

You do realise the update you mention, is not a general update. It is a Beta, and expect issues like CTD's. Its all part of testing.

I assumed it had been downloaded as my spash screen was full of NZ shots. Is this not the case? (I've not signed up to beta test!)

10 minutes ago, BWBriscoe said:

I assumed it had been downloaded as my spash screen was full of NZ shots. Is this not the case? (I've not signed up to beta test!)

 

1 hour ago, BWBriscoe said:

Have just installed the latest SU. 

If you downloaded the SU, SU meaning Sim Update, then it's a beta you downloaded. Sim Update 12 has not been officially released yet.

The World Update for New Zealand has been released.  World Updates these days (as opposed to the first year of MSFS) generally have no code changes. Since your flight was from EGLL - LGAV, it's highly unlikely (although not impossible, since there were bugs with World Updates in the past) that the New Zealand World Update is the reason why MSFS CTDed on you.

Edited March 4, 20233 yr by Flightsky

3 minutes ago, Flightsky said:

 

If you downloaded the SU, SU meaning Sim Update, then it's a beta you downloaded. Sim Update 12 has not been officially released yet.

The World Update for New Zealand has been released.  World Updates these days (as opposed to the first year of MSFS) generally have no code changes. Since your flight was from EGLL - LGAV, it's highly unlikely (although not impossible, since there were bugs with World Updates in the past) that the New Zealand World Update is the reason why MSFS CTDed on you.

Ah ok, apologies, I confused world update with SU.

Still, would appreciate any help with my CTD...!

11 minutes ago, BWBriscoe said:

Still, would appreciate any help with my CTD...!

You may never know what caused it..  MSFS is pretty stable, but not CTD proof at present.

You are not the only one experiencing CTD(s).. 😉

that’s so annoying!

It’s worth looking up the exception code in your Windows Event Viewer (Applications) though, if you know how.

Typically an outdated Addon in your Community folder will be the culprit (it usually is in my case). 
I’ve been flying the FBW in WU12 and SU12beta with no problems, except for the aforementioned old addons. 

Best to disable them if you can.

good luck with it

2 hours ago, rayharris108 said:

that’s so annoying!

It’s worth looking up the exception code in your Windows Event Viewer (Applications) though, if you know how.

Typically an outdated Addon in your Community folder will be the culprit (it usually is in my case). 
I’ve been flying the FBW in WU12 and SU12beta with no problems, except for the aforementioned old addons. 

Best to disable them if you can.

good luck with it

How do I look up the exception code?

Type in Event Viewer in the tool bar search window (Win 11)

First CTD?

LUCKY man

5 hours ago, BWBriscoe said:

How do I look up the exception code?

Type in 'Event Viewer' in the Windows search bar

Then select;  Windows Logs -> Applications. You should click on any red 'error' line where the 'faulting application is named as flightsimulator.exe and search for exception code: the google that code to interpret it. 

Just had my second crash to dektop in a week (after not experiencing any in three/four months) in the same place...just off the south east coast of the UK. 

How can I track and solve this? I've got Event Viewer but I can't see how to properly get any data out of it.

This is what I get from Event Viewer:
Faulting application name: FlightSimulator.exe, version: 1.30.12.0, time stamp: 0x63c56d8f
Faulting module name: FlightSimulator.exe, version: 1.30.12.0, time stamp: 0x63c56d8f
Exception code: 0xc0000005
Fault offset: 0x0000000000223ac3
Faulting process ID: 0x11ec
Faulting application start time: 0x01d95391f50ce87f
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.30.12.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.30.12.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report ID: 73ab0c98-559e-47d2-a24c-a818cbad9f3b
Faulting package full name: Microsoft.FlightSimulator_1.30.12.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Edited March 10, 20233 yr by BWBriscoe

Hi there,

check this out:

https://www.fsdeveloper.com/forum/threads/about-the-dreaded-exception-code-0xc0000005.449958/

What I take from this forum is, It seems to be an add on in your sim. I would try with an empty community folder.

Good luck

Mick

 

 

22 minutes ago, Micko said:

Hi there,

check this out:

https://www.fsdeveloper.com/forum/threads/about-the-dreaded-exception-code-0xc0000005.449958/

What I take from this forum is, It seems to be an add on in your sim. I would try with an empty community folder.

Good luck

Mick

 

 

0xc0000005 could be a lot of things.
This code is not telling you there is something wrong in your community folder.
It could be but it also could not be,

So referring 0xc0000005 to an issue in the community folder is nonsense

 

Edited March 11, 20233 yr by altenae

12 hours ago, BWBriscoe said:

Just had my second crash to dektop in a week (after not experiencing any in three/four months) in the same place...just off the south east coast of the UK. 

How can I track and solve this? I've got Event Viewer but I can't see how to properly get any data out of it.

This is what I get from Event Viewer:
Faulting application name: FlightSimulator.exe, version: 1.30.12.0, time stamp: 0x63c56d8f
Faulting module name: FlightSimulator.exe, version: 1.30.12.0, time stamp: 0x63c56d8f
Exception code: 0xc0000005
Fault offset: 0x0000000000223ac3
Faulting process ID: 0x11ec
Faulting application start time: 0x01d95391f50ce87f
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.30.12.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.30.12.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report ID: 73ab0c98-559e-47d2-a24c-a818cbad9f3b
Faulting package full name: Microsoft.FlightSimulator_1.30.12.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Use AddonLinker to scan ALL your addons for modellib-conflicts. Those conflicts are the reason for 0xc0000005 CTDs. It does not have to be the airports you actually fly to, but ANY airport you loaded into MSFS (community folder and official folder, including all ORBX, Contrail etc. stuff). Most devs are aware of this conflict by now and avoid it during development, but some still are not.
You have to do this after every scenery update because the updates regenerate the conflict.

In general I recommend to use AddonLinker to only load the airports you use for a given flight to minimise the risk of missing an updated "offender".