Hello,

 

Been having FSX problems, all CTD crashes.

 

My rig specs:

 

HP bought in 2009
Model #: p6340f
PCBRAND: Pavilion
Processor: Intel® Core2 Quad CPU Q8400 @ 2.66GHz 2.67GHz
RAM: 8.00 GB
Windows 7 64 bit OP
Graphics Card: Nvidia GeForce GTX 770 Driver Version 332.21

 

FSX Add-ons I have installed in my rig:

 

FSX Sp 1 and 2
FSUIPC4 + FSUIPC490 update
EZdok 1.17
A2A Accu-Feel V2
PMDG MD-11
FS2Crew MD-11
QW 757
Navgragh FMS Manager

 

Here are the 6 CTD messages I have in just 2 days:

 

#1

 

Log Name:      Application
Source:        Application Error
Date:          2/15/2014 8:38:41 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      GeorgeMB-PC
Description:
Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3
Faulting module name: PMDG_MD11.DLL, version: 10.0.61355.62, time stamp: 0x49b7c81d
Exception code: 0xc0000005
Fault offset: 0x00118301
Faulting process id: 0xea4
Faulting application start time: 0x01cf2a4db4bbc1d6
Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\PMDG_MD11.DLL
Report Id: 7b2fb04f-9646-11e3-99d7-00038a000015
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-02-15T13:38:41.000000000Z" />
    <EventRecordID>3763</EventRecordID>
    <Channel>Application</Channel>
    <Computer>GeorgeMB-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>fsx.exe</Data>
    <Data>10.0.61472.0</Data>
    <Data>475e17d3</Data>
    <Data>PMDG_MD11.DLL</Data>
    <Data>10.0.61355.62</Data>
    <Data>49b7c81d</Data>
    <Data>c0000005</Data>
    <Data>00118301</Data>
    <Data>ea4</Data>
    <Data>01cf2a4db4bbc1d6</Data>
    <Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe</Data>
    <Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\PMDG_MD11.DLL</Data>
    <Data>7b2fb04f-9646-11e3-99d7-00038a000015</Data>
  </EventData>
</Event>

 

 

 

#2

 

Log Name:      Application
Source:        Application Error
Date:          2/14/2014 3:47:02 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      GeorgeMB-PC
Description:
Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3
Faulting module name: A2A_Feel.dll, version: 0.0.0.0, time stamp: 0x50dc6814
Exception code: 0xc0000005
Fault offset: 0x0002af92
Faulting process id: 0x1764
Faulting application start time: 0x01cf2960ce5389b4
Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\A2A_Feel.dll
Report Id: 91fdf46b-9554-11e3-8d65-00038a000015
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-02-14T08:47:02.000000000Z" />
    <EventRecordID>3525</EventRecordID>
    <Channel>Application</Channel>
    <Computer>GeorgeMB-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>fsx.exe</Data>
    <Data>10.0.61472.0</Data>
    <Data>475e17d3</Data>
    <Data>A2A_Feel.dll</Data>
    <Data>0.0.0.0</Data>
    <Data>50dc6814</Data>
    <Data>c0000005</Data>
    <Data>0002af92</Data>
    <Data>1764</Data>
    <Data>01cf2960ce5389b4</Data>
    <Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe</Data>
    <Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\A2A_Feel.dll</Data>
    <Data>91fdf46b-9554-11e3-8d65-00038a000015</Data>
  </EventData>
</Event>

 

 

 

#3

 

Log Name:      Application

Source:        Application Error
Date:          2/14/2014 3:42:10 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      GeorgeMB-PC
Description:
Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3
Faulting module name: A2A_Feel.dll, version: 0.0.0.0, time stamp: 0x50dc6814
Exception code: 0xc0000005
Fault offset: 0x0002af92
Faulting process id: 0x120c
Faulting application start time: 0x01cf295df4175d35
Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\A2A_Feel.dll
Report Id: e3fa2cf8-9553-11e3-8d65-00038a000015
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-02-14T08:42:10.000000000Z" />
    <EventRecordID>3519</EventRecordID>
    <Channel>Application</Channel>
    <Computer>GeorgeMB-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>fsx.exe</Data>
    <Data>10.0.61472.0</Data>
    <Data>475e17d3</Data>
    <Data>A2A_Feel.dll</Data>
    <Data>0.0.0.0</Data>
    <Data>50dc6814</Data>
    <Data>c0000005</Data>
    <Data>0002af92</Data>
    <Data>120c</Data>
    <Data>01cf295df4175d35</Data>
    <Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe</Data>
    <Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\A2A_Feel.dll</Data>
    <Data>e3fa2cf8-9553-11e3-8d65-00038a000015</Data>
  </EventData>
