Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

FSX CRASHES SHORTLY AFTER CRUISE ALT ACHIEVED

Featured Replies

Hello fellow enthusiasts.  I am a simmer for a little more than 2 years now.  I have about 2,500 hours in flying multi-engine long-haul routes in the POSKY 777-200LR.  Like you, I've invested a few thousand dollars in equipment and software, as well as 4,000 to 5,000 hours researching my way around software and computer issues, investigating add ons, furthering my understanding of flight rules and practices, and the like.  I'm mildly competent in regard to computers, but certainly no candidate for the IP team.

 

I recently acquired ActiveSky Next, and have it implemented directly (non-networked).

 

The other night, after everyone was put to bed, I planned out and began to undertake a flight from KBOS to UUEE (Moscow).  I got to cruise altitude at FL390 over Maine and then FSX crashed on me.  I have no idea why this happened, although I suspect it has something to do with my new implementation of ActiveSky Next because I've since run several test flights using the FSX-standard Jeppesen weather generator instead, and had no crash event.  That's not to say its ActiveSky's fault, because it could be an incompatibility issue, or it could be their program, or I could be completely off base.

 

I've read up on the crash issues in various forums and have taken the following steps to try to resolve this issue, to no avail:

 

- Taken ownership of all directories directly or tangentially involved with or accessed by FSX;

- AV is unable to scan the FSX and related directories;

- Win Firewall is turned off;

- UAC is turned off;

- The Vista version of uiautomationcore.dll is deposited in the FSX directory; and

- Increased UserVA to 3072 (CMD command).

 

When none of these worked, I downloaded appcrashview and generated a report on the crash, as well as located it in the Win Event Viewer and produced a copy of it's details.  Because I am weak in the area of computerese, I was hoping to lay out the details here and maybe have some of you with a stronger knowledge base look it over, as well as make recommendations.  So here is the lay of the land:

 

1. MY SPECS: Intel® Core i5-3570 @ 3.8GHz O/C | Gigabyte GA-Z77-HD3  Mobo | Nvidia GTX660 2GB Vid Card Superclocked 1046 MHz | B2330HD Samsung Display | Custom Liquid Cooled @ CPU & Multiple 120mm Fans | NZXT 650W P/S | WD 1TB 7200 RPM HD w/ 32Mb Cache | 16Gb DDR3 1333 | Win7 Pro x64 | ActiveSky Next Weather Generation | RealityXP WX500 Weather Radar | GEX North America and Europe | REX Essential + OD Textures | FSUIPC4 v. 4.90 (5/13) | FSX Gold Ed. w/ Acceleration Pkg. | World of AI | FSWidgets EFBFSX | Extreme FSX PC Tweak Tool | Posky NWA  Boeing 777-200LR (2008).

 

2. APPCRASHVIEW:

 

