Cfoley

I have always had problems with KSFO. I had KSFO Blue Print add on, but got rid of it because it would cause fatal errors with PMDG 747 when I would go to the fuel menu and change the fuel level while at the gate, when I went back to the screen a CTD would occur. I also have Flightbeam KSFO. But no matter what KSFO add on airport I have, I get fatal errors either on taxi, or after take off and it has been that way for years. I made 4 attempts this weekend to fly from KSFO to KJFK. The first flight was with a Level-D 767 and I was on final approach at KJFK when the fatal error took place. Actually, I was surprised I was able to fly out of the San Francisco bay area without a fatal error! Today I attempted again with a QW757 and got a fatal error over Sacramento at about 25,000 feet. I made a third attempt and got a fatal error over Reno, Nevada. And the fourth attempt I got the fatal error with Level D767 at the gate when I clicked on the add on menu button. I don't have these problems at other add on airports such as KLAX, KDFW, EGLL, etc. Just departing KSFO and it has been a constant problem for some reason. Another California airport where I get nothing but fatal errors is the FSX default Sacramento KSMF. I have never been able to land, or fly very far without a fatal error from that airport, and it is not even an add on airport! So I have KSMF off limits.

I was able to get the lights back on a 2nd try, but at a different airport.

I Already know. It has been a nightmare with GSX's June download updates. I have had nothing but continuous problems. Fatal Errors, GSX vehicles missing, UT2 disappearing in flight, some SODE issue that I am not familiar with and never heard of SODE before the latest updates placed it in my add on menu.. I regret downloading the latest update because everything was working fine before that. DX10 has been turned off. I also checked for the OC for updates and there were none.

It is DX10.

I use FSX. What is OC? I have GSX and had a lot of problems with their latest update. But I don't know if that would have caused the NAV lights not to work.

I was using my PMDG 777-200 at the FSDT add on KLAX and all the lighting on the plane would not turn on even after the APU completed and engines running. No navigations, taxi lights, or landing lights would function. I read the posts about the APU cannot handle so much power during start up, but mine would not even work during taxi and APU turned off. Did I miss anything? This is the first time this has happened.

Jim, How can you tell if it is a "StackHash" crash? I never hard that term before unit this fatal error problem this month. I don't see that word when I check the list when my FSX crashes. Cray

Jim, Thanks, I will give it a try this weekend. Also, I was in the GSX forum today and they are getting more complaints of fatal errors and Stackhash issues with the GSX June updates. I am glad it's just not my computer. All the same problems I am having. Hopefully they will get the issue resolved.

Jim, Thanks for the help you have given me. I hope you get your FSX issues fixed too. It is funny, in June 2013 and 2014, I seemed to be plagued with FSX fatal error issues, and now again in June 2016. The one in June 2013 was so bad that I gave up after a month of trouble shooting and I quit flight simming altogether in frustration until I decided to try it again around September that same year and expecting a fatal error to show up when I booted up FSX, but it didn't and as though "time" seemed to fix the problem without me doing anything to FSX. One thing I learned, I will not download any add-on "updates" until I see from forum posts later on what the outcome of those updates. There has been a couple GSX posts for the same issue I have, but only a few, so I am not alone. The "fix's" for those issues are basically the same ones that I have already done. If I had done this with GSX and saw the outcome, I would not have downloaded the update. Another strange issue is that FSDT has something called SODE 1.3.3. In my add on menu it states I have SODE 1.3.1. FSDT is telling me that 1.3.1. is not from them and I should have 1.3.3, the most current version and that should have installed in my FSX Add on menu with the latest installer. I did install from the latest full installer, but I still have 1.3.1 in my add on menu. I also had my anti virus turned off during the download. This seems to get more and more frustrating each day. Cray

Jim, I have attempted the Stand Alone several times, but it has not helped. I updated GSX last week and that is when the missing vehicles and UT2 disappearing started, but I did not get fatal errors during that time. Matter of fact, On Saturday I was able to fly from KMSP to LIRF without any fatal errors, but UT2 disappeared when I arrived over France and the link from the menu bar for UT2 was missing as well. The UT2 link came back when I restarted FSX after the flight to see if I had to download UT2 or not. The fatal errors started today for some reason. Cray