</Event>

 

 

 

#4

 

Log Name:      Application
Source:        Application Error
Date:          2/13/2014 9:54:31 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      GeorgeMB-PC
Description:
Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x751ec9f5
Faulting process id: 0x178c
Faulting application start time: 0x01cf293005a44772
Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: unknown
Report Id: 537ebe0d-9523-11e3-8bec-00038a000015
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-02-14T02:54:31.000000000Z" />
    <EventRecordID>3394</EventRecordID>
    <Channel>Application</Channel>
    <Computer>GeorgeMB-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>fsx.exe</Data>
    <Data>10.0.61472.0</Data>
    <Data>475e17d3</Data>
    <Data>unknown</Data>
    <Data>0.0.0.0</Data>
    <Data>00000000</Data>
    <Data>c0000005</Data>
    <Data>751ec9f5</Data>
    <Data>178c</Data>
    <Data>01cf293005a44772</Data>
    <Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe</Data>
    <Data>unknown</Data>
    <Data>537ebe0d-9523-11e3-8bec-00038a000015</Data>
  </EventData>
</Event>

 

 

 

#5

 

Log Name:      Application
Source:        Application Error
Date:          2/13/2014 9:22:22 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      GeorgeMB-PC
Description:
Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x751ec9f5
Faulting process id: 0x1444
Faulting application start time: 0x01cf292b7b35f399
Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: unknown
Report Id: d589cd2f-951e-11e3-8bec-00038a000015
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-02-14T02:22:22.000000000Z" />
    <EventRecordID>3360</EventRecordID>
    <Channel>Application</Channel>
    <Computer>GeorgeMB-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>fsx.exe</Data>
    <Data>10.0.61472.0</Data>
    <Data>475e17d3</Data>
    <Data>unknown</Data>
    <Data>0.0.0.0</Data>
    <Data>00000000</Data>
    <Data>c0000005</Data>
    <Data>751ec9f5</Data>
    <Data>1444</Data>
    <Data>01cf292b7b35f399</Data>
    <Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe</Data>
    <Data>unknown</Data>
    <Data>d589cd2f-951e-11e3-8bec-00038a000015</Data>
  </EventData>
</Event>

 

 

 

#6

Log Name:      Application
Source:        Application Error
Date:          2/13/2014 9:20:32 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      GeorgeMB-PC
Description:
Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x751ec9f5
Faulting process id: 0x14d0
Faulting application start time: 0x01cf292b1ee63bce
Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: unknown
Report Id: 93bc8328-951e-11e3-8bec-00038a000015
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-02-14T02:20:32.000000000Z" />
    <EventRecordID>3356</EventRecordID>
    <Channel>Application</Channel>
    <Computer>GeorgeMB-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>fsx.exe</Data>
    <Data>10.0.61472.0</Data>
    <Data>475e17d3</Data>
    <Data>unknown</Data>
    <Data>0.0.0.0</Data>
    <Data>00000000</Data>
    <Data>c0000005</Data>
    <Data>751ec9f5</Data>
    <Data>14d0</Data>
    <Data>01cf292b1ee63bce</Data>
    <Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe</Data>
    <Data>unknown</Data>
    <Data>93bc8328-951e-11e3-8bec-00038a000015</Data>
  </EventData>
</Event>

 

I reinstalled everything on my computer 7 days ago with the hope that it would stabilize FSX, no such luck. The GeForce GTX 770 is a month old and I'm not touching it's settings at all. I do have all graphics sliders in FSX maxed out but a few settings unchecked and AI planes and airport vehicles set to zero. it was handling it so well the first few weeks I didn't see that being a issue. I didn't change anything in my FSX config file. I have made changes in the simobjects airplane folder to shut off some panels to clean up the aircraft select menu.

 

The crashes happen at different times, like today I was just changing the heading selector on the MD-11 with the mouse wheel and it crashed. Other times just flying the default Cessna 172 it crashed.

 

Thanks for any help.

 

