Help with FSX CTD

[mrlip 54]

Hi All

 

I am hoping for some help with a CTD issue I am having with FSX (standalone version). This has occured whilst flying EGLL-OMDB with the PMDG T7. I had flown KORD-EGLL previously last week and had no issues, also with the PMDG T7. I had done a couple of flights prior to that also with the T7 and NGX, all with no issues. I did have some CTD's earlier in the year with the T7 and from what I remember they usually occured when in Europe rather than NA. The flight today crashed about 2 hours in so I reloaded, it carried on for an hour then crashed again. The faulting module path are unknown although when I exited after the second crash it did point to terrain.dll as the faulting module. Logs are below, please let me know if other details are needed.

 

(Crash 1)

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000000f7
Faulting process id: 0xfb0
Faulting application start time: 0x01d1a90c5c89f169
Faulting application path: D:\FSX\fsx.exe
Faulting module path: unknown
Report Id: 1661e326-1514-11e6-8e67-8aff6bb15baf

 

(Crash 2)

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000004
Faulting process id: 0x774
Faulting application start time: 0x01d1a927e9cdb05e
Faulting application path: D:\FSX\fsx.exe
Faulting module path: unknown
Report Id: bf7c114b-1521-11e6-b37a-c3b6e32b90a0

 

(Crash 3, seemed to occur when exiting from crash 2)

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: terrain.dll, version: 10.0.61637.0, time stamp: 0x46fadb59
Exception code: 0xc0000005
Fault offset: 0x0005595e
Faulting process id: 0x774
Faulting application start time: 0x01d1a927e9cdb05e
Faulting application path: D:\FSX\fsx.exe
Faulting module path: D:\FSX\terrain.dll
Report Id: 8d5651ba-1525-11e6-b37a-c3b6e32b90a0

[Jim Young 2,356]

The terrain.dll CTD is the only clue in your crash reports.  This indicates high scenery/terrain settings, especially Autogen.  This crash usually occurs occasionally depending on many things such as the aircraft flying, the flight plan, weather, and whether you are arriving at eye-candy commercial scenery (which take up a lot of resources).  Try it again without Autogen or Autogen set to normal.  If you have any tweaks, then move your fsx.cfg to a temporary folder and restart fsx and the config will be rebuilt.  Leave your settings at the default except you can change the monitor resolution in the settings and make sure AA/AF are enabled and, if you like DX10 preview, it is turned on.  You might want to monitor VAS (see page 15, AVSIM CTD Guide) because, when you run out of VAS or get low on VAS, all kinds of nasty things start happening to your simulator.  If, after a long flight and your VAS is down to somewhere between 200 and 500 MB's, it indicates you are almost out of VAS and you won't be able to run long flight anymore w/o the possibility of a freeze or CTD.

[mrlip 54]

The terrain.dll CTD is the only clue in your crash reports.  This indicates high scenery/terrain settings, especially Autogen.  This crash usually occurs occasionally depending on many things such as the aircraft flying, the flight plan, weather, and whether you are arriving at eye-candy commercial scenery (which take up a lot of resources).  Try it again without Autogen or Autogen set to normal.  If you have any tweaks, then move your fsx.cfg to a temporary folder and restart fsx and the config will be rebuilt.  Leave your settings at the default except you can change the monitor resolution in the settings and make sure AA/AF are enabled and, if you like DX10 preview, it is turned on.  You might want to monitor VAS (see page 15, AVSIM CTD Guide) because, when you run out of VAS or get low on VAS, all kinds of nasty things start happening to your simulator.  If, after a long flight and your VAS is down to somewhere between 200 and 500 MB's, it indicates you are almost out of VAS and you won't be able to run long flight anymore w/o the possibility of a freeze or CTD.

 

Hi Jim.

 

I have autogen set to normal at the minute, I can try it without autogen to see if that works. I already montor VAS as I know about the trouble OOM can cause. if I remember rightly I think I had around 1.2GB VAS remaining when it crashed. I only enable add-on scenery for the 2 airports i am flying between to try help VAS as well.

 

I think I will try rebuilding the fsx.cfg as well. Can you just remind me what are the 'must have' tweaks that need adding back in? I seem to remember highmemfix is one? Also, if I delete my fsx.cfg will I lose my keyboard commands that I have customised?

 

Thanks for your help.

[Jim Young 2,356]

 

 

I think I will try rebuilding the fsx.cfg as well. Can you just remind me what are the 'must have' tweaks that need adding back in? I seem to remember highmemfix is one? Also, if I delete my fsx.cfg will I lose my keyboard commands that I have customised?

 

