Jump to content
Sign in to follow this  
supernova48

FSX Fatal Crash

Recommended Posts

I just started getting this fatal crash during startup on FSX.  I never make it past the opeing screen. I have attached the error log from Windows 7 event log.  Hopefully someone out can direct me to where I might be having a problem.  I am running Windows 7 x64.

 

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x000ce064

Faulting process id: 0x1348

Faulting application start time: 0x01ce2700bffec503

Faulting application path: D:\Microsoft Flight Simulator X\fsx.exe

Faulting module path: unknown

Report Id: b4bd8dd3-92f4-11e2-a93e-00242113f13a

 

Thanks in advance,

Ken

 

Share this post


Link to post
Share on other sites

You need to download and run AppCrashView - http://www.nirsoft.net/utils/app_crash_view.html as it provides more information regarding your crash(es).  This error report provides no useful information.  If you can't make it past the opening screen it is possible that you do not have Microsoft Visual C++ 2005, 2008, and 2010 installed.  The 2005 version is required to run FSX.  Another possibility might be a corrupt logbook in your C:\MyDocuments\FSX folder.  You can delete or rename the file (but it contains all the data regarding your missions completed) or you can go into the AVSIM Library and download a program that will check to see if it is corrupt and fix it.  Just search for logbook in the Library.

 

Best regards,

Jim


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important 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 

 

Share this post


Link to post
Share on other sites

Ok, so I ran AppCrashView.  I last module loaded was number 188 then the log ends with the following:

 

LoadedModule[188]=C:\Windows\system32\SensApi.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=D:\Microsoft Flight Simulator X\fsx.exe

 

Does that provide the info to fix?

 

Thanks,

Ken

 

Share this post


Link to post
Share on other sites

Here is the whole event log:

