October 13, 201213 yr So I've really been enjoying the tweaks made to DX10 and now that it is finally in a more usable state, I haven't taken another look back at DX9! However, I wanted to compare the performance between the two a bit more precisely and decided to switch temporarily back to the old version, but to my surprise, discovered that FSX is apparently too in love with DX10 to go back! Every time I try to launch in DX9 mode, it pulls up the splash screen then within about 10 seconds, I get the dreaded fatal error. But when I switched it back to DX10 mode via the fsx.cfg, it worked just fine. No crashes, no errors, or anything. Rock solid. So I assume the problem lies somewhere with the DirectX10 tweaks. Prior to adding them, I never had this issue, but now it seems I am stuck on DX10. Not good considering the amount of old addons I'm running! So, any assistance would be greatly appreciated...
October 13, 201213 yr I have switched back and forth between DX9 and DX10 several times and have not been able to duplicate your issue. When you go from DX10 Preview to DX9, are you unchecking DX10 Preview in the FSX setup screen, then closing and restarting FSX? Or, are you going into your FSX.cfg and changing the D3D10=1 line to D3D10=0? It shouldn't make any difference but you should try one or the other and see if FSX is still crashing. I think FSX prefers starting up FSX and enabling/disabling DX10 there. The only modification to DX10 was the FSX Shader folder. All FSX tweaks and display driver settings should work properly whether you are in DX9 or DX10 mode. So there is something else wrong with your computer or FSX setup. Download and install App Crash View and post the crash report here so we can see what caused the crash - http://www.nirsoft.net/utils/app_crash_view.html. Best regards, Jim Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
October 13, 201213 yr Author Okay, here's the dump log it came up with. Version=1 EventType=BEX EventTime=129946188167839783 ReportType=2 Consent=1 UploadTime=129946188168569825 ReportIdentifier=df5106c0-1551-11e2-b75e-8c89a5136e5a IntegratorReportIdentifier=df5106bf-1551-11e2-b75e-8c89a5136e5a WOW64=1 Response.type=4 Sig[0].Name=Application Name Sig[0].Value=fsx.exe Sig[1].Name=Application Version Sig[1].Value=10.0.61637.0 Sig[2].Name=Application Timestamp Sig[2].Value=46fadb14 Sig[3].Name=Fault Module Name Sig[3].Value=unknown Sig[4].Name=Fault Module Version Sig[4].Value=0.0.0.0 Sig[5].Name=Fault Module Timestamp Sig[5].Value=00000000 Sig[6].Name=Exception Offset Sig[6].Value=09a8f1c8 Sig[7].Name=Exception Code Sig[7].Value=c0000005 Sig[8].Name=Exception Data Sig[8].Value=00000008 DynamicSig[1].Name=OS Version DynamicSig[1].Value=6.1.7601.2.1.0.768.3 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=1033 UI[2]=C:\FSX\fsx.exe UI[3]=A fatal error occurred. UI[4]=Windows can check online for a solution to the problem. UI[5]=Check online for a solution and close the program UI[6]=Check online for a solution later and close the program UI[7]=Close the program LoadedModule[0]=C:\FSX\fsx.exe LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll LoadedModule[2]=C:\Windows\syswow64\kernel32.dll LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll LoadedModule[4]=C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL LoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll LoadedModule[6]=C:\Windows\syswow64\msvcrt.dll LoadedModule[7]=C:\Windows\syswow64\GDI32.dll LoadedModule[8]=C:\Windows\syswow64\USER32.dll LoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dll LoadedModule[10]=C:\Windows\SysWOW64\sechost.dll LoadedModule[11]=C:\Windows\syswow64\RPCRT4.dll LoadedModule[12]=C:\Windows\syswow64\SspiCli.dll LoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dll LoadedModule[14]=C:\Windows\syswow64\LPK.dll LoadedModule[15]=C:\Windows\syswow64\USP10.dll LoadedModule[16]=C:\Windows\syswow64\SHLWAPI.dll LoadedModule[17]=C:\Windows\syswow64\ole32.dll LoadedModule[18]=C:\Windows\system32\apphelp.dll LoadedModule[19]=C:\Windows\AppPatch\AcGenral.DLL LoadedModule[20]=C:\Windows\system32\UxTheme.dll LoadedModule[21]=C:\Windows\system32\WINMM.dll LoadedModule[22]=C:\Windows\system32\samcli.dll LoadedModule[23]=C:\Windows\syswow64\OLEAUT32.dll LoadedModule[24]=C:\Windows\system32\MSACM32.dll LoadedModule[25]=C:\Windows\system32\VERSION.dll LoadedModule[26]=C:\Windows\syswow64\SHELL32.dll LoadedModule[27]=C:\Windows\system32\sfc.dll LoadedModule[28]=C:\Windows\system32\sfc_os.DLL LoadedModule[29]=C:\Windows\system32\USERENV.dll LoadedModule[30]=C:\Windows\system32\profapi.dll LoadedModule[31]=C:\Windows\system32\dwmapi.dll LoadedModule[32]=C:\Windows\syswow64\SETUPAPI.dll LoadedModule[33]=C:\Windows\syswow64\CFGMGR32.dll LoadedModule[34]=C:\Windows\syswow64\DEVOBJ.dll LoadedModule[35]=C:\Windows\syswow64\urlmon.dll LoadedModule[36]=C:\Windows\syswow64\iertutil.dll LoadedModule[37]=C:\Windows\syswow64\WININET.dll LoadedModule[38]=C:\Windows\syswow64\Normaliz.dll LoadedModule[39]=C:\Windows\system32\MPR.dll LoadedModule[40]=C:\Windows\AppPatch\AcLayers.DLL LoadedModule[41]=C:\Windows\system32\WINSPOOL.DRV LoadedModule[42]=C:\Windows\AppPatch\AcSpecfc.DLL LoadedModule[43]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\COMCTL32.dll LoadedModule[44]=C:\Windows\system32\mscms.dll LoadedModule[45]=C:\Windows\system32\DDRAW.dll LoadedModule[46]=C:\Windows\system32\DCIMAN32.dll LoadedModule[47]=C:\Windows\syswow64\COMDLG32.dll LoadedModule[48]=C:\Windows\syswow64\IMM32.dll LoadedModule[49]=C:\Windows\syswow64\MSCTF.dll LoadedModule[50]=C:\Windows\syswow64\WS2_32.dll LoadedModule[51]=C:\Windows\syswow64\NSI.dll LoadedModule[52]=C:\Windows\system32\msi.dll LoadedModule[53]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL LoadedModule[54]=C:\FSX\language.dll LoadedModule[55]=C:\FSX\API.DLL LoadedModule[56]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll LoadedModule[57]=C:\FSX\ablscpt.dll LoadedModule[58]=C:\FSX\flight.dll LoadedModule[59]=C:\FSX\ai_player.dll LoadedModule[60]=C:\FSX\acontain.dll LoadedModule[61]=C:\FSX\controls.dll LoadedModule[62]=C:\Windows\system32\DINPUT8.dll LoadedModule[63]=C:\FSX\fsui.dll LoadedModule[64]=C:\FSX\atc.dll LoadedModule[65]=C:\FSX\facilities.dll LoadedModule[66]=C:\FSX\demo.dll LoadedModule[67]=C:\FSX\main.dll LoadedModule[68]=C:\FSX\fe.dll LoadedModule[69]=C:\FSX\util.dll LoadedModule[70]=C:\FSX\simprop.dll LoadedModule[71]=C:\FSX\g2d.dll LoadedModule[72]=C:\Windows\system32\d3dx9_34.dll LoadedModule[73]=C:\Windows\system32\d3dx10_34.dll LoadedModule[74]=C:\FSX\d3d9.dll LoadedModule[75]=C:\Windows\system32\d3dx9_43.dll LoadedModule[76]=C:\FSX\g3d.dll LoadedModule[77]=C:\FSX\panels.dll LoadedModule[78]=C:\FSX\multiplayer.dll LoadedModule[79]=C:\FSX\ui.dll LoadedModule[80]=C:\FSX\sound.dll LoadedModule[81]=C:\FSX\sim1.dll LoadedModule[82]=C:\FSX\simscheduler.dll LoadedModule[83]=C:\FSX\visualfx.dll LoadedModule[84]=C:\FSX\window.dll LoadedModule[85]=C:\FSX\terrain.dll LoadedModule[86]=C:\FSX\weather.dll LoadedModule[87]=C:\Windows\system32\DSOUND.dll LoadedModule[88]=C:\Windows\system32\POWRPROF.dll LoadedModule[89]=C:\FSX\symmap.dll LoadedModule[90]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17825_none_72d273598668a06b\gdiplus.dll LoadedModule[91]=C:\Windows\system32\MSIMG32.dll LoadedModule[92]=C:\FSX\xuipc.dll LoadedModule[93]=C:\FSX\livingwater.dll LoadedModule[94]=C:\FSX\fs-traffic.dll LoadedModule[95]=C:\FSX\gps.dll LoadedModule[96]=C:\Windows\system32\MSWSOCK.dll LoadedModule[97]=C:\Windows\system32\SHFOLDER.dll LoadedModule[98]=C:\Windows\system32\d3d9.dll LoadedModule[99]=C:\Windows\system32\d3d8thk.dll LoadedModule[100]=C:\Windows\system32\CRYPTSP.dll LoadedModule[101]=C:\Windows\system32\rsaenh.dll LoadedModule[102]=C:\Windows\syswow64\WINTRUST.dll LoadedModule[103]=C:\Windows\syswow64\CRYPT32.dll LoadedModule[104]=C:\Windows\syswow64\MSASN1.dll LoadedModule[105]=C:\Windows\syswow64\CLBCatQ.DLL LoadedModule[106]=C:\Windows\system32\wbem\wbemprox.dll LoadedModule[107]=C:\Windows\system32\wbemcomn.dll LoadedModule[108]=C:\Windows\system32\RpcRtRemote.dll LoadedModule[109]=C:\Windows\system32\wbem\wbemsvc.dll LoadedModule[110]=C:\Windows\system32\wbem\fastprox.dll LoadedModule[111]=C:\Windows\system32\NTDSAPI.dll LoadedModule[112]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL LoadedModule[113]=C:\Windows\system32\dxgi.dll LoadedModule[114]=C:\Windows\system32\nvd3dum.dll LoadedModule[115]=C:\Windows\syswow64\PSAPI.DLL LoadedModule[116]=C:\Windows\system32\D3DCompiler_34.dll LoadedModule[117]=C:\Windows\system32\WindowsCodecs.dll LoadedModule[118]=C:\Windows\system32\d3d10_1.dll LoadedModule[119]=C:\Windows\system32\d3d10_1core.dll LoadedModule[120]=C:\Windows\SysWOW64\dxdiagn.dll LoadedModule[121]=C:\Windows\SysWOW64\d3d10.dll LoadedModule[122]=C:\Windows\SysWOW64\d3d10core.dll LoadedModule[123]=C:\Windows\SysWOW64\d3d11.dll LoadedModule[124]=C:\Windows\system32\winbrand.dll LoadedModule[125]=C:\Windows\system32\WTSAPI32.DLL LoadedModule[126]=C:\Windows\system32\WINSTA.dll LoadedModule[127]=C:\Windows\SysWOW64\gameux.dll LoadedModule[128]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll LoadedModule[129]=C:\Windows\SysWOW64\XmlLite.dll LoadedModule[130]=C:\Windows\SysWOW64\wer.dll LoadedModule[131]=C:\Windows\System32\Wpc.dll LoadedModule[132]=C:\Windows\System32\wevtapi.dll LoadedModule[133]=C:\Windows\System32\msxml6.dll LoadedModule[134]=C:\Windows\system32\SAMLIB.dll LoadedModule[135]=C:\Windows\system32\netutils.dll LoadedModule[136]=C:\FSX\uiautomationcore.dll LoadedModule[137]=C:\Windows\system32\OLEACC.dll LoadedModule[138]=C:\Windows\System32\MMDevApi.dll LoadedModule[139]=C:\Windows\System32\PROPSYS.dll LoadedModule[140]=C:\Windows\system32\AUDIOSES.DLL LoadedModule[141]=C:\Windows\system32\RICHED20.DLL LoadedModule[142]=C:\Windows\system32\HID.DLL LoadedModule[143]=C:\Windows\system32\XInput9_1_0.dll LoadedModule[144]=C:\Windows\system32\wdmaud.drv LoadedModule[145]=C:\Windows\system32\ksuser.dll LoadedModule[146]=C:\Windows\system32\AVRT.dll LoadedModule[147]=C:\Windows\system32\msacm32.drv LoadedModule[148]=C:\Windows\system32\midimap.dll LoadedModule[149]=C:\Windows\system32\dinput.DLL LoadedModule[150]=C:\Windows\System32\wship6.dll LoadedModule[151]=C:\Windows\System32\wshtcpip.dll LoadedModule[152]=C:\Program Files (x86)\FlightSimTools.com\Addon Converter X\AddonConverterX.dll LoadedModule[153]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll LoadedModule[154]=C:\FSX\bglmanx.dll LoadedModule[155]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll LoadedModule[156]=C:\Windows\system32\inetmib1.dll LoadedModule[157]=C:\Windows\system32\IPHLPAPI.DLL LoadedModule[158]=C:\Windows\system32\WINNSI.DLL LoadedModule[159]=C:\Windows\system32\snmpapi.dll LoadedModule[160]=C:\FSX\Modules\GPSModule.dll LoadedModule[161]=C:\FSX\PMDG\DLLs\PMDG_HUD_interface.dll LoadedModule[162]=C:\Windows\system32\MSVCR100.dll LoadedModule[163]=C:\FSX\Modules\FSUIPC4.dll LoadedModule[164]=C:\FSX\MD80.dll LoadedModule[165]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll LoadedModule[166]=C:\Program Files (x86)\FS Recorder for FSX\FSRecorder_FSX.dll LoadedModule[167]=C:\FSX\Modules\A2A_Feel.dll LoadedModule[168]=C:\Windows\SysWow64\XAudio2_6.dll LoadedModule[169]=C:\FSX\Modules\AccuFeelMenu.dll Sec[0].Key=LCID Sec[0].Value=1033 State[0].Key=Transport.DoneStage1 State[0].Value=1 FriendlyEventName=Stopped working ConsentKey=BEX AppName=Microsoft® Flight Simulator X AppPath=C:\FSX\fsx.exe
October 13, 201213 yr Is that the only one? This one doesn't provide enough info. I'm looking for the faulting modue in the Sig3 line. Do you have an anti-virus program running. I have seen this type of crash caused if you have automatic updates setup and while using FSX, the anti-virus program is running in the background looking for updates or looking for changes to your system. The Exception Code oxc0000005 indicates you had a Memory_Access_Violation which usually shows up in every FSX crash. It could be FSX was trying to call a texture, a gauge, an effect, a module and it could not be located so FSX crashed. Event type BEX indicates a buffer overflow or DEP exception: The primary benefit of DEP is that it helps to prevent code execution from data pages such as the default heap, various stacks, and memory pools. In normal operations of the system, code is not typically executed from the default heap and stack. Hardware-enforced DEP detects code that is running from these locations and raises an exception when execution occurs. If the exception is unhandled, the process will be terminated. Execution of code from protected memory in kernel mode results in an error. Although terminating a process or causing the system to fail with an error do not appear to be ideal experiences, this helps prevent malicious code from executing. Preventing malicious code from executing on the system may prevent damage to the system or propagation of malicious code whose harmful effects could easily exceed those of a terminated process or system error. DEP can help prevent some exploits in which a virus or other attack has injected a process with executable code and then attempts to execute the injected code. On a system with DEP, execution of the injected code should result in an exception. Software-enforced DEP can help mitigate exploits of exception handling mechanisms within Windows. You cannot disable DEP for FSX. Impossible. So I'm thinking maybe a bad setting in your FSX.cfg causes the crash as you are moving from DX10 to DX9 and vice-versa. It could be your display driver settings too. Run your anti-virus program and make sure you have no viruses installed. If you have a program that looks for Malware, run Windows Defender to see if any spyware and other unwanted software protection is installed. Microsoft Essentials (free) can also do this. Make sure your virtual memory (page file) is set to System Managed Size. Click on the Start button and in the search box, type Virtual, then look up and click on how to change virtual memory. Follow the steps but don't manually set a size. Instead, at the Virtual Memory page, click on System Managed Size. Turn off your User Access Controls (UAC). Click on the Start button and type UAC in the search box, then look up and click on Change User Account Settings. Pull the slider all the way down and click okay. With this turned on too high, Microsoft security may prevent certain programs to open up thus causing the crash. If we cannot find a faulting module, then I recommend renaming your FSX.cfg, restarting FSX and let the config rebuild. Now try to go from DX10 to DX9 and vice-versa. If it works, then we can probably assume there's an issue in the config. Best regards, Jim Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
October 13, 201213 yr Author I have tried letting FSX rebuild the config from scratch, have scanned my computer for viruses and disabled my antivirus to no avail. And also, that was the only relevant dump log from FSX. I have many more of them, but the majority of them were caused by Airbus X. the rest of the crashes produced the same dump log as this one, line for line. I think I will also try removing the shader cache and let FSX rebuild that as well. Could that help? *Edit: tried flushing the shader cache...nope, didn't help :|
October 13, 201213 yr I think I will also try removing the shader cache and let FSX rebuild that as well. Could that help? It may help but doubt that's the problem as BEX events are more serious. How about trying what I advised another individual here on how to fix their installation of the DX10 Shader fix. Perhaps yours got corrupted. Here's what I advised: "Well Paul has posted the complete ShaderHLSL mod folder up in the pinned topic about installation problems. This has all of the 3.1 mods done so you don't need to run Steve's install program. Download that to your desktop. Delete the ShadersHLSL directory from the main FSX directory then drag and drop the unzipped ShadersHLSL folder into the main FSX directory. Before starting FSX, go up to the (USER) AppData\Local\Microsoft\FSX\ and delete the Shaders10 folder (it will be rebuilt). Now restart FSX and see if it works. Sometimes these anti-virus programs mess up a good install...." It won't hurt to try at least. Best regards, Jim Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
October 13, 201213 yr Author No dice. Tried reinstalling the fix and it's just the same as before: it pulls up the splash screen for about 10 seconds then does a faceplant. EDIT: Okay, this is unbelievable, but apparently the cause of the crashing was none other than the good 'ol ENB series mod. As soon as I removed it, the thing ran and just wouldn't stop for anything but the little red 'x' in the corner... Edit #2: Well after about two minutes of looking into this further, I have discovered that I've once again been foiled by the PPIT mod. Apparently the D3D9.dll version it uses doesn't play nice with the new shaders. After switching back to the original one that I was using...it's like there was never anything wrong.
October 14, 201213 yr Yes, I heard the ENB series mod is not compatible. You can remove the d3d9.dll in your FSX main directory and move it to a temporary directory which you use DX10. You also need to move the enb.ini from the main FSX directory or you will get crashes trying to start FSX. As I stated in post #7, you do not need to run Steve's setup program to install this DX10 fix. You can simply download the whole DX10 3.1 folder that Paul has posted in the Installation Problems post. Delete the one in the FSX directory and drop Paul's ShaderHLSL folder into its place. Best regards, Jim Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
Create an account or sign in to comment