The only thing to add to the fsx.cfg is in the Graphics section - highmemfix=1 (which is not a tweak but an actual fix).

 

Again, I would leave your settings at the default or as close as to the default just for testing purposes.  If you moved your fsx.cfg to a temp folder, you can return it if you want.  I would not mess with any other settings or configurations like just enabling your departure/arrival airports.  You are testing your fsx.cfg to see if that was the problem and, if you disable other stuff, you won't know whether it was the config or the other stuff you disabled.

 

The fsx.cfg will not mess with your keyboard or joystick settings.  Those are in the standard.xml in your main fsx folder.

[mrlip 54]

The only thing to add to the fsx.cfg is in the Graphics section - highmemfix=1 (which is not a tweak but an actual fix).

 

Again, I would leave your settings at the default or as close as to the default just for testing purposes.  If you moved your fsx.cfg to a temp folder, you can return it if you want.  I would not mess with any other settings or configurations like just enabling your departure/arrival airports.  You are testing your fsx.cfg to see if that was the problem and, if you disable other stuff, you won't know whether it was the config or the other stuff you disabled.

 

The fsx.cfg will not mess with your keyboard or joystick settings.  Those are in the standard.xml in your main fsx folder.

 

Ok, done, I have rebuilt the FSX.cfg file and loaded the flight back up to try again. Will report back

[mrlip 54]

Crashed again after about 45 mins of flying Reports below 

 

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x465962cc
Faulting process id: 0xd38
Faulting application start time: 0x01d1a943312bd531
Faulting application path: D:\FSX\fsx.exe
Faulting module path: unknown
Report Id: c545fe18-153d-11e6-ad16-abdc5a017e93

 

