26F (-3C) is almost tropical!

 

With the wind chill here this morning the temps are below 0 F which, of course is 32 C.  My cold water pipe to the kitchen sink is frozen.  I let the water drip all night by opening the faucet but guess not enough dripping....

 

That's encouraging news regarding the texture file in MyTrafficX.  I suppose you could rename it.  I doubt it is needed unless you are sitting next to the AI.  MyTrafficX also employs a few hundred AFCAD's which are needed for the AI aircraft to takeoff and land. This file must have been added in the upgrade to 5.4c.  This can explain why so many people are suddenly having ntdll and stackhash errors.  More than the norm as I have been monitoring the CTD forum for a long time. Of course, StackHash and NTDLL crashes can be caused by many other things, but this is a step forward.

 

Best regards,

Hi Jim,

 

I'm delighted to report that reflying EGKK-LIPZ with that texture file renamed didn't cause a crash and I completed the flight. I can't tell you how happy I am Burkhard has identified this problem. There may be other StackHash problems in the future but with Process Monitor I can at least identify what FSX doesn't like.

 

We had some severe frosts a few years ago and the water pipes to my washing machine in the garage froze up. They did thaw eventually and I was just relieved the machine wasn't broken. I guess you're going to need a plumber to sort out the cracked pipe.

 

 

There may be other StackHash problems in the future but with Process Monitor I can at least identify what FSX doesn't like.

 

Hey Ray!

 

Absolutely awesome the file was found.  I'll have to reinstall and delete rename that file.  Out of hundreds of texture files, how did he find the one that was bad?  Maybe through Process Monitor.

 

I just ran my fifth flight without a crash and, of course, ran Process Monitor in the background.  For an hour flight, the log will use 6-7GB's of disk space (not to worry as you can delete it after you have analyzed it).  You want to filter it to just run with the process FSX.exe and nothing else otherwise the log file will be about 15GB's and it will be impossible to diagnose.  I start my Process Monitor up just before takeoff on the runway.  Today I found more Orbx/FTX files loading during the flight (through FTX Central I have disabled Orbx/FTX scenery and switched it to the default).  Nothing in my Scenery Library relating to Orbx/FTX is activated yet the files are loading, like Orcas and FTX trees (which is Autogen and I have Autogen turned off!!).  Doesn't the off switch mean off?  I saw too that it was loading default scenery all around the world.  Autogen too and every default aircraft and all of the PMDG aircraft were being loaded.  No wonder many see so many stutters and stuff.  Wonder what would happen if I disabled all of the default scenery as I fly over photoscenery and fly in/out of FSDT airports?

 

But this is good news that a potential fix for the StackHash/NTDLL crashes has been found.

 

Best regards,

Hi Jim,

 

Encouraging news indeed. Points taken about how to use PM.

 

I have a strategy on how to (hopefully) identify the cause of any future StackHash (and other) errors. I always fly jets with a flightplan and because I run the CDU on a second PC I know exactly where I am when FSX crashes. PM should show the last file that was tried to be loaded and that will be very helpful.

 

I can then rename that file and use my last saved flight (every 5 minutes) to easily recreate the crash situation. If it still crashes then it's back to square one but if another aircraft texture file is corrupted it's a easy thing to notify Burkhard.

 

I too don't understand why FSX loads scenery for places you're nowhere near. Only Aces can answer that and they never will of course.

 

I'm going to locate the nearest airport to the DIK VOR and fly around it just to make sure the fix is fixed. next up is the crash I had west of Denver but that didn't occur a second time so might be harder to spot.

 

Up and up! :Big Grin:

 

 

always fly jets with a flightplan and because I run the CDU on a second PC I know exactly where I am when FSX crashes. PM should show the last file that was tried to be loaded and that will be very helpful.

 

Hi Ray,

 

If you get another StackHash (or NTDLL) I will be 'very' interested as I really think the cause was MyTrafficX.  I'm a little confused as how you can see the last file loaded after a crash as I couldn't see mine when fsx froze or locked up on me once.  I just saw a lot of AI being loaded about that time.  Next time I get a repeatable crash, I'll have to try to see if the last file loaded was the crash.

 

