FSX Fails to Open After Installing SP2

[IADZRH 0]

I've been a long time user of FS9, but in late 2014 I decided to give FSX a try.  Before installing FSX Deluxe Edition for the first time, I made sure that my video drivers were up to speed and my hard drive was cleaned up.  I also read up on the installation of FSX just to make sure I was doing everything correctly.

 

So with that said, I successfully loaded FSX on my D:drive, and was able to do a quick fly around just to make sure everything worked correctly.  I then downloaded and successfully installed SP1, and again I was able to do a quick fly around with no problems.  I then proceeded to download SP2 and install it.  Everything seemed fine, but when I clicked on the FSX icon the splash screen would come up and after about 10-15 seconds I would get a fatal error warning and the program would shut down.

 

That was in November 2014.  After reading through the AVSIM CTD Guide v2, and doing more online research, I tried several of the recommended suggestions to fix the problem but to no avail.  I also made a few more attempts at installing FSX again, but I kept getting the same problem.  As a result, I set FSX aside and got on with real life.

 

In the past few days, I decided to give FSX another go.  I followed the How to Uninstall/Reinstall FSX directions from PMDG, made sure I had all of the MSV's and Microsoft.Net installed, updated my nVidia drivers, cleaned the registry and defraged the hard drive.  Everything went well with the installation of FSX and SP1 on my D:drive.  SP2 installed properly as well it seemed, but when I clicked on the FSX icon to open the program I had the exact same response as I did when I first installed the program.

 

Needless to say, I am rather annoyed and frustrated that I cannot get FSX to work after I install SP2.  If anyone is able to please help me solve this issue and get my FSX to successfully run, I would be most grateful.  Please see the results from the AppCrashView program below:

 

Version=1

EventType=BEX

EventTime=131026483589995944

ReportType=2

Consent=1

UploadTime=131026483590307944

ReportIdentifier=c03643d8-ebd7-11e5-b8d4-80ee73282d44

IntegratorReportIdentifier=c03643d7-ebd7-11e5-b8d4-80ee73282d44

WOW64=1

Response.BucketId=50

Response.BucketTable=5

Response.type=4

Sig[0].Name=Application Name

Sig[0].Value=fsx.exe

Sig[1].Name=Application Version

Sig[1].Value=10.0.61472.0

Sig[2].Name=Application Timestamp

Sig[2].Value=475e17d3

Sig[3].Name=Fault Module Name

Sig[3].Value=unknown

Sig[4].Name=Fault Module Version

Sig[4].Value=0.0.0.0

Sig[5].Name=Fault Module Timestamp

Sig[5].Value=00000000

Sig[6].Name=Exception Offset

Sig[6].Value=04ab3f34

Sig[7].Name=Exception Code

Sig[7].Value=c0000005

Sig[8].Name=Exception Data

Sig[8].Value=00000008

DynamicSig[1].Name=OS Version

DynamicSig[1].Value=6.1.7601.2.1.0.256.48

DynamicSig[2].Name=Locale ID

DynamicSig[2].Value=1033

UI[2]=D:\FSX\fsx.exe

UI[3]=A fatal error occurred.

UI[4]=Windows can check online for a solution to the problem.

UI[5]=Check online for a solution and close the program

UI[6]=Check online for a solution later and close the program

UI[7]=Close the program

LoadedModule[0]=D:\FSX\fsx.exe

LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll

LoadedModule[2]=C:\Windows\syswow64\kernel32.dll

LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll

LoadedModule[4]=C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL

LoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll

LoadedModule[6]=C:\Windows\syswow64\msvcrt.dll

LoadedModule[7]=C:\Windows\syswow64\GDI32.dll

LoadedModule[8]=C:\Windows\syswow64\USER32.dll

LoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dll

LoadedModule[10]=C:\Windows\SysWOW64\sechost.dll

LoadedModule[11]=C:\Windows\syswow64\RPCRT4.dll

LoadedModule[12]=C:\Windows\syswow64\SspiCli.dll

LoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dll

LoadedModule[14]=C:\Windows\syswow64\LPK.dll

LoadedModule[15]=C:\Windows\syswow64\USP10.dll

LoadedModule[16]=C:\Windows\syswow64\SHLWAPI.dll

LoadedModule[17]=C:\Windows\syswow64\ole32.dll

LoadedModule[18]=C:\Windows\system32\apphelp.dll