Jim, My autogen is set at normal. I noticed also if I switch screens, such as going into google, the fatal error instantly hits. I pulled up FSX with this site open and when I clicked over to this site, the fatal error occurred. It never us to do that as well. The fatal error still takes place even if I don't have another site open, it just does not hit instantly. I am convinced GSX latest download had something to do with this problem. Everything was running fine until then.

Jim, I never heard of "StackHash" before. I shut down my computer 7 times after each fatal error, but it kept coming back. I keep my FSX settings to a minimum because I had issues years ago and keep low settings that helped. For example, I keep my air traffic at 35% and weather to a low setting, etc. All this mess started with the GSX June update, which I deeply regret uploading. I am not that great with computers, so as far as my Microsoft visual settings you mentioned, I would not have a clue what to do to update that. That repair tool link you provided, it will not change my Windows 7 into Windows 10? Cray

Hi, It has been a long time since I had major Fatal Error issues. (Sometimes I will get them on long flights overseas) but now I get them just a few minutes after loading FSX. It all started when FS Dream Team came up with an update download for GSX for June 2016, which I did, and it caused GSX vehicles to disappear, or cause UT2 to disappear in flight . I sent posts to FSDT about the problem and they say it could be a Simconnect issue because of the 3rd party add ons. I have UT2, ASN, FSDT airports, and FSpassangers. I never had these issues before with GSX updates, but until the June 2016 update. But as of today, I get constant fatal errors minutes after loading an airport. I tested it several times. I would open up, for example, KSFO or KJFK, and use a default ultra light aircraft. I would fly for a few minutes and then a fatal error would show up. At first I thought ASN was causing it, but even when I did not use ASN, I still get fatal errors. I use Windows 7. I downloaded all of FSDT's GSX current downloads, including the "Stand Alone", to no avail. Attached is the APPcrash report. I could not get the Event Properties to copy. The "Copy to copy to clipboard" which I can't locate in windows 7, so I could not "copy" the event properties anywhere. I also have "System Mechanic" that I use to keep my computer system cleaned up and current, plus I empty my temp files on a regular basis. My computer system: HP 700-215xt Intel ® Core i7-4771 CPU 3.50 GHz 8.00 GB 64 Bit Version=1 EventType=APPCRASH EventTime=131110002692761245 ReportType=2 Consent=1 UploadTime=131110002694461342 ReportIdentifier=8ea1cf4c-37cd-11e6-9363-142d27d599c6 IntegratorReportIdentifier=8ea1cf4b-37cd-11e6-9363-142d27d599c6 WOW64=1 Response.BucketId=1577139987 Response.BucketTable=1 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=StackHash_0a9e 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 Code Sig[6].Value=c0000005 Sig[7].Name=Exception Offset Sig[7].Value=ffb801b7 DynamicSig[1].Name=OS Version DynamicSig[1].Value=6.1.7601.2.1.0.768.3 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=1033 DynamicSig[22].Name=Additional Information 1 DynamicSig[22].Value=0a9e DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=0a9e372d3b4ad19135b953a78882e789 DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=0a9e DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=0a9e372d3b4ad19135b953a78882e789 UI[2]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe UI[3]=Microsoft Flight Simulator® has stopped working 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]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\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.762_none_0c178a139ee2a7ed\MFC80.DLL LoadedModule[5]=C:\windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_d08cc06a442b34fc\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\system32\USERENV.dll LoadedModule[30]=C:\windows\system32\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.762_none_43efccf17831d131\MFC80ENU.DLL LoadedModule[60]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\language.dll LoadedModule[61]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\API.DLL LoadedModule[62]=C:\windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_d08cc06a442b34fc\MSVCP80.dll LoadedModule[63]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ablscpt.dll LoadedModule[64]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\flight.dll LoadedModule[65]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ai_player.dll LoadedModule[66]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\acontain.dll LoadedModule[67]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\controls.dll LoadedModule[68]=C:\windows\system32\DINPUT8.dll LoadedModule[69]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsui.dll LoadedModule[70]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\atc.dll LoadedModule[71]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\facilities.dll LoadedModule[72]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\demo.dll LoadedModule[73]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\main.dll LoadedModule[74]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fe.dll LoadedModule[75]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\util.dll LoadedModule[76]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\simprop.dll LoadedModule[77]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\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]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\g3d.dll LoadedModule[83]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\panels.dll LoadedModule[84]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\multiplayer.dll LoadedModule[85]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ui.dll LoadedModule[86]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\sound.dll LoadedModule[87]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\sim1.dll LoadedModule[88]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\simscheduler.dll LoadedModule[89]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\visualfx.dll LoadedModule[90]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\window.dll LoadedModule[91]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\terrain.dll LoadedModule[92]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\weather.dll LoadedModule[93]=C:\windows\system32\DSOUND.dll LoadedModule[94]=C:\windows\system32\POWRPROF.dll LoadedModule[95]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\symmap.dll LoadedModule[96]=C:\windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.23407_none_5c02a2f5a011f9be\gdiplus.dll LoadedModule[97]=C:\windows\system32\MSIMG32.dll LoadedModule[98]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\xuipc.dll LoadedModule[99]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\livingwater.dll LoadedModule[100]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fs-traffic.dll LoadedModule[101]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\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.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL LoadedModule[118]=c:\Program Files\WIDCOMM\Bluetooth Software\SysWOW64\BtMmHook.dll LoadedModule[119]=C:\windows\syswow64\PSAPI.DLL LoadedModule[120]=C:\windows\system32\dxgi.dll LoadedModule[121]=C:\windows\system32\d3d11.dll LoadedModule[122]=C:\windows\system32\nvd3dum.dll LoadedModule[123]=C:\windows\system32\bcrypt.dll LoadedModule[124]=C:\windows\system32\D3DCompiler_34.dll LoadedModule[125]=C:\windows\SysWOW64\bcryptprimitives.dll LoadedModule[126]=C:\windows\system32\WindowsCodecs.dll LoadedModule[127]=C:\windows\system32\d3d10_1.dll LoadedModule[128]=C:\windows\system32\d3d10_1core.dll LoadedModule[129]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll LoadedModule[130]=C:\Windows\SysWOW64\dxdiagn.dll LoadedModule[131]=C:\Windows\SysWOW64\d3d10.dll LoadedModule[132]=C:\Windows\SysWOW64\d3d10core.dll LoadedModule[133]=C:\windows\system32\winbrand.dll LoadedModule[134]=C:\windows\system32\nvapi.dll LoadedModule[135]=C:\windows\system32\WTSAPI32.DLL LoadedModule[136]=C:\windows\system32\WINSTA.dll LoadedModule[137]=C:\Windows\SysWOW64\gameux.dll LoadedModule[138]=C:\windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18837_none_41e855142bd5705d\COMCTL32.dll LoadedModule[139]=C:\Windows\SysWOW64\XmlLite.dll LoadedModule[140]=C:\Windows\SysWOW64\wer.dll LoadedModule[141]=C:\windows\System32\Wpc.dll LoadedModule[142]=C:\windows\System32\wevtapi.dll LoadedModule[143]=C:\windows\System32\msxml6.dll LoadedModule[144]=C:\windows\system32\SAMLIB.dll LoadedModule[145]=C:\windows\system32\netutils.dll LoadedModule[146]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\uiautomationcore.dll LoadedModule[147]=C:\windows\system32\OLEACC.dll LoadedModule[148]=C:\windows\System32\MMDevApi.dll LoadedModule[149]=C:\windows\System32\PROPSYS.dll LoadedModule[150]=C:\windows\system32\AUDIOSES.DLL LoadedModule[151]=C:\windows\system32\HID.DLL LoadedModule[152]=C:\windows\system32\XInput9_1_0.dll LoadedModule[153]=C:\windows\system32\wdmaud.drv LoadedModule[154]=C:\windows\system32\ksuser.dll LoadedModule[155]=C:\windows\system32\AVRT.dll LoadedModule[156]=C:\windows\system32\msacm32.drv LoadedModule[157]=C:\windows\system32\midimap.dll LoadedModule[158]=C:\windows\system32\dinput.DLL LoadedModule[159]=C:\windows\System32\wship6.dll LoadedModule[160]=C:\windows\System32\wshtcpip.dll LoadedModule[161]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\bglmanx.dll LoadedModule[162]=C:\windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll LoadedModule[163]=C:\windows\system32\MSVCP120.dll LoadedModule[164]=C:\windows\system32\MSVCR120.dll LoadedModule[165]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FsPassengers\bin\fspassengersx.dll LoadedModule[166]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\PMDG\DLLs\PMDGOptions.dll LoadedModule[167]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\PMDG_SimConnect_Ldr.dll LoadedModule[168]=C:\windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4940_none_50916076bcb9a742\MSVCP90.dll LoadedModule[169]=C:\windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4940_none_50916076bcb9a742\MSVCR90.dll LoadedModule[170]=C:\windows\WinSxS\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.1_none_dcc7eae99ad0d9cf\mfc90.dll LoadedModule[171]=C:\windows\WinSxS\x86_microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.1_none_da4695fc507e16e1\MFC90ENU.DLL LoadedModule[172]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\PMDG\DLLs\PMDGEvents.dll LoadedModule[173]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\PMDG\DLLs\PMDGSounds.dll LoadedModule[174]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\WaveLib.dll LoadedModule[175]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\LVLD.dll LoadedModule[176]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Level-D Simulations\B767-300\leveld.dll LoadedModule[177]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\PMDG\DLLs\PMDG_HUD_interface.dll LoadedModule[178]=C:\windows\system32\MSVCR100.dll LoadedModule[179]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\VistaMare\ViMaCoreX.dll LoadedModule[180]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\VistaMare\bin\VMCX_SP2.dll LoadedModule[181]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\VistaMare\bin\ViMaNET.dll LoadedModule[182]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\PMDG\DLLs\PMDG_Interface.dll LoadedModule[183]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\RAASPRO\RAASPRO.dll LoadedModule[184]=C:\windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll LoadedModule[185]=C:\Program Files (x86)\Common Files\System\ado\msado15.dll LoadedModule[186]=C:\windows\system32\MSDART.DLL LoadedModule[187]=C:\Program Files (x86)\Common Files\System\Ole DB\oledb32.dll LoadedModule[188]=C:\Program Files (x86)\Common Files\System\Ole DB\OLEDB32R.DLL LoadedModule[189]=C:\windows\system32\comsvcs.dll LoadedModule[190]=C:\windows\system32\ATL.DLL LoadedModule[191]=C:\Windows\SysWOW64\msjetoledb40.dll LoadedModule[192]=C:\Windows\SysWOW64\msjet40.dll LoadedModule[193]=C:\Windows\SysWOW64\mswstr10.dll LoadedModule[194]=C:\Windows\SysWOW64\msjter40.dll LoadedModule[195]=C:\Windows\SysWOW64\MSJINT40.DLL LoadedModule[196]=C:\Windows\SysWOW64\mstext40.dll LoadedModule[197]=C:\windows\system32\mlang.dll LoadedModule[198]=C:\windows\system32\RAASAUDIO32.DLL LoadedModule[199]=C:\windows\system32\X3DAudio1_6.dll LoadedModule[200]=C:\windows\SysWow64\xactengine3_4.dll LoadedModule[201]=C:\windows\SysWow64\XAudio2_4.dll LoadedModule[202]=C:\Program Files (x86)\12bPilot\SODE\SimObjectAnimationModule.dll LoadedModule[203]=C:\windows\syswow64\imagehlp.dll LoadedModule[204]=C:\windows\system32\GPAPI.dll LoadedModule[205]=C:\windows\system32\asycfilt.dll LoadedModule[206]=C:\windows\system32\Secur32.dll LoadedModule[207]=C:\windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll LoadedModule[208]=C:\windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll LoadedModule[209]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.dll LoadedModule[210]=C:\windows\system32\IPHLPAPI.DLL LoadedModule[211]=C:\windows\system32\WINNSI.DLL LoadedModule[212]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\as_srv\as_btstrp.dll State[0].Key=Transport.DoneStage1 State[0].Value=1 State[1].Key=DataRequest State[1].Value=Bucket=1577139987/nBucketTable=1/nResponse=1/n FriendlyEventName=Stopped working ConsentKey=APPCRASH AppName=Microsoft Flight Simulator® AppPath=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

