Been getting this now radomly over a period of about a month, well before SU9, i only fly the TBM and the FBW development version A320, some flights are just fine and then out of nowhere I get this a application error and then its back to the desktop, very very frustrating, the last one happend today just feet from touching down at LEBL after a 2hr flight in the FBW A320. My pc is quite modern running a RTX 3060 12 GB, 32.0 GB Ram, 11th Gen Intel(R) Core(TM) i7-11700F @ 2.50GHz   2.50 GHz.....it run FS2020 very very well on High end settings, I have even had it on Ultra and it runs pretty smooth, I have 4 orbx airports and vfr region 1 in my community folder. just last week I flew form Boston in the USA over the atlantic to Shannon in the A320 without an hitch, just a perfect flight but like I say some days I get the error. Any advice here would be most welcome please, I,ve been simming since 1998 so I am no novice but Im a bit stuck here and I dont know what to do.

Application Error reads:

The instruction at 0x00007FF7A23D0BC0 referenced memory at

0xFFFFFFFFFFFFFFFFF. The memory could not be read.

Click ok to terminate program

 

 

Thanks

Regards

Paul EGCC

I am getting it too, occasionally. The sim crashes and I have to start over. Usually happens after about an hour or so into the flight. Does not happen all the time though.

You may have some bad RAM.

Download a RAM / HDW checker app and run it.

You need to run the app in continuous testing mode to stress the ram the way is stressed by FS2020.

There are many apps for this on the WEB, I can't recommend one as I have not had any problems for many years now, but in the past  I have had similar issues and bad RAM chip was the cause.

I sometimes leave the test app running loops overnight. If still good in the morning then you are OK. If a bad chip shows up it will be obvious in the app.

Good luck, let us know if this helps.

I'm getting this too now. Never happened before SU9. Highly doubt my RAM is bad. I run some pretty other stressful games/programs and it doesn't happen.

32 minutes ago, flyboy0425 said:

I'm getting this too now. Never happened before SU9. Highly doubt my RAM is bad. I run some pretty other stressful games/programs and it doesn't happen.

You may well be right. But it is easy to eliminate hardware problem using these apps for stress testing.

If it is not hardware then you can start double shooting SW or SW conflicts. I used to work for Apple as a tech and this was always our approach to problems. It works well, for PCs as well. First make sure HDW is in good shape, then system software, then specific apps. 

It can be very hard to diagnose intermittent problems. If you can find a specific action or series of actions that cause the problem then it is easier. With a flight sim with so many different programs involved it is a bit of a night mare to analyze. The trick is to start with easy to eliminate factors and HDW is #1.

 

How are you CPU temps etc?  Windows updates all completed?

well thanks for your replys guys, to be honest just 5 mins ago i was goming into land into Nantes in France flying up from LEBL, 32 miles out my FS2020 just froze, so Im done with FS2020, Ill prob give it another go in a few months, its one thing after another with this simulator, as you  know it takes time setting a flight up, flightplan etc and when things like this happed I want to throw the computer threw the window....anyway hanks again guys....im going to fire up XP11 and get back into the TolissA319.

Cheers

With that error, I've read that updating .Net framework helps - there was a cumulative update in April, too.  Might have to check under optional updates.  Stick with it, Paul, we like to see the ending of the movie.

Edited May 1, 20224 yr by irocx

yeah I will, just so bloody frustrating ya know, I will try the advice you have all given me...thank you

2 hours ago, tull said:

just 5 mins ago i was goming into land into Nantes in France flying up from LEBL, 32 miles out my FS2020 just froze

I had that happen half way through a 3.5 hr. flight earlier today. Went ahead and closed Spad, FS Flight Control, TrackIR and AIG-TC on my way to closing task manager quitting MSFS. Never did as I was busy chatting with someone so just left MSFS froze. About 20mins later it started going again. Had to grab the stick and stop a dive, relaunch all those programs and ask ATC to retry with last IFR flightplan, but was able to finish my flight (another 2hrs).

I don't know what happened but MSFS was completely froze and unresponsive when it did until it finally started going again 20 mins later. I just hope it's not going to be a thing from now on.