Version=1
EventType=AppHangB1
EventTime=130450375640775075
ReportType=3
Consent=1
UploadTime=130450375667656612
ReportIdentifier=2a7c9d57-dfe0-11e3-b91f-00038a000015
IntegratorReportIdentifier=2a7c9d58-dfe0-11e3-b91f-00038a000015
WOW64=1
Response.BucketId=651592957
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.61637.0
Sig[2].Name=Application Timestamp
Sig[2].Value=46fadb14
Sig[3].Name=Hang Signature
Sig[3].Value=f7fc
Sig[4].Name=Hang Type
Sig[4].Value=256
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
DynamicSig[22].Name=Additional Hang Signature 1
DynamicSig[22].Value=f7fc88831a14516a1a53b7dc654b9c89
DynamicSig[23].Name=Additional Hang Signature 2
DynamicSig[23].Value=f3d5
DynamicSig[24].Name=Additional Hang Signature 3
DynamicSig[24].Value=f3d55c16b65012e01598a03e518668c0
DynamicSig[25].Name=Additional Hang Signature 4
DynamicSig[25].Value=f7fc
DynamicSig[26].Name=Additional Hang Signature 5
DynamicSig[26].Value=f7fc88831a14516a1a53b7dc654b9c89
DynamicSig[27].Name=Additional Hang Signature 6
DynamicSig[27].Value=f3d5
DynamicSig[28].Name=Additional Hang Signature 7
DynamicSig[28].Value=f3d55c16b65012e01598a03e518668c0
UI[3]=Microsoft Flight Simulator® is not responding
UI[4]=Windows can check online for a solution. If you close the program, you might lose information.
UI[5]=Check for a solution and close the program
UI[6]=Check for a solution 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.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\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.18201_none_ec80f00e8593ece5\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]=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.6195_none_d09154e044272b9a\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:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\d3d9.dll
LoadedModule[81]=C:\Windows\system32\d3dx9_26.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.18120_none_72d2e82386681b36\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\CRYPTSP.dll
LoadedModule[105]=C:\Windows\system32\rsaenh.dll
LoadedModule[106]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[107]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[108]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[109]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[110]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[111]=C:\Windows\system32\wbemcomn.dll
LoadedModule[112]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[113]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[114]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[115]=C:\Windows\system32\NTDSAPI.dll
LoadedModule[116]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL
LoadedModule[117]=C:\Windows\system32\dxgi.dll
LoadedModule[118]=C:\Windows\system32\d3d11.dll
LoadedModule[119]=C:\Windows\system32\d3d9.dll
LoadedModule[120]=C:\Windows\system32\d3d8thk.dll
LoadedModule[121]=C:\Windows\system32\nvd3dum.dll
LoadedModule[122]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[123]=C:\Windows\system32\nvspcap.dll
LoadedModule[124]=C:\Windows\system32\nvapi.dll
LoadedModule[125]=C:\Windows\system32\D3DCompiler_34.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\WTSAPI32.DLL
LoadedModule[135]=C:\Windows\system32\WINSTA.dll
LoadedModule[136]=C:\Windows\SysWOW64\gameux.dll
LoadedModule[137]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll
LoadedModule[138]=C:\Windows\SysWOW64\XmlLite.dll
LoadedModule[139]=C:\Windows\SysWOW64\wer.dll
LoadedModule[140]=C:\Windows\System32\Wpc.dll
LoadedModule[141]=C:\Windows\System32\wevtapi.dll
LoadedModule[142]=C:\Windows\System32\msxml6.dll
LoadedModule[143]=C:\Windows\system32\SAMLIB.dll
LoadedModule[144]=C:\Windows\system32\netutils.dll
LoadedModule[145]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\uiautomationcore.dll
LoadedModule[146]=C:\Windows\system32\OLEACC.dll
LoadedModule[147]=C:\Windows\System32\MMDevApi.dll
LoadedModule[148]=C:\Windows\System32\PROPSYS.dll
LoadedModule[149]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[150]=C:\Windows\system32\RICHED20.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\Modules\FSWidgets\EFBFSX\EFBFSX.dll
LoadedModule[162]=C:\Windows\system32\ntmarta.dll
LoadedModule[163]=C:\Windows\syswow64\WLDAP32.dll
LoadedModule[164]=C:\Windows\system32\Secur32.dll
LoadedModule[165]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll
LoadedModule[166]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FeelThere\E170\EJetH.dll
LoadedModule[167]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[168]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.dll
LoadedModule[169]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[170]=C:\Windows\system32\WINNSI.DLL
LoadedModule[171]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\as_srv\as_btstrp.dll
LoadedModule[172]=C:\Windows\system32\mscoree.dll
LoadedModule[173]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
LoadedModule[174]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll
LoadedModule[175]=C:\Windows\assembly\NativeImages_v2.0.50727_32\mscorlib\ede2c6c842840e009f01bcc74fa4c457\mscorlib.ni.dll
LoadedModule[176]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorsec.dll
LoadedModule[177]=C:\Windows\syswow64\imagehlp.dll
LoadedModule[178]=C:\Windows\system32\ncrypt.dll
LoadedModule[179]=C:\Windows\system32\bcrypt.dll
LoadedModule[180]=C:\Windows\SysWOW64\bcryptprimitives.dll
LoadedModule[181]=C:\Windows\system32\GPAPI.dll
LoadedModule[182]=C:\Windows\system32\cryptnet.dll
LoadedModule[183]=C:\Windows\system32\SensApi.dll
LoadedModule[184]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\as_srv\as_connect.dll
LoadedModule[185]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorjit.dll
LoadedModule[186]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System\b3a78269847005365001c33870cd121f\System.ni.dll
LoadedModule[187]=C:\Windows\SysWOW64\ieframe.dll
LoadedModule[188]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll
LoadedModule[189]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll
LoadedModule[190]=C:\Windows\SysWOW64\mshtml.dll
LoadedModule[191]=C:\Windows\system32\msimtf.dll
LoadedModule[192]=C:\Windows\system32\msls31.dll
LoadedModule[193]=C:\Windows\system32\d2d1.dll
LoadedModule[194]=C:\Windows\system32\DWrite.dll
LoadedModule[195]=C:\Windows\system32\D3D10Warp.dll
LoadedModule[196]=C:\Windows\system32\MLANG.dll
LoadedModule[197]=C:\Windows\SysWOW64\uiautomationcore.dll
LoadedModule[198]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61242.0_none_e079b46b85043c20\SimConnect.dll
LoadedModule[199]=C:\Windows\system32\msadp32.acm
LoadedModule[200]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Drawing\5c24d3b0041ebf4f48a93615b9fa3de9\System.Drawing.ni.dll
LoadedModule[201]=C:\Program Files (x86)\Common Files\microsoft shared\ink\tiptsf.dll
LoadedModule[202]=C:\Windows\system32\explorerframe.dll
LoadedModule[203]=C:\Windows\system32\DUser.dll
LoadedModule[204]=C:\Windows\system32\DUI70.dll
LoadedModule[205]=C:\Windows\system32\EhStorShell.dll
LoadedModule[206]=C:\Windows\system32\ntshrui.dll
LoadedModule[207]=C:\Windows\system32\srvcli.dll
LoadedModule[208]=C:\Windows\system32\cscapi.dll
LoadedModule[209]=C:\Windows\system32\slc.dll
LoadedModule[210]=C:\Windows\System32\StructuredQuery.dll
LoadedModule[211]=C:\Windows\SysWOW64\actxprxy.dll
LoadedModule[212]=C:\Program Files (x86)\Internet Explorer\ieproxy.dll
LoadedModule[213]=C:\Windows\SysWOW64\thumbcache.dll
LoadedModule[214]=C:\Windows\system32\SHDOCVW.dll
LoadedModule[215]=C:\Windows\system32\NetworkExplorer.dll
LoadedModule[216]=C:\Windows\system32\LINKINFO.dll
LoadedModule[217]=C:\Windows\System32\drprov.dll
LoadedModule[218]=C:\Windows\System32\ntlanman.dll
LoadedModule[219]=C:\Windows\System32\davclnt.dll
LoadedModule[220]=C:\Windows\System32\DAVHLPR.dll
LoadedModule[221]=C:\Windows\system32\wkscli.dll
LoadedModule[222]=C:\Windows\system32\dfscli.dll
LoadedModule[223]=C:\Windows\system32\browcli.dll
LoadedModule[224]=C:\Windows\system32\DNSAPI.dll
LoadedModule[225]=C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live\WLIDNSP.DLL
LoadedModule[226]=C:\Windows\system32\rasadhlp.dll
LoadedModule[227]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[228]=C:\Windows\system32\dhcpcsvc6.DLL
LoadedModule[229]=C:\Windows\system32\dhcpcsvc.DLL
LoadedModule[230]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Configuration\5b6ddf934128d538cd5cd77bf4209b93\System.Configuration.ni.dll
LoadedModule[231]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Xml\d48ae2536cb914a7668e22303d484bf6\System.Xml.ni.dll
LoadedModule[232]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\BoeingGeneric.DLL
LoadedModule[233]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\XGauge.DLL
LoadedModule[234]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\rxpWX500.DLL
LoadedModule[235]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\rxpDrop.DLL
LoadedModule[236]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\NWAB777-200LR\panel\b777serv.DLL
LoadedModule[237]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\Magnetic_Compass.DLL
LoadedModule[238]=C:\Windows\system32\prnfldr.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped responding and was closed
ConsentKey=AppHangXProcB1
AppName=Microsoft Flight Simulator®
AppPath=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
ReportDescription=A problem caused this program to stop interacting with Windows.
 