I may do a flight today.  I reinstalled MTX 5.4 (no a, b, or c, just 5.4).  Just did some short hops in the area to check out the AI and my airports are crowded.

 

Best regards,

Hi Jim,

 

FSUIPC has an option to save flights every x minutes. I use that to load the last flight before any crash.

 

Actually, if you do that you don't need to run Process Monitor. You just start it after you restart a flight from your last save. If you save every 5 minutes you'll get the crash within 5 minutes so the PM log will be quite small.

 

I'm currently enroute to KSFO from KSLC. So far so good.

Just had a crash - ntldll.dll - 43DME from MVA on the PECOP4 SID from KSLC. :(

 

But when I reload from the last saved flight it doesn't crash again. Hmmm, that's a new one.

Jim,

 

Here's the details of the crash over a sparsely populated area of the mid West. Damed if I know what that was down to! It crashes in a remote area but never at KSFO! Work that one out. :unsure:

 

I've just applied Burkhard's patch to MTX. Might try this one again to see if it makes any difference. No further problems and landed at KSFO.

 

Version=1
EventType=APPCRASH
EventTime=130351417999572470
ReportType=2
Consent=1
UploadTime=130351418000082499
ReportIdentifier=cb7d1d7e-85df-11e3-b5fa-94de80a6c959
IntegratorReportIdentifier=cb7d1d7d-85df-11e3-b5fa-94de80a6c959
WOW64=1
Response.BucketId=3885479630
Response.BucketTable=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=fsx.exe
Sig[1].Name=Application Version
Sig[1].Value=10.0.61472.0
Sig[2].Name=Application Timestamp
Sig[2].Value=475e17d3
Sig[3].Name=Fault Module Name
Sig[3].Value=ntdll.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=6.1.7601.18247
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=521ea8e7
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=0002e41b
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
UI[2]=D:\FSX\fsx.exe
UI[3]=A fatal error occurred.
UI[4]=Windows can check online for a solution to the problem and try to restart the program.
UI[5]=Check online for a solution and restart 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\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]=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.18120_none_72d2e82386681b36\gdiplus.dll
LoadedModule[97]=C:\Windows\system32\MSIMG32.dll
LoadedModule[98]=D:\FSX\xuipc.dll
LoadedModule[99]=D:\FSX\livingwater.dll
LoadedModule[100]=D:\FSX\fs-traffic.dll
LoadedModule[101]=D:\FSX\gps.dll
LoadedModule[102]=C:\Windows\system32\MSWSOCK.dll
LoadedModule[103]=C:\Windows\system32\SHFOLDER.dll
LoadedModule[104]=C:\Windows\system32\RICHED20.DLL
LoadedModule[105]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[106]=C:\Windows\system32\rsaenh.dll
LoadedModule[107]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[108]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[109]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[110]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[111]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[112]=C:\Windows\system32\wbemcomn.dll
LoadedModule[113]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[114]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[115]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[116]=C:\Windows\system32\NTDSAPI.dll
LoadedModule[117]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL
LoadedModule[118]=C:\Windows\system32\dxgi.dll
LoadedModule[119]=C:\Windows\system32\d3d11.dll
LoadedModule[120]=C:\Windows\system32\nvd3dum.dll
LoadedModule[121]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[122]=C:\Windows\system32\D3DCompiler_34.dll
LoadedModule[123]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[124]=C:\Windows\system32\d3d10_1.dll
LoadedModule[125]=C:\Windows\system32\d3d10_1core.dll
LoadedModule[126]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll
LoadedModule[127]=C:\Windows\SysWOW64\dxdiagn.dll
LoadedModule[128]=C:\Windows\SysWOW64\d3d10.dll
LoadedModule[129]=C:\Windows\SysWOW64\d3d10core.dll
LoadedModule[130]=C:\Windows\system32\winbrand.dll
LoadedModule[131]=C:\Windows\system32\nvapi.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.17514_none_41e6975e2bd6f2b2\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\HID.DLL
LoadedModule[149]=C:\Windows\system32\ntmarta.dll
LoadedModule[150]=C:\Windows\syswow64\WLDAP32.dll
LoadedModule[151]=C:\Windows\system32\XInput9_1_0.dll
LoadedModule[152]=C:\Windows\system32\wdmaud.drv
LoadedModule[153]=C:\Windows\system32\ksuser.dll
LoadedModule[154]=C:\Windows\system32\AVRT.dll
LoadedModule[155]=C:\Windows\system32\msacm32.drv
LoadedModule[156]=C:\Windows\system32\midimap.dll
LoadedModule[157]=C:\Windows\system32\dinput.DLL
LoadedModule[158]=C:\Windows\system32\BfLLR.dll
LoadedModule[159]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[160]=C:\Windows\system32\WINNSI.DLL
LoadedModule[161]=C:\Windows\system32\dhcpcsvc.DLL
LoadedModule[162]=C:\Windows\system32\dhcpcsvc6.DLL
LoadedModule[163]=C:\Windows\System32\wshtcpip.dll
LoadedModule[164]=C:\Windows\System32\wship6.dll
LoadedModule[165]=D:\FSX\bglmanx.dll
LoadedModule[166]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[167]=C:\Windows\system32\inetmib1.dll
LoadedModule[168]=C:\Windows\system32\snmpapi.dll
LoadedModule[169]=D:\FSX\FS_Earth\fs_earth.dll
LoadedModule[170]=C:\Windows\system32\WSOCK32.dll
LoadedModule[171]=D:\FSX\fs_earth\simconnect.dll
LoadedModule[172]=C:\Program Files (x86)\AFX\AFXModuleFSX.dll
LoadedModule[173]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll
LoadedModule[174]=D:\FSX\VistaMare\ViMaCoreX.dll
LoadedModule[175]=D:\FSX\VistaMare\bin\VMCX_SP2.dll
LoadedModule[176]=D:\FSX\VistaMare\bin\ViMaNET.dll
LoadedModule[177]=D:\FSX\FSLabs\DLLs\FSLOptions.dll
LoadedModule[178]=D:\FSX\FSL_SimConnect_Ldr.dll
LoadedModule[179]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCP90.dll
LoadedModule[180]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll
LoadedModule[181]=C:\Windows\WinSxS\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_4bf7e3e2bf9ada4c\mfc90.dll
LoadedModule[182]=C:\Windows\WinSxS\x86_microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_49768ef57548175e\MFC90ENU.DLL
LoadedModule[183]=D:\FSX\FSLabs\DLLs\FSLEvents.dll
LoadedModule[184]=D:\FSX\FSLabs\DLLs\FSLSounds.dll
LoadedModule[185]=D:\FSX\WaveLib.dll
LoadedModule[186]=D:\FSX\as_srv\as_btstrp.dll
LoadedModule[187]=C:\Windows\system32\mscoree.dll
LoadedModule[188]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
LoadedModule[189]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll
LoadedModule[190]=C:\Windows\assembly\NativeImages_v2.0.50727_32\mscorlib\9a6c1b7af18b4d5a91dc7f8d6617522f\mscorlib.ni.dll
LoadedModule[191]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorsec.dll
LoadedModule[192]=C:\Windows\syswow64\imagehlp.dll
LoadedModule[193]=C:\Windows\system32\ncrypt.dll
LoadedModule[194]=C:\Windows\system32\bcrypt.dll
LoadedModule[195]=C:\Windows\SysWOW64\bcryptprimitives.dll
LoadedModule[196]=C:\Windows\system32\GPAPI.dll
LoadedModule[197]=C:\Windows\system32\cryptnet.dll
LoadedModule[198]=C:\Windows\system32\SensApi.dll
LoadedModule[199]=D:\FSX\as_srv\as_connect.dll
LoadedModule[200]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorjit.dll
LoadedModule[201]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System\5d22a30e587e2cac106b81fb351e7c08\System.ni.dll
LoadedModule[202]=C:\Windows\system32\Secur32.dll
LoadedModule[203]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll
LoadedModule[204]=D:\FSX\Modules\FSUIPC4.dll
LoadedModule[205]=C:\Windows\system32\msadp32.acm
LoadedModule[206]=C:\Windows\SysWOW64\ieframe.dll
LoadedModule[207]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll
LoadedModule[208]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll
LoadedModule[209]=C:\Windows\SysWOW64\mshtml.dll
LoadedModule[210]=C:\Windows\system32\msimtf.dll
LoadedModule[211]=C:\Windows\system32\msls31.dll
LoadedModule[212]=C:\Windows\system32\d2d1.dll
LoadedModule[213]=C:\Windows\system32\DWrite.dll
LoadedModule[214]=C:\Windows\system32\D3D10Warp.dll
LoadedModule[215]=C:\Windows\system32\MLANG.dll
LoadedModule[216]=C:\Windows\SysWOW64\uiautomationcore.dll
LoadedModule[217]=D:\FSX\GAUGES\FSFK-ACARS.GAU
LoadedModule[218]=D:\FSX\GAUGES\737-400.DLL
LoadedModule[219]=D:\FSX\GAUGES\XGauge.DLL
LoadedModule[220]=D:\FSX\VistaMare\bin\ViMaIScnX.dll
LoadedModule[221]=C:\Windows\system32\d3dx9_31.dll
LoadedModule[222]=C:\Program Files (x86)\GoFlight\GFDEV.DLL
LoadedModule[223]=D:\FSX\Aerosoft\AES\ViMaCli.dll
Sec[0].Key=LCID
Sec[0].Value=2057
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=DataRequest
State[1].Value=Bucket=-409487666/nBucketTable=1/nResponse=1/n
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Microsoft® Flight Simulator X
AppPath=D:\FSX\fsx.exe