LoadedModule[19]=C:\Windows\AppPatch\AcGenral.DLL

LoadedModule[20]=C:\Windows\system32\UxTheme.dll

LoadedModule[21]=C:\Windows\system32\WINMM.dll

LoadedModule[22]=C:\Windows\system32\samcli.dll

LoadedModule[23]=C:\Windows\syswow64\OLEAUT32.dll

LoadedModule[24]=C:\Windows\system32\MSACM32.dll

LoadedModule[25]=C:\Windows\system32\VERSION.dll

LoadedModule[26]=C:\Windows\syswow64\SHELL32.dll

LoadedModule[27]=C:\Windows\system32\sfc.dll

LoadedModule[28]=C:\Windows\system32\sfc_os.DLL

LoadedModule[29]=C:\Windows\syswow64\USERENV.dll

LoadedModule[30]=C:\Windows\syswow64\profapi.dll

LoadedModule[31]=C:\Windows\system32\dwmapi.dll

LoadedModule[32]=C:\Windows\syswow64\SETUPAPI.dll

LoadedModule[33]=C:\Windows\syswow64\CFGMGR32.dll

LoadedModule[34]=C:\Windows\syswow64\DEVOBJ.dll

LoadedModule[35]=C:\Windows\syswow64\urlmon.dll

LoadedModule[36]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll

LoadedModule[37]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll

LoadedModule[38]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll

LoadedModule[39]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll

LoadedModule[40]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll

LoadedModule[41]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll

LoadedModule[42]=C:\Windows\syswow64\normaliz.DLL

LoadedModule[43]=C:\Windows\syswow64\iertutil.dll

LoadedModule[44]=C:\Windows\syswow64\WININET.dll

LoadedModule[45]=C:\Windows\system32\MPR.dll

LoadedModule[46]=C:\Windows\AppPatch\AcLayers.DLL

LoadedModule[47]=C:\Windows\system32\WINSPOOL.DRV

LoadedModule[48]=C:\Windows\AppPatch\AcSpecfc.DLL

LoadedModule[49]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18837_none_ec86b8d6858ec0bc\COMCTL32.dll

LoadedModule[50]=C:\Windows\system32\mscms.dll

LoadedModule[51]=C:\Windows\system32\DDRAW.dll

LoadedModule[52]=C:\Windows\system32\DCIMAN32.dll

LoadedModule[53]=C:\Windows\syswow64\COMDLG32.dll

LoadedModule[54]=C:\Windows\syswow64\IMM32.dll

LoadedModule[55]=C:\Windows\syswow64\MSCTF.dll

LoadedModule[56]=C:\Windows\syswow64\WS2_32.dll

LoadedModule[57]=C:\Windows\syswow64\NSI.dll

LoadedModule[58]=C:\Windows\system32\msi.dll

LoadedModule[59]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL

LoadedModule[60]=D:\FSX\language.dll

LoadedModule[61]=D:\FSX\API.DLL

LoadedModule[62]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll

LoadedModule[63]=D:\FSX\ablscpt.dll

LoadedModule[64]=D:\FSX\flight.dll

LoadedModule[65]=D:\FSX\ai_player.dll

LoadedModule[66]=D:\FSX\acontain.dll

LoadedModule[67]=D:\FSX\controls.dll

LoadedModule[68]=C:\Windows\system32\DINPUT8.dll

LoadedModule[69]=D:\FSX\fsui.dll

LoadedModule[70]=D:\FSX\atc.dll

LoadedModule[71]=D:\FSX\facilities.dll

LoadedModule[72]=D:\FSX\demo.dll

LoadedModule[73]=D:\FSX\main.dll

LoadedModule[74]=D:\FSX\fe.dll

LoadedModule[75]=D:\FSX\util.dll

LoadedModule[76]=D:\FSX\simprop.dll

LoadedModule[77]=D:\FSX\g2d.dll

LoadedModule[78]=C:\Windows\system32\d3dx9_34.dll

LoadedModule[79]=C:\Windows\system32\d3dx10_34.dll

LoadedModule[80]=C:\Windows\system32\d3d9.dll

LoadedModule[81]=C:\Windows\system32\d3d8thk.dll

LoadedModule[82]=D:\FSX\g3d.dll

LoadedModule[83]=D:\FSX\panels.dll

LoadedModule[84]=D:\FSX\multiplayer.dll