I have Windows 7. I did not make any tweeks to fsx/cfg or any type of changes. Maybe it was just this one time thing that happened. I did do a flight from KLAS to KJFK yesterday and there was no scenery issues. If I do a repeat of the same one from KATL to KLAS and it it appears over Arkansas again, I guess something could be corrupted.

Thank you for the instructions how to do this image.

Sorry, I have not been able to respond for the KDFW problem and almost forgot about it due to other issues and lately I am unable able to spend much time with FSX for the past few weeks. I try and check AVSIM messages when I can. It seems like half the time is spent trouble shooting than flight simulating. I could not resolve the KDFW issue. If it gets too complex, it causes new problems to try and fix. Fortunately it is only KDFW that is the problem. I am not that good with software issues. I do have a screenshot of the black squares, but I am unable to attach the image because AVSIM wants a "URL"? I remember there use to be an easy link to attach images.

I had something strange that never occured before out of my 4 years of FSX flight simulating. While doing a flight from KATL to KLAS at 34,000 feet, which I have done several times in the past, over Arkansas, a long portion of the state over my route was covered with black squares below me. I checked the forums and the only thing I could find is that it could have been caused by DX10 or FTX Global, which I don't use. I do keep my computer updated and defragmated regularly and use System Mechanic. While this was the first time that it happened and hopefuly will not a to be a cronic problem, can anyone tell me what could have caused it? The black squares seemed to be mixed in with the clouds and I do use Active Sky Next.