Hi Ray,

 

If you are getting a crash and you go back to the last saved flight and that doesn't cause a crash, then I think it has to be your memory configuration in the BIOS (freq/timings/dram voltage) and/or CPU voltage.  The CPU voltage is sort of out of my league and I leave that one alone and let the BIOS handle it.  I am probably wrong but it's something to think about as you troubleshoot. 

 

Your AppCrashView report shows AES ViMaCli.dll loading last before the crash.  ViMaCli manages connections for AES.  Maybe to call home and say your software is authorized??  It would be interesting if that module showed up in Process Monitor. 

 

Regarding Process Monitor, I think I mentioned I write down the time when a freeze, crash, or I have a sudden loss of fps and there's a large stutter occurs during a flight.  At least the cause is narrowed down to something that happened in that minute.  I didn't know about Pete's utility being able to save flights.  I really don't use the registered portion of it and only bought the registered version as he pretty much fixed the g3d.dll CTD which was major crash.

 

One last thing, I see you might be running Internet Explorer in the background while running a flight.  I use to do that but had several unexplained freezes and when I went into the Task Manager, it showed Internet Explorer was using a massive amount of resources (I have 4 or 5 tabs and each tab equals one Internet Explorer running.  Four tabs, four iterations of Internet Explorer running.  Sometimes when I shut Internet Explorer down, it really does not close it down completely (it might be one of these programs I have on my computer that is constantly looking for updates for me).  After I had all iterations of Internet Explorer shutdown in the Task Manager and ran FSX, FSX seemed to start up much faster and the flights were much smoother.  This is why the AVSIM CTD Guide recommends the IE browser be closed when running fsx.  I have a laptop and will use that sometimes to browse while flying (sort of like what you do in real life on a real aircraft!!). 

 

Best regards,

Hi Jim,

 

It would be surprising if my memory was faulty as it was bench-tested for 24hours by the people who built it. It's been professionally overclocked too so I won't totally discount that possibility but if it was faulty memory wouldn't it cause crashes far more often? I've had several long flights across Europe and no ntldll.dll crashes at all. This one was in the middle of nowhere with only a few Ai around. Hardly the place where the memory is being stressed.

 

AES is bona-fide as are all the credits for it. Also, I didn't use it until arriving at KSFO so it was effectively dormant during the flight. Not sure what you mean about it being authorised???

 

Why do you think IE was running because it wasn't. Only things running were a few apps related to FSX. I can't see any reference to IE in the crash log.

 

I'm going to fly this route again on Monday at the same time. if I can reproduce this problem as I did with the DIK one then there's a chance it can be identified and fixed.

 

One thing I did after that flight is install Burkhard's MTX update which he says fixes some ntldll.dll crashes.  I'll also start PM around 20DME from the point FSX crashed and hopefully it will catch the offender.

 

 

AES is bona-fide as are all the credits for it. Also, I didn't use it until arriving at KSFO so it was effectively dormant during the flight. Not sure what you mean about it being authorised???

 

You have to pay for the credits.  I believe the program checks for proper licensing.  It's the least of possibilities though for causing the crash but anytime a program is going on the Internet to get data (like your weather program) errors could occur.  In fact, I proved this on a crash I had a year or so ago when FSX would crash at the same spot between Chicago and St Louis.  I had AS2012 running.  If I used the default weather program instead, no crash.  Turned on AS2012 and the crash occurred at the same spot.  Maybe their servers were down or there was connection problems.  It's strange though that it happened at nearly the same spot with everything running smoothly and with high fps.  Then boom!

 

I still think you have problems with MyTrafficX 5.4c even though you just updated the fix.  That's the fix I had installed and I stopped getting ntdll.dll errors and got StackHash errors instead.  After I completely removed MyTrafficX 5.4c from my system and went back to the default (this was on Jan 21st), I have not had any ntdll or StackHash crashes.  No freezes and no lockups either.  Yesterday I installed MyTrafficX 5.4 (no a, b, or c) and so far it's work great without any StackHash errors.  I did two more flights today and no crash.  I am almost positive my problem has been fixed with the removal of 5.4c.  I like MTX and the developer Burkhard but, if fsx is crashing with it running, I have no other choice but to uninstall.  I want to enjoy my flights.

 

Got my System Internals books last Tuesday and starting to read them as I find time.  So far I'm on page 7 of Part I.... :Hypnotized:  

 

Good luck Ray in getting your problem resolved.  I really appreciate your help too in resolving or clarifying issues.  I learned a lot in this thread and will probably learn a whole lot more.

 

Best regards,

 

 

You have to pay for the credits. I believe the program checks for proper licensing. It's the least of possibilities though for causing the crash but anytime a program is going on the Internet to get data (like your weather program) errors could occur. In fact, I proved this on a crash I had a year or so ago when FSX would crash at the same spot between Chicago and St Louis. I had AS2012 running. If I used the default weather program instead, no crash. Turned on AS2012 and the crash occurred at the same spot. Maybe their servers were down or there was connection problems. It's strange though that it happened at nearly the same spot with everything running smoothly and with high fps. Then boom!

I've been running AES for years and would be amazed if the 'checking' caused any kind of crash. I think we can discount AES as the culprit. And as you suggest the AS2012 issue was probably a server problem.

 

I still think you have problems with MyTrafficX 5.4c even though you just updated the fix. That's the fix I had installed and I stopped getting ntdll.dll errors and got StackHash errors instead. After I completely removed MyTrafficX 5.4c from my system and went back to the default (this was on Jan 21st), I have not had any ntdll or StackHash crashes. No freezes and no lockups either. Yesterday I installed MyTrafficX 5.4 (no a, b, or c) and so far it's work great without any StackHash errors. I did two more flights today and no crash. I am almost positive my problem has been fixed with the removal of 5.4c. I like MTX and the developer Burkhard but, if fsx is crashing with it running, I have no other choice but to uninstall. I want to enjoy my flights.

You're not alone in reporting problems with 5.4c. But I feel sorry for Burkhard because unless people can give him a precise scenario and he can reproduce it it's impossible to fix. Has he changed anything significantly with the c release? I haven't a clue but if a commercial release is causing crashes then people have a decision to make.

 

I'm not close to making that decision yet but if things continue then who knows. It's easy to revert to a 2012 schedule apparently without the need to uninstall and reinstall. I may try that if I can consistently reproduce a crash with the 2013 © release.

 

Got my System Internals books last Tuesday and starting to read them as I find time. So far I'm on page 7 of Part I.... :Hypnotized:

Won't have any problems getting to sleep then! :biggrin: Good luck with that!

 

Good luck Ray in getting your problem resolved. I really appreciate your help too in resolving or clarifying issues. I learned a lot in this thread and will probably learn a whole lot more.

Thanks Jim and you have been very helpful to me and others. Don't know what we'd do without you. :Applause:

An update after a log flight today - Bratislava, Slovakia to Manchester, England without any problems.

 

Last night I ran the MyTrafficX update to correct some ntldll.dll and StackHash errors. Everything seemed okay departing Bratislava but I started to notice as I crossed the North Sea a distinct lack of Ai despite leaving the setting at 40.

 

After landing I used the MyTrafficX configurator tool to rebuild the aircraft, flights and schedule using the 2012 schedule. It stopped with an error for one of the aircraft - an Antonov I think - and after OKing the error it finished okay. I then noticed there were plenty of Ai once again. I have raised a question on the MTX forum why that error occurred.

 

if it's because some texture is inaccessible there seems to me a likelihood that a ntldll.dll or StackHash error could occur once that aircraft became active.

 

You can follow that post here. http://forum.simflight.com/topic/76141-rebuild-mytraffic-aircraft-scenery-and-schedules-an24mx-error/

Some interesting info there Ray.  I still have just MTX 5.4 installed and at 40% but never saw so much AI in my life (with FSX)!  My FPS have dramatically fallen and mainly staying in the teens.  Sometimes it stutters and goes into the single digits and I think I am going to have a crash and it doesn't crash (or freeze up).  I successfully did a long flight in my Duke B60 to Philadelphia.  Tons of AI at Reagan National.  I did not use the MTX configurator tool.  I just left everything as it was after installation.  I'm going to take ownership of the folder and see if that helps.

 

I've done 10 flights since January 21 without a crash or StackHash error.  Since I only reinstalled MTX yesterday, I haven't given it enough testing to see if my issue is completely fixed.  I do know I cannot live with low FPS on an overclocked Haswell 4770 w/ a GTX780 video card.

 

Best regards,

I still have just MTX 5.4 installed and at 40% but never saw so much AI in my life (with FSX)! My FPS have dramatically fallen and mainly staying in the teens. Sometimes it stutters and goes into the single digits and I think I am going to have a crash and it doesn't crash (or freeze up). I successfully did a long flight in my Duke B60 to Philadelphia. Tons of AI at Reagan National. I did not use the MTX configurator tool. I just left everything as it was after installation. I'm going to take ownership of the folder and see if that helps.

 

Jim, you should be getting similar fps to me as we have identical CPus and the 780GTX. It only drops into the teens for me at EGLL, LFPG, KIAD etc. Where did you depart from? Reagan? You should be able to keep 30fps there.

 

It might be worth your time running that rebuild option. At least it would confirm one way or another whether there is a problem with your MTX installation. In fact I would go as far to say it should be recommended action for those having StackHash or ntldll errors as it will confirm if the MTX installation is without obvious problems.

 

I'm determined to get to the bottom of these crashes but I can only do this by making sure everything works as it should. Currently that is not the case.

 

 

 

I've done 10 flights since January 21 without a crash or StackHash error. Since I only reinstalled MTX yesterday, I haven't given it enough testing to see if my issue is completely fixed. I do know I cannot live with low FPS on an overclocked Haswell 4770 w/ a GTX780 video card.

 

Give me an airport, time, and Ai percentage and I'll tell you what I get there. Your system should only encounter low fps at the busiest airports and should eat most for breakfast.

 

 

Give me an airport, time, and Ai percentage and I'll tell you what I get there. Your system should only encounter low fps at the busiest airports and should eat most for breakfast.

 

Thanks Ray.  Things appear to be back to normal and, in fact, I have 4.5b installed.  I now have fps locked at 35 and it is a solid 35 fps while on Reagan National (KDCA) with a lot of AI on the ground.  One thing I did was update the ATC sound files through MTX Communicator>Manage FSX Settings.  Also Managed MyTrafficX Configurations through MTX Communicator>Configure.  AI level is 40%.  In other words, I read the manual!! B)  I knew I could eventually work it out.  Also read your posts there at MyTrafficX Forum and some others.

 

Thanks!

 

Best regards,