Version=1
EventType=BEX
EventTime=130084743604833984
ReportType=2
Consent=1
UploadTime=130084743605976562
ReportIdentifier=d2ecad3a-9355-11e2-aacf-00242113f13a
IntegratorReportIdentifier=d2ecad39-9355-11e2-aacf-00242113f13a
WOW64=1
Response.BucketId=1700375555
Response.BucketTable=5
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=000ce064
Sig[7].Name=Exception Code
Sig[7].Value=c0000005
Sig[8].Name=Exception Data
Sig[8].Value=badc0de1
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=D:\Microsoft Flight Simulator X\fsx.exe
UI[3]=A fatal error occurred.
UI[4]=Windows can check online for a solution to the problem and try to restart the program.
UI[5]=Check online for a solution and restart the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=D:\Microsoft 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\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]=D:\Microsoft Flight Simulator X\language.dll
LoadedModule[55]=D:\Microsoft Flight Simulator X\API.DLL
LoadedModule[56]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll
LoadedModule[57]=D:\Microsoft Flight Simulator X\ablscpt.dll
LoadedModule[58]=D:\Microsoft Flight Simulator X\flight.dll
LoadedModule[59]=D:\Microsoft Flight Simulator X\ai_player.dll
LoadedModule[60]=D:\Microsoft Flight Simulator X\acontain.dll
LoadedModule[61]=D:\Microsoft Flight Simulator X\controls.dll
LoadedModule[62]=C:\Windows\system32\DINPUT8.dll
LoadedModule[63]=D:\Microsoft Flight Simulator X\fsui.dll
LoadedModule[64]=D:\Microsoft Flight Simulator X\atc.dll
LoadedModule[65]=D:\Microsoft Flight Simulator X\facilities.dll
LoadedModule[66]=D:\Microsoft Flight Simulator X\demo.dll
LoadedModule[67]=D:\Microsoft Flight Simulator X\main.dll
LoadedModule[68]=D:\Microsoft Flight Simulator X\fe.dll
LoadedModule[69]=D:\Microsoft Flight Simulator X\util.dll
LoadedModule[70]=D:\Microsoft Flight Simulator X\simprop.dll
LoadedModule[71]=D:\Microsoft Flight Simulator X\g2d.dll
LoadedModule[72]=C:\Windows\system32\d3dx9_34.dll
LoadedModule[73]=C:\Windows\system32\d3dx10_34.dll
LoadedModule[74]=C:\Windows\system32\d3d9.dll
LoadedModule[75]=C:\Windows\system32\d3d8thk.dll
LoadedModule[76]=D:\Microsoft Flight Simulator X\g3d.dll
LoadedModule[77]=D:\Microsoft Flight Simulator X\panels.dll
LoadedModule[78]=D:\Microsoft Flight Simulator X\multiplayer.dll
LoadedModule[79]=D:\Microsoft Flight Simulator X\ui.dll
LoadedModule[80]=D:\Microsoft Flight Simulator X\sound.dll
LoadedModule[81]=D:\Microsoft Flight Simulator X\sim1.dll
LoadedModule[82]=D:\Microsoft Flight Simulator X\simscheduler.dll
LoadedModule[83]=D:\Microsoft Flight Simulator X\visualfx.dll
LoadedModule[84]=D:\Microsoft Flight Simulator X\window.dll
LoadedModule[85]=D:\Microsoft Flight Simulator X\terrain.dll
LoadedModule[86]=D:\Microsoft Flight Simulator X\weather.dll
LoadedModule[87]=C:\Windows\system32\DSOUND.dll
LoadedModule[88]=C:\Windows\system32\POWRPROF.dll
LoadedModule[89]=D:\Microsoft Flight Simulator X\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]=D:\Microsoft Flight Simulator X\xuipc.dll
LoadedModule[93]=D:\Microsoft Flight Simulator X\livingwater.dll
LoadedModule[94]=D:\Microsoft Flight Simulator X\fs-traffic.dll
LoadedModule[95]=D:\Microsoft Flight Simulator X\gps.dll
LoadedModule[96]=C:\Windows\system32\MSWSOCK.dll
LoadedModule[97]=C:\Windows\system32\SHFOLDER.dll
LoadedModule[98]=C:\Program Files\Logitech\SetPoint\x86\GameHook.dll
LoadedModule[99]=C:\Program Files\Logitech\SetPoint\x86\lgscroll.dll
LoadedModule[100]=C:\Windows\system32\ntmarta.dll
LoadedModule[101]=C:\Windows\syswow64\WLDAP32.dll
LoadedModule[102]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[103]=C:\Windows\system32\rsaenh.dll
LoadedModule[104]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[105]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[106]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[107]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[108]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[109]=C:\Windows\system32\wbemcomn.dll
LoadedModule[110]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[111]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[112]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[113]=C:\Windows\system32\NTDSAPI.dll
LoadedModule[114]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL
LoadedModule[115]=C:\Windows\system32\dxgi.dll
LoadedModule[116]=C:\Windows\system32\d3d11.dll
LoadedModule[117]=C:\Windows\system32\nvd3dum.dll
LoadedModule[118]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[119]=C:\Windows\system32\D3DCompiler_34.dll
LoadedModule[120]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[121]=C:\Windows\system32\d3d10_1.dll
LoadedModule[122]=C:\Windows\system32\d3d10_1core.dll
LoadedModule[123]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll
LoadedModule[124]=C:\Windows\SysWOW64\dxdiagn.dll
LoadedModule[125]=C:\Windows\SysWOW64\d3d10.dll
LoadedModule[126]=C:\Windows\SysWOW64\d3d10core.dll
LoadedModule[127]=C:\Windows\system32\winbrand.dll
LoadedModule[128]=C:\Windows\system32\nvapi.dll
LoadedModule[129]=C:\Windows\system32\WTSAPI32.DLL
LoadedModule[130]=C:\Windows\system32\WINSTA.dll
LoadedModule[131]=C:\Windows\SysWOW64\gameux.dll
LoadedModule[132]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll
LoadedModule[133]=C:\Windows\SysWOW64\XmlLite.dll
LoadedModule[134]=C:\Windows\SysWOW64\wer.dll
LoadedModule[135]=C:\Windows\System32\Wpc.dll
LoadedModule[136]=C:\Windows\System32\wevtapi.dll
LoadedModule[137]=C:\Windows\System32\msxml6.dll
LoadedModule[138]=C:\Windows\system32\SAMLIB.dll
LoadedModule[139]=C:\Windows\system32\netutils.dll
LoadedModule[140]=D:\Microsoft Flight Simulator X\uiautomationcore.dll
LoadedModule[141]=C:\Windows\system32\OLEACC.dll
LoadedModule[142]=C:\Windows\System32\MMDevApi.dll
LoadedModule[143]=C:\Windows\System32\PROPSYS.dll
LoadedModule[144]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[145]=C:\Windows\system32\RICHED20.DLL
LoadedModule[146]=C:\Windows\system32\HID.DLL
LoadedModule[147]=C:\Windows\system32\XInput9_1_0.dll
LoadedModule[148]=C:\Windows\system32\wdmaud.drv
LoadedModule[149]=C:\Windows\system32\ksuser.dll
LoadedModule[150]=C:\Windows\system32\AVRT.dll
LoadedModule[151]=C:\Windows\system32\msacm32.drv
LoadedModule[152]=C:\Windows\system32\midimap.dll
LoadedModule[153]=C:\Windows\system32\dinput.DLL
LoadedModule[154]=C:\Windows\System32\wship6.dll
LoadedModule[155]=C:\Windows\System32\wshtcpip.dll
LoadedModule[156]=D:\Microsoft Flight Simulator X\bglmanx.dll
LoadedModule[157]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[158]=C:\Windows\system32\inetmib1.dll
LoadedModule[159]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[160]=C:\Windows\system32\WINNSI.DLL
LoadedModule[161]=C:\Windows\system32\snmpapi.dll
LoadedModule[162]=C:\Flight One Software\Instant Object Studio\InstantObjectStudioFSX.dll
LoadedModule[163]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll
LoadedModule[164]=C:\Windows\system32\oledlg.dll
LoadedModule[165]=D:\Microsoft Flight Simulator X\ORBX\FTX_NA\FTX_AA_CEN4\Scenery\ObjectFlow_cen4.dll
LoadedModule[166]=D:\Microsoft Flight Simulator X\ORBX\FTX_NA\FTX_AA_KSFF\Scenery\ObjectFlow_KSFF.dll
LoadedModule[167]=D:\Microsoft Flight Simulator X\ORBX\FTX_NA\FTX_AA_KWYS\Scenery\ObjectFlow_KWYS.dll
LoadedModule[168]=D:\Microsoft Flight Simulator X\ORBX\FTX_NA\FTX_AA_KJAC\Scenery\ObjectFlow_KJAC.dll
LoadedModule[169]=D:\Microsoft Flight Simulator X\ORBX\FTX_NA\FTX_AA_PAKT\Scenery\ObjectFlow_PAKT.dll
LoadedModule[170]=D:\Microsoft Flight Simulator X\ORBX\FTX_NA\FTX_AA_KBVS\Scenery\Objectflow_KBVS.dll
LoadedModule[171]=C:\Program Files (x86)\Instant Scenery 2\InstantSceneryFSX.dll
LoadedModule[172]=D:\Microsoft Flight Simulator X\PMDG\DLLs\PMDG_HUD_interface.dll
LoadedModule[173]=C:\Windows\system32\MSVCR100.dll
LoadedModule[174]=D:\Microsoft Flight Simulator X\VistaMare\ViMaCoreX.dll
LoadedModule[175]=D:\Microsoft Flight Simulator X\VistaMare\bin\VMCX_AP.dll
LoadedModule[176]=D:\Microsoft Flight Simulator X\VistaMare\bin\ViMaNET_AP.dll
LoadedModule[177]=D:\Microsoft Flight Simulator X\Aerosoft\ASE_DATA\AseData.dll
LoadedModule[178]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61242.0_none_e079b46b85043c20\SimConnect.dll
LoadedModule[179]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCP90.dll
LoadedModule[180]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll
LoadedModule[181]=D:\Microsoft Flight Simulator X\Modules\FSUIPC4.dll
LoadedModule[182]=C:\Windows\syswow64\imagehlp.dll
LoadedModule[183]=C:\Windows\system32\ncrypt.dll
LoadedModule[184]=C:\Windows\system32\bcrypt.dll
LoadedModule[185]=C:\Windows\SysWOW64\bcryptprimitives.dll
LoadedModule[186]=C:\Windows\system32\GPAPI.dll
LoadedModule[187]=C:\Windows\system32\cryptnet.dll
LoadedModule[188]=C:\Windows\system32\SensApi.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=D:\Microsoft Flight Simulator X\fsx.exe
 

 