Event ID 100 is a generic application error that doesn't really tell you much but in your case the first error has to do with the MD-11 possibly something in that is causing the crash.

Error #2 and #3 is down to an app called A2A_Feel.dll, you may need the updated version http://a2asimulations.com/forum/viewtopic.php?f=90&t=34173.

Error #4, 5 and 6 is a mismatch or possibly an illegal call to a non-existent or otherwise RAM address possibly caused by 1, 2, or 3. You might have a corrupt gauges.dll but I'm not sure.

 

Might be worth a look on the PMDG and A2A forums.

 

There may be other explanations.

pH

CTD's 4, 5, and 6 you can forget about.  They happened a couple of days ago and, so far, have not returned.  But they are indications you have serious problems with your installation.  Each one indicated you had a Memory_Access_Violation during your sessions and FSX had to quit.  CTD's 2 and 3 indicate the A2A Accu-Feel product is not functioning properly.  Make sure the dll.xml is not corrupted.  The entry in the dll.xml should look like the following:

 

<Launch.Addon>
<Name>A2A Feel</Name>
<Disabled>False</Disabled>
<Path>Modules\A2A_Feel.dll</Path>
<DllStartName>module_init</DllStartName>
<DllStopName>module_deinit</DllStopName>
</Launch.Addon>
<Launch.Addon>
<Name>AccuFeelMenu</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>Modules\AccuFeelMenu.dll</Path>
</Launch.Addon>

 

There was also an update last year to 2.09 - http://a2asimulations.com/forum/viewtopic.php?f=90&t=34173.  Make sure you have that version installed.  I have seen a lot of CTD's here with AccuFeel but not since the 2.09 update. 

 