Version=1
EventType=BEX
EventTime=131072001739405817
ReportType=2
Consent=1
UploadTime=131072001740545883
ReportIdentifier=c545fe19-153d-11e6-ad16-abdc5a017e93
IntegratorReportIdentifier=c545fe18-153d-11e6-ad16-abdc5a017e93
WOW64=1
Response.BucketId=2564907304
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=Fault Module Name
Sig[3].Value=StackHash_2264
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=465962cc
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.1
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=2057
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=2264
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=2264db07e74365624c50317d7b856ae9
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=875f
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=875fa2ef9d2bdca96466e8af55d1ae6e
UI[2]=D:\FSX\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]=D:\FSX\fsx.exe
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
LoadedModule[3]=C:\Program Files (x86)\AVG\Av\avghookx.dll
LoadedModule[4]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL
LoadedModule[6]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll
LoadedModule[7]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[8]=C:\Windows\syswow64\GDI32.dll
LoadedModule[9]=C:\Windows\syswow64\USER32.dll
LoadedModule[10]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[11]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[12]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[13]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[14]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[15]=C:\Windows\syswow64\LPK.dll
LoadedModule[16]=C:\Windows\syswow64\USP10.dll
LoadedModule[17]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[18]=C:\Windows\syswow64\ole32.dll
LoadedModule[19]=C:\Windows\system32\apphelp.dll
LoadedModule[20]=C:\Windows\AppPatch\AcGenral.DLL
LoadedModule[21]=C:\Windows\system32\UxTheme.dll
LoadedModule[22]=C:\Windows\system32\WINMM.dll
LoadedModule[23]=C:\Windows\system32\samcli.dll
LoadedModule[24]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[25]=C:\Windows\system32\MSACM32.dll
LoadedModule[26]=C:\Windows\system32\VERSION.dll
LoadedModule[27]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[28]=C:\Windows\system32\sfc.dll
LoadedModule[29]=C:\Windows\system32\sfc_os.DLL
LoadedModule[30]=C:\Windows\syswow64\USERENV.dll
LoadedModule[31]=C:\Windows\syswow64\profapi.dll
LoadedModule[32]=C:\Windows\system32\dwmapi.dll
LoadedModule[33]=C:\Windows\syswow64\SETUPAPI.dll
LoadedModule[34]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[35]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[36]=C:\Windows\syswow64\urlmon.dll
LoadedModule[37]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll
LoadedModule[38]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll
LoadedModule[39]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll
LoadedModule[40]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll
LoadedModule[41]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll
LoadedModule[42]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll
LoadedModule[43]=C:\Windows\syswow64\normaliz.DLL
LoadedModule[44]=C:\Windows\syswow64\iertutil.dll
LoadedModule[45]=C:\Windows\syswow64\WININET.dll
LoadedModule[46]=C:\Windows\system32\MPR.dll
LoadedModule[47]=C:\Windows\AppPatch\AcLayers.DLL
LoadedModule[48]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[49]=C:\Windows\AppPatch\AcSpecfc.DLL
LoadedModule[50]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18837_none_ec86b8d6858ec0bc\COMCTL32.dll
LoadedModule[51]=C:\Windows\system32\mscms.dll
LoadedModule[52]=C:\Windows\system32\DDRAW.dll
LoadedModule[53]=C:\Windows\system32\DCIMAN32.dll
LoadedModule[54]=C:\Windows\syswow64\COMDLG32.dll
LoadedModule[55]=C:\Windows\syswow64\IMM32.dll
LoadedModule[56]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[57]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[58]=C:\Windows\syswow64\NSI.dll
LoadedModule[59]=C:\Windows\system32\msi.dll
LoadedModule[60]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL
LoadedModule[61]=D:\FSX\language.dll
LoadedModule[62]=D:\FSX\API.DLL
LoadedModule[63]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll
LoadedModule[64]=D:\FSX\ablscpt.dll
LoadedModule[65]=D:\FSX\flight.dll
LoadedModule[66]=D:\FSX\ai_player.dll
LoadedModule[67]=D:\FSX\acontain.dll
LoadedModule[68]=D:\FSX\controls.dll
LoadedModule[69]=C:\Windows\system32\DINPUT8.dll
LoadedModule[70]=D:\FSX\fsui.dll
LoadedModule[71]=D:\FSX\atc.dll
LoadedModule[72]=D:\FSX\facilities.dll
LoadedModule[73]=D:\FSX\demo.dll
LoadedModule[74]=D:\FSX\main.dll
LoadedModule[75]=D:\FSX\fe.dll
LoadedModule[76]=D:\FSX\util.dll
LoadedModule[77]=D:\FSX\simprop.dll
LoadedModule[78]=D:\FSX\g2d.dll
LoadedModule[79]=C:\Windows\system32\d3dx9_34.dll
LoadedModule[80]=C:\Windows\system32\d3dx10_34.dll
LoadedModule[81]=C:\Windows\system32\d3d9.dll
LoadedModule[82]=C:\Windows\system32\d3d8thk.dll
LoadedModule[83]=D:\FSX\g3d.dll
LoadedModule[84]=D:\FSX\panels.dll
LoadedModule[85]=D:\FSX\multiplayer.dll
LoadedModule[86]=D:\FSX\ui.dll
LoadedModule[87]=D:\FSX\sound.dll
LoadedModule[88]=D:\FSX\sim1.dll
LoadedModule[89]=D:\FSX\simscheduler.dll
LoadedModule[90]=D:\FSX\visualfx.dll
LoadedModule[91]=D:\FSX\window.dll
LoadedModule[92]=D:\FSX\terrain.dll
LoadedModule[93]=D:\FSX\weather.dll
LoadedModule[94]=C:\Windows\system32\DSOUND.dll
LoadedModule[95]=C:\Windows\system32\POWRPROF.dll
LoadedModule[96]=D:\FSX\symmap.dll
LoadedModule[97]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.23407_none_5c02a2f5a011f9be\gdiplus.dll
LoadedModule[98]=C:\Windows\system32\MSIMG32.dll
LoadedModule[99]=D:\FSX\xuipc.dll
LoadedModule[100]=D:\FSX\livingwater.dll
LoadedModule[101]=D:\FSX\fs-traffic.dll
LoadedModule[102]=D:\FSX\gps.dll
LoadedModule[103]=C:\Windows\system32\MSWSOCK.dll
LoadedModule[104]=C:\Windows\system32\SHFOLDER.dll
LoadedModule[105]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[106]=C:\Windows\system32\rsaenh.dll
LoadedModule[107]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL
LoadedModule[108]=C:\Windows\system32\dxgi.dll
LoadedModule[109]=C:\Windows\system32\d3d11.dll
LoadedModule[110]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[111]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[112]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[113]=C:\Windows\system32\nvd3dum.dll
LoadedModule[114]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[115]=C:\Windows\system32\bcrypt.dll
LoadedModule[116]=C:\Windows\system32\D3DCompiler_34.dll
LoadedModule[117]=C:\Windows\SysWOW64\bcryptprimitives.dll
LoadedModule[118]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[119]=C:\Windows\system32\d3d10_1.dll
LoadedModule[120]=C:\Windows\system32\d3d10_1core.dll
LoadedModule[121]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[122]=C:\Windows\SysWOW64\dxdiagn.dll
LoadedModule[123]=C:\Windows\SysWOW64\d3d10.dll
LoadedModule[124]=C:\Windows\SysWOW64\d3d10core.dll
LoadedModule[125]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[126]=C:\Windows\system32\wbemcomn.dll
LoadedModule[127]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[128]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[129]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[130]=C:\Windows\system32\NTDSAPI.dll
LoadedModule[131]=C:\Windows\system32\winbrand.dll
LoadedModule[132]=C:\Windows\system32\WTSAPI32.DLL
LoadedModule[133]=C:\Windows\system32\WINSTA.dll
LoadedModule[134]=C:\Windows\SysWOW64\gameux.dll
LoadedModule[135]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18837_none_41e855142bd5705d\COMCTL32.dll
LoadedModule[136]=C:\Windows\SysWOW64\XmlLite.dll
LoadedModule[137]=C:\Windows\SysWOW64\wer.dll
LoadedModule[138]=C:\Windows\System32\Wpc.dll
LoadedModule[139]=C:\Windows\System32\wevtapi.dll
LoadedModule[140]=C:\Windows\System32\msxml6.dll
LoadedModule[141]=C:\Windows\system32\SAMLIB.dll
LoadedModule[142]=C:\Windows\system32\netutils.dll
LoadedModule[143]=D:\FSX\uiautomationcore.dll
LoadedModule[144]=C:\Windows\system32\OLEACC.dll
LoadedModule[145]=C:\Windows\System32\MMDevApi.dll
LoadedModule[146]=C:\Windows\System32\PROPSYS.dll
LoadedModule[147]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[148]=C:\Windows\system32\RICHED20.DLL
LoadedModule[149]=C:\Windows\system32\HID.DLL
LoadedModule[150]=C:\Windows\system32\XInput9_1_0.dll
LoadedModule[151]=C:\Windows\system32\wdmaud.drv
LoadedModule[152]=C:\Windows\system32\ksuser.dll
LoadedModule[153]=C:\Windows\system32\AVRT.dll
LoadedModule[154]=C:\Windows\system32\msacm32.drv
LoadedModule[155]=C:\Windows\system32\midimap.dll
LoadedModule[156]=C:\Windows\system32\dinput.DLL
LoadedModule[157]=C:\Windows\System32\wship6.dll
LoadedModule[158]=C:\Windows\System32\wshtcpip.dll
LoadedModule[159]=C:\Windows\system32\msadp32.acm
LoadedModule[160]=C:\Windows\SysWOW64\ieframe.dll
LoadedModule[161]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll
LoadedModule[162]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll
LoadedModule[163]=C:\Windows\system32\Secur32.dll
LoadedModule[164]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll
LoadedModule[165]=C:\Windows\SysWOW64\mshtml.dll
LoadedModule[166]=C:\Windows\system32\msimtf.dll
LoadedModule[167]=C:\Windows\system32\msls31.dll
LoadedModule[168]=C:\Windows\system32\d2d1.dll
LoadedModule[169]=C:\Windows\system32\DWrite.dll
LoadedModule[170]=C:\Windows\system32\D3D10Warp.dll
LoadedModule[171]=C:\Windows\system32\MLANG.dll
LoadedModule[172]=C:\Windows\system32\ntmarta.dll
LoadedModule[173]=C:\Windows\syswow64\WLDAP32.dll
LoadedModule[174]=C:\Windows\SysWOW64\uiautomationcore.dll
LoadedModule[175]=C:\Windows\syswow64\imagehlp.dll
LoadedModule[176]=C:\Windows\system32\GPAPI.dll
LoadedModule[177]=D:\FSX\GAUGES\PMDG_777X.DLL
LoadedModule[178]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[179]=C:\Windows\system32\NETAPI32.dll
LoadedModule[180]=C:\Windows\system32\srvcli.dll
LoadedModule[181]=C:\Windows\system32\wkscli.dll
LoadedModule[182]=C:\Windows\system32\WSOCK32.dll
LoadedModule[183]=C:\Windows\SysWow64\XAudio2_7.dll
LoadedModule[184]=D:\FSX\Gauges\PMDG_777X_2.dll
LoadedModule[185]=C:\Windows\system32\iphlpapi.dll
LoadedModule[186]=C:\Windows\system32\WINNSI.DLL
LoadedModule[187]=C:\Windows\system32\snmpapi.dll
LoadedModule[188]=C:\Windows\system32\NLAapi.dll
LoadedModule[189]=C:\Windows\system32\napinsp.dll
LoadedModule[190]=C:\Windows\system32\pnrpnsp.dll
LoadedModule[191]=C:\Windows\system32\DNSAPI.dll
LoadedModule[192]=C:\Windows\System32\winrnr.dll
LoadedModule[193]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[194]=C:\Windows\system32\rasadhlp.dll
LoadedModule[195]=C:\Windows\system32\icmp.Dll
LoadedModule[196]=D:\FSX\FS2Crew2010\Versions\PMDG777\Gauges\FS2Crew777.GAU
LoadedModule[197]=D:\FSX\libcurl.dll
LoadedModule[198]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCP90.dll
LoadedModule[199]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll
LoadedModule[200]=C:\Windows\system32\FS2AUDIO.dll
LoadedModule[201]=C:\Windows\system32\X3DAudio1_6.dll
LoadedModule[202]=C:\Windows\SysWow64\xactengine3_4.dll
LoadedModule[203]=C:\Windows\SysWow64\XAudio2_4.dll
LoadedModule[204]=C:\Windows\system32\dhcpcsvc6.DLL
LoadedModule[205]=C:\Windows\System32\netprofm.dll
LoadedModule[206]=C:\Windows\system32\dhcpcsvc.DLL
LoadedModule[207]=C:\Windows\System32\npmproxy.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=DataRequest
State[1].Value=Bucket=-1730059992/nBucketTable=5/nResponse=1/n
FriendlyEventName=Stopped working
ConsentKey=BEX
AppName=Microsoft Flight Simulator®
AppPath=D:\FSX\fsx.exe
 