Thanks again,

Ken

Share this post


Link to post
Share on other sites

No.  I need to see everything that was loaded.  Just copy and paste everything on the bottom tier regarding the crash.

 

Best regards,

Jim



"Here is the whole event log:"

 

That was fast!  Give me a second or two.

 

Best regards,

Jim


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important 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 

 

Share this post


Link to post
Share on other sites

You have Microsoft Visual C++ 2005, 2008, and 2010 with all updates installed.  Good!  Did you check the logbook.bin in the MyDocuments\FSX folder?  To test to see if it is corrupt or not, simply rename it to logbook.bin.orig then restart FSX and see if FSX will load.  If not, it's not a corrupt logbook and you need to go back in there and delete the logbook.bin that was created when you restarted FSX (if one was created), then rename the orig back to logbook.bin.

 

There are many things that load when FSX is started up.  One looks at your previous flight and of course your default flight.  If you saved another flight as your default flight, it starts loading that flight and, if any of the components to that new default flight are missing, fsx may not start up.

 

Since you are running FSX on a laptop, you want to be sure you have plenty of PC power and you do not have your settings set too high.

 

I suspect Instant SceneryFSX and/or InstantObjectStudio, as possible causes for FSX not to start up.  Aerosoft's ASE has caused problems in the past too. 

 