3. WIN EVENT VIEWER / LOG DETAILS:
 
Log Name:      Application
Source:        Application Hang
Date:          5/20/2014 1:33:00 AM
Event ID:      1002
Task Category: (101)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      PilotSteve-PC
Description:
The program fsx.exe version 10.0.61637.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
 Process ID: c10
 Start Time: 01cf73aba7d50ecb
 Termination Time: 123
 Application Path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
 Report Id: 2a7c9d58-dfe0-11e3-b91f-00038a000015
 
Event Xml:
  <System>
    <Provider Name="Application Hang" />
    <EventID Qualifiers="0">1002</EventID>
    <Level>2</Level>
    <Task>101</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-05-20T05:33:00.000000000Z" />
    <EventRecordID>13532</EventRecordID>
    <Channel>Application</Channel>
    <Computer>PilotSteve-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>fsx.exe</Data>
    <Data>10.0.61637.0</Data>
    <Data>c10</Data>
    <Data>01cf73aba7d50ecb</Data>
    <Data>123</Data>
    <Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe</Data>
    <Data>2a7c9d58-dfe0-11e3-b91f-00038a000015</Data>
    <Binary>55006E006B006E006F0077006E0000000000</Binary>
  </EventData>
</Event>

 

I would genuinely appreciate any interpretative assistance you may be able to give in terms of how to prevent/fix this crash from reoccurring.

 

