Recommended Posts

Hi everyone,

This community is pretty much my last resort.

I have been getting CTD's since last night after installing Steve's freeware DX10 fix. 
After enchanging a couple of emails, Steve assured me that the CTD's have nothing to do with installing the fix and that the timing of the first CTD was purely coincidental. He sent me the link to the (very impressive) CTD guide.

I tried all the relevant options from the "How to fix most CTD's" section. Because neither of them had any succes.

AppCrashView tells me that the failing module is ntdll.dll. So I moved to on the more hardcore solutions like replacing the UIAutomationCore.dll.
As you can guess, this didn't work either. 

Am I missing something? Am I doing something wrong?
All the help I can get is grately appreciated.

 

Here's the full log if that is any help:

Version=1
EventType=APPCRASH
EventTime=131436698910559823
ReportType=2
Consent=1
UploadTime=131436698911498600
ReportIdentifier=72a60008-60ee-11e7-bde7-a0a8cd1ed2b3
IntegratorReportIdentifier=0399b1ad-fbc8-439a-a1c3-8bbe76d0298b
WOW64=1
NsAppName=fsx.exe
AppSessionGuid=0000286c-0002-000c-fa13-a734fbf4d201
TargetAppId=W:000637a153a159d5c2b9b8242acf4aaf242300000904!0000eb723381c97f481af15094e7ac42101d371bd1ba!fsx.exe
TargetAppVer=2015//07//10:10:12:42!2ac31c!fsx.exe
BootId=4294967295
Response.type=4
Sig[0].Name=Naam van de toepassing
Sig[0].Value=fsx.exe
Sig[1].Name=Versie van toepassing
Sig[1].Value=10.0.62615.0
Sig[2].Name=Tijdstempel van toepassing
Sig[2].Value=559f9a9a
Sig[3].Name=Naam van foutmodule
Sig[3].Value=ntdll.dll
Sig[4].Name=Versie van foutmodule
Sig[4].Value=10.0.14393.479
Sig[5].Name=Tijdstempel van foutmodule
Sig[5].Value=58256ca0
Sig[6].Name=Uitzonderingscode
Sig[6].Value=c0000005
Sig[7].Name=Uitzonderingsmarge
Sig[7].Value=00045d28
DynamicSig[1].Name=Versie van besturingssysteem
DynamicSig[1].Value=10.0.14393.2.0.0.768.101
DynamicSig[2].Name=Landinstelling-id
DynamicSig[2].Value=1043
DynamicSig[22].Name=Aanvullende informatie 1
DynamicSig[22].Value=b115
DynamicSig[23].Name=Aanvullende informatie 2
DynamicSig[23].Value=b1156ea10f1269a85162403523d15a0f
DynamicSig[24].Name=Aanvullende informatie 3
DynamicSig[24].Value=bfed
DynamicSig[25].Name=Aanvullende informatie 4
DynamicSig[25].Value=bfed9631da94f986cd8724a167dd43b5
UI[2]=C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe
UI[3]=Microsoft Flight Simulator® werkt niet meer
UI[4]=U kunt online naar een oplossing voor het probleem zoeken.
UI[5]=Online naar een oplossing zoeken en dit programma sluiten
UI[6]=Later online naar een oplossing zoeken en dit programma sluiten
UI[7]=Het programma sluiten
LoadedModule[0]=C:\Program Files (x86)\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.447_none_5507ded2cb4f7f4c\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\SortWindows61.dll
LoadedModule[50]=C:\WINDOWS\system32\uxtheme.dll
LoadedModule[51]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL
LoadedModule[52]=C:\Program Files (x86)\Steam\steamapps\common\FSX\steam_api.dll
LoadedModule[53]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9268_none_d08e1538442a243e\MSVCR80.dll
LoadedModule[54]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9268_none_d08e1538442a243e\MSVCP80.dll
LoadedModule[55]=C:\Program Files (x86)\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\tier0_s.dll
LoadedModule[63]=C:\WINDOWS\SYSTEM32\VERSION.dll
LoadedModule[64]=C:\Program Files (x86)\Steam\vstdlib_s.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:\Program Files (x86)\Steam\DbgHelp.dll
LoadedModule[69]=C:\Program Files (x86)\Steam\CSERHelper.dll
LoadedModule[70]=C:\Program Files (x86)\Steam\gameoverlayrenderer.dll
LoadedModule[71]=C:\Program Files (x86)\Steam\steamapps\common\FSX\API.DLL
LoadedModule[72]=C:\Program Files (x86)\Steam\steamapps\common\FSX\ablscpt.dll
LoadedModule[73]=C:\Program Files (x86)\Steam\steamapps\common\FSX\acontain.dll
LoadedModule[74]=C:\Program Files (x86)\Steam\steamapps\common\FSX\ai_player.dll
LoadedModule[75]=C:\Program Files (x86)\Steam\steamapps\common\FSX\atc.dll
LoadedModule[76]=C:\Program Files (x86)\Steam\steamapps\common\FSX\controls.dll
LoadedModule[77]=C:\Program Files (x86)\Steam\steamapps\common\FSX\demo.dll
LoadedModule[78]=C:\Program Files (x86)\Steam\steamapps\common\FSX\facilities.dll
LoadedModule[79]=C:\Program Files (x86)\Steam\steamapps\common\FSX\fe.dll
LoadedModule[80]=C:\Program Files (x86)\Steam\steamapps\common\FSX\flight.dll
LoadedModule[81]=C:\Program Files (x86)\Steam\steamapps\common\FSX\fsui.dll
LoadedModule[82]=C:\Program Files (x86)\Steam\steamapps\common\FSX\g2d.dll
LoadedModule[83]=C:\Program Files (x86)\Steam\steamapps\common\FSX\g3d.dll
LoadedModule[84]=C:\Program Files (x86)\Steam\steamapps\common\FSX\gps.dll
LoadedModule[85]=C:\Program Files (x86)\Steam\steamapps\common\FSX\livingwater.dll
LoadedModule[86]=C:\Program Files (x86)\Steam\steamapps\common\FSX\main.dll
LoadedModule[87]=C:\Program Files (x86)\Steam\steamapps\common\FSX\multiplayer.dll
LoadedModule[88]=C:\Program Files (x86)\Steam\steamapps\common\FSX\panels.dll
LoadedModule[89]=C:\Program Files (x86)\Steam\steamapps\common\FSX\sim1.dll
LoadedModule[90]=C:\Program Files (x86)\Steam\steamapps\common\FSX\simprop.dll
LoadedModule[91]=C:\Program Files (x86)\Steam\steamapps\common\FSX\simscheduler.dll
LoadedModule[92]=C:\Program Files (x86)\Steam\steamapps\common\FSX\sound.dll
LoadedModule[93]=C:\Program Files (x86)\Steam\steamapps\common\FSX\symmap.dll
LoadedModule[94]=C:\Program Files (x86)\Steam\steamapps\common\FSX\terrain.dll
LoadedModule[95]=C:\Program Files (x86)\Steam\steamapps\common\FSX\fs-traffic.dll
LoadedModule[96]=C:\Program Files (x86)\Steam\steamapps\common\FSX\ui.dll
LoadedModule[97]=C:\Program Files (x86)\Steam\steamapps\common\FSX\util.dll
LoadedModule[98]=C:\Program Files (x86)\Steam\steamapps\common\FSX\visualfx.dll
LoadedModule[99]=C:\Program Files (x86)\Steam\steamapps\common\FSX\weather.dll
LoadedModule[100]=C:\Program Files (x86)\Steam\steamapps\common\FSX\window.dll
LoadedModule[101]=C:\Program Files (x86)\Steam\steamapps\common\FSX\xuipc.dll
LoadedModule[102]=C:\WINDOWS\SYSTEM32\MSWSOCK.dll
LoadedModule[103]=C:\WINDOWS\SYSTEM32\SHFOLDER.dll
LoadedModule[104]=C:\WINDOWS\SYSTEM32\DINPUT8.dll
LoadedModule[105]=C:\WINDOWS\SYSTEM32\d3dx9_34.dll
LoadedModule[106]=C:\WINDOWS\SYSTEM32\d3dx10_34.dll
LoadedModule[107]=C:\WINDOWS\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.14393.953_none_baad48403594ab3f\gdiplus.dll
LoadedModule[108]=C:\WINDOWS\SYSTEM32\d3d9.dll
LoadedModule[109]=C:\WINDOWS\SYSTEM32\WININET.dll
LoadedModule[110]=C:\Program Files (x86)\Steam\steamapps\common\FSX\sdkencryptedappticket.dll
LoadedModule[111]=C:\WINDOWS\SYSTEM32\DSOUND.dll
LoadedModule[112]=C:\WINDOWS\SYSTEM32\MSACM32.dll
LoadedModule[113]=C:\WINDOWS\SYSTEM32\MSIMG32.dll
LoadedModule[114]=C:\WINDOWS\System32\MSCTF.dll
LoadedModule[115]=C:\WINDOWS\SYSTEM32\CRYPTSP.dll
LoadedModule[116]=C:\WINDOWS\system32\rsaenh.dll
LoadedModule[117]=C:\WINDOWS\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9818.0_none_b7e811947b297f6d\MSXML4.DLL
LoadedModule[118]=C:\WINDOWS\System32\clbcatq.dll
LoadedModule[119]=C:\Windows\System32\urlmon.dll
LoadedModule[120]=C:\Windows\System32\iertutil.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
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Werkt niet meer
ConsentKey=APPCRASH
AppName=Microsoft Flight Simulator®
AppPath=C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=381DF571ED60C2BD257C942B863BDC44
MetadataHash=-266304033