[Jim Young 2,356]

Remove the uiautomationcore.dll from your main fsx folder.

 

Best regards,

[mrlip 54]

Ok will do, will try that tonight.

 

Just out of interest, what in the error report is pointing to that?

[mrlip 54]

Well.........removed UIautomationcore.dll from my FSX folder, reloaded the last FSUIPC autosave of the flight from yesterday.......and so far 2 hours further, all seems well!

 

How strange?! I have had the uiautomationcore.dll file in my FSX folder for a long time and as I said yesterday, I did a long haul flight in the PMDG T7 just last week without issue.

 

I am going to do EGLL-WSSS at the weekend I think so will report back if any issues.

 

Thanks for all your help Jim!

[Jim Young 2,356]

 

 

Well.........removed UIautomationcore.dll from my FSX folder, reloaded the last FSUIPC autosave of the flight from yesterday.......and so far 2 hours further, all seems well!

 

Glad it worked!  Many people do not realize the uiautomationcore.dll is part of Microsoft.net which is continually updated to fix bugs.  When you load a really old module like this file in your main fsx folder, it might conflict with the system uiautomationcore.dll that was updated to fix bugs.  I have never had this module in my main fsx folder and have never ever had problems with menu crashes.

 

Best regards,

[mrlip 54]

Hi JIm

