IADZRH

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,

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,

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.

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.

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.

First time poster, long time reader. :smile: Last May I ended up getting a new computer after my old one died. The specs of my current computer are as follows: Shuttle SH67H3 Intel Core i7/i5/i3 Intel Socket H2 Barebone Intel Core i5-3570K Ivy Bridge 3.40GHz Quad Core 8GB RAM GeForce GTX550 Ti 1GB Windows 7 Professional SP1 It seems that since I got this new computer, FS9 continues to run in the background even though I have closed the program by either hitting the X in upper right-hand corner or by selecting End Flight. The only way that I can close FS9 completely is by going into Windows Task Master, selecting FS9.exe under the Process Tab, and then clicking the End Process button. Over time things would continue to get worse. When I had FSUIPC installed, I would receive a message that duplicate FUIPCs were installed and the program would not start - it would just hang on the splash screen. When I went to the Task Master window it would say that FS9 was not responding. If I closed the program using the previously mentioned method in the Process Tab, FS9 would restart. It eventually got so bad that FS9 would never restart. So I decided to uninstall FS9 and start anew. (I even did a disk clean and a disk defrag after uninstalling.) After a lot or reading, here is what I have done so far. I reinstalled FS9 under a separate folder called Program Files on my D-drive. (I did not install it under the default folder.) I installed the FS9.1 Upgrade as instructed. I then made the program Large Address Aware using the 4g patch and CFF Explorer. I also made sure that FS9 was being run as an administrator. Unfortunately after all that, FS9 still continues to run in the background after closing and will only close completely if I go into the Task Master program. I am obviously rather frustrated and out of ideas on how to solve this problem. Does anyone have any possible solutions to this problem? If anyone can help me solve this problem, I would be most grateful. I really would like to get back to rebuilding my FS9 and actually flying it as opposed to dealing with this annoying problem. Thank you in advance for any help you might be able to give. PS I hope that this is the right forum. If it is not, please advise. PPS Once I am in FS9, it runs beautifully and is very stable. I am sorry to do this, but I did forget something. When I first ran the fresh install of FS9, I received the following error upon closing from Microsoft: Files that help describe the problem: C:\Users\xxx\AppData\Roaming\Microsoft\FS9\fs9.CFG.txt C:\Users\xxx\AppData\Roaming\Microsoft\FS9\dxdiag.xml C:\Users\xxx\AppData\Roaming\Microsoft\FS9\scenery.cfg C:\Users\xxx\AppData\Local\Temp\WERFDA1.tmp.WERInternalMetadata.xml C:\Users\xxx\AppData\Local\Temp\WER13A1.tmp.appcompat.txt C:\Users\xxx\AppData\Local\Temp\WER144E.tmp.mdmp I hope that this additional info might help.