The latest crash (#1) belongs to the PMDG MD11.  This has something to do with your Flight Management System (FMS).  It is probably because the cruise segment is missing. When you go from climb directly to descent, the FMS will crash. So just make sure you transfer the FMS to CRZ before entering an ILS.  If you saved a flight plan for the PMDG MD11, that is probably corrupted.  Delete it and rebuild a new one.

 

 

 

I have made changes in the simobjects airplane folder to shut off some panels to clean up the aircraft select menu.

 

This is dangerous as even payware needs some of the gauges and panels to function properly.  Most of the default aircraft use other panels, gauges, sound, etc. too.

 

Best regards,

CTD's 4, 5, and 6 you can forget about.  They happened a couple of days ago and, so far, have not returned.  But they are indications you have serious problems with your installation.  Each one indicated you had a Memory_Access_Violation during your sessions and FSX had to quit.  CTD's 2 and 3 indicate the A2A Accu-Feel product is not functioning properly.  Make sure the dll.xml is not corrupted.  The entry in the dll.xml should look like the following:

 

<Launch.Addon>

<Name>A2A Feel</Name>

<Disabled>False</Disabled>

<Path>Modules\A2A_Feel.dll</Path>

<DllStartName>module_init</DllStartName>

<DllStopName>module_deinit</DllStopName>

</Launch.Addon>

<Launch.Addon>

<Name>AccuFeelMenu</Name>

<Disabled>False</Disabled>

<ManualLoad>False</ManualLoad>

<Path>Modules\AccuFeelMenu.dll</Path>

</Launch.Addon>

 

There was also an update last year to 2.09 - http://a2asimulations.com/forum/viewtopic.php?f=90&t=34173.  Make sure you have that version installed.  I have seen a lot of CTD's here with AccuFeel but not since the 2.09 update. 

 

The latest crash (#1) belongs to the PMDG MD11.  This has something to do with your Flight Management System (FMS).  It is probably because the cruise segment is missing. When you go from climb directly to descent, the FMS will crash. So just make sure you transfer the FMS to CRZ before entering an ILS.  If you saved a flight plan for the PMDG MD11, that is probably corrupted.  Delete it and rebuild a new one.

 

 

 

 

This is dangerous as even payware needs some of the gauges and panels to function properly.  Most of the default aircraft use other panels, gauges, sound, etc. too.

 

Best regards,

 

 

Thanks for the replies, this all sounds terrible.

 

I'll try the A2A update, hopefully that will stabilize one issue. The MD-11 issue is weird because all I was going to do was a few traffic patterns. I didn't need to put much FMS route data other then DEP and DEST airport ICAO info. I took off no issue but then went to turn the heading knob and CTD.  I find it cool that you guys can dissect issues with FSX CTD messages, wish I understood it but it's Greek to me.

 

I have some more questions.

 

Does Memory_Access_Violation mean I have damaged RAM cards or motherboard slots? 

 

will running FSX.exe in Compatibility mode for Windows 7 help stabilize it?

 

I was told by someone in a other forum to make sure that I'm ''running with UAC turned off and run FSX from the right click menu item "run as administrator" Any app you run that touches FSX should be run the same way. The error messages all indicate an access violation which is typical if you have FSX in the default directory'' as I do. 

 

Does this UAC settings change suggestion hold water? 

 

I also been told to consider uninstalling FSX and reinstalling it but to load it into a different folder example C:\FSX instead of  C:\Program Files (x86)

 

Is uninstalling FSX and reinstalling FSX into a different folder advisable?

 

As you can see I'm not all that computer confident.

 

Well thanks again,

best regards. 

 

 

Does Memory_Access_Violation mean I have damaged RAM cards or motherboard slots?

No.  Almost all CTD's have a Memory_Access_Violation code 005.  It's very common. 

will running FSX.exe in Compatibility mode for Windows 7 help stabilize it?

Depends on what you are running.  If you are running something made for FS9 (which used XP) then you might consider running in compatibility mode.

I was told by someone in a other forum to make sure that I'm ''running with UAC turned off and run FSX from the right click menu item "run as administrator" Any app you run that touches FSX should be run the same way. The error messages all indicate an access violation which is typical if you have FSX in the default directory'' as I do.

This is exactly correct.  There are too many security features built into Windows 7 to save you from evil people around the world.  User Access Controls are used by Windows to make sure you know that software is being installed or other administrative actions are happening.  Anti-virus programs are even more dangerous as they try to prevent evil people from installing products on your system too without your permission and sometimes will have a "false positive" where it thinks a file in the installation program is a virus and will put the file into quarantine to "protect you".  Meanwhile, you get unexplained crashes because the product did not install properly with all of its required files.  Anti-virus programs - bad!

Does this UAC settings change suggestion hold water?

Yes.  Here's an excellent guide on properly installing FSX - http://support.precisionmanuals.com/KB/a87/how-to-uninstall-and-reinstall-fsx.aspx.

I also been told to consider uninstalling FSX and reinstalling it but to load it into a different folder example C:\FSX instead of C:\Program Files (x86)

I don't believe in this concept whatsoever.  I have always had mine installed in the default (x86).  I have had crashes but I can verify beyond all reasonable doubts that they were caused by something else and not my installation into the x86 folder.  But the installation guide above also suggests placing the installation into a different folder.  Either way it's okay.

Is uninstalling FSX and reinstalling FSX into a different folder advisable?

 

No.

 

My responses in red. 

 

Best regards,

I also been told to consider uninstalling FSX and reinstalling it but to load it into a different folder example C:\FSX instead of C:\Program Files (x86)

 

I don't believe in this concept whatsoever.  I have always had mine installed in the default (x86).  I have had crashes but I can verify beyond all reasonable doubts that they were caused by something else and not my installation into the x86 folder.  But the installation guide above also suggests placing the installation into a different folder.  Either way it's okay.

 

Is uninstalling FSX and reinstalling FSX into a different folder advisable?

 

No.

 

I agree with firehawk44 that if correctly configured as mentioned above you do not need to move to a different folder than default. I, however installed FSX on a different drive all together for better performance. I put my operating system on one SSD and FSX on another SSD and yes it loads very fast. I am now considering a third SSD for utilities running in the background.

I agree with firehawk44 that if correctly configured as mentioned above you do not need to move to a different folder than default. I, however installed FSX on a different drive all together for better performance. I put my operating system on one SSD and FSX on another SSD and yes it loads very fast. I am now considering a third SSD for utilities running in the background.

 

 

You must of had to use simconnect and WideFS right? Great idea but sounds very complex to set up.

You must of had to use simconnect and WideFS right? Great idea but sounds very complex to set up.

Do not know how to use simconnect or wideFS. It was very simple. Your registry will tell most where FSX lives. As far as I know, simconnect and WideFS are utilities to connect more than one computer with FSX.

 

 

Sent from my iPhone using Tapatalk.