Just an update, I managed to complete London - Singapore last night without any trouble which is great! Sim was running for about 13.5 hours total. I then went to do a second leg (without closing the sim) of Singapore - Sydney but after an hour or so into the flight I had a CTD and the sim rebooted. The faulting module was gdiplus.dll which I think is a new one that I personally haven't seen before! Details below (I can post the full log if needed).

 

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: gdiplus.dll, version: 6.1.7601.23407, time stamp: 0x56fac8b2
Exception code: 0xc0000005
Fault offset: 0x00099b8d
Faulting process id: 0x10c4
Faulting application start time: 0x01d1ae1aad5d6a9e
Faulting application path: D:\FSX\fsx.exe
Faulting module path: C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.23407_none_5c02a2f5a011f9be\gdiplus.dll
Report Id: 192df23c-1a8c-11e6-b01c-954c86a978a5

 

Any thoughts?

[Jim Young 2,356]

You have a later version than me.  Mine is 6.1.7601.23265.  You might have gotten a security update via Windows Update.  Probably means nothing but sometimes Windows Updates are buggy.

 

I would run the System File Checker (page 13, AVSIM CTD Guide) to see if it finds any corrupted or missing Windows files.  GDIPlus interacts with device drivers on behalf of applications so you want to make sure all of your device drivers are up-to-date (page 14, AVSIM CTD Guide). 

 

Hope this helps.

 

Best regards,

[mrlip 54]

I ran Windows update and downloaded several security updates last week so it may have been in that.

I will run SFC now and check all my drivers are up to date, hopefully that will sort any remaining issues.

Thanks

[mrlip 54]

Well after a couple of flights (both short and long haul) without issue I thought my problems were fixed. However last flight I had a CTD, reloaded and carried on no issue and now I have just had another CTD on taxi out at Auckland with the Airbus X. There doesn't seem to be any consistency with these crashed in regards to same aircraft or scenery area as they have happened with the 737NGX, the 777, and now the Airbus X.