Share this post


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

If you did all of the actions on how to fix most CTD's and freezes, then you have a bad overclock or something is wrong with your memory configurations.  It is not a problem with FSX-SE.  FSX-SE only triggers the crash as your computer system is not working properly.  The AVSIM CTD Guide tells you how other members have fixed the ntdll.dll error and the list is not inclusive as members are finding incompatibilities with scenery add-ons too.  When things don't work right in your configuration of FSX, it places more strain on your system requiring more resources.  This triggers the crash.  So, I thought, to fix any crash, why not return FSX back to the default configuration where no addon scenery is being loaded, no bad tweaks in the FSX.cfg, no bad modules in the dll.xml.  Years ago, members would uninstall FSX or reformat their HDD and reinstall Windows and then FSX.  That was the fix!  Everyone who did that got rid of the ntdll.dll error!  Then they started adding their add-ons again and putting horrible tweaks in their FSX.cfg which did nothing but give an individual some sort of belief the tweak was making their FSX work perfectly without any stuttering or other problems.  Today we find out that most tweaks are not needed as our computers are 10 times better than those used in 2006 when FSX was first developed.  The ntdll.dll is related to memory and, if your cpu voltage is too high or too low, FSX will crash as soon as you load your fsx.cfg with horrible tweaks or high settings.  That's it in a nutshell.  There's no known fix that works for everyone.  You have to investigate your computer issues as there are no two computers exactly alike and members have several different add-ons and FSX/Display driver settings.  The guide is to give you basic instructions on how to investigate.  Again, if you brought your FSX-SE back to the default by rebuilding your fsx and scenery configs and you are not loading your dll.xml, and you are still getting the ntdll.dll error, then you will have to reformat your HDD or SSD, reinstall Windows, reinstall FSX-SE and run it a couple of times, and then reinstall any add-ons.  That should fix it.  I was just trying to save you some time with some guidance in the CTD Guide.