LoadedModule[85]=D:\FSX\ui.dll

LoadedModule[86]=D:\FSX\sound.dll

LoadedModule[87]=D:\FSX\sim1.dll

LoadedModule[88]=D:\FSX\simscheduler.dll

LoadedModule[89]=D:\FSX\visualfx.dll

LoadedModule[90]=D:\FSX\window.dll

LoadedModule[91]=D:\FSX\terrain.dll

LoadedModule[92]=D:\FSX\weather.dll

LoadedModule[93]=C:\Windows\system32\DSOUND.dll

LoadedModule[94]=C:\Windows\system32\POWRPROF.dll

LoadedModule[95]=D:\FSX\symmap.dll

LoadedModule[96]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.19061_none_72d6d48d86649709\gdiplus.dll

LoadedModule[97]=C:\Windows\system32\MSIMG32.dll

LoadedModule[98]=D:\FSX\xuipc.dll

LoadedModule[99]=D:\FSX\livingwater.dll

LoadedModule[100]=D:\FSX\fs-traffic.dll

LoadedModule[101]=D:\FSX\gps.dll

LoadedModule[102]=C:\Windows\system32\MSWSOCK.dll

LoadedModule[103]=C:\Windows\system32\SHFOLDER.dll

LoadedModule[104]=C:\Windows\system32\RICHED20.DLL

LoadedModule[105]=C:\Windows\system32\CRYPTSP.dll

LoadedModule[106]=C:\Windows\system32\rsaenh.dll

LoadedModule[107]=C:\Windows\syswow64\WINTRUST.dll

LoadedModule[108]=C:\Windows\syswow64\CRYPT32.dll

LoadedModule[109]=C:\Windows\syswow64\MSASN1.dll

LoadedModule[110]=C:\Windows\syswow64\CLBCatQ.DLL

LoadedModule[111]=C:\Windows\system32\wbem\wbemprox.dll

LoadedModule[112]=C:\Windows\system32\wbemcomn.dll

LoadedModule[113]=C:\Windows\system32\RpcRtRemote.dll

LoadedModule[114]=C:\Windows\system32\wbem\wbemsvc.dll

LoadedModule[115]=C:\Windows\system32\wbem\fastprox.dll

LoadedModule[116]=C:\Windows\system32\NTDSAPI.dll

LoadedModule[117]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9818.0_none_b7e811947b297f6d\MSXML4.DLL

LoadedModule[118]=C:\Windows\system32\dxgi.dll

LoadedModule[119]=C:\Windows\system32\d3d10.dll

LoadedModule[120]=C:\Windows\system32\d3d10core.dll

LoadedModule[121]=C:\Windows\system32\d3d11.dll

LoadedModule[122]=C:\Windows\system32\atklumdisp.dll

LoadedModule[123]=C:\Windows\system32\nvd3dum.dll

LoadedModule[124]=C:\Windows\syswow64\PSAPI.DLL

LoadedModule[125]=C:\Windows\system32\atkdx11disp.dll

LoadedModule[126]=C:\Windows\system32\nvwgf2um.dll

LoadedModule[127]=C:\Windows\system32\bcrypt.dll

LoadedModule[128]=C:\Windows\system32\D3DCompiler_34.dll

LoadedModule[129]=C:\Windows\SysWOW64\bcryptprimitives.dll

LoadedModule[130]=C:\Windows\system32\WindowsCodecs.dll

LoadedModule[131]=C:\Windows\system32\d3d10_1.dll

LoadedModule[132]=C:\Windows\system32\d3d10_1core.dll

Sec[0].Key=LCID

Sec[0].Value=1033

State[0].Key=Transport.DoneStage1

State[0].Value=1

State[1].Key=DataRequest

State[1].Value=Bucket=50/nBucketTable=5/nResponse=1/n

FriendlyEventName=Stopped working

ConsentKey=BEX

AppName=Microsoft® Flight Simulator X

AppPath=D:\FSX\fsx.exe

 

Thank you in advance for your help.  If there is any further information needed, please advise.

[pete_auau 1,153]

Could  be  wrong  here,  you shouldn't  install sp2   since  the version  you have  has   accel   included,  you would  only install  sp2  if  you havnt  got  accell.  Some  one  can  confirm this hopefuuly  soon for  you

[Jim Young 2,356]

