Sign in to follow this  
Dazkent

FSX freezes in mid flight

Recommended Posts

Hello

 

My system has been running fine for a couple of months but today I have tried to do two flights but after about an hour FSX just freezes and I have to CRL-ALT-DEL to end the sim, Am not very good with computers so hopefully I have attached the right files. I run ASN for weather and UT2 for AI traffic. Any help would really be apprieciated.

 

Kind regards

Darran

 

 

Description:
  A problem caused this program to stop interacting with Windows.

Problem signature:
  Problem Event Name:    AppHangB1
  Application Name:    fsx.exe
  Application Version:    10.0.61637.0
  Application Timestamp:    46fadb14
  Hang Signature:    f7fc
  Hang Type:    2304
  OS Version:    6.1.7601.2.1.0.768.3
  Locale ID:    2057
  Additional Hang Signature 1:    f7fc88831a14516a1a53b7dc654b9c89
  Additional Hang Signature 2:    0a03
  Additional Hang Signature 3:    0a0361110b548a85e6238b8d704beae7
  Additional Hang Signature 4:    f7fc
  Additional Hang Signature 5:    f7fc88831a14516a1a53b7dc654b9c89
  Additional Hang Signature 6:    0a03
  Additional Hang Signature 7:    0a0361110b548a85e6238b8d704beae7

Version=1
EventType=AppHangB1
EventTime=130496648365800341
ReportType=1
Consent=1
UploadTime=130496649666022335
ReportIdentifier=dde88d66-09f5-11e4-af1e-74d4351cea95
IntegratorReportIdentifier=dde88d67-09f5-11e4-af1e-74d4351cea95
WOW64=1
Response.BucketId=751282487
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=2304
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.768.3
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=2057
DynamicSig[22].Name=Additional Hang Signature 1
DynamicSig[22].Value=f7fc88831a14516a1a53b7dc654b9c89
DynamicSig[23].Name=Additional Hang Signature 2
DynamicSig[23].Value=0a03
DynamicSig[24].Name=Additional Hang Signature 3
DynamicSig[24].Value=0a0361110b548a85e6238b8d704beae7
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=0a03
DynamicSig[28].Name=Additional Hang Signature 7
DynamicSig[28].Value=0a0361110b548a85e6238b8d704beae7
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
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped responding and was closed
ConsentKey=AppHangXProcB1
AppName=Microsoft Flight Simulator®
AppPath=C:\FSX\fsx.exe
ReportDescription=A problem caused this program to stop interacting with Windows.










Log Name:      Application
Source:        Application Hang
Date:          12/07/2014 19:56:17
Event ID:      1002
Task Category: (101)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Owner-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: ecc
 Start Time: 01cf9df94acef395
 Termination Time: 100
 Application Path: C:\FSX\fsx.exe
 Report Id:

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Hang" />
    <EventID Qualifiers="0">1002</EventID>
    <Level>2</Level>
    <Task>101</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-07-12T18:56:17.000000000Z" />
    <EventRecordID>5098</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Owner-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>fsx.exe</Data>
    <Data>10.0.61637.0</Data>
    <Data>ecc</Data>
    <Data>01cf9df94acef395</Data>
    <Data>100</Data>
    <Data>C:\FSX\fsx.exe</Data>
    <Data>
    </Data>
    <Binary>55006E006B006E006F0077006E0000000000</Binary>
  </EventData>
</Event>

 

 

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

FSX is just hanging up and those are always hard to find. In the AVSIM CTD Guide, page 8, there are several possible solutions. The AVSIM CTD Guide is located to the right of this forum under Hot Spots.

 

Best regards,

Share this post


Link to post
Share on other sites

Thanks Jim, I will take a look. I did a couple of tests . Flightplan Nice to Stansted with ASN running on both occasions FSX froze but with on the third occasion i used the default weather and not ASN and i was able to complete the flight with no problems so maybe its to do with ASN?

Share this post


Link to post
Share on other sites