Error report below, any ideas??

 

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0xcccccccc
Faulting process id: 0x1780
Faulting application start time: 0x01d1ba980d8375bd
Faulting application path: D:\FSX\fsx.exe
Faulting module path: unknown
Report Id: afd4cf3a-2690-11e6-b41f-ad820741f1a0

 

Fault bucket 2563111285, type 5
Event Name: BEX
Response: Not available
Cab Id: 0

Problem signature:
P1: fsx.exe
P2: 10.0.61637.0
P3: 46fadb14
P4: StackHash_0a9e
P5: 0.0.0.0
P6: 00000000
P7: cccccccc
P8: c0000005
P9: 00000008
P10:

Attached files:
C:\Users\Marc\AppData\Local\Temp\WERDF28.tmp.WERInternalMetadata.xml

These files may be available here:
C:\Users\Marc\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_c9aa5643e9223dbc309c57d32c286c725d172df_11e519e7

Analysis symbol:
Rechecking for solution: 0
Report Id: afd4cf3a-2690-11e6-b41f-ad820741f1a0
Report Status: 0

 

Version=1
EventType=BEX
EventTime=131091049560014498
ReportType=2
Consent=1
UploadTime=131091049561484582
ReportIdentifier=afd4cf3b-2690-11e6-b41f-ad820741f1a0
IntegratorReportIdentifier=afd4cf3a-2690-11e6-b41f-ad820741f1a0
WOW64=1
Response.BucketId=2563111285
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=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 Offset
Sig[6].Value=cccccccc
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.1
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=2057
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]=D:\FSX\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]=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.23407_none_5c02a2f5a011f9be\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\CRYPTSP.dll
LoadedModule[105]=C:\Windows\system32\rsaenh.dll
LoadedModule[106]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL
LoadedModule[107]=C:\Windows\system32\dxgi.dll
LoadedModule[108]=C:\Windows\system32\d3d11.dll
LoadedModule[109]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[110]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[111]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[112]=C:\Windows\system32\nvd3dum.dll
LoadedModule[113]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[114]=C:\Windows\system32\bcrypt.dll
LoadedModule[115]=C:\Windows\system32\D3DCompiler_34.dll
LoadedModule[116]=C:\Windows\SysWOW64\bcryptprimitives.dll
LoadedModule[117]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[118]=C:\Windows\system32\d3d10_1.dll
LoadedModule[119]=C:\Windows\system32\d3d10_1core.dll
LoadedModule[120]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[121]=C:\Windows\SysWOW64\dxdiagn.dll
LoadedModule[122]=C:\Windows\SysWOW64\d3d10.dll
LoadedModule[123]=C:\Windows\SysWOW64\d3d10core.dll
LoadedModule[124]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[125]=C:\Windows\system32\wbemcomn.dll
LoadedModule[126]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[127]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[128]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[129]=C:\Windows\system32\NTDSAPI.dll
LoadedModule[130]=C:\Windows\system32\winbrand.dll
LoadedModule[131]=C:\Windows\system32\WTSAPI32.DLL
LoadedModule[132]=C:\Windows\system32\WINSTA.dll
LoadedModule[133]=C:\Windows\SysWOW64\gameux.dll
LoadedModule[134]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18837_none_41e855142bd5705d\COMCTL32.dll
LoadedModule[135]=C:\Windows\SysWOW64\XmlLite.dll
LoadedModule[136]=C:\Windows\SysWOW64\wer.dll
LoadedModule[137]=C:\Windows\System32\Wpc.dll
LoadedModule[138]=C:\Windows\System32\wevtapi.dll
LoadedModule[139]=C:\Windows\System32\msxml6.dll
LoadedModule[140]=C:\Windows\system32\SAMLIB.dll
LoadedModule[141]=C:\Windows\system32\netutils.dll
LoadedModule[142]=C:\Windows\system32\uiautomationcore.dll
LoadedModule[143]=C:\Windows\system32\OLEACC.dll
LoadedModule[144]=C:\Windows\System32\MMDevApi.dll
LoadedModule[145]=C:\Windows\System32\PROPSYS.dll
LoadedModule[146]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[147]=C:\Windows\system32\RICHED20.DLL
LoadedModule[148]=C:\Windows\system32\HID.DLL
LoadedModule[149]=C:\Windows\system32\XInput9_1_0.dll
LoadedModule[150]=C:\Windows\system32\wdmaud.drv
LoadedModule[151]=C:\Windows\system32\ksuser.dll
LoadedModule[152]=C:\Windows\system32\AVRT.dll
LoadedModule[153]=C:\Windows\system32\msacm32.drv
LoadedModule[154]=C:\Windows\system32\midimap.dll
LoadedModule[155]=C:\Windows\system32\dinput.DLL
LoadedModule[156]=C:\Windows\System32\wship6.dll
LoadedModule[157]=C:\Windows\System32\wshtcpip.dll
LoadedModule[158]=D:\FSX\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow.dll
LoadedModule[159]=C:\Windows\system32\Secur32.dll
LoadedModule[160]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll
LoadedModule[161]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[162]=C:\Windows\system32\WINNSI.DLL
LoadedModule[163]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll
LoadedModule[164]=C:\Windows\system32\DNSAPI.dll
LoadedModule[165]=C:\Windows\system32\dhcpcsvc6.DLL
LoadedModule[166]=C:\Windows\System32\netprofm.dll
LoadedModule[167]=C:\Windows\System32\nlaapi.dll
LoadedModule[168]=C:\Windows\system32\rasadhlp.dll
LoadedModule[169]=C:\Windows\System32\npmproxy.dll
LoadedModule[170]=C:\Windows\system32\dhcpcsvc.DLL
LoadedModule[171]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[172]=D:\FSX\Aerosoft\Flight Recorder\AS-FlightRecorder.dll
LoadedModule[173]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[174]=D:\FSX\RAASPRO\RAASPRO.dll
LoadedModule[175]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll
LoadedModule[176]=C:\Program Files (x86)\Common Files\System\ado\msado15.dll
LoadedModule[177]=C:\Windows\system32\MSDART.DLL
LoadedModule[178]=C:\Program Files (x86)\Common Files\System\Ole DB\oledb32.dll
LoadedModule[179]=C:\Program Files (x86)\Common Files\System\Ole DB\OLEDB32R.DLL
LoadedModule[180]=C:\Windows\system32\comsvcs.dll
LoadedModule[181]=C:\Windows\system32\ATL.DLL
LoadedModule[182]=C:\Windows\SysWOW64\msjetoledb40.dll
LoadedModule[183]=C:\Windows\SysWOW64\msjet40.dll
LoadedModule[184]=C:\Windows\SysWOW64\mswstr10.dll
LoadedModule[185]=C:\Windows\SysWOW64\msjter40.dll
LoadedModule[186]=C:\Windows\SysWOW64\MSJINT40.DLL
LoadedModule[187]=C:\Windows\SysWOW64\mstext40.dll
LoadedModule[188]=C:\Windows\system32\mlang.dll
LoadedModule[189]=C:\Windows\system32\RAASAUDIO32.DLL
LoadedModule[190]=C:\Windows\system32\X3DAudio1_6.dll
LoadedModule[191]=C:\Windows\SysWow64\xactengine3_4.dll
LoadedModule[192]=C:\Windows\SysWow64\XAudio2_4.dll
LoadedModule[193]=D:\FSX\PMDG\DLLs\PMDG_HUD_interface.dll
LoadedModule[194]=C:\Windows\system32\MSVCR100.dll
LoadedModule[195]=D:\FSX\VistaMare\ViMaCoreX.dll
LoadedModule[196]=D:\FSX\VistaMare\bin\VMCX_AP.dll
LoadedModule[197]=D:\FSX\VistaMare\bin\ViMaNET_AP.dll
LoadedModule[198]=D:\FSX\Modules\LVLD.dll
LoadedModule[199]=D:\FSX\Level-D Simulations\B767-300\leveld.dll
LoadedModule[200]=D:\FSX\PMDG\DLLs\PMDG_Interface.dll
LoadedModule[201]=D:\FSX\Modules\FSUIPC4.dll
LoadedModule[202]=D:\FSX\as_srv\as_btstrp.dll
LoadedModule[203]=C:\Windows\system32\msadp32.acm
LoadedModule[204]=C:\Windows\SysWOW64\ieframe.dll
LoadedModule[205]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll
LoadedModule[206]=C:\Windows\SysWOW64\mshtml.dll
LoadedModule[207]=C:\Windows\system32\msimtf.dll
LoadedModule[208]=C:\Windows\system32\msls31.dll
LoadedModule[209]=C:\Windows\system32\d2d1.dll
LoadedModule[210]=C:\Windows\system32\DWrite.dll
LoadedModule[211]=C:\Windows\system32\D3D10Warp.dll
LoadedModule[212]=C:\Windows\system32\ntmarta.dll
LoadedModule[213]=C:\Windows\syswow64\WLDAP32.dll
LoadedModule[214]=D:\FSX\SimObjects\Airplanes\Aerosoft Airbus A320_A321 Base\Panel_Fallback\DLLs\FMGS.DLL
LoadedModule[215]=D:\FSX\FS2Crew2010\Versions\AerosoftAirbusX\Gauges\FS2CrewAirbusButton.GAU
LoadedModule[216]=D:\FSX\libcurl.dll
LoadedModule[217]=C:\Windows\system32\WSOCK32.dll
LoadedModule[218]=C:\Windows\system32\FS2AUDIO.dll
LoadedModule[219]=C:\Windows\system32\napinsp.dll
LoadedModule[220]=C:\Windows\system32\pnrpnsp.dll
LoadedModule[221]=C:\Windows\System32\winrnr.dll
LoadedModule[222]=D:\FSX\SimObjects\Airplanes\Aerosoft Airbus A320_A321 Base\Panel_Fallback\Airbus_ECAMD2D.DLL
LoadedModule[223]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCP90.dll
LoadedModule[224]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll
LoadedModule[225]=D:\FSX\SimObjects\Airplanes\Aerosoft Airbus A320_A321 Base\Panel_Fallback\ASC.DLL
LoadedModule[226]=D:\FSX\SimObjects\Airplanes\Aerosoft Airbus A320_A321 Base\Panel_Fallback\ND\AB_ND_GDI.DLL
LoadedModule[227]=D:\FSX\SimObjects\Airplanes\Aerosoft Airbus A320_A321 Base\Panel_Fallback\DLLs\AsInput.DLL
LoadedModule[228]=D:\FSX\SimObjects\Airplanes\Aerosoft Airbus A320_A321 Base\Panel_Fallback\DLLs\FBW.DLL
LoadedModule[229]=D:\FSX\SimObjects\Airplanes\Aerosoft Airbus A320_A321 Base\Panel_Fallback\AirbusXE2.DLL
LoadedModule[230]=D:\FSX\SimObjects\Airplanes\Aerosoft Airbus A320_A321 Base\Panel_Fallback\AirbusXE.DLL
LoadedModule[231]=D:\FSX\VistaMare\bin\ViMaIScnX_AP.dll
LoadedModule[232]=C:\Windows\system32\nvwgf2um.dll
LoadedModule[233]=C:\Windows\SysWOW64\msjtes40.dll
LoadedModule[234]=C:\Windows\system32\VBAJET32.DLL
LoadedModule[235]=C:\Windows\system32\expsrv.dll
LoadedModule[236]=C:\Program Files (x86)\Common Files\System\ado\msadrh15.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=DataRequest
State[1].Value=Bucket=-1731856011/nBucketTable=5/nResponse=1/n
FriendlyEventName=Stopped working
ConsentKey=BEX
AppName=Microsoft Flight Simulator®
AppPath=D:\FSX\fsx.exe
 

[Jim Young 2,356]

You are still getting a StackHash.  A StackHash is very difficult to fix.  I had to completely reinstall Windows 7 and then reinstall FSX to get rid of it.  That was some time ago and I have gotten StackHashes since then but I have been able to troubleshoot and find the cause.  Once it was MyTraffic.  Once it was a wrong cpu voltage setting in my BIOS.  There is no common explanation for a StackHash.  You have to return FSX back to the default settings as explained on page 10 of the AVSIM CTD Guide.  That means you have to move the dll.xml, exe.xml, the fsx.cfg and the scenery.cfg to a temporary folder.  Your fsx.cfg and scenery.cfg will be rebuilt.  The dll.xml and exe.xml are not default files so, if you want to run your Aerosoft Airbus to see if this fixed the crashes, you should move the dll.xml and exe.xml back to their proper folders first.  For the fsx.cfg, I would not change a setting except you need to adjust the resolution and you can place the fix in the fsx.cfg under the graphics section - highmemfix=1.  Go fly and see if this eliminates the StackHash.  If it does, then the problem was in your fsx.cfg or scenery.cfg. 

 

If the StackHash returns, try a default aircraft as the problem could be with the Airbus.  If the StackHash shows up then the problem is most likely in your BIOS and with any overclock.  If it is overclocked, return the overclock to the optimal default settings.  Things get corrupted in the BIOS on occasion.  Maybe you had a power outage. 

 

I think a StackHash is caused by a wrong variable somewhere, either in your BIOS or in one of your configuration files, a bad installation of a product or even a corrupted userprofile (the AVSIM CTD Guide shows you how to repair a userprofile.  Be forewarned, it's not easy).  Unfortunately, you have to do a lot of investigating to find it.  Some are lucky and find it right away.  Some have to reinstall Windows and start all over again.  Good luck!

 

Best regards,