Thank you and best regards.

 

Steve, a/k/a Atteckus


Forgot to mention one more thing I tried in order to fix this on my own:

 

- Disabled wind smoothing in FSUIPC4.

 

Sorry for the omission.

 

Steve

Remove the uiautomationcore.dll from your main fsx folder. It obviously did not prevent a crash. Do you know what the uiautomationcore.dll does? It's part of the Microsoft.net Framework package which is used by developers to make sure their products run properly in the way they intended including memory management. Some individuals state they have prevented crashes by placing a Vista version of the uiautomationcore.dll in their main fsx folder. It has never worked for me and many others. In fact, many have removed this from their main fsx folder and no crashes/freezes anymore. So that's a simple fix you can try. The AVSIM CTD Guide, located to the right of this forum under Hot Spots provides more information about the uiautomationcore.dll. You will see in this forum thousands of individuals who have had freezes/crashes and they had the Vista version of the uiautomationcore.dll in their main fsx folder. So, it is not a fix but a placebo.

There are instances where the ASN program causes a freeze/crash if not properly installed. You can test to see if this is the problem by making sure no real weather is turned on during your flight. Just the default and do not use any weather that's in the default program. Just the default when you first start up FSX. It could be a simconnect issue, maybe the wrong version of the fsuipc.dll installed.

When I got unexplained freezes, it always happened at the same spot while flying from Chicago to St Louis. At cruise altitude and FSX stops working. So, I disabled my weather program (ActiveSky2012 at the time; I have ASN now) and the freezes stopped. Reinstalled the program with Admin rights and my problems went away. When things are not as simple as that, I used Process Monitor to track down my freeze. Here's how to use the process monitor:

Setting up the Process Monitor for FSX – Another investigative tool used to pin down a situation where FSX/P3D freezes, crashes, or stutters/pauses during a flight is to run a utility called Process Monitor - http://technet.microsoft.com/en-us/sysinternals/bb896645. During your flight, this utility monitors activity such as calling textures, AI aircraft schedules, ATC, weather updates, and scenery loading. When FSX/P3D stutters or FPS drop dramatically you simply write down the time it occurred. This is important as thousands of entries are made every minute, every second. Continue doing this throughout the flight. Of course, if it freezes, you will know what was going on before the sim froze. This utility will not show you a definitive cause of your issue but it will show you what add-ons were being loaded about when you received the stutter, the long pause(s), and the freeze and you can further investigate by disabling that scenery, that aircraft, or whatever might have caused the event. One member used this utility to determine that My Traffic X, version 5.4c was the cause of a BEX/StackHash/NTDLL.dll crash he was getting. It was easy to disable My Traffic X in the Scenery Library and find that FSX no longer crashed.