Best regards,

Jim

Share this post


Link to post
Share on other sites

That's a very clear answer. Thank you.

To be clear, I have never used any add-ons up until the DX10 fix I tried to install last night. I did two complete reinstalls of FSX with no succes.

The guide mentioned deleting or deactivating fsx.cfg. I did so, but at this point, it isn't even rebuilding the config file. It just leaves me with a blank file.

I tried overwriting the file with a config file I had as a backup from yesterday, no succes.

I'll look into the memory issues you mentioned tomorrow if I have time (and motivation).

Anyway, thank you again for your time and help. I honestly appreciate it!

Share this post


Link to post
Share on other sites

You are suppose to have a version of the uiautomationcore.dll in your main fsx folder.  I did not see it loading in your report.  DTG installs a special version just for FSX-SE users. 

I have Windows 10 installed with the Boxed version of FSX and FSX would not start up until I placed a copy of the uiautomationcore.dll in my main FSX folder.  Not sure why Windows 8 and Windows 10 users have to have this module in the main fsx folder.  It is really not required for Windows 7 users.  The fact that FSX will now not even start up indicates to me this might be the problem.  FSX needs to start up in order to rebuild the FSX.cfg (and scenery.cfg if you renamed your scenery.cfg).

Is your computer overclocked?  If so, even a computer professional could have placed the cpu voltage too high or too low.  The only way to fix is to return your BIOS to the optimal defaults.  This is unlikely the problem though as you haven't even started up FSX. 