This happened to me once and I ended up running Process Monitor during the flight to see what in the heck was happening when it froze. At the time I had AS2012 running and it froze up almost at the exact same spot. I would change to the default weather and the freezes would stop and I could complete the flight. Problem with suspecting ASN or AS2012 is the fact that these programs handle the default weather too. So I ran the Process Monitor and found My Traffic X was loading traffic at the time of the freeze. I disabled My Traffic X in the Scenery Library and the freezes stopped. I have since moved back to My Traffic X 5.4b and I think some of the schedules in 5.4c are buggy. Since going back to 5.4b, all my issues went away. Soon you will start getting ntdll.dll or Stackhash faulting modules and crashes or at least I did. Now, if this doesn't fit your situation (you don't use MyTrafficX), then let me know and I'll tell you how to run Process Monitor to try and find your issue.

Hope this helps.

 

Best regards,

Share this post


Link to post
Share on other sites

Hi Jim

 

I tried running it again with ASN and am getting another error, this one is a different one , A runtime error R6025, this time FSX did not freeze it just crashed. I have enclosed a log for you. I am beginning to develop a love hate relationship with FSX, Cant understand how it can work fine for months and then not work properly :(

 

I will try again on Sunday without ASN and see if it works ok ( its early morning here in the uk)

 

Version=1
EventType=APPCRASH
EventTime=130496824442537542
ReportType=2
Consent=1
ReportIdentifier=dedad546-0a1e-11e4-af1e-74d4351cea95
IntegratorReportIdentifier=dedad545-0a1e-11e4-af1e-74d4351cea95
WOW64=1
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=terrain.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.61637.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=46fadb59
Sig[6].Name=Exception Code
Sig[6].Value=40000015
Sig[7].Name=Exception Offset
Sig[7].Value=0008443a
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.768.3
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=2057
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=8f9a
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=8f9a81d7df9edae429b8a925b93ecd1b
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=8f9e
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=8f9eac692bdf4c4a29bb0f81c4c66e3f
UI[2]=C:\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]=C:\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\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:\FSX\language.dll
LoadedModule[61]=C:\FSX\API.DLL
LoadedModule[62]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll
LoadedModule[63]=C:\FSX\ablscpt.dll
LoadedModule[64]=C:\FSX\flight.dll
LoadedModule[65]=C:\FSX\ai_player.dll
LoadedModule[66]=C:\FSX\acontain.dll
LoadedModule[67]=C:\FSX\controls.dll
LoadedModule[68]=C:\Windows\system32\DINPUT8.dll
LoadedModule[69]=C:\FSX\fsui.dll
LoadedModule[70]=C:\FSX\atc.dll
LoadedModule[71]=C:\FSX\facilities.dll
LoadedModule[72]=C:\FSX\demo.dll
LoadedModule[73]=C:\FSX\main.dll
LoadedModule[74]=C:\FSX\fe.dll
LoadedModule[75]=C:\FSX\util.dll
LoadedModule[76]=C:\FSX\simprop.dll
LoadedModule[77]=C:\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]=C:\FSX\g3d.dll
LoadedModule[83]=C:\FSX\panels.dll
LoadedModule[84]=C:\FSX\multiplayer.dll
LoadedModule[85]=C:\FSX\ui.dll
LoadedModule[86]=C:\FSX\sound.dll
LoadedModule[87]=C:\FSX\sim1.dll
LoadedModule[88]=C:\FSX\simscheduler.dll
LoadedModule[89]=C:\FSX\visualfx.dll
LoadedModule[90]=C:\FSX\window.dll
LoadedModule[91]=C:\FSX\terrain.dll
LoadedModule[92]=C:\FSX\weather.dll
LoadedModule[93]=C:\Windows\system32\DSOUND.dll
LoadedModule[94]=C:\Windows\system32\POWRPROF.dll
LoadedModule[95]=C:\FSX\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:\FSX\xuipc.dll
LoadedModule[99]=C:\FSX\livingwater.dll
LoadedModule[100]=C:\FSX\fs-traffic.dll
LoadedModule[101]=C:\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\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\nvd3dum.dll
LoadedModule[120]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[121]=C:\Windows\system32\D3DCompiler_34.dll
LoadedModule[122]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[123]=C:\Windows\system32\d3d10_1.dll
LoadedModule[124]=C:\Windows\system32\d3d10_1core.dll
LoadedModule[125]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll
LoadedModule[126]=C:\Windows\SysWOW64\dxdiagn.dll
LoadedModule[127]=C:\Windows\SysWOW64\d3d10.dll
LoadedModule[128]=C:\Windows\SysWOW64\d3d10core.dll
LoadedModule[129]=C:\Windows\system32\winbrand.dll
LoadedModule[130]=C:\Windows\system32\nvapi.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.17514_none_41e6975e2bd6f2b2\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:\FSX\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]=C:\FSX\Modules\LHBP_objectPlacer.dll
LoadedModule[159]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[160]=C:\Windows\system32\MSVCP100.dll
LoadedModule[161]=C:\Windows\system32\MSVCR100.dll
LoadedModule[162]=C:\FSX\VistaMare\ViMaCoreX.dll
LoadedModule[163]=C:\FSX\VistaMare\bin\VMCX_AP.dll
LoadedModule[164]=C:\FSX\VistaMare\bin\ViMaNET_AP.dll
LoadedModule[165]=C:\FSX\as_srv\as_btstrp.dll
LoadedModule[166]=C:\Windows\system32\mscoree.dll
LoadedModule[167]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
LoadedModule[168]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll
LoadedModule[169]=C:\Windows\assembly\NativeImages_v2.0.50727_32\mscorlib\ede2c6c842840e009f01bcc74fa4c457\mscorlib.ni.dll
LoadedModule[170]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorsec.dll
LoadedModule[171]=C:\Windows\syswow64\imagehlp.dll
LoadedModule[172]=C:\Windows\system32\ncrypt.dll
LoadedModule[173]=C:\Windows\system32\bcrypt.dll
LoadedModule[174]=C:\Windows\SysWOW64\bcryptprimitives.dll
LoadedModule[175]=C:\Windows\system32\GPAPI.dll
LoadedModule[176]=C:\Windows\system32\cryptnet.dll
LoadedModule[177]=C:\Windows\syswow64\WLDAP32.dll
LoadedModule[178]=C:\Windows\system32\SensApi.dll
LoadedModule[179]=C:\FSX\as_srv\as_connect.dll
LoadedModule[180]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorjit.dll
LoadedModule[181]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System\b3a78269847005365001c33870cd121f\System.ni.dll
LoadedModule[182]=C:\Windows\system32\ntmarta.dll
LoadedModule[183]=C:\Windows\system32\Secur32.dll
LoadedModule[184]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll
LoadedModule[185]=C:\Windows\SysWOW64\ieframe.dll
LoadedModule[186]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll
LoadedModule[187]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll
LoadedModule[188]=C:\Windows\SysWOW64\mshtml.dll
LoadedModule[189]=C:\Windows\system32\msimtf.dll
LoadedModule[190]=C:\Windows\system32\msls31.dll
LoadedModule[191]=C:\Windows\system32\d2d1.dll
LoadedModule[192]=C:\Windows\system32\DWrite.dll
LoadedModule[193]=C:\Windows\system32\D3D10Warp.dll
LoadedModule[194]=C:\Windows\system32\MLANG.dll
LoadedModule[195]=C:\Windows\SysWOW64\uiautomationcore.dll
LoadedModule[196]=C:\FSX\VistaMare\bin\ViMaIScnX_AP.dll
LoadedModule[197]=C:\FSX\GAUGES\737-400.DLL
LoadedModule[198]=C:\Windows\system32\msadp32.acm
LoadedModule[199]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Drawing\5c24d3b0041ebf4f48a93615b9fa3de9\System.Drawing.ni.dll
LoadedModule[200]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Configuration\5b6ddf934128d538cd5cd77bf4209b93\System.Configuration.ni.dll
LoadedModule[201]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Xml\217ece46920546d718414291d463bb1c\System.Xml.ni.dll
LoadedModule[202]=C:\Program Files (x86)\Common Files\microsoft shared\ink\tiptsf.dll
LoadedModule[203]=C:\Windows\system32\explorerframe.dll
LoadedModule[204]=C:\Windows\system32\DUser.dll
LoadedModule[205]=C:\Windows\system32\DUI70.dll
LoadedModule[206]=C:\Windows\system32\EhStorShell.dll
LoadedModule[207]=C:\Windows\system32\ntshrui.dll
LoadedModule[208]=C:\Windows\system32\srvcli.dll
LoadedModule[209]=C:\Windows\system32\cscapi.dll
LoadedModule[210]=C:\Windows\system32\slc.dll
LoadedModule[211]=C:\Windows\System32\StructuredQuery.dll
LoadedModule[212]=C:\Windows\SysWOW64\actxprxy.dll
LoadedModule[213]=C:\Program Files (x86)\Internet Explorer\ieproxy.dll
LoadedModule[214]=C:\Windows\SysWOW64\thumbcache.dll
LoadedModule[215]=C:\Windows\system32\SearchFolder.dll
LoadedModule[216]=C:\Windows\system32\SHDOCVW.dll
LoadedModule[217]=C:\Windows\system32\NetworkExplorer.dll
LoadedModule[218]=C:\Windows\system32\LINKINFO.dll
LoadedModule[219]=C:\Windows\System32\drprov.dll
LoadedModule[220]=C:\Windows\System32\ntlanman.dll
LoadedModule[221]=C:\Windows\System32\davclnt.dll
LoadedModule[222]=C:\Windows\System32\DAVHLPR.dll
LoadedModule[223]=C:\Windows\system32\wkscli.dll
LoadedModule[224]=C:\Windows\system32\PortableDeviceApi.dll
LoadedModule[225]=C:\Windows\system32\EhStorAPI.dll
LoadedModule[226]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\diasymreader.dll
File[0].CabName=AppCompat.txt
File[0].Path=WER73A0.tmp.appcompat.txt
File[0].Flags=65538
File[0].Type=5
File[0].Original.Path=C:\Users\Owner\AppData\Local\Temp\WER73A0.tmp.appcompat.txt
File[1].CabName=WERInternalMetadata.xml
File[1].Path=WER741D.tmp.WERInternalMetadata.xml
File[1].Flags=65538
File[1].Type=5
File[1].Original.Path=C:\Users\Owner\AppData\Local\Temp\WER741D.tmp.WERInternalMetadata.xml
File[2].CabName=memory.hdmp
File[2].Path=WER741E.tmp.hdmp
File[2].Flags=2097152
File[2].Type=3
File[2].Original.Path=C:\Users\Owner\AppData\Local\Temp\WER741E.tmp.hdmp
File[3].CabName=minidump.mdmp
File[3].Path=WER8751.tmp.mdmp
File[3].Flags=2162690
File[3].Type=2
File[3].Original.Path=C:\Users\Owner\AppData\Local\Temp\WER8751.tmp.mdmp
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Microsoft Flight Simulator®
AppPath=C:\FSX\fsx.exe
 