Similar problems I have experienced. Still awaiting response (sent 22 April 2022)

Application Error 1

Log Name:      Application
Source:        Application Error
Date:          4/22/2022 9:18:00 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-H9DAHAT
Description:
Faulting application name: FlightSimulator.exe, version: 1.24.5.0, time stamp: 0x00000000
Faulting module name: CoherentUIGT.dll, version: 2.9.5.0, time stamp: 0x619d1ccf
Exception code: 0xc0000409
Fault offset: 0x000000000015dfb9
Faulting process id: 0x934
Faulting application start time: 0x01d855d902125aba
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.24.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.24.5.0_x64__8wekyb3d8bbwe\CoherentUIGT.dll
Report Id: 08a3905d-199b-42d5-bbd0-6ca4dfb200c6
Faulting package full name: Microsoft.FlightSimulator_1.24.5.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2022-04-21T23:48:00.2969863Z" />
    <EventRecordID>46380</EventRecordID>
    <Correlation />
    <Execution ProcessID="2740" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-H9DAHAT</Computer>
    <Security />
  </System>
  <EventData>
    <Data>FlightSimulator.exe</Data>
    <Data>1.24.5.0</Data>
    <Data>00000000</Data>
    <Data>CoherentUIGT.dll</Data>
    <Data>2.9.5.0</Data>
    <Data>619d1ccf</Data>
    <Data>c0000409</Data>
    <Data>000000000015dfb9</Data>
    <Data>934</Data>
    <Data>01d855d902125aba</Data>
    <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.24.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
    <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.24.5.0_x64__8wekyb3d8bbwe\CoherentUIGT.dll</Data>
    <Data>08a3905d-199b-42d5-bbd0-6ca4dfb200c6</Data>
    <Data>Microsoft.FlightSimulator_1.24.5.0_x64__8wekyb3d8bbwe</Data>
    <Data>App</Data>
  </EventData>
</Event>

 

Application Error 2

Log Name:      Application
Source:        Application Error
Date:          4/22/2022 10:55:16 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-H9DAHAT
Description:
Faulting application name: FlightSimulator.exe, version: 1.24.5.0, time stamp: 0x00000000
Faulting module name: d3d11.dll, version: 10.0.22000.527, time stamp: 0xf920f323
Exception code: 0xc0000005
Fault offset: 0x0000000000134e17
Faulting process id: 0x1ea8
Faulting application start time: 0x01d855e7519c6cb9
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.24.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Windows\SYSTEM32\d3d11.dll
Report Id: 59e2ba81-3383-45f2-83c7-e1e8d306471b
Faulting package full name: Microsoft.FlightSimulator_1.24.5.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2022-04-22T01:25:16.3731689Z" />
    <EventRecordID>46429</EventRecordID>
    <Correlation />
    <Execution ProcessID="9848" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-H9DAHAT</Computer>
    <Security />
  </System>
  <EventData>
    <Data>FlightSimulator.exe</Data>
    <Data>1.24.5.0</Data>
    <Data>00000000</Data>
    <Data>d3d11.dll</Data>
    <Data>10.0.22000.527</Data>
    <Data>f920f323</Data>
    <Data>c0000005</Data>
    <Data>0000000000134e17</Data>
    <Data>1ea8</Data>
    <Data>01d855e7519c6cb9</Data>
    <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.24.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
    <Data>C:\Windows\SYSTEM32\d3d11.dll</Data>
    <Data>59e2ba81-3383-45f2-83c7-e1e8d306471b</Data>
    <Data>Microsoft.FlightSimulator_1.24.5.0_x64__8wekyb3d8bbwe</Data>
    <Data>App</Data>
  </EventData>
</Event>

Noel Southam

noels7

 

I removed everything from my Community folder, rebooted the computer and started MSFS with the Cessna 172, so I have a vanilla MSFS. Just completed a three hour test flight with no CTD. I will start to add back in all my stuff I had in the Community folder one by one and test flight after every added mod until I get a CDT and then will hopefully know which one is causing the problem.