I made a mental note never to purchase anything from Imaginesim again. They have lousy troubleshooting help.

I now longer use the PMDG 737. I get too many fatal errors with them.

Jim, I thought the same thing. I recall that PMDG has settings to disable failures. I will need to check. Cray

JIm, Thanks for the help. i attempted another flight with PMDG 737-900 NGX from KLAX to PANC with ASN. It was 5 hours. It went smoothly and I used your suggestions with the settings in ASN. But get this, when I was attempting to land, the landing gear would not come down. I used FS Passengers on this flight and the FS Passengers pilot voice said there is some type of malfunction when I attempted to put the landing gear down. I did have FSX failures disabled and did not use GSX ground services. Actually, I can't use GSX with the PMDG 737 because the auto pilot will not work. No big deal though. I had to belly land the plane on the runway. Don't know what would have caused this. Never happened before. Funny how one ploblem after another seems to crop up. Cray

Another new problem. GSX Ground services now have no sound. I wonder if ASN had anything to do with this new problem?

In my research, I cannot find any type of "Updated" software for FSGlobal Weaher. Just the download.

Jim, I am afraid I don't know what REX or FEX is or where it is located. They can be adjusted? I did not make any changes in the ASN settings. Everyting was set when I purchased. As for that flight from KLAX to KSEA with QW757 (The only plane that has good VAS and no fatal errors), my VAS at the start was 68 In flight it was around 123, and 55 at landing. Without ASN, it would usually be aroud 230. Both are add on airports, so I know those would take a hit, but not with QW757. Update: I found out that REX is a weather add on. I thought it was a file in FSX for weather, etc. I don't have REX. I guess FEX is also another weather add on? Other than FSGlobal Weather, and now ASN, I don't have any other weather add on. And as for FSX weather, I have it set as what I mentioned in my above post. Pretty much to a minimum. Sincerely, Cray

Update what software? Windows 7?