Share this post


Link to post
Share on other sites

The terrain.dll CTD is caused by having your sliders set too high. In this case the Exception Code 0x40000015 means STATUS_FATAL_APP_EXIT and FSX caused an unhandled runtime exception during shutdown.

 

A runtime error R6025 is part of the Microsoft Visual C++ code that developers put in to tell you there is something wrong with the installation of your application. So, to investigate this problem, you need to figure out when you started receiving these runtime errors. What application was installed and these errors started happening? You should be able to determine this via the System Event Viewer or the AppCrashView program (see AVSIM CTD Guide). That application should be uninstalled to see if this fixes the problem. If so, then reinstall using Administrator Rights. Microsoft Visuals are used by developers for applications like FSX and FSX addons, like PMDG products, to make sure the application is installed properly as they intended. If the application was not installed properly, then it will throw these runtime errors and that is by design. I have seen this runtime error a lot when Simconnect is not working properly (believe ASN uses Simconnect).

 

Best regards,

Share this post


Link to post
Share on other sites

Hi Jim

 

Thanks for your reply.

 

I must admit I had never had the Terrain.dll error before. I do run my settings pretty high (see enclosed shots),  I see our systems are pretty similar, Do you think I run them too high?

 

b4qTv.jpg

 

dGBNT.jpg

 

