Sign in to follow this  
jjf

ntdll.dll again

Recommended Posts

Hello,

 

I am being plagued by FSX crashes which are being blamed on ntdll.dll, according to the event viewer.

 

Context: today's event -  I was about 1-1.5 hours into a flight from KIAH - EGLL in the PMDG 777. Using RC4 on the FS PC, and ASN on the laptop via WideFS. MYT5.4c, FS2Crew 777.

My system specs: W7 Sp2 64bit (up to date with updates), i7-4740k, Asus Z97 Pro wifi AC, 8Gb RAM, GTX 780, H80i cooling with plenty of case fans.  recently rebuilt my FS PC with brand new components (these have been stress tested). No overclocking. I am confident that overclocking and/or heat are not the issues here, during FS sessions the CPU temps are in the 50-60C range.

 

I'd be grateful if anyone could help me to get to the bottom of this issue. Could this particular error be related to my Sidewinder FF joystick (which I love but it is getting on a bit!)? If not, what else could be causing this?

 

Thanks Jonathan

 

Here's the report:

 

Version=1
EventType=APPCRASH
EventTime=130598757356648037
ReportType=2
Consent=1
UploadTime=130598757357218069
ReportIdentifier=fa031c92-66d3-11e4-bd97-7824af45a895
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=3081
UI[2]=D:\Flight Simulator X\fsx.exe
UI[3]=Microsoft Flight Simulator® has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=D:\Flight Simulator X\fsx.exe
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[4]=C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL
LoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll
LoadedModule[6]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[7]=C:\Windows\syswow64\GDI32.dll
LoadedModule[8]=C:\Windows\syswow64\USER32.dll
LoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[10]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[11]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[12]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[14]=C:\Windows\syswow64\LPK.dll
LoadedModule[15]=C:\Windows\syswow64\USP10.dll
LoadedModule[16]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[17]=C:\Windows\syswow64\ole32.dll
LoadedModule[18]=C:\Windows\system32\apphelp.dll
LoadedModule[19]=C:\Windows\AppPatch\AcGenral.DLL
LoadedModule[20]=C:\Windows\system32\UxTheme.dll
LoadedModule[21]=C:\Windows\system32\WINMM.dll
LoadedModule[22]=C:\Windows\system32\samcli.dll
LoadedModule[23]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[24]=C:\Windows\system32\MSACM32.dll
LoadedModule[25]=C:\Windows\system32\VERSION.dll
LoadedModule[26]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[27]=C:\Windows\system32\sfc.dll
LoadedModule[28]=C:\Windows\system32\sfc_os.DLL
LoadedModule[29]=C:\Windows\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.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:\Flight Simulator X\language.dll
LoadedModule[61]=D:\Flight Simulator X\API.DLL
LoadedModule[62]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll
LoadedModule[63]=D:\Flight Simulator X\ablscpt.dll
LoadedModule[64]=D:\Flight Simulator X\flight.dll
LoadedModule[65]=D:\Flight Simulator X\ai_player.dll
LoadedModule[66]=D:\Flight Simulator X\acontain.dll
LoadedModule[67]=D:\Flight Simulator X\controls.dll
LoadedModule[68]=C:\Windows\system32\DINPUT8.dll
LoadedModule[69]=D:\Flight Simulator X\fsui.dll
LoadedModule[70]=D:\Flight Simulator X\atc.dll
LoadedModule[71]=D:\Flight Simulator X\facilities.dll
LoadedModule[72]=D:\Flight Simulator X\demo.dll
LoadedModule[73]=D:\Flight Simulator X\main.dll
LoadedModule[74]=D:\Flight Simulator X\fe.dll
LoadedModule[75]=D:\Flight Simulator X\util.dll
LoadedModule[76]=D:\Flight Simulator X\simprop.dll
LoadedModule[77]=D:\Flight Simulator X\g2d.dll
LoadedModule[78]=C:\Windows\system32\d3dx9_34.dll
LoadedModule[79]=D:\Flight Simulator X\d3dx10_34.dll
LoadedModule[80]=C:\Windows\system32\MSVCR100.dll
LoadedModule[81]=D:\Flight Simulator X\reald3dx10_34.DLL
LoadedModule[82]=D:\Flight Simulator X\dx10fixerlib.DLL
LoadedModule[83]=C:\Windows\system32\d3d9.dll
LoadedModule[84]=C:\Windows\system32\d3d8thk.dll
LoadedModule[85]=D:\Flight Simulator X\g3d.dll
LoadedModule[86]=D:\Flight Simulator X\panels.dll
LoadedModule[87]=D:\Flight Simulator X\multiplayer.dll
LoadedModule[88]=D:\Flight Simulator X\ui.dll
LoadedModule[89]=D:\Flight Simulator X\sound.dll
LoadedModule[90]=D:\Flight Simulator X\sim1.dll
LoadedModule[91]=D:\Flight Simulator X\simscheduler.dll
LoadedModule[92]=D:\Flight Simulator X\visualfx.dll
LoadedModule[93]=D:\Flight Simulator X\window.dll
LoadedModule[94]=D:\Flight Simulator X\terrain.dll
LoadedModule[95]=D:\Flight Simulator X\weather.dll
LoadedModule[96]=C:\Windows\system32\DSOUND.dll
LoadedModule[97]=C:\Windows\system32\POWRPROF.dll
LoadedModule[98]=D:\Flight Simulator X\symmap.dll
LoadedModule[99]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18455_none_72d576ad8665e853\gdiplus.dll
LoadedModule[100]=C:\Windows\system32\MSIMG32.dll
LoadedModule[101]=D:\Flight Simulator X\xuipc.dll
LoadedModule[102]=D:\Flight Simulator X\livingwater.dll
LoadedModule[103]=D:\Flight Simulator X\fs-traffic.dll
LoadedModule[104]=D:\Flight Simulator X\gps.dll
LoadedModule[105]=C:\Windows\system32\MSWSOCK.dll
LoadedModule[106]=C:\Windows\system32\SHFOLDER.dll
LoadedModule[107]=C:\Windows\system32\RICHED20.DLL
LoadedModule[108]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[109]=C:\Windows\system32\rsaenh.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\syswow64\CLBCatQ.DLL
LoadedModule[114]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[115]=C:\Windows\system32\wbemcomn.dll
LoadedModule[116]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[117]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[118]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[119]=C:\Windows\system32\NTDSAPI.dll
LoadedModule[120]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL
LoadedModule[121]=C:\Windows\system32\dxgi.dll
LoadedModule[122]=C:\Windows\system32\d3d10.dll
LoadedModule[123]=C:\Windows\system32\d3d10core.dll
LoadedModule[124]=C:\Windows\system32\d3d11.dll
LoadedModule[125]=C:\Windows\system32\nvd3dum.dll
LoadedModule[126]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[127]=C:\Windows\system32\nvwgf2um.dll
LoadedModule[128]=C:\Windows\system32\bcrypt.dll
LoadedModule[129]=C:\Windows\system32\D3DCompiler_34.dll
LoadedModule[130]=C:\Windows\SysWOW64\bcryptprimitives.dll
LoadedModule[131]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[132]=C:\Windows\system32\d3d10_1.dll
LoadedModule[133]=C:\Windows\system32\d3d10_1core.dll
LoadedModule[134]=C:\Windows\system32\WTSAPI32.DLL
LoadedModule[135]=C:\Windows\system32\WINSTA.dll
LoadedModule[136]=C:\Windows\SysWOW64\gameux.dll
LoadedModule[137]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll
LoadedModule[138]=C:\Windows\SysWOW64\XmlLite.dll
LoadedModule[139]=C:\Windows\SysWOW64\wer.dll
LoadedModule[140]=C:\Windows\System32\Wpc.dll
LoadedModule[141]=C:\Windows\System32\wevtapi.dll
LoadedModule[142]=C:\Windows\System32\msxml6.dll
LoadedModule[143]=C:\Windows\system32\SAMLIB.dll
LoadedModule[144]=C:\Windows\system32\netutils.dll
LoadedModule[145]=C:\Windows\system32\uiautomationcore.dll
LoadedModule[146]=C:\Windows\system32\OLEACC.dll
LoadedModule[147]=C:\Windows\System32\MMDevApi.dll
LoadedModule[148]=C:\Windows\System32\PROPSYS.dll
LoadedModule[149]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[150]=C:\Windows\system32\HID.DLL
LoadedModule[151]=C:\Windows\system32\ntmarta.dll
LoadedModule[152]=C:\Windows\syswow64\WLDAP32.dll
LoadedModule[153]=C:\Windows\system32\XInput9_1_0.dll
LoadedModule[154]=C:\Windows\system32\wdmaud.drv
LoadedModule[155]=C:\Windows\system32\ksuser.dll
LoadedModule[156]=C:\Windows\system32\AVRT.dll
LoadedModule[157]=C:\Windows\system32\msacm32.drv
LoadedModule[158]=C:\Windows\system32\midimap.dll
LoadedModule[159]=C:\Windows\system32\dinput.DLL
LoadedModule[160]=C:\Windows\SysWOW64\pid.dll
LoadedModule[161]=C:\Windows\system32\DNSAPI.dll
LoadedModule[162]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[163]=C:\Windows\system32\WINNSI.DLL
LoadedModule[164]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[165]=C:\Windows\system32\rasadhlp.dll
LoadedModule[166]=C:\Windows\System32\wship6.dll
LoadedModule[167]=C:\Windows\System32\wshtcpip.dll
LoadedModule[168]=D:\Flight Simulator X\bglmanx.dll
LoadedModule[169]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[170]=D:\Flight Simulator X\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow.dll
LoadedModule[171]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll
LoadedModule[172]=d:\Program Files (x86)\Flight One Software\Audio Environment\AEMODULE.dll
LoadedModule[173]=D:\Flight Simulator X\VistaMare\ViMaCoreX.dll
LoadedModule[174]=D:\Flight Simulator X\VistaMare\bin\VMCX_SP2.dll
LoadedModule[175]=D:\Flight Simulator X\VistaMare\bin\ViMaNET.dll
LoadedModule[176]=D:\Flight Simulator X\Modules\A2A_Feel.dll
LoadedModule[177]=C:\Windows\SysWow64\XAudio2_6.dll
LoadedModule[178]=D:\Flight Simulator X\Modules\AccuFeelMenu.dll
LoadedModule[179]=D:\Flight Simulator X\Modules\FSUIPC4.dll
LoadedModule[180]=D:\Flight Simulator X\PMDG\DLLs\PMDGOptions.dll
LoadedModule[181]=D:\Flight Simulator X\PMDG_SimConnect_Ldr.dll
LoadedModule[182]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCP90.dll
LoadedModule[183]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll
LoadedModule[184]=C:\Windows\WinSxS\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_4bf7e3e2bf9ada4c\mfc90.dll
LoadedModule[185]=C:\Windows\WinSxS\x86_microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_49768ef57548175e\MFC90ENU.DLL
LoadedModule[186]=D:\Flight Simulator X\PMDG\DLLs\PMDGEvents.dll
LoadedModule[187]=D:\Flight Simulator X\PMDG\DLLs\PMDGSounds.dll
LoadedModule[188]=D:\Flight Simulator X\WaveLib.dll
LoadedModule[189]=D:\Flight Simulator X\PMDG\DLLs\PMDG_HUD_interface.dll
LoadedModule[190]=D:\Flight Simulator X\PMDG\DLLs\PMDG_Interface.dll
LoadedModule[191]=D:\Flight Simulator X\Modules\LVLD.dll
LoadedModule[192]=D:\Flight Simulator X\Level-D Simulations\B767-300\leveld.dll
LoadedModule[193]=D:\Flight Simulator X\Aerosoft\Flight Recorder\AS-FlightRecorder.dll
LoadedModule[194]=D:\Flight Simulator X\as_srv\as_btstrp.dll
LoadedModule[195]=C:\Windows\system32\mscoree.dll
LoadedModule[196]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
LoadedModule[197]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll
LoadedModule[198]=C:\Windows\assembly\NativeImages_v2.0.50727_32\mscorlib\38bf604432e1a30c954b2ee40d6a2d1c\mscorlib.ni.dll
LoadedModule[199]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorsec.dll
LoadedModule[200]=C:\Windows\syswow64\imagehlp.dll
LoadedModule[201]=C:\Windows\system32\ncrypt.dll
LoadedModule[202]=C:\Windows\system32\GPAPI.dll
LoadedModule[203]=C:\Windows\system32\cryptnet.dll
LoadedModule[204]=C:\Windows\system32\SensApi.dll
LoadedModule[205]=D:\Flight Simulator X\as_srv\as_connect.dll
LoadedModule[206]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorjit.dll
LoadedModule[207]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System\908ba9e296e92b4e14bdc2437edac603\System.ni.dll
LoadedModule[208]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Drawing\836e10dfd0811b303553216f5cb092ef\System.Drawing.ni.dll
LoadedModule[209]=C:\Windows\system32\Secur32.dll
LoadedModule[210]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll
LoadedModule[211]=D:\Program Files (x86)\FSForce 2\FSForce.dll
LoadedModule[212]=C:\Windows\SysWOW64\ieframe.dll
LoadedModule[213]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll
LoadedModule[214]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll
LoadedModule[215]=C:\Windows\SysWOW64\mshtml.dll
LoadedModule[216]=C:\Windows\system32\msimtf.dll
LoadedModule[217]=C:\Windows\system32\msls31.dll
LoadedModule[218]=C:\Windows\system32\d2d1.dll
LoadedModule[219]=C:\Windows\system32\DWrite.dll
LoadedModule[220]=C:\Windows\system32\D3D10Warp.dll
LoadedModule[221]=C:\Windows\system32\MLANG.dll
LoadedModule[222]=D:\Flight Simulator X\VistaMare\bin\ViMaIScnX.dll
LoadedModule[223]=D:\Flight Simulator X\GAUGES\PMDG_777X.DLL
LoadedModule[224]=C:\Windows\system32\NETAPI32.dll
LoadedModule[225]=C:\Windows\system32\srvcli.dll
LoadedModule[226]=C:\Windows\system32\wkscli.dll
LoadedModule[227]=C:\Windows\system32\WSOCK32.dll
LoadedModule[228]=C:\Windows\SysWow64\XAudio2_7.dll
LoadedModule[229]=D:\Flight Simulator X\GAUGES\PMDG_777X_3.DLL
LoadedModule[230]=D:\Flight Simulator X\FS2Crew2010\Versions\PMDG777\Gauges\FS2Crew777.GAU
LoadedModule[231]=D:\Flight Simulator X\libcurl.dll
LoadedModule[232]=C:\Windows\system32\FS2AUDIO.dll
LoadedModule[233]=C:\Windows\system32\X3DAudio1_6.dll
LoadedModule[234]=C:\Windows\SysWow64\xactengine3_4.dll
LoadedModule[235]=C:\Windows\SysWow64\XAudio2_4.dll
LoadedModule[236]=C:\Windows\system32\dhcpcsvc.DLL
LoadedModule[237]=C:\Windows\System32\netprofm.dll
LoadedModule[238]=C:\Windows\System32\nlaapi.dll
LoadedModule[239]=C:\Windows\system32\dhcpcsvc6.DLL
LoadedModule[240]=C:\Windows\System32\npmproxy.dll
LoadedModule[241]=C:\Windows\system32\napinsp.dll
LoadedModule[242]=C:\Windows\system32\pnrpnsp.dll
LoadedModule[243]=C:\Windows\System32\winrnr.dll
LoadedModule[244]=D:\Flight Simulator X\Gauges\PMDG_777X_2.dll
LoadedModule[245]=C:\Windows\system32\snmpapi.dll
LoadedModule[246]=C:\Windows\system32\icmp.Dll
LoadedModule[247]=C:\Windows\system32\msadp32.acm
LoadedModule[248]=D:\Flight Simulator X\Aerosoft\AES\ViMaCli.dll
LoadedModule[249]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Configuration\d3c11f742f22b34baf347da15c4a975e\System.Configuration.ni.dll
LoadedModule[250]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Xml\d49908aa93a23c84847b1f8b1b667860\System.Xml.ni.dll
LoadedModule[251]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\diasymreader.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=DataRequest
State[1].Value=Bucket=-409487666/nBucketTable=1/nResponse=1/n
FriendlyEventName=APPCRASH
ConsentKey=APPCRASH
AppName=Microsoft Flight Simulator®
AppPath=D:\Flight Simulator X\fsx.exe
ReportDescription=Stopped working
 

 

 

 

Share this post


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

Thanks for providing your system specs, appcrashview report, and detailed information about the crash.  To be honest I have never heard of the i7-4740k cpu.  Did you mean 4770K?

 

You state you are not overclocked but have the 'k' series which means your system can be overclocked.  In any case, this error is mostly caused by a bad voltage setting in the BIOS if the system is not overclocked.  If you have it set to optimal defaults, that's great.  But, if you changed just one tiny setting, that could be the cause.

 

If you have MyTrafficX, version 5.4c, installed, this will cause this crash, then maybe a StackHash and then later back to ntdll.dll.  It is caused by using the 2012 or 2013 schedules posted on the developers website.  Just reinstall and do not use those schedules and just the default.  You can make a simple check by disabling MyTrafficX in the Scenery Library.

 

Although you have a super fantastic system that is almost exactly like mine, you cannot throw your fsx/display driver settings to the max.  This will cause the crash.

 

Any tweaks in the FSX.cfg will cause this crash.  The BufferPool tweak causes the most instability and this crash.  This is why I recommend you move your fsx.cfg to a temporary folder (or rename it), restart FSX and let the config rebuild.  They say do this is better than reinstalling FSX.  It gets rid of those nasty tweaks you might have added and/or high settings.  There is no tweak that can allow FSX to run at max settings.  Certainly you will have no problems on many flights but it won't last and you will get periodic crashes or freezes.  I don't think we'll ever see max settings in FSX as it is an old engine and cannot use all of the cpu cores (even with Affinity Mask employed). If you want to just see if the BufferPool tweak is causing your problems (if you have it employed), you can comment it out of your FSX.cfg and it will not load when you start up FSX again. This is how you comment out a parameter:

 

//[bufferpools] (note the two slashes before the entry. This will prevent the item to load)

 

AVSIM has a great FSX Configuration Guide, located to the right of this forum under Hot Spots, for the best fsx settings for most systems.  I use them.  They are great.  I do have Texture_Max_Load set to 2048 (had 4096 but got periodic anomalies), and LOD_Radius=6.5.  No tweaks.  I get great graphics.  I do not think FSX was developed to use the max settings.  I do believe that the FSX development team probably thought they could update the product periodically to better optimize FSX, but never to use the max settings. 

 

AVSIM also has a great CTD Guide which I think you might have already seen as you got very defensive in your post in regards to overclocking.  But, if not, there are other possible solutions to this problem.  There is no known fix for everyone who gets this error.  You have to investigate the cause yourself.  We have a new update in the offing and this is one of the recommendations for investigating your crash:

 

Return FSX/P3D to the default configuration. This is done by rebuilding your FSX/P3D configuration; disabling add-on scenery; and disabling modules in your dll.xml or exe.xml as follows –

 

Rebuild the FSX/P3D Configurations – Many CTD’s can be fixed by renaming your FSX or P3D configuration to FSX or P3D.orig (or you can move the file to a temporary folder), restarting FSX/P3D and letting the configuration rebuild. The FSX/P3D configurations are hidden (C:\User\(yourusername)\AppData\ Roaming\ Microsoft or Lockheed Martin\FSX or P3D. It has been said that rebuilding your configuration is about the same as uninstalling/reinstalling FSX or P3D, as appropriate, as it removes tweaks or other parameters that you have added and may be causing more harm than good.

Disable Add-on Scenery – Disable all your add-on scenery in the Scenery Library (Hidden - C:\Program Data\Microsoft or LockHeed Martin\FSX or P3D), then run the program and see if this fixes the problem. If it does, then the problem is probably associated with one or more of your add-on sceneries. To find the offending scenery, enable your add-ons 3-4 at a time until the CTD returns.

Disable modules in dll.xml and exe.dll– Sometimes a module you have installed is corrupted or is somehow duplicated in the dll.xml. You can check to see if any modules are the cause of your crashes by disabling all modules (except the first one). Change the parameter False in the line <Disabled>False</Disabled> to True or simply move the dll.xml and exe.xml to a temporary folder and restart your program. If the problem is fixed, move the xml file back into the proper fsx folder and enable each module one by one until the culprit is found.

 

Hope this helps.

 

Best regards,

Share this post


Link to post
Share on other sites

Hi Jim

 

A typo - I did mean 4770k!

 

Anyway, thanks for the information. I will investigate the MYT 5.4 and bufferpool routes first. I have very little in the way of tweaks in the config file and settings are not OTT - mainly what is recommended by NickN except for LOD is set at 4.5 for now. It is certainly not what I would call 'over tweaked'.

 

Jonathan

Share this post


Link to post
Share on other sites

Well, NickN does not like the BufferPool tweak either but has some recommendations in case you want to try it. Tweaks in fast systems like yours are useless IMHO.

 

Best regards,

Share this post


Link to post
Share on other sites

I had that crash when I was using the DX10 Fixer. Great program but I could not figure out how to eliminate the CTD's so I don't run it. Are you by any chance running DX10?

Share this post


Link to post
Share on other sites

Hi Mike,

 

Yes I am running DX10 with DX10 fixer. That gives me something else to investigate.

 

Jonathan

Share this post


Link to post
Share on other sites

Hi Mike,

 

Yes I am running DX10 with DX10 fixer. That gives me something else to investigate.

 

Jonathan

 

I am curious if you find anything. I also would appreciate if you do find anything to post it here. I did research it but I could never get anywhere. I have a suspicion that it may be related to the Nvidia drivers. Since Nvidia does not offer much support for us measly FSX users in their driver updates I am unsure a fix would ever be available. 

Share this post


Link to post
Share on other sites

So, through some trial and error here is what I have discovered. I reverted the MYT schedules back to 2012, and removed the bufferpools tweak. I was able to successfully complete 2 long haul flights in a row with the T7. I added bufferpools tweak back in and again was able to complete 2 long flights in the PMDG747. I kept DX10 in. So I may have narrowed this down to MYT 5.4. I will keep with config as it is for now and see how I go.

Share this post


Link to post
Share on other sites

So I may have narrowed this down to MYT 5.4. I will keep with config as it is for now and see how I go.

If you look in the developer's forum for My Traffic X, a lot of people had the NTDLL.dll and/or StackHash with the 5.4c version of My Traffic X. Personally I reverted back to 5.4b and did not load any schedule he has on his website. Just used the one that came with the program and I have tons of traffic and FSX/P3D have not worked so good (except for yesterday I got an OOM which was easily fixed). Hopefully that was your fix and you can once again enjoy FSX.

 

Best regards,

Share this post


Link to post
Share on other sites

So, through some trial and error here is what I have discovered. I reverted the MYT schedules back to 2012, and removed the bufferpools tweak. I was able to successfully complete 2 long haul flights in a row with the T7. I added bufferpools tweak back in and again was able to complete 2 long flights in the PMDG747. I kept DX10 in. So I may have narrowed this down to MYT 5.4. I will keep with config as it is for now and see how I go.

 

I am glad that you narrowed it down to the MYT schedules. I tried that and had no luck. I even uninstalled MT and reinstalled UT2. The only way to eliminate the error was to not run in DX10. Which is too bad because it was a tradeoff for the odd OOM at the end of some long hauls. I  even had the error on a new rig I built. I have almost zero knowledge about these matters by I suspect that it is a driver issue with certain Nvidia cards. 

Share this post


Link to post
Share on other sites

I am glad that you narrowed it down to the MYT schedules. I tried that and had no luck. I even uninstalled MT and reinstalled UT2. The only way to eliminate the error was to not run in DX10. Which is too bad because it was a tradeoff for the odd OOM at the end of some long hauls. I  even had the error on a new rig I built. I have almost zero knowledge about these matters by I suspect that it is a driver issue with certain Nvidia cards.

Respectfully, it has been proven beyond any reasonable doubts that the information provided by jjf is accurate. It has happened to a lot of individuals and there are even discussions about it on the developers website. That's more than sufficient proof. It is impossible, literally impossible, for DX10 to cause an ntdll.dll error by itself. There has to be another denominator involved like the BuffersPool tweak or another bad tweak that was not properly entered in the FSX.cfg. If it were certain video cards, then all of those individuals with certain video cards would be having ntdll.dll errors. Please understand that there has been a lot of investigations conducted by several to find the reasons for the ntdll.dll errors and they are documented in the AVSIM CTD Guide. Never has the video card been document to cause the ntdll.dll crash. Hardware that fails usually results in a Blue Screen of Death (BSOD), not a system module.

 

I think your last sentence says it all.

 

Best regards,

Share this post


Link to post
Share on other sites

Respectfully, it has been proven beyond any reasonable doubts that the information provided by jjf is accurate. It has happened to a lot of individuals and there are even discussions about it on the developers website. That's more than sufficient proof. It is impossible, literally impossible, for DX10 to cause an ntdll.dll error by itself. There has to be another denominator involved like the BuffersPool tweak or another bad tweak that was not properly entered in the FSX.cfg. If it were certain video cards, then all of those individuals with certain video cards would be having ntdll.dll errors. Please understand that there has been a lot of investigations conducted by several to find the reasons for the ntdll.dll errors and they are documented in the AVSIM CTD Guide. Never has the video card been document to cause the ntdll.dll crash. Hardware that fails usually results in a Blue Screen of Death (BSOD), not a system module.

 

I think your last sentence says it all.

 

Best regards,

 

Jim, do you mean the part about me having zero knowledge or about the part that I suspect that the Nvidia drivers are at fault.  :wink: Certainly I am open to looking through my cfg and trying to determine what is at fault because I would love to eliminate the error myself so that I can return to using DX10. What do you suggest? For me it was as simple as turning the DX10 off and that solved the issue.   

Share this post


Link to post
Share on other sites

Certainly I am open to looking through my cfg and trying to determine what is at fault because I would love to eliminate the error myself so that I can return to using DX10. What do you suggest? For me it was as simple as turning the DX10 off and that solved the issue.

DX10 Preview works if your have FSX SP2 or Acceleration installed. It's when you start tweaking your FSX.cfg and messing with other files when DX10 might have issues. There are no secrets in enabling DX10 Preview. It's a higher technology than DX9 (duh!) but Microsoft techs were not able to finish the programming to make DX10 Preview work the best and give you optimal performance. It never crashed when it was first released in 2007 (and everyone had underpowered computer systems and kept their settings at modest levels). You simply enabled it and you saw new technology at work, like shadows in the cockpit. But there were faults and the most obvious issue was the "flickering" on runways and taxiways. Along came SteveP who found that there were wrong figures (parameters) in the General10.fx file located in the ShadersHLSL folder (note that General10.fx was changed. That's the DX10 file. The DX9 files is just General.fx and it is in the same folder. So, when you turn off DX10 Preview, the General.fx file will be used. When you enable DX10 Preview, then General10.fx will be used by FSX. Hopefully no one tried to modify the General.fx file instead of the General10.fx file!!). Anyway, SteveP changed several parameters in this file and the anomalies, for the most part, went away. This is when I decided to turn DX10 Preview ('Preview' is there for a purpose - it's not a finished product and Microsoft FSX developers were going to improve the technology but they were released by Microsoft before they could complete the programming)(sorry for saying this again but it is most important). So, DX10 Preview is really nothing major. It fixes the "flickering" on the runways/taxiways and that was one of the major issues when it was first released. Everyone loved the shadow immersion in the virtual cockpits but hated that flickering when they landed. So SteveP fixed this problem and it was a freeware fix. Again, nothing major but a needed fix and many, especially me, were very happy he found the solution.

 

AVSIM then set up a DX10 Preview forum to discuss how to install this free fix from Steve as even I had problems. Then, members began discussing tweaking DX10 Preview and SteveP found more enhancements to DX10 Preview and he was talked into releasing a commercial program to install DX10 Preview by several members and he added some fsx.cfg tweaks and he fix a few other things in FSX, like water, rain, and provided support for legacy aircraft people imported from older versions of flight simulator. I now use DX10 Preview exclusively. I think having the shadowing in the VC's is great. I have no tweaks in my cfg's. Don't believe in them and I have perfect DX10 Preview and no crashes. Again, DX10 Preview is really nothing super special. FSX was developed for DX9 technology. DX10 only really enhances your immersion in the VC and, of course, you have the flickering gone at all of the airports in the world (well mostly). So, why did FSX crash when you unticked DX10 Preview and went back to DX9? (the General.fx file). Could be several issues. It could be the tweaks that were loaded in your fsx.cfg w/o your knowledge. I have never heard of anyone have this issue but it is a possibility. You could have installed a BufferPools tweak as I think it is one of the recommendations. That causes more instability to FSX than any other tweak. You have to know exactly what the parameters are for YOUR system and not for everyone else's system.

 

The ntdll.dll is a system module and it crashes for a lot of reasons. Again, the cause for the crash is not the same for everyone. It's one of those things you have to investigate. I got the ntdll.dll crash just for changing a voltage setting in my BIOS. Some computer expert (NickN) recommended the change and he had the same exact motherboard and cpu as I owned so I figured it would work for me. It didn't. He said I had to test for stability. I didn't. I thought that since he has the same system as mine, it will work just the same for me. I'm telling you this as to emphasize that not every system is the same. There are some really great i7 4770K CPU's that will overclock without any problems to 4.8GHz and maybe higher and there are i7 4770K CPU's like mine that can barely overclock above 4.2GHz without having stability problems. Go figure. Go ahead, look on the Internet. It is documented that not all CPU's are the same. This problem is inherent with every Intel CPU currently on the market. You just have to be lucky to be that one who gets the really great CPU that overclocks easily and is really stable. If not, then you have to lower your voltages, your overclocks, etc., etc., until your system does become stable because, if you do not, you are most like going to get an ntdll.dll crash. Maybe a StackHash too. This is why I recommend in the AVSIM CTD Guide that individuals return their bios back to the Optimal defaults to see if the bios is the issue here (just one part of the investigation). That's a simple fix if it proves your system is now more stable with the optimal defaults rather than the overclock. You can slowly start the process of overclocking or keep it at the optimal defaults.

 

In the AVSIM CTD Guide (just updated), there's a section at the beginning on what to do once you encounter a crash. I give explicit instructions on how to return FSX to the default for testing. Isn't this better than completely uninstalling FSX and all of your addons and then installing them again? If you can get your system back to the default and it works perfectly without a crash (albeit with some ugly textures), then you are on the road to completely fixing your problem. You simply move files over to temporary directory's, go to the default, and then start moving those same files back, one at a time until you see the crashes again.

 

So, there is a lot of guidance here at AVSIM to help you solve your problems. Every crash can be fixed and it may be as simple as just using a FSX.cfg without tweaks and default settings or just returning your overclock back to the optimal defaults.

 

Hope this helps.

 

Best regards,

Share this post


Link to post
Share on other sites

Thanks Jim. I will read through your response and try your suggestions. You certainly put a lot of time and energy into helping people such as myself, thank you.

Share this post


Link to post
Share on other sites

Well I did some work based on Jim's recommendation and I am going to backtrack a bit here and admit that my original reply to the OP was wrong. I had confused the ntdll.dll error with another error that I was getting that about a year ago and to the best of my ability determined was related to an Nvidia driver incompatibility. When I first purchased Steve's DX10 Fixer it eliminated the OOM's I had been getting  but introduced nvwgf2um.dll errors. Along with this error I was getting ntdll.dll and a stackhash error. It took literally months of trying to isolate each error and solve the issue. I did solve the issues one by one. As for MyTraffic I was never able to fix the error even from help from MyTraffic forums. I uninstalled the program and re installed UT2 which was fine. There are trade offs that are not relevant for this conversation. In terms of my confusion with the errors, I am an Nvidia 3d Vision user. I use 3D glasses and find them a necessity when flying. When using this hardware with DX10 I would consistently get a  nvwgf2um.dll error. I Googled the issue and found very little in the way of help and as  FS users are a very small minority and FSX users that are 3D vision users are and even smaller sample size there was very little help available.  Since I cannot live without 3D I elected to not use DX10 and put up with the occasional OOM. So if someone is reading this thread I hope that this clears things up. Oh, and Jim any thoughts on nvwgf2um.dll errors with Nvidia 3D vision? 

Share this post


Link to post
Share on other sites

As for MyTraffic I was never able to fix the error even from help from MyTraffic forums. I uninstalled the program and re installed UT2 which was fine.

The only thing I have found wrong with MyTrafficX, V5.4c is the schedules you can download from the developers website. If you do not install one of these schedules, no crash. Some have found a problem with objects in one of the AFCAD's that come with MyTrafficX (there are hundreds of them installed with MyTrafficX so that the AI can properly takeoff and land). I have not seen this [yet].

 

Oh, and Jim any thoughts on nvwgf2um.dll errors with Nvidia 3D vision?

It's a display driver crash. Some say using software rendering rather than hardware rendering fixed their problem. Many others stated it was fixed if they turned off 3D Vision (which is not an option for you). If it is overclocked or you messed around with the base clock offset or memory clock offset, then that could be the problem too. I know it is for the nvlddmkm.dll CTD. There are some video card makers who have programs to mess around with the GPU OC.

 

I'm not sure whether 3D works with DX10. I have never tried it since Steve's DX10 fix was released. I have 3d Vision too but don't use it as it's a hassle to set up my monitor that can display it. I also would have to install and enable 3D. I see no reason why it should not work in DX10 though. DX10 is the same as DX9 except it is better technology and it provides shadows in the VC's and some other minor things. Microsoft never really got DX10 programmed properly and that's why Steve is throwing on bandages with his fixer.

 

Since I cannot live without 3D I elected to not use DX10 and put up with the occasional OOM.

So you are getting an OOM and not the nvwgf2um.dll error? Or you are getting both. The OOM has several fixes and they are listed in the AVSIM CTD Guide. DX10 definitely does not cause OOM's.

 

Best regards,

Share this post


Link to post
Share on other sites

My wording must have been confusing. I don't get OOM's when using DX10 I only get them using DX9.  So that is not an issue. As far as 3D vision is concerned it works perfectly except for the aforementioned issues. I should also mention that when I am using 3D and DX10 I only get that  nvwgf2um.dll error plus toward the end of the flight especially long hauls the 3D vision will just stop working or worse yet the screen will start to freeze.  As far as overclocking I have no over clocking of the GPU or CPU on this rig yet. 

Share this post


Link to post
Share on other sites

I should also mention that when I am using 3D and DX10 I only get that nvwgf2um.dll error plus toward the end of the flight especially long hauls the 3D vision will just stop working or worse yet the screen will start to freeze.

This is a known symptom of OOM's based on depletion of VAS. Are you monitoring your VAS usage? In the AVSIM CTD Guide we included a method to monitor VAS.

 

Best regards,

Share this post


Link to post
Share on other sites

This is a known symptom of OOM's based on depletion of VAS. Are you monitoring your VAS usage? In the AVSIM CTD Guide we included a method to monitor VAS.

 

Best regards,

 

Thanks Jim, I will continue to look at the guide and experiment. One of the issues that hampers my ability to solve this issue, is time. Just being able to have a flight is a luxury. Most of the time I do not wish to trouble shoot, I just want to fly successfully. This week I have been able to put more time into flying and these forums simply because I have a stomach virus and I have been home sick. Setting up a flight and then flying and watching it crash is so infuriating  that ultimately I just go with what will give success rather than a CTD after a long flight or even an hour setting up a long haul. These issues I have been chasing have taken a lot of time to research an implement. Most of that reach is done on these forums and I have read through a lot of your suggestions, so thanks. 

Share this post


Link to post
Share on other sites

Setting up a flight and then flying and watching it crash is so infuriating that ultimately I just go with what will give success rather than a CTD after a long flight or even an hour setting up a long haul. These issues I have been chasing have taken a lot of time to research an implement.

VAS is the biggest problem we are having with FSX now. Most everyone has upgraded to the new i7 cpu's and most everyone tries to crank up their settings to the max thinking their computer can now handle it. It just makes things worse. PMDG has information about it starting around page 21 of the Intro Guide that comes with their 777. AVSIM has some information in the AVSIM CTD Guide. If you lower your FSX.cfg settings and display driver settings, you might make it past two hours. Several have gone longer than that. It all depends on what you have running during the flight.

 

Best regards,

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