When you install FSX-SE, make sure User Access Controls (UAC) are disabled.  Any anti-virus program must be set up to exclude scanning the FSX drive.  So, you want to make sure C:\Program Files (x86) is excluded from scanning.  It is possible the uiautomationcore.dll and some other files were quarantined.  When quarantined, the files are moved to the quarantine folder until you delete them but it destroys the installation of FSX-SE.   Many experts recommend you install FSX-SE out of the C:\Program Files (x86) folder and place it into a folder of your own choosing such as C:\FSX or D:\FSX, etc.  You can change that at the beginning of the installation where it states where it is going to install FSX.  Look for an Option.

Now that I know more details about what you have installed and some of the actions you have taken, I believe we can solve this problem soon.  Hang in there!

Best regards,

Jim

Share this post


Link to post
Share on other sites

Ah, now we're getting somewhere!

No,  I don't have any overclocked components. Also, uiautomationcore.dll is there in the main FSX folder, I just tried to replace it with a windows 7 version, because some people said this fixed their problems. This didn't work, so I have the original file in there now.

I have to go to work soon but I'll try all the things you mentioned as soon as I get home. I'll keep you posted!

Share this post


Link to post
Share on other sites
5 hours ago, Regjit said:

I just tried to replace it with a windows 7 version, because some people said this fixed their problems.

The one that was installed by DTG must be in the folder.  FSX is a very old and used an old Microsoft.net v1.1.  The uiautomationcore.dll is part of the Microsoft.net packages.  Microsoft.net's are used by developers to make sure their runs properly as intended.

All .dll's in your main FSX-SE folder will load whether you want them to load or not.  So it is strange it did not load in your crash report above unless FSX-SE crashed before fully loading.  Make sure you have the exact version that was originally installed.

Best regards,

Jim

Share this post


Link to post
Share on other sites

Straight after coming home, and making a poor excuse for dinner, I once again did a complete, fresh reinstall of FSX. 
I disabled the UAC and moved my Steamapps folder outside of Program Files and FSX succesfully started!

Thank you so much for your help and time, Jim! 

One last question, though: do you think it would be unwise to try to install the DX10 fix again? Even though it was assured to have nothing to do with the crash, I'm still going to be very cautious about this one.

Share this post


Link to post
Share on other sites

The DX10 Fixer is a must for DX10 users as it fixes most, if not all, of the anomalies.  Super happy my suggestions worked.

Best regards,

Jim

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