nu6Rg.jpg

Share this post


Link to post
Share on other sites

The only killer is Autogen in your settings. For terrain and water settings, I would return those settings to the default except that I would max LOD_Radius (I have mine set at 6.5). Your mesh and texture resolutions are very high and I know of no scenery or texture program that would use those high settings. Not sure why you turned off AI except for ships. AI is not hard on your fps if you keep it around 20-25%.

 

You can try one other thing that I used to track down My Traffic X StackHash crashes. I had no idea it as My Traffic X causing the problems and figured it had to be my weather program. But I ran Process Monitor while running FSX and jotted down on a notepad the time of every glitch, stutter, whatever occurring during the flight. Of course, when FSX crashes or hung up, I shutdown Process Monitor immediately and then shutdown FSX. I then analyzed the Process Monitor log. Thousands of entries made every minute into the log so pinpointing the problem was not easy but I compared the times I jotted down to the times in the log and saw that My Traffic X was calling a lot of traffic around the world. I disabled My Traffic X and the problem went away. Here's how to set up Process Monitor for FSX:

 

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 (very important that you actually click on the Process Monitor application to bring it in focus) 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!

 

This will be in the next update to the AVSIM CTD Guide.

 

Best regards,

Share this post


Link to post
Share on other sites

Hi Jim

 