The report indicates you have SP2 installed and you only installed FSX Deluxe.  I would uninstall SP2 and reinstall.  You do this by going to the Add/Remove Programs and selecting FSX.  It will not uninstall FSX or mess with your fsx.cfg or scenery.cfg as it was just an update.  Make sure UAC and any anti-virus program is off and then try to reinstall with admin privileges.

 

When FSX crashes during startup, it means the dll.xml is not loading a module correctly, the module is not there, or it is corrupted.  That's what happens when you first start up FSX.  Your modules are loaded.  You did not indicate if you had any addons installed.  PMDG adds a module to the dll.xml.  The fsuipc.dll adds a module.

 

Run a driver updater if you have not already.  Just a bad USB port driver could cause this problem.  I use Driver Booster which is freeware.

 

I'm a little concerned with the fact you stated you uninstalled your MSV's and dotnets.  Not good.  However, you have the proper version of Microsoft Visual C++2005 w/SP1 installed.  Good!  I did not see where Microsoft.net 1.1 or 2.0 was loaded in your crash report.  Check to make sure one of these are installed.  Microsoft.net 1.1 is installed when you first install FSX Deluxe and Windows Update will upgrade to 2.0.

 

If you have any addons that require Microsoft Visual 2008 w/SP1, then that module did not load.  Some older programs require MSV 2008 w/SP1 but it did not load.  Your crash report is the first one I've seen where MSV 2008 did not load.

 

Hope this helps.

 

Best regards,

[IADZRH 0]

JIm, thank you for taking the time to respond to my post and look into my problem.  I really appreciate it.

 

I tried the uninstall/reinstall of SP2 via the Programs and Features section of my Control Panel as suggested.  The UAC and anti-virus programs were turned off and I have full admin privileges.  Unfortunately that did not work.  One item I did notice is that if I click on the SP2 update after I have already installed it, the repair option is grayed out and I am unable to select it.  Does this mean anything?

 