One way to investigate this is to download and run process monitor http://technet.microsoft.com/en-US/sysinternals.  Once process monitor is running, immediately start up FSX and, after FSX quits running hit Ctrl-E.  This will capture all the events that were running up to the time of your crash.  Look for any anomalies near the end of the report.  What was it trying to load?  A scenery?  A fsx file, an Effect?  This will give you a good idea as to what caused fsx to stop working.  I see you are running several Orbx sceneries.  Disable this sceneries by going into FTX Central and clicking on Default.  Then run FSX.  If FSX starts up, then it is one of those sceneries at fault.

 

Hope this helps.

 

Best regards,

Jim


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important 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 

 

Share this post


Link to post
Share on other sites

Wow that was also quick.

 

Logbook OK, default flight same for over a year, I haven't used Instant Scenery in a while, Instant Object Studio is a demo that I have not messed with yet.  Not sure what Aerosoft ASE is.  I will download the process moniter and try that as well as disabling FTX sceneries.

 

My computer is a desktop, not a laptop.

 

Again thanks for your time and suggestions,

Back to troubleshooting,

Ken

Share this post


Link to post
Share on other sites

ASE is a module from Aerosoft that monitors your Aerosoft software you have installed on your computer.  It checks to make sure you have the latest version and it is authorized.  Make sure you have the latest version as previous versions had a lot of problems.

 

That last module that loaded - SensApi.dll - indicates it is a module for connectivity and connection for mobile computer users so that's why I assumed you had a laptop.  Here's more info on it - http://dll.paretologic.com/detail.php/sensapi

 

Best regards,

Jim


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important 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 

 

Share this post


Link to post
Share on other sites

OK,

I ran process monitor during FSX startup.  The last fsx.exe entry was:

                  HKLM\SOFTWARE\Wow6432Node\Aerosoft\Fairbanks X                                          SUCCESS

 

So I'm still lost on what to look for.

 

Ken

Share this post


Link to post
Share on other sites

The Process Monitor will not necessarily show exactly what caused the crash.  Everything that is happening to your computer when you start up FSX is being recorded and it may not have been FSX related that caused your crash.  It could have been a Windows service or your video card or just anything.  I thought maybe you could see what was the last module just as FSX crashed.  It should have recorded the crash too.

 

Your crash was caused by a Buffer Exception Overrun (BEX) and those are hard to determine the exact cause for the crash.  I had one once and I fixed my problem by reinstalling Windows then FSX.  I'm still in the process of reinstalling FSX addons but about finished. 

 

I think it is the Aerosoft ASE program causing the problem.  Look in your Add/Remove programs and look for Aerosoft ASE.  If there, uninstall it then run FSX again.  As I recall it is really not needed.  If that did not solve the problem, then go into your Scenery Library and disable FairbanksX. Run FSX and see if that fixed the problem.

 

If that doesn't work then you'll have to reinstall Windows and FSX.

 

Best regards,

Jim


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important 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 

 

Share this post


Link to post
Share on other sites

You can try just reinstalling FSX - http://support.precisionmanuals.com/KB/a87/how-to-uninstall-and-reinstall-fsx.aspx.  Before you do, try disabling all of your addon scenery (everything down to Propeller Objects).  Just untick the box next to each scenery to disable.  If this fixes the problem, then you can try enabling 3-4 at a time until the crash reappears.

 

Best regards,

Jim


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important 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 

 

Share this post


Link to post
Share on other sites

I have been working through a PM with another individual who had the same error msg as you had (BEX with no known faulting module).  Turned out it was an external program - GamerOSD, which came with the ASUS-Nvidia card.  I'm relaying this on as you might have a similar program installed. 

 

Best regards,

Jim


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important 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 

 

Share this post


Link to post
Share on other sites

Since this has only been happening the past week, I removed any updates that were installed since 3/15.  No luck so far.  I don't have GamerOSD.  I have been removing sceneries and aircraft.  Still no luck.  New FSX.cfg file and did not run any of the addon dll's.  Still no luck.  Looks like re install is the next step.

 

My son is home for spring break, he will be working at Microsoft starting this summer and interned there last year.  I'll have him look it, maybe he'll have some additional suggestions.

 

Again, thanks for the suggestions.

 

Ken

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  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...