AVSIM recommends you do not run a flight any longer than 60 minutes as the Process Monitor log becomes quite large. For a 60 minutes flight, expect the file to be at least as large as 8GB’s or tens of millions of captured events. Make sure you delete the log or move it to another drive after you have finished your testing to free up HDD space. Another recommended tip is to make sure you use system time to mark the time of each event and do not use an external clock unless they are sync’d. Going through one minute of a glitch is a massive amount of data needed to be reviewed (it goes fast as thousands of entries just show a scenery being loaded).

To run this utility properly, you need to capture only FSX/P3D events. It would be nearly impossible to find a possible glitch if Windows events or other system activities were being logged too. AVSIM recommends opening of the Process Monitor when you are on the active runway and preparing to takeoff to save space on your HDD:

Open Process Monitor. Click on the Filter tab and then Filter….
Display entries matching these conditions:
Where it says Architecture, click on that and select “Process Name”
Go next to the blank box and click on that and select FSX or P3D.exe and make sure “Include” is shown (FSX or P3D must be running when you do this!!). Once completed, click on Add and then click OK at the bottom of the form and Go Fly.

You can use the utility while in Full Screen mode or Windowed Mode. In Windowed Mode you can monitor what is happening instantly but it is best to run Process Monitor in Full Screen (unless you are seeing freezes in Windowed Mode.

When the flight is finished, immediately go to the Process Monitor application and hit Ctrl+E on your keyboard to capture the events (event logging will continue until you do this). Shutdown FSX/P3D and begin your investigating!

 

Your problem could be a tweak too.  That's why 91% of all freezes/crashes are fixed by placing the fsx.cfg in another temporary folder, restarting FSX and letting the config rebuild.  It gets rid of those bad tweaks computer "experts" tell you is the best thing to make FSX run properly.  BufferPools, AffinityMask are two of the major culprits.  They might work okay for many but they have to be properly configured and, if not properly employed, you are going to have problems.

 

So I hope this helps you some in tracking down your freezes.  Good luck!

 

Best regards,

 

Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

  • Author

Firehawk, thank you for your time and effort.

 

Implicit in your response is the fact that the appcrash and event viewer reports don't seem to show what caused this crash -- not even the module that was involved.  I thought I was just missing something or needed to decipher a special code.

 

I will try the process monitor that you recommended.

 

I do not have an "fsx.cfg" file in my root directory.  I have 4 FSX_??????.cfg files, where the ?????? represent (i) display, (ii) scenery, (iii) terrain and (iv) Elumens.  Do you rename all 4 of these in order to have the program rebuild them?

 

Thanks.

 

Steve

The fsx.cfg is hidden and you have to open up Windows Explorer, then the Organize tab in the menu and then Folder and Search Options. In folder and search options, click on the View tab then scroll down and uncheck 'don't show hidden files, folders, or drives' and make sure Show hidden files, folders, and drives is checked. You can then get to your fsx.cfg by going to C:\Users\YourUserName\AppData\Roaming\Microsoft\FSX. If I did not understand you correctly and you are in the folder that contains your FSX.cfg, then there should be several FSX files in this folder. If you have a FSX crash, FSX will automatically make a FSX.txt file (Microsoft intended to have this file sent to them whenever you had an error but they do not provide crash support). Some software programs will make a backup FSX.cfg so that when you uninstall their program they can go back to the original. So, what you are looking for is the fsx file with the cfg extension. I can place my cursor over my files and it will show me the type of file so, if you see FSX standing alone in this folder, just place your cursor over it and if it says Type CFG, that's the one you need to move to a temporary directory, restart FSX, and see if that fixes the program. If not, you can always go back to the old file.

 

Do not delete your scenery.cfg as it won't be rebuilt. There is a scenery.cfg in the folder that has the FSX.cfg but this is a non-working or dummy config and should never be modified or deleted. The working one is located in a hidden folder in C:\Program Data\Microsoft\FSX.

 

Best regards

Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

  • Author

Bingo.  Found it and that did the trick.  Might need to rework the graphics parameters (texture sizes), but otherwise, a sweet fix.

 

Thank you Jim!!!!!

 

Steve

Glad you have found the fix.  Rebuilding the FSX.cfg is one of the best fixes for most crashes.

 

Best regards,

Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.