Just to add a couple of clarifications.  I do not have any addons installed.  (I'm not sure if you would count nVidia Inspector as one or not.)  The UAC is always off, and I have not uninstalled any of the MSVs or .NET programs.  I did download Microsoft Visual C++ 2008 Express Edition after your post.  Hopefully that is the right version.  I can't seem to find the non-Express version.

 

I would love to paste a screen snippet here to show you the MSVs and .NET programs I have loaded, but I cannot.  Any ideas on how I can do it?  I've been struggling with this for quite some time.

 

Here is what the .NET Framework Setup Verification Utility says about my .NET frameworks:

 

[03/20/16,12:15:10] Beginning of new SetupVerifier activity logging session

[03/20/16,12:15:10] Build created on June 24, 2014

[03/20/16,12:15:10] For more information about repairing the .NET Framework, see http://support.microsoft.com/kb/2698555 and http://go.microsoft.com/fwlink/?LinkID=246062

[03/20/16,12:15:10] Activity log file location: C:\Users\MARK~1.PAR\AppData\Local\Temp\setupverifier_main_03-20-16_12.15.10.txt

[03/20/16,12:15:10] Error log file location: C:\Users\MARK~1.PAR\AppData\Local\Temp\setupverifier_errors_03-20-16_12.15.10.txt

[03/20/16,12:15:10] Detected operating system: Windows 7 (x64)

[03/20/16,12:15:10] Windows directory: C:\Windows

[03/20/16,12:15:10] System directory: C:\Windows\system32

[03/20/16,12:15:10] Program Files directory: C:\Program Files (x86)

[03/20/16,12:15:10] Common Files directory: C:\Program Files (x86)\Common Files

[03/20/16,12:15:10] Install state for .NET Framework 1.0: not installed.

[03/20/16,12:15:10] Install state for .NET Framework 1.1: installed with no service packs.

[03/20/16,12:15:10] Install state for .NET Framework 2.0: installed with service pack 2.

[03/20/16,12:15:10] Install state for .NET Framework 3.0: installed with service pack 2.

[03/20/16,12:15:10] Install state for .NET Framework 3.5: installed with service pack 1.

[03/20/16,12:15:10] Install state for .NET Framework 4 Client: installed with no service packs.

[03/20/16,12:15:10] Install state for .NET Framework 4 Full: installed with no service packs.

[03/20/16,12:15:10] Install state for .NET Framework 4.5: installed with no service packs.

[03/20/16,12:15:10] Install state for .NET Framework 4.5.1: installed with no service packs.

[03/20/16,12:15:10] Install state for .NET Framework 4.5.2: installed with no service packs.

[03/20/16,12:15:10] Not adding product '.NET Framework 1.0' because it is not currently installed

[03/20/16,12:15:10] Not adding product '.NET Framework 1.1 SP1' because it is not currently installed

[03/20/16,12:15:10] Not adding product '.NET Framework 2.0' because it is not currently installed

[03/20/16,12:15:10] Not adding product '.NET Framework 2.0 SP1' because it is not currently installed

[03/20/16,12:15:10] Not adding product '.NET Framework 3.0' because it is not currently installed

[03/20/16,12:15:10] Not adding product '.NET Framework 3.0 SP1' because it is not currently installed

[03/20/16,12:15:10] Not adding product '.NET Framework 3.5' because it is not currently installed

 

 

I also downloaded and ran Driver Booster, but the results were still the same.  SP1 works, but SP2 does not.  Thank you for the program suggestion.  Driver Booster is a nice little program.

 

Lastly, I double-checked my AppViewerCrash report after my last attempt and everything seems to be the same as what I previously posted.  I can post it again if you would like.

 

Well that is everything for now.  Any more suggestions or tips?  Thanks again for all of your help.

[Jim Young 2,356]

 

 

Everything seemed fine, but when I clicked on the FSX icon the splash screen would come up and after about 10-15 seconds I would get a fatal error warning and the program would shut down.

 

Whenever FSX fails to load to the setup screen, it means you have a corrupted, outdated, or missing module.  The first thing FSX does when it starts up is to load the dll.xml and the exe.xml.  Many developers provide updates to their modules regularly.  Most crashes occur if you have the wrong version of the FSUIPC utility as it is updated frequently to fix bugs found when products are updated such as PMDG aircraft, the RAASPRO utility, ASN, etc.

 

What got me confused was the fact your AppCrashView report appeared complete.  You would not receive a complete AppCrashView report in most cases if the sim crashed at startup.

 

Best regards,

[IADZRH 0]

It really is a strange situation.  The fact that you are seeing things that you haven't seen before is bit troubling.  I am sure there is a solution to this, but I am completely out of ideas.    Hopefully someone has a possible solution.

 

One question, in post #4 you will see the .NET framework versions listed by the Verification Utility tool.  In my Programs and Features section only .NET Framework 1.1 and 4.6.1 are showing.  Could this be a possible problem?

 

Additionally, I am not sure if this sheds anymore light on the subject, but here is what the Event Viewer is showing:

 

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: 0x0510006c

Faulting process id: 0x550

Faulting application start time: 0x01d182c1fea74ae1

Faulting application path: D:\FSX\fsx.exe

Faulting module path: unknown

Report Id: 3f05a204-eeb5-11e5-92b9-80ee73282d44

 

Thanks again.

[IADZRH 0]

Not sure if this is helpful or not, but here is what my dll.xml file is saying:

 

<?xml version="1.0" encoding="WINDOWS-1252"?>

-<SimBase.Document version="1,0" Type="Launch">

<Descr>Launch</Descr>

<Filename>dll.xml</Filename>

<Disabled>False</Disabled>

<Launch.ManualLoad>False</Launch.ManualLoad>

 

-<Launch.Addon>

<Name>Object Placement Tool</Name>

<Disabled>True</Disabled>

<ManualLoad>False</ManualLoad>

<Path>..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path>

</Launch.Addon>

 

-<Launch.Addon>

<Name>Traffic Toolbox</Name>

<Disabled>True</Disabled>

<ManualLoad>False</ManualLoad>

<Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path>

</Launch.Addon>

 

-<Launch.Addon>

<Name>Visual Effects Tool</Name>

<Disabled>True</Disabled>

<ManualLoad>False</ManualLoad>

<Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path>

</Launch.Addon>

</SimBase.Document>

 

Best regards and many thanks,

[Jim Young 2,356]

Not sure if this is helpful or not, but here is what my dll.xml file is saying:

 

The dll.xml is loading some of the tools in the SDK.  Are you a developer?  I would move the dll.xml to a temporary folder or rename it to dll.old.  It is not needed in your investigation of your CTD.

 

Did you move the dll.xml to a temporary folder and run fsx again?

 

One question, in post #4 you will see the .NET framework versions listed by the Verification Utility tool. In my Programs and Features section only .NET Framework 1.1 and 4.6.1 are showing. Could this be a possible problem?

 

FSX will use the .net the developer (Microsoft) used when they developed FSX.  FSX needs version 1.1 (which was installed when you installed FSX/Acceleration) or version 2.0.  Either version will work just as well as the other.  If you did not have 1.1 or 2.0 installed, then there would definitely be a problem.  We had one member a couple of years ago who wanted to get rid of his "old" dotnets and Microsoft Visual 2005 and 2008 as later versions had been installed on his system and he wanted to clean things up.  I told him not to do it as dotnets and MIcrosoft Visuals are not backward compatible (according to Google) but he went ahead and uninstalled the old stuff.  FSX would not start up.

 

The fact that you are seeing things that you haven't seen before is bit troubling.

 

Your crash is not abnormal.  Many members have this type of crash.  It's just that there is no solution to the problem.  You have to investigate what is happening on YOUR computer system.  What fixed a problem on a computer belonging to someone else may or may not work on your computer.  For instance, we almost have to go to the basics of computing to figure out what is wrong with your installation.  That means moving your fsx.cfg, your dll.xml, your exe.xml (if you have it), and your scenery.cfg to a temporary folder and then restart fsx.  This brings FSX back to the default installation and your fsx should now run (now that we know you have to proper Microsoft Visual and dotnet installed).  If not, then, it is a problem with Microsoft Windows as it would be impossible for it to be a problem with FSX.  This means you need to make sure your UserAccessControls are disabled and any anti-virus program is not running or scanning FSX when you run it.  If UserAccessControls were enabled when you installed FSX, this may be the problem.  If any anti-virus program was enabled when you installed FSX, this could be the problem.

 

Since you do not appear to have any addons installed, I would uninstall FSX per the uninstall guide and then reinstall it using the reinstall guide - http://support.precisionmanuals.com/kb/a87/how-to-uninstall-and-reinstall-fsx.aspx. I would do this only if deleting or moving your fsx.cfg as recommended above in this post did not fix the problem.

 

Make sure any anti-virus program has been disabled. Anti-virus programs - Bad! Make sure UserAccessControls are disabled too.

 

Best regards,

[IADZRH 0]

Just to give a brief update.  I tried all of the suggestions above from Jim in response #8, but the same results remained the same.  FSX will start, give me a fatal error message, and then shut down all after I installed SP2.  Even the AppCrashView report is exactly the same as the one posted in my original post.

 

I then uninstalled FSX as per the PMDG instructions.  I then turned off my Avast anti-virus program, and my UAC is always turned off.  I then reinstalled FSX as per the same PMDG instructions.  Everything worked fine up until I installed SP2.  After I installed SP2, the the same fatal error message would pop up and FSX would close.  The error report was exactly the same as it was before.

 

At this point in time, I have no idea what more can be done to solve this problem.  Thanks again for all of your help, and if anyone has any further suggestions I am all ears.

 

Best regards,

[Jim Young 2,356]

Do you have any FSDT or FlightBeam airports installed?  If so, download and run the latest Standalone Addon Manager.

 

What is loaded when you first startup FSX?  Answer:  All of the modules in the dll.xml and any .dll located in your main fsx directory.  Then your AI aircraft and flight plans for your AI aircraft.  Of course, your FSX.cfg.  Then all the licensing stuff for FSDT/FlightBeam airports.  Then your scenery.cfg and all of the scenery is loaded.  Any photoscenery that is enabled will load all of their scenery files (.bgl's) (that takes some time).  Simconnect will load and so will the PMDG Interface located in the PMDG\dlls\ folder.  That's about it.  No aircraft will load as you haven't selected any yet in the setup area.  So the problem is in your scenery.cfg, your dll.xml, or licensing for FSDT airports.  I had this happen to me once a year or so ago and I discovered my FSDT scenery had somehow become unlicensed and the sim would not load and crashed after the splash screen.  I downloaded the latest Standalone Addon Manager and that fixed the problem.  I do not know what you have installed but, as I stated earlier, the problem with startups is in the dll.xml or scenery.cfg.

 

You are out of options if you have moved your dll.xml and scenery.cfg to a temporary folder and the sim still does not start up.  Well, you have one option left and that would be to completely uninstall FSX and your addons, make sure everything has been removed per the PMDG install/reinstall guide, run a registry cleaner to make sure nothing is left in the registry, and then reinstall. 

 

Best regards,