Many thanks for your reply, I have been doing some troubleshooting with this over the past few weeks and it looks like i have solved it, I did the following.

 

Opened Security Essentials and went to settings.

Under Excluded files and Locations added the following folder locations:

Your Drive Letter:\HiFi\ASNext_FSX

Your Drive Letter:\Your Microsoft Fight Simulator X directory

With Windows Firewall under Advanced settings I made a new inbound rule and a new outbound rule.

 Add ASNext.exe and Allow Connection, and then under the "Protocols and Ports Tab" Allow Any.
Local and remote ports should now be set to "All Ports"

Under the Advanced Tab all 3 profile boxes should be checked. Domain, Private and Public.

 

 

I then  tested this by doing 6 flights between 2 and 3 hours and the 8 min freeze has gone. I noticed that when ASN was installed it had incoming port but nothing for outgoing so I am assuming that it was unable to comminicate properly with FSX.

 

Re my settings I have turned down the autogen a notch and also introduced some road traffic, My airtraffic is controlled by Ultimate Traffic 2 so the sliders are set to zero in FSX. I just get the odd microstutter but its a vast improvement.

 

Thanks once again :smile:

 

flyuk_sig.php?id=UKV1523
 

Share this post


Link to post
Share on other sites

With Windows Firewall under Advanced settings I made a new inbound rule and a new outbound rule.

Glad you problem is resolved (for now) but you should not have had to mess with the Windows Firewall or Microsoft Essentials. It sounds more like you have a sharing problem.

 

In the last crash report you provided above, under Module 226 I noticed a lot of temporary files were loaded and that definitely should not have happened. You should periodically clean out your temporary folder (C:\Users\Owner\AppData\Local\Temp\). I do this at least once a week as Windows does not do it. Since this temporary folder is normally hidden, a lot of people do not see this folder. You can safely delete everything in the temporary folder.

 

Best regards,

Share this post


Link to post
Share on other sites

Do you mean a sharing problem between FSX and ASN?

 

Thanks for the tip with the temporary files folder, I must admit that I never knew about this so will make sure I delete them once a week too

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this