FSX crashes after I go to desktop then try to open it again

[tonyprent22 0]

I'll attempt to be as detailed as I can.

I've had FSX steam edition for over a year now.  Just recently I decided to try and stretch my legs a little in the simulator, and began adding on to it. 

 

First I downloaded ORBX Global Base Pack and Global openLC NA Alaska/Canada.

 

Then, I downloaded PMDG's 737 NGX, and began flying.  I use Track IR, so I generally load straight into the virtual cockpit.  Everything seemed fine EXCEPT if I hit Shift-1 and pulled up the main panel, it was compressed, and most of the gauges missing.  I read that it could be an error in the install, but the other symptoms they said would be there, weren't (i.e. autopilot issues, gear not being there, etc.).

Soon after, I joined simbrief for flight planning, and PRO-ATC-X.  I was using all the different applications smoothly, with the only issue being the main panel issue that I'd pull up with shift-1, the virtual cockpit being completely fine.  Then trouble hit.  The other night I was flying KMCO to KEWR.  I noticed on takeoff there were globes of light flying by me, as though the sim had glitched and I was passing incoming flights that were only 50 feet off the ground.  I ignored it, but midway through the flight my auto pilot began glitching so I shut down, restarted my machine, and everything seemed fine again but I didn't do a flight, I shut down for the night. 

The next day I downloaded the trial version of GSX.  The install got hung up on installing SODE, so I stopped it and tried again, still hung up, so I went in and uninstalled GSX.  I went in to fly, and set up PRO ATC X then jumped into the flight, getting my ground power connected and running before jumping out of the sim to start PRO ATC.  Boom, FSX crashed.  I tried again, and crash.  I kept trying to start FSX, then jump to PRO ATC and then back, and each time it would crash.  I decided to work backwards.  Sans PRO ATC I loaded my flight and jumped to desktop, crash.  I don't load PROATC and only load FTX Central for ORBX and try again.  Crash.  I then discovered I needed to uninstall SimObject Display Engine which was still installed from the hung up GSX install.  I deleted it last night, and surprise, I was able to jump to desktop, starts PRO ATC and jump back in just fine.  Flew from KMCO to KEWR no issues.  Thought issue was resolved.  Until today.  I get home from work and jump into the sim, load everything up, jump to desktop to start PRO ATC and crash.  I'm a bit lost at where to go from here now and hoping someone here can lend a hand.  I know it's a long read but I wanted to be detailed.

[Jim Young 2,356]

 

 

Until today. I get home from work and jump into the sim, load everything up, jump to desktop to start PRO ATC and crash.

 

I think you have answered your question.  It's ProATC that is causing the crash.  I mean, you loaded everything up and it was working great until you went to desktop and started the ProATC app.  I always start ProATC first, then AS16, then start FSX but there really is no proper way of starting up apps.  So, just starting up ProATC and not clicking on Fly Now?  What's loading?  Nothing.  ProATC is just starting up when you open up the app.  It has no interaction with FSX until you click on Fly Now with a flight plan.  You did import the lastest AIRAC?  If you clicked on Fly Now and it crashed, make sure the flight plan is compatible with YOUR version of ProATC.  Normally, ProATC will tell you to open and save your flight plan first if it finds it incompatible.  The latest version seems to be accepting all previous flight plans so, if you have the latest version of ProATC, then that should not be an issue.

 

An old version of FSUIPC is sometimes incompatible if not kept up-to-date.  ProATC does not need FSUIPC though.

 

TrackIR might be an issue in that going to the desktop causes it to lose focus until you get back to the application.  Hard to tell.

 

When you start up FSX, all of the modules in the dll.xml load before you get to the setup screen and, since you loaded everything successfully, you cannot blame the dll.xml (I mention as it causes a lot of crashes).

 

You need to check your Event Viewer for an event surrounding this crash.  It might give you a clue.  See page 7 of the AVSIM CTD Guide regarding how to use the Event Viewer properly.  You cannot simply go to the Application Events so you must follow the guidance in the AVSIM CTD Guide.

 

On the same page, there's a download link and guidance for installing and running AppCrashView.  This program interprets all of your Windows Error Reports (WERs) and provides a possible faulting module.  Heck, it might show that your video card caused the crash or some other Windows program.

 

It could be that SimBrief is causing the problems too.  SimBrief and ProATC use simconnect and maybe there's a conflict?  I've never used SimBrief so not sure what it does.  I looked it up on the Internet and it seems like a legitimate program.  Not sure why you would use SimBrief AND ProATC.  ProATC provides flightplans and you can modify those flightplans to mesh with whatever SimBrief recommends for a good flight plan.  You then must save the flightplan in ProATC so there is absolutely no need for SimBrief to be running (unless you are not loading any of the ProATC flightplans and I have never heard of that before).

 

So some suggestions.  Hope one works for you.

 

Best regards,

Jim

[tonyprent22 0]

Thanks for your reply! My apologies, I wasn't very clear in the original post.  I've read that the process of Pro ATC is to start it up, then go into FSX and set up your flight and then fly now inside of FSX.  Once the power is connected in the plane, it's then that I'm backing out of FSX to click "Fly Now" inside of Pro ATC, following the steps that Pro ATC has lined out.  The crash happens after the power is on onboard, and when I take FSX out of full screen, and click on ANY window outside of FSX.  It's at that moment I get an immediate crash.  I can't even click the fly now option in Pro ATC because generally if I just click outside the FSX window it crashes.  I do also have the current AIRAC and the most current version of Pro ATC.  Although I feel as though the issue has more to do with the install of GSX.

 

Not sure if track IR would be the issue, as I had already flown about 200 hours in the game with Track IR before I installed GSX and the crashes began.

Thanks for the tip on SimBrief and utilizing just Pro ATC for flight planning.  What I do generally is save the flight plan and export it out of sim brief and then load it into Pro ATC since I find the user interface of SimBrief to be more user friendly. 

I'll check out the crash report and see if I can glean any information from that next time it crashes. 

[Jim Young 2,356]

 

 

The crash happens after the power is on onboard, and when I take FSX out of full screen, and click on ANY window outside of FSX.

 

This is a known bug in FSX depending on the exact procedure you are using.  I use Alt+Enter to go from Full Screen to Windows and then back to Full Screen.  If you are in Full Screen and click on the Tab key, FSX will crash or will make it very difficult to get back to your flight session.

 

Best regards,

Jim

[tonyprent22 0]

Mr. Young,
Thank you SO MUCH for this.  I had no idea.  I'm using steam, so to go to desktop I'm utilizing Shift + Tab to bring up the Steam interface, then I press the Windows key to force to the desktop.  As I'm typing this however, I realize that currently my process has been to go to the menu bar, uncheck full screen to have FSX go to a windowed screen, and then I click outside that screen at it crashes, so actually I abandoned using the tab button as of a week ago.  I'm going to try Alt+Enter tonight when I get home, and also try the crash report software you mentioned.  Hopefully with the work week over I can dive back into the issue and perhaps post a screen grab or just record my process and link it here so people can see.  Again, you've been so helpful, I appreciate it.  What a great community this is.

[Jim Young 2,356]

Glad to be able to help.  I used Shift+Tab soon after release of FSX and once or twice was finally able to get back into my flight but mostly it crashed or I had to manually shut FSX down.

 

Best regards,

Jim

[tonyprent22 0]

Happened again so on your advice I copied both the APPCRASHVIEW report and the Event report.  First is the appcrashview report:

Version=1
EventType=APPCRASH
EventTime=131215776139309026
ReportType=2
Consent=1
UploadTime=131215776140253731
ReportIdentifier=db5665aa-9800-11e6-9c0c-d8cb8a9e2a08
IntegratorReportIdentifier=23a93e5d-3f34-4371-a093-3390e9ded745
WOW64=1
NsAppName=fsx.exe
AppSessionGuid=0000097c-0004-000a-3365-ee360d2cd201
TargetAppId=W:0000da39a3ee5e6b4b0d3255bfef95601890afd80709!0000da39a3ee5e6b4b0d3255bfef95601890afd80709!fsx.exe
TargetAppVer=2015//07//10:10:12:42!2ac31c!fsx.exe
BootId=4294967295
Response.BucketId=41573d8a7bd512fb31896b88a4e53064
Response.BucketTable=1
Response.LegacyBucketId=108434071517
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=fsx.exe
Sig[1].Name=Application Version
Sig[1].Value=10.0.62615.0
Sig[2].Name=Application Timestamp
Sig[2].Value=559f9a9a
Sig[3].Name=Fault Module Name
Sig[3].Value=ntdll.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.14393.206
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=57dacde1
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=00026d39
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.14393.2.0.0.768.101
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=1557
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=1557cf1a4e7c47eaa71023ae77db5ccd
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=70ee
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=70ee799d3e6c56ac9376d6ed1fce1baa
UI[2]=H:\Steam\steamapps\common\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]=H:\Steam\steamapps\common\FSX\fsx.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\System32\KERNEL32.DLL
LoadedModule[3]=C:\WINDOWS\System32\KERNELBASE.dll
LoadedModule[4]=C:\WINDOWS\system32\apphelp.dll
LoadedModule[5]=C:\WINDOWS\AppPatch\AcLayers.DLL
LoadedModule[6]=C:\WINDOWS\System32\msvcrt.dll
LoadedModule[7]=C:\WINDOWS\System32\USER32.dll
LoadedModule[8]=C:\WINDOWS\System32\win32u.dll
LoadedModule[9]=C:\WINDOWS\System32\GDI32.dll
LoadedModule[10]=C:\WINDOWS\System32\gdi32full.dll
LoadedModule[11]=C:\WINDOWS\System32\SHELL32.dll
LoadedModule[12]=C:\WINDOWS\System32\cfgmgr32.dll
LoadedModule[13]=C:\WINDOWS\System32\windows.storage.dll
LoadedModule[14]=C:\WINDOWS\System32\combase.dll
LoadedModule[15]=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule[16]=C:\WINDOWS\System32\RPCRT4.dll
LoadedModule[17]=C:\WINDOWS\System32\SspiCli.dll
LoadedModule[18]=C:\WINDOWS\System32\CRYPTBASE.dll
LoadedModule[19]=C:\WINDOWS\System32\bcryptPrimitives.dll
LoadedModule[20]=C:\WINDOWS\System32\sechost.dll
LoadedModule[21]=C:\WINDOWS\System32\powrprof.dll
LoadedModule[22]=C:\WINDOWS\System32\advapi32.dll
LoadedModule[23]=C:\WINDOWS\System32\shlwapi.dll
LoadedModule[24]=C:\WINDOWS\System32\kernel.appcore.dll
LoadedModule[25]=C:\WINDOWS\System32\shcore.dll
LoadedModule[26]=C:\WINDOWS\System32\profapi.dll
LoadedModule[27]=C:\WINDOWS\System32\OLEAUT32.dll
LoadedModule[28]=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule[29]=C:\WINDOWS\System32\SETUPAPI.dll
LoadedModule[30]=C:\WINDOWS\SYSTEM32\MPR.dll
LoadedModule[31]=C:\WINDOWS\SYSTEM32\sfc.dll
LoadedModule[32]=C:\WINDOWS\SYSTEM32\WINSPOOL.DRV
LoadedModule[33]=C:\WINDOWS\SYSTEM32\bcrypt.dll
LoadedModule[34]=C:\WINDOWS\SYSTEM32\sfc_os.DLL
LoadedModule[35]=C:\WINDOWS\AppPatch\AcSpecfc.DLL
LoadedModule[36]=C:\WINDOWS\System32\ole32.dll
LoadedModule[37]=C:\WINDOWS\System32\COMDLG32.dll
LoadedModule[38]=C:\WINDOWS\System32\IMM32.dll
LoadedModule[39]=C:\WINDOWS\System32\WS2_32.dll
LoadedModule[40]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.14393.0_none_88fef4c26039fb25\COMCTL32.dll
LoadedModule[41]=C:\WINDOWS\SYSTEM32\mscms.dll
LoadedModule[42]=C:\WINDOWS\SYSTEM32\WINMM.dll
LoadedModule[43]=C:\WINDOWS\SYSTEM32\DDRAW.dll
LoadedModule[44]=C:\WINDOWS\SYSTEM32\USERENV.dll
LoadedModule[45]=C:\WINDOWS\SYSTEM32\dwmapi.dll
LoadedModule[46]=C:\WINDOWS\SYSTEM32\msi.dll
LoadedModule[47]=C:\WINDOWS\SYSTEM32\WINMMBASE.dll
LoadedModule[48]=C:\WINDOWS\SYSTEM32\DCIMAN32.dll
LoadedModule[49]=C:\WINDOWS\system32\uxtheme.dll
LoadedModule[50]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9268_none_d08e1538442a243e\MSVCR80.dll
LoadedModule[51]=H:\Steam\steamapps\common\FSX\steam_api.dll
LoadedModule[52]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9268_none_d08e1538442a243e\MSVCP80.dll
LoadedModule[53]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL
LoadedModule[54]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL
LoadedModule[55]=H:\Steam\steamapps\common\FSX\language.dll
LoadedModule[56]=C:\Program Files (x86)\Steam\steamclient.dll
LoadedModule[57]=C:\WINDOWS\System32\CRYPT32.dll
LoadedModule[58]=C:\WINDOWS\System32\MSASN1.dll
LoadedModule[59]=C:\WINDOWS\System32\imagehlp.dll
LoadedModule[60]=C:\WINDOWS\System32\PSAPI.DLL
LoadedModule[61]=C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL
LoadedModule[62]=C:\Program Files (x86)\Steam\vstdlib_s.dll
LoadedModule[63]=C:\Program Files (x86)\Steam\tier0_s.dll
LoadedModule[64]=C:\WINDOWS\SYSTEM32\VERSION.dll
LoadedModule[65]=C:\WINDOWS\SYSTEM32\Secur32.dll
LoadedModule[66]=C:\Program Files (x86)\Steam\steam.dll
LoadedModule[67]=C:\Program Files (x86)\Steam\Steam2.dll
LoadedModule[68]=C:\WINDOWS\SYSTEM32\DbgHelp.dll
LoadedModule[69]=C:\WINDOWS\SYSTEM32\dbgcore.DLL
LoadedModule[70]=C:\Program Files (x86)\Steam\CSERHelper.dll
LoadedModule[71]=C:\Program Files (x86)\Steam\gameoverlayrenderer.dll
LoadedModule[72]=H:\Steam\steamapps\common\FSX\API.DLL
LoadedModule[73]=H:\Steam\steamapps\common\FSX\ablscpt.dll
LoadedModule[74]=H:\Steam\steamapps\common\FSX\acontain.dll
LoadedModule[75]=H:\Steam\steamapps\common\FSX\ai_player.dll
LoadedModule[76]=H:\Steam\steamapps\common\FSX\atc.dll
LoadedModule[77]=H:\Steam\steamapps\common\FSX\controls.dll
LoadedModule[78]=H:\Steam\steamapps\common\FSX\demo.dll
LoadedModule[79]=H:\Steam\steamapps\common\FSX\facilities.dll
LoadedModule[80]=H:\Steam\steamapps\common\FSX\fe.dll
LoadedModule[81]=H:\Steam\steamapps\common\FSX\flight.dll
LoadedModule[82]=H:\Steam\steamapps\common\FSX\fsui.dll
LoadedModule[83]=H:\Steam\steamapps\common\FSX\g2d.dll
LoadedModule[84]=H:\Steam\steamapps\common\FSX\g3d.dll
LoadedModule[85]=H:\Steam\steamapps\common\FSX\gps.dll
LoadedModule[86]=H:\Steam\steamapps\common\FSX\livingwater.dll
LoadedModule[87]=H:\Steam\steamapps\common\FSX\main.dll
LoadedModule[88]=H:\Steam\steamapps\common\FSX\multiplayer.dll
LoadedModule[89]=H:\Steam\steamapps\common\FSX\panels.dll
LoadedModule[90]=H:\Steam\steamapps\common\FSX\sim1.dll
LoadedModule[91]=H:\Steam\steamapps\common\FSX\simprop.dll
LoadedModule[92]=H:\Steam\steamapps\common\FSX\simscheduler.dll
LoadedModule[93]=H:\Steam\steamapps\common\FSX\sound.dll
LoadedModule[94]=H:\Steam\steamapps\common\FSX\symmap.dll
LoadedModule[95]=H:\Steam\steamapps\common\FSX\terrain.dll
LoadedModule[96]=H:\Steam\steamapps\common\FSX\fs-traffic.dll
LoadedModule[97]=H:\Steam\steamapps\common\FSX\ui.dll
LoadedModule[98]=H:\Steam\steamapps\common\FSX\util.dll
LoadedModule[99]=H:\Steam\steamapps\common\FSX\visualfx.dll
LoadedModule[100]=H:\Steam\steamapps\common\FSX\weather.dll
LoadedModule[101]=H:\Steam\steamapps\common\FSX\window.dll
LoadedModule[102]=H:\Steam\steamapps\common\FSX\xuipc.dll
LoadedModule[103]=C:\WINDOWS\SYSTEM32\MSWSOCK.dll
LoadedModule[104]=C:\WINDOWS\SYSTEM32\SHFOLDER.dll
LoadedModule[105]=C:\WINDOWS\SYSTEM32\DINPUT8.dll
LoadedModule[106]=C:\WINDOWS\SYSTEM32\d3dx9_34.dll
LoadedModule[107]=C:\WINDOWS\SYSTEM32\d3dx10_34.dll
LoadedModule[108]=C:\WINDOWS\SYSTEM32\d3d9.dll
LoadedModule[109]=C:\WINDOWS\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.14393.321_none_baab3cb4359688b4\gdiplus.dll
LoadedModule[110]=C:\WINDOWS\SYSTEM32\WININET.dll
LoadedModule[111]=C:\WINDOWS\SYSTEM32\DSOUND.dll
LoadedModule[112]=C:\WINDOWS\SYSTEM32\MSACM32.dll
LoadedModule[113]=C:\WINDOWS\SYSTEM32\MSIMG32.dll
LoadedModule[114]=H:\Steam\steamapps\common\FSX\sdkencryptedappticket.dll
LoadedModule[115]=C:\WINDOWS\System32\MSCTF.dll
LoadedModule[116]=C:\WINDOWS\SYSTEM32\CRYPTSP.dll
LoadedModule[117]=C:\WINDOWS\system32\rsaenh.dll
LoadedModule[118]=C:\WINDOWS\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9818.0_none_b7e811947b297f6d\MSXML4.DLL
LoadedModule[119]=C:\WINDOWS\System32\clbcatq.dll
LoadedModule[120]=C:\Windows\System32\urlmon.dll
LoadedModule[121]=C:\Windows\System32\iertutil.dll
LoadedModule[122]=C:\WINDOWS\SYSTEM32\dxgi.dll
LoadedModule[123]=C:\WINDOWS\SYSTEM32\d3d11.dll
LoadedModule[124]=C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_674733509ab83d72\nvd3dum.dll
LoadedModule[125]=C:\WINDOWS\system32\nvspcap.dll
LoadedModule[126]=C:\WINDOWS\SYSTEM32\WINHTTP.dll
LoadedModule[127]=C:\WINDOWS\system32\nvapi.dll
LoadedModule[128]=C:\WINDOWS\SYSTEM32\D3DCompiler_34.dll
LoadedModule[129]=C:\WINDOWS\SYSTEM32\WindowsCodecs.dll
LoadedModule[130]=C:\WINDOWS\SYSTEM32\d3d10_1.dll
LoadedModule[131]=C:\WINDOWS\SYSTEM32\d3d10_1core.dll
LoadedModule[132]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll
LoadedModule[133]=C:\Windows\System32\dxdiagn.dll
LoadedModule[134]=C:\Windows\System32\d3d12.dll
LoadedModule[135]=C:\Windows\System32\msvcp110_win.dll
LoadedModule[136]=C:\WINDOWS\system32\wbem\wbemprox.dll
LoadedModule[137]=C:\WINDOWS\SYSTEM32\wbemcomn.dll
LoadedModule[138]=C:\WINDOWS\system32\wbem\wbemsvc.dll
LoadedModule[139]=C:\WINDOWS\system32\wbem\fastprox.dll
LoadedModule[140]=C:\WINDOWS\system32\winbrand.dll
LoadedModule[141]=C:\WINDOWS\SYSTEM32\DEVOBJ.dll
LoadedModule[142]=C:\WINDOWS\System32\WINTRUST.dll
LoadedModule[143]=C:\WINDOWS\System32\NSI.dll
LoadedModule[144]=C:\WINDOWS\SYSTEM32\WTSAPI32.DLL
LoadedModule[145]=C:\WINDOWS\SYSTEM32\WINSTA.dll
LoadedModule[146]=C:\Windows\System32\gameux.dll
LoadedModule[147]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.14393.0_none_74bc87d3d22d9abe\COMCTL32.dll
LoadedModule[148]=H:\Steam\steamapps\common\FSX\uiautomationcore.dll
LoadedModule[149]=C:\WINDOWS\SYSTEM32\OLEACC.dll
LoadedModule[150]=C:\WINDOWS\System32\MMDevApi.dll
LoadedModule[151]=C:\WINDOWS\System32\PROPSYS.dll
LoadedModule[152]=C:\WINDOWS\SYSTEM32\AUDIOSES.DLL
LoadedModule[153]=C:\WINDOWS\SYSTEM32\wintypes.dll
LoadedModule[154]=C:\WINDOWS\SYSTEM32\RICHED20.DLL
LoadedModule[155]=C:\WINDOWS\System32\USP10.dll
LoadedModule[156]=C:\WINDOWS\SYSTEM32\msls31.dll
LoadedModule[157]=C:\WINDOWS\SYSTEM32\HID.DLL
LoadedModule[158]=C:\WINDOWS\SYSTEM32\XInput9_1_0.dll
LoadedModule[159]=C:\WINDOWS\SYSTEM32\wdmaud.drv
LoadedModule[160]=C:\WINDOWS\SYSTEM32\ksuser.dll
LoadedModule[161]=C:\WINDOWS\SYSTEM32\AVRT.dll
LoadedModule[162]=C:\WINDOWS\SYSTEM32\msacm32.drv
LoadedModule[163]=C:\WINDOWS\SYSTEM32\midimap.dll
LoadedModule[164]=C:\WINDOWS\SYSTEM32\dinput.DLL
LoadedModule[165]=C:\WINDOWS\SYSTEM32\XInput1_4.dll
LoadedModule[166]=H:\Steam\steamapps\common\FSX\PMDG\DLLs\PMDG_HUD_interface.dll
LoadedModule[167]=C:\WINDOWS\SYSTEM32\MSVCR100.dll
LoadedModule[168]=C:\WINDOWS\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[169]=H:\Steam\steamapps\common\FSX\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow.dll
LoadedModule[170]=C:\WINDOWS\SYSTEM32\ondemandconnroutehelper.dll
LoadedModule[171]=C:\WINDOWS\SYSTEM32\WINNSI.DLL
LoadedModule[172]=C:\WINDOWS\SYSTEM32\DNSAPI.dll
LoadedModule[173]=C:\Program Files (x86)\Bonjour\mdnsNSP.dll
LoadedModule[174]=C:\Windows\System32\rasadhlp.dll
LoadedModule[175]=C:\WINDOWS\System32\fwpuclnt.dll
LoadedModule[176]=C:\Windows\System32\ieframe.dll
LoadedModule[177]=C:\Windows\System32\NETAPI32.dll
LoadedModule[178]=C:\Windows\System32\NETUTILS.DLL
LoadedModule[179]=C:\Windows\System32\WKSCLI.DLL
LoadedModule[180]=C:\WINDOWS\system32\dataexchange.dll
LoadedModule[181]=C:\WINDOWS\system32\dcomp.dll
LoadedModule[182]=C:\WINDOWS\system32\twinapi.appcore.dll
LoadedModule[183]=C:\Windows\System32\mshtml.dll
LoadedModule[184]=C:\Windows\System32\srpapi.dll
LoadedModule[185]=C:\Windows\System32\ieapfltr.dll
LoadedModule[186]=C:\WINDOWS\system32\msimtf.dll
LoadedModule[187]=C:\Windows\System32\d2d1.dll
LoadedModule[188]=C:\Windows\System32\DWrite.dll
LoadedModule[189]=C:\WINDOWS\SYSTEM32\d3d10warp.dll
LoadedModule[190]=C:\WINDOWS\SYSTEM32\MLANG.dll
LoadedModule[191]=C:\Windows\System32\jscript9.dll
LoadedModule[192]=C:\Windows\System32\uiautomationcore.dll
LoadedModule[193]=C:\WINDOWS\System32\schannel.dll
LoadedModule[194]=C:\WINDOWS\SYSTEM32\mskeyprotect.dll
LoadedModule[195]=C:\WINDOWS\SYSTEM32\ncrypt.dll
LoadedModule[196]=C:\WINDOWS\SYSTEM32\NTASN1.dll
LoadedModule[197]=C:\WINDOWS\System32\DPAPI.DLL
LoadedModule[198]=C:\Windows\System32\cryptnet.dll
LoadedModule[199]=C:\WINDOWS\system32\ncryptsslp.dll
LoadedModule[200]=C:\WINDOWS\SYSTEM32\sxs.dll
LoadedModule[201]=C:\WINDOWS\System32\UIAnimation.dll
LoadedModule[202]=C:\Windows\System32\XmlLite.dll
LoadedModule[203]=H:\Steam\steamapps\common\FSX\gauges\PMDG_737NGX.dll
LoadedModule[204]=C:\WINDOWS\SYSTEM32\WSOCK32.dll
LoadedModule[205]=C:\WINDOWS\SYSTEM32\MSVCP100.dll
LoadedModule[206]=C:\WINDOWS\System32\XAudio2_7.dll
LoadedModule[207]=H:\Steam\steamapps\common\FSX\Gauges\PMDG_737NGX_2.dll
LoadedModule[208]=C:\WINDOWS\SYSTEM32\snmpapi.dll
LoadedModule[209]=C:\WINDOWS\system32\napinsp.dll
LoadedModule[210]=C:\WINDOWS\system32\pnrpnsp.dll
LoadedModule[211]=C:\WINDOWS\system32\NLAapi.dll
LoadedModule[212]=C:\WINDOWS\System32\winrnr.dll
LoadedModule[213]=C:\WINDOWS\SYSTEM32\ntmarta.dll
LoadedModule[214]=C:\WINDOWS\SYSTEM32\icmp.Dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Microsoft Flight Simulator®
AppPath=H:\Steam\steamapps\common\FSX\fsx.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=381DF571ED60C2BD257C942B863BDC44
MetadataHash=-278149125

 

 

 

And here is the Event report:
 

Log Name:      Application
Source:        Application Error
Date:          10/21/2016 10:40:13 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Anthony-PC
Description:
Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: ntdll.dll, version: 10.0.14393.206, time stamp: 0x57dacde1
Exception code: 0xc0000005
Fault offset: 0x00026d39
Faulting process id: 0x97c
Faulting application start time: 0x01d22c0d36ee6533
Faulting application path: H:\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 23a93e5d-3f34-4371-a093-3390e9ded745
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-10-22T02:40:13.846291200Z" />
    <EventRecordID>3037</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Anthony-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>fsx.exe</Data>
    <Data>10.0.62615.0</Data>
    <Data>559f9a9a</Data>
    <Data>ntdll.dll</Data>
    <Data>10.0.14393.206</Data>
    <Data>57dacde1</Data>
    <Data>c0000005</Data>
    <Data>00026d39</Data>
    <Data>97c</Data>
    <Data>01d22c0d36ee6533</Data>
    <Data>H:\Steam\steamapps\common\FSX\fsx.exe</Data>
    <Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
    <Data>23a93e5d-3f34-4371-a093-3390e9ded745</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

 

I wanted to note that this is now a sporadic issue since having removed simobject display engine.  The first time I was able to load tonight everything was fine but I needed to restart because the buttons on the plane were not working (clickable) and after restart I did the same process and when exiting the window (utilizing ALT+Enter) and it crashed immediately after I clicked outside the window.  I'm going to attempt to figure this out tonight.

[Jim Young 2,356]

 

 

I wanted to note that this is now a sporadic issue since having removed simobject display engine. The first time I was able to load tonight everything was fine but I needed to restart because the buttons on the plane were not working (clickable) and after restart I did the same process and when exiting the window (utilizing ALT+Enter) and it crashed immediately after I clicked outside the window. I'm going to attempt to figure this out tonight.

 

There are many possibilities when the ntdll.dll is the faulting module (see page 33, AVSIM CTD Guide).  The solution regarding MyTrafficX or MyTraffic6 appears to be the most common fix.

 

Best regards,

Jim

[tonyprent22 0]

Thanks again for all your help.  Last night I completed a clean uninstall and reinstall for all add ons and FSX itself after reading the issues people experience regarding GSX add ons, where I felt the issue came from.  I haven't given it a go yet but I'm about to.  If I find another issue my next step will be the MyTrafficX solution.  Again thanks for all your help!

[tonyprent22 0]

I believe I spoke too soon.

Everything was working fine after the reinstall and then tonight out of no where I began crashing again when doing the same thing as before, trying to exit to start up PRO-ATCX.  The moment I click outside the FSX window, it crashes.  I went through the CTD guide and tried every NTDLL.dll fix you listed, with the exception of:

 

A.) removing UIAutomationcore.dll - You have "if installed" in bold.  This file is inside of my FSX folder, but I don't know if it's installed or not, and am not sure how to check if it's installed so I don't want to go deleting the file if unnecessary.

 

B.) the MyTraffic fix.  I have not been able to locate these files in my scenery folder.  Perhaps the Scenery folder is different from the Scenery Library folder, but a search of my computer does not list either the "MyTraffixX" file or the "MyTraffic6a" file, so I don't believe i even have these files on my machine.

 

C.) checking my dll.xml for duplicate entries.  I have no idea where this file resides, and trying to search online has been futile.  Perhaps someone here can point me in the direction, but I can't seem to find it.

I've cleaned the registry using CC Cleaner, I've scanned the System File Checker, I've updated my video card drivers, I've done everything I can possibly think of to do.  I'm at a loss for where to turn next, and I worry that this issue is not a normal one, as it involves a crash when I'm leaving FSX window.  The program runs fine if I stay inside of FSX, but then I'd be wasting ProATC.  I'm just at a complete loss at this point.  I got it to work fine immediately after I cleaned the registry folder using CC Cleaner the first time, but this was temporary, as I exited, started up ProATC just fine, went back in, and then during startup I was struck by a stupid ground vehicle randomly, and it stated I crashed, then the program CTD'd without resetting the flight.

[Jim Young 2,356]

 

 

removing UIAutomationcore.dll - You have "if installed" in bold. This file is inside of my FSX folder, but I don't know if it's installed or not, and am not sure how to check if it's installed so I don't want to go deleting the file if unnecessary.

 

Hi again Anthony!

 

Anything in your main fsx folder loads at startup.  So, if you have the uiautomationcore.dll located in the folder, it will load (it is installed as a default file by Dovetail for FSX-SE so you should not remove it as suggested by the guide.  I understand they modified it slightly).  No other installation is necessary.  When I say installed, I mean placing the uiautomationcore.dll into the main FSX directory (it is not installed in FSX by default.  You have to locate the proper version and place it in your main FSX folder if you own FSX boxed).  Many have fixed crashes by moving the uiautomationcore.dll to a temporary folder and then restarting FSX.  The uiautomationcore.dll is purported to be the "holy grail" of all FSX crashes and I have proven beyond any reasonable doubts that that is rubbish.  I personally have never 'knowingly' had the dll in my FSX folder.  Without it in my folder, I have tried to make FSX crash clicking on the FSX menu, right clicking on the panel many times and still no joy (you have to right click on the panel at least 19 times to make it crash according to the "holy grail" experts).  It does more harm than good.  I am oblivious as to why Dovetail would have included it in their installation but they did. 

 

 

 

checking my dll.xml for duplicate entries. I have no idea where this file resides, and trying to search online has been futile. Perhaps someone here can point me in the direction, but I can't seem to find it.

 

On page 13 of the AVSIM CTD Guide, it tells you where it is located and has pictures of how to troubleshoot. 

 

I really have not heard about a crash whenever clicking outside the main FSX window when using Alt+Enter.  I would suggest your video card drivers are the issue if this is happening but you state you have updated your video card drivers.  You do know there was a bug in one recent release (375.57) that caused crashes and NVidia released an updated version (375.63)?

 

On page 10 of the AVSIM CTD Guide, it tells you how to fix most crashes and freezes.

 

 

 

I've cleaned the registry using CC Cleaner, I've scanned the System File Checker, I've updated my video card drivers, I've done everything I can possibly think of to do. I'm at a loss for where to turn next, and I worry that this issue is not a normal one, as it involves a crash when I'm leaving FSX window. The program runs fine if I stay inside of FSX, but then I'd be wasting ProATC. I'm just at a complete loss at this point. I got it to work fine immediately after I cleaned the registry folder using CC Cleaner the first time, but this was temporary, as I exited, started up ProATC just fine, went back in, and then during startup I was struck by a stupid ground vehicle randomly, and it stated I crashed, then the program CTD'd without resetting the flight.

 

 

 

Perhaps the Scenery folder is different from the Scenery Library folder,

 

The Scenery.cfg is the same as the Scenery Library.  There is no folder.  The scenery.cfg shows all scenery that is installed and where it is located on your computer.  If you do not see MyTrafficX in your scenery.cfg or Scenery Library, you do not have it installed.  It is a payware program so you would have had to buy it and then install it.  I mentioned the "fix" for MyTrafficX in case someone had MyTrafficX installed (it is a very, very popular payware program). 

 

Your comments indicate you have tried everything possible to fix your crash(es) and you have not.  The guide only provides suggestions to possibly fix a crash.  There is no magic bullet that fixes all crashes.  The guide provides some suggestions as I have gleaned from looking around the Internet at all of the flight simulation websites (including AVSIM) for fixes to FSX crashes.  A suggestion such as cleaning the registry fixed some crashes but it did not for others.  Looking for corrupt system files and having any fixed was a solution for many others but not for everyone.  99% of all crashes are fixed by deleting or moving your fsx.cfg to a temporary folder and letting FSX rebuild it when you restart FSX because people like to tweak and they put these awful tweaks in their FSX.cfg that do not work for them.  For instance, they think the parameters for the Affinity Mask tweak are the same for everyone so they put it in their FSX.cfg.  That will cause a crash 100% of the time.  Tweaks are bad....

 

The NTDLL.dll crash is one of the most common crashes in FSX/P3D.  It indicates there is a major conflict between your setup of your application and your computer system.  It relates to memory.  If you have your system overclocked, even by professionals, just having too high or too low CPU voltage can trigger this crash.  Even after running programs like Prime95 or the Intel Burn Test and passing these tests with flying colors FSX will crash because of a bad overclock (too high, too low voltages).  I know because it has happened to me.  If I bring my overclock back to the optimal settings, the crashes go away.  FSX uses resources like no other application every developed.  It is poorly programmed to take advantage of the latest computer technologies.  

 

Best regards,

Jim

[CB_Pilot 54]

Hi Anthony

An interesting thread and great help - as always - from Jim. I've experienced your crash on change of focus and it's usually after I update my NVidia card drivers. For me, it's a conflict in the resolutions set in the FSX.cfg file. There are multiple display entries but with different settings. I always comment these out of the file (prefix with "//") and rerun FSX to let the cfg file rebuild. It always resolves the conflict.

I'm not too technical so I can't guarantee it's the right answer but it's worth checking out.

Good luck.

Rupert

[ArjenVdv 190]

Here's a suggestion for you. Lately, I have been having these crashes happen also when ALT+ENTERing. It was the first time flying on Windows 10, and could not recall having anything like this on Windows 7. It happened everytime when going to windowed mode and then clicking anything in the background. Jim says this is a common error. I think this shouldn't be happening at all as long as your system is stable, sufficient, and balanced. Also, ALT+TAB should be a problem, I have been doing this for years without trouble.

 

My system is stable, sufficient, and balanced, as far as I know, but I was still experiencing the errors. The crash report would sometimes indicate ntdll.dll and other times d3d9.dll as the faultmodule. The first step to do in this case is to think of any changes I had made lately, which was setting "Aircraft casts shadows on the ground" to on and updating my NVIDIA drivers. I switched it off and the crashes went away. Switched it on, and the crashes returned. It is 100% reproduceable. It might be a bug in the newest NVIDIA drivers, because I think it is unlikely this is due to system instability, and cannot recall FSX doing this. I have seen more people reporting this lately. 

 

If it does not work, verify your system specs. Do you either have a bad CPU or a bad video card, then your system is unbalanced, and ntdll.dll errors are bound to happen. I had mine happening too around 5 years ago, and fixed it by buying a proper video card. Also, check for updates, update your NVIDIA drivers, rebuild fsx.CFG.

[Jim Young 2,356]

 

 

Lately, I have been having these crashes happen also when ALT+ENTERing. It was the first time flying on Windows 10, and could not recall having anything like this on Windows 7. It happened everytime when going to windowed mode and then clicking anything in the background. Jim says this is a common error.

 

When you Alt+Enter, FSX will go from Windowed Mode to Full Screen Mode and then back to Windowed Mode.  If in Full Screen Mode you cannot click on anything in the background.  In Windowed Mode you can click on anything in the background and that will not cause a crash and this is not a common error as you suggest I stated.  It is a common error if you Alt+Tab between Windows from Full Screen mode.  There is a bug in FSX that will cause FSX to freeze or crash most of the time when you do this.  Sometimes, on rare occasions, you can get back into FSX but that is certainly rare (I have done it a few times but mostly I just shut FSX down and restart it). 

 

 

 

Also, ALT+TAB should be a problem, I have been doing this for years without trouble.

 

Here you state Alt+Tab should be a problem but you have been doing this for years without trouble.  Perhaps a language problem?  You have contradicting statements in one sentence.

 

 

 

The crash report would sometimes indicate ntdll.dll and other times d3d9.dll as the faultmodule.

 

The AVSIM CTD Guide provides clear suggestions for fixing these errors.  The errors are very common.  The Guide has suggestions I found that fixed the problem from members here at AVSIM as well as from other flight simulation websites around the Internet.  The latest suggestion for the ntdll.dll error was to rename the military traffic bgl in MyTrafficX or MyTraffic6.  The d3d9.dll does not belong to FSX by default.  It is a system file.  Some hackers have suggested putting their version of the d3d9.dll in their FSX folder.  The guide suggests that you remove it if you get crashes.

 

 

 

The first step to do in this case is to think of any changes I had made lately, which was setting "Aircraft casts shadows on the ground" to on and updating my NVIDIA drivers. I switched it off and the crashes went away. Switched it on, and the crashes returned. It is 100% reproduceable. It might be a bug in the newest NVIDIA drivers, because I think it is unlikely this is due to system instability, and cannot recall FSX doing this. I have seen more people reporting this lately.

 

I appreciate the fact you investigate your crashes by thinking back to what you did before the crashes started occurring.  I have the latest Nvidia drivers and turned on "Aircraft casts shadows on the ground" and I had no crash so it is not 100% reproducible.  Turning on this option does take up a lot of resources within FSX (and reason why I usually keep this option disabled), and that might have triggered the ntdll.dll error as the ntdll.dll error is related to memory resources.  So, if you had high FSX and display driver settings and you loaded resource intensive payware aircraft, weather and scenery, this certainly could have triggered the crash and probably why you were able to reproduce it 100% of the time.  When I see statements that there could have been a bug in the newest Nvidia drivers, I cringe and goosebumps go up and down my spine because, if the problem was a bug in the latest drivers, then everyone would be seeing these crashes until they went back to older drivers or updated to a driver that fixed the "bug".  I do not understand why everyone does not blame their FSX setup. 

 

I do like your recommendation to rebuild the fsx.cfg as that has fixed almost all FSX crashes.  Programs like FSDT sometimes trick you into employing their tweaks to make THEIR scenery potentially work better.  Each one of the tweaks they suggest could cause a crash on your system and not on others.  Tweaks are bad, especially the ones recommended by FSDT.  So, when you rebuild the fsx.cfg, it has no tweaks and the settings are set to the default and, you have no crashes.  A week or two later, you open up the FSDT addon manager and you see the suggestions for automatically tweaking your FSX.cfg.  FSX works okay for a few days then suddenly, without explanation, it starts crashing.  It is most likely the addition of the tweaks. 

 

Best regards,

Jim

[ArjenVdv 190]

Jim, excuse me. I had understood that you consider "clicking anything after going to windowed mode" as a "known error", from one of your previous posts.

 

 

 

ALT+TAB should be a problem, I have been doing this for years without trouble.

 

This is indeed a language error, I meant ALT+TAB should not be a problem. And yes, I have been doing this for years. I have just done it again, and tried ALT+TABbing tens of times, and everytime I could return to FSX.

 

 

 

 

So, if you had high FSX and display driver settings and you loaded resource intensive payware aircraft, weather and scenery, this certainly could have triggered the crash and probably why you were able to reproduce it 100% of the time. 

 

Actually, in my case the CTDs when clicking anything outside of FSX, were completely reproducible regardless of the circumstances. In fact, I could even trigger the crash using the trike above Friday Harbor. For the rest, my settings are nothing over the top.

 

You say everyone should be experiencing this crash if it was related to NVIDIA drivers. This is not true, because every system and it's configuration is unique. Certain configurations and certain FSX settings could cause unique conflicts and errors. I don't see why us FSX users should always have to blame our settings, and stop using certain options in the simulator, to avoid a conflict with our system, operating system and its drivers. On the other hand, I know Microsoft and NVIDIA don't bother adapting to us either.

Secondly, even though I am not saying everybody is experiencing the error, I have seen more of such threads lately on FSX (SE) related forums, including on the Steam forums. It could very well be any Windows or NVIDIA update that triggers the crash, in combination with a particular setting.

 

I know I have a very stable and capable system. I haven't used FSX for a while so my settings and my installation are unchanged. Everything still worked as it should, and yet I can reproduce this crash everytime, at least in my situation. A crash that I had never had before. It is then very logical to suspect an update that causes a conflict.

 

I must also admit I partially disagree with your conservativeness with regard to tweaks. Even though I agree we should not let any third party add-on tweak our fsx.CFG, I do believe that certain tweaks are essential to our FSX experience, and make the sim more usable, and often more stable as well. There is absolutely nothing wrong with HIGHMEMFIX=1, AFFINITYMASK=[correct value], WideViewAspect=True. BufferPools=0 is debatable. As long as you have a capable videocard, and don't do a lot of panning in external views, this is a tweak that unleashes the framerates and should cause no further instability from my experience. I do think manually increasing your LOD for example, is something we should avoid.