Sign in to follow this  
abh_jc_03

froze at splash screen

Recommended Posts

I originally was having problems with Couatl so I deleted all their stuff.  I created a new fsx.cfg file and it asked me to trust all the different modules and I did.  Now FSX just sits and spins at the Microsoft Simulator X splash screen and spins and never opens.  Can someone help?  I have already had to reinstall FSX once and I am trying to prevent the headache of doing it all over again and ALL my addons.  Thank you.

Share this post


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

I am not sure if it's acceleration or if I should had skipped that and just installed service pack 2. I use military aircraft though so I'm not sure if it would work without acceleration. I did a repair to FSX and said it repaired but still won't load. I Uninstaller all fsdreamteam software that I hope to be able to reinstall later.

Share this post


Link to post
Share on other sites

Have you tried renaming the Logbook.bin file in My Documents/Flight Simulator X folder and see if FSX will

 

start up and build a new one?  That seems to be the usual problem when you can't get past the Splash Screen.

Share this post


Link to post
Share on other sites

Thank you. I will try that out. I just had to reformat my computer so I hope this will save me the headache of Uninstall ingredients fsx.

Share this post


Link to post
Share on other sites

Check that your FSX.exe is in the FSX tree. Mine got stuck doing this some time ago, I had a complete copy of that installation on an external HD, I copied the .exe from that and that solved my long waiting issue.

 

Berlopez

Share this post


Link to post
Share on other sites

Fsx tree? It's in my F drive in my Microsoft flight simulator folder and my fsx cfg is in my appdata/roaming folder on my C drive.

Share this post


Link to post
Share on other sites

Josh: I only have My C:\ That's where my FSX.exe resides ( Look Down the tree).  My .cfg is also in app.data\roaming...

 

Berlopez

Share this post


Link to post
Share on other sites

I don't know. I hover over fsx task bar and there is no other window asking about anything.

I'm going to try renaming the logbook.bin tonight. I've got my fingers crossed.

Share this post


Link to post
Share on other sites

Have you updated your Nvidia driver by any chance?

 

The latest release 361.43 does not work with FSX and it freezes it as described. You need to roll back to 359.06 which definitely works with no issues, as I have it.

Share this post


Link to post
Share on other sites

I have AMD.  I had spybot installed on my computer and uninstalled that thinking maybe that had something to do with it but nothing.  It's weird because it acts like it wants to  go and I even get the click sound when it is about to work but it just spins and it doesn't give an error until I go into the task manager and end the process.  It just does the fatal error has occured.


I uninstalled My traffic x 5.4c update and It started to load.  It ran through the generating scenery index and all but still just hung at the splash screen.

Share this post


Link to post
Share on other sites

A fatal error?  It's time to check the Events Log to see what the "Faulting Module" is.

Share this post


Link to post
Share on other sites

Just type in on your Start  search window depending on what version OS you are running, EventVwr and it should come up. Then look in there.

Share this post


Link to post
Share on other sites

This is what I found. 

 

The program fsx.exe version 10.0.61637.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
 Process ID: de4
 Start Time: 01d148d895fe0bb9
 Termination Time: 14
 Application Path: F:\FSX\fsx.exe
 Report Id: 698b5a63-b4cc-11e5-910d-5404a64b79fe
 
 
I dont see a area for problem history.

Share this post


Link to post
Share on other sites

Control Panel-> Administrative Tools-> Event Viewer, select Custom Views-> Administrative Events.
One of the listed events will be for your CTD. The "Faulting Module" should point to the problem area.

Tell us what the Faulting Module is! That will point us in the direction of the proper error, aiding in troubleshooting.


Below is just an example of what you MIGHT see!

General Tab:
Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: This is what we need to Know!
Exception code: 0xc0000005
Fault offset: 0x0000ee3a
Faulting process id: 0x748
Faulting application start time: 0x01ce0253dc4b69d4
Faulting application path: R:\FSX\fsx.exe
Faulting module path: R:\FSX\window.dll
Report Id: 9caf77b4-6e50-11e2-8570-3085a99825d1

If there is not one listed:
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000,
you will need to do as previously noted


No Faulting Module? ->
Remove all of the add-ons, and test the sim. If it works OK, then reinstall them one at a time and test.
Be sure to test each thoroughly before moving on to the next

 

Share this post


Link to post
Share on other sites

Hi Josh,

 

I would, in your case, avoid making too many changes in your installation. Every further move could cause an even more difficult situation. If you have your windows set to create restore points, you might try to restore your system to a date before you encountered the problem (i.e. before you uninstalled couatle etc.). Restoring to an earlier state helped me several times already.

 

A method which also helped me some times is to keep the latest fsx.cfg, but only delete the application-specific entries (which you have to confirm again on the next start). Or just use an older fsx.cfg, which you might have backed up.

 

In addition, I recommend you to backup your whole drive from time to time (preferably including operating system). This helps you to always go back to a certain state by recovering the whole drive. An effective tool to do so Acronis True Image. It saved me numerous hours of installation already!

Share this post


Link to post
Share on other sites

 

 


Faulting module path: R:\FSX\window.dll

 

In the AVSIM CTD Guide, here is the possible solution:

 

Window.dll - The window.dll in the main FSX folder is used by FSX to take advantage of the capabilities of DirectX9. When using DirectX9, FSX calls on the window.dll functions to automatically minimize, maximize or restore the FSX window. For instance, the function 'WindowInit' is called to whether the window is currently minimized or maximized. The 'WindowFree' function can set the focus on the window and check whether the window has current focus. The dll has many more functions.  This error has been fixed by reinstalling video card drivers (WHQL – no BETA).

 

Best regards,

Share this post


Link to post
Share on other sites

I will continue looking for faulting module. I reinstalled my AMD drivers last night. They are up to date currently.

Share this post


Link to post
Share on other sites

In the AVSIM CTD Guide, here is the possible solution:

 

Window.dll - The window.dll in the main FSX folder is used by FSX to take advantage of the capabilities of DirectX9. When using DirectX9, FSX calls on the window.dll functions to automatically minimize, maximize or restore the FSX window. For instance, the function 'WindowInit' is called to whether the window is currently minimized or maximized. The 'WindowFree' function can set the focus on the window and check whether the window has current focus. The dll has many more functions.  This error has been fixed by reinstalling video card drivers (WHQL – no BETA).

 

Best regards,

Sorry Jim, This was just a "sample" of what he might see when looking for the actual "Faulting module"  It's the

 

"What we need to know"  that is important.

Share this post


Link to post
Share on other sites

Sorry Jim, This was just a "sample" of what he might see when looking for the actual "Faulting module"  It's the

 

"What we need to know"  that is important.

Oh, okay.  Didn't see that as an example.  He can also get valuable information by downloading AppCrashView as it provides more information about a crash than the Event Viewer (albeit the faulting module is a good clue and should show up in the Event Viewer too).  The AppCrashView link can be found on Page 1 of the AVSIM CTD Guide.

 

Best regards,

Share this post


Link to post
Share on other sites

I downloaded app crash viewer and this was what showed up

 

Version=1
EventType=AppHangB1
EventTime=130965999883692692
ReportType=3
Consent=1
UploadTime=130965999968917566
ReportIdentifier=4a52ce48-b4d5-11e5-b3ed-5404a64b79fe
IntegratorReportIdentifier=4a52ce49-b4d5-11e5-b3ed-5404a64b79fe
WOW64=1
Response.BucketId=471917438
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=Hang Signature
Sig[3].Value=d6e3
Sig[4].Name=Hang Type
Sig[4].Value=0
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
DynamicSig[22].Name=Additional Hang Signature 1
DynamicSig[22].Value=d6e380c96bd1020246eb6c57961843df
DynamicSig[23].Name=Additional Hang Signature 2
DynamicSig[23].Value=6da0
DynamicSig[24].Name=Additional Hang Signature 3
DynamicSig[24].Value=6da0391431969e9d82cd173555ec5f8d
DynamicSig[25].Name=Additional Hang Signature 4
DynamicSig[25].Value=d6e3
DynamicSig[26].Name=Additional Hang Signature 5
DynamicSig[26].Value=d6e380c96bd1020246eb6c57961843df
DynamicSig[27].Name=Additional Hang Signature 6
DynamicSig[27].Value=6da0
DynamicSig[28].Name=Additional Hang Signature 7
DynamicSig[28].Value=6da0391431969e9d82cd173555ec5f8d
UI[3]=Microsoft Flight Simulator® is not responding
UI[4]=If you close the program, you might lose information.
UI[5]=Close the program
UI[6]=Close the program
UI[7]=Close the program
LoadedModule[0]=F:\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\syswow64\USERENV.dll
LoadedModule[30]=C:\Windows\syswow64\profapi.dll
LoadedModule[31]=C:\Windows\system32\dwmapi.dll
LoadedModule[32]=C:\Windows\syswow64\SETUPAPI.dll
LoadedModule[33]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[34]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[35]=C:\Windows\syswow64\urlmon.dll
LoadedModule[36]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll
LoadedModule[37]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll
LoadedModule[38]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll
LoadedModule[39]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll
LoadedModule[40]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll
LoadedModule[41]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll
LoadedModule[42]=C:\Windows\syswow64\normaliz.DLL
LoadedModule[43]=C:\Windows\syswow64\iertutil.dll
LoadedModule[44]=C:\Windows\syswow64\WININET.dll
LoadedModule[45]=C:\Windows\system32\MPR.dll
LoadedModule[46]=C:\Windows\AppPatch\AcLayers.DLL
LoadedModule[47]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[48]=C:\Windows\AppPatch\AcSpecfc.DLL
LoadedModule[49]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18837_none_ec86b8d6858ec0bc\COMCTL32.dll
LoadedModule[50]=C:\Windows\system32\mscms.dll
LoadedModule[51]=C:\Windows\system32\DDRAW.dll
LoadedModule[52]=C:\Windows\system32\DCIMAN32.dll
LoadedModule[53]=C:\Windows\syswow64\COMDLG32.dll
LoadedModule[54]=C:\Windows\syswow64\IMM32.dll
LoadedModule[55]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[56]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[57]=C:\Windows\syswow64\NSI.dll
LoadedModule[58]=C:\Windows\system32\msi.dll
LoadedModule[59]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL
LoadedModule[60]=F:\FSX\language.dll
LoadedModule[61]=F:\FSX\API.DLL
LoadedModule[62]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll
LoadedModule[63]=F:\FSX\ablscpt.dll
LoadedModule[64]=F:\FSX\flight.dll
LoadedModule[65]=F:\FSX\ai_player.dll
LoadedModule[66]=F:\FSX\acontain.dll
LoadedModule[67]=F:\FSX\controls.dll
LoadedModule[68]=C:\Windows\system32\DINPUT8.dll
LoadedModule[69]=F:\FSX\fsui.dll
LoadedModule[70]=F:\FSX\atc.dll
LoadedModule[71]=F:\FSX\facilities.dll
LoadedModule[72]=F:\FSX\demo.dll
LoadedModule[73]=F:\FSX\main.dll
LoadedModule[74]=F:\FSX\fe.dll
LoadedModule[75]=F:\FSX\util.dll
LoadedModule[76]=F:\FSX\simprop.dll
LoadedModule[77]=F:\FSX\g2d.dll
LoadedModule[78]=C:\Windows\system32\d3dx9_34.dll
LoadedModule[79]=C:\Windows\system32\d3dx10_34.dll
LoadedModule[80]=C:\Windows\system32\d3d9.dll
LoadedModule[81]=C:\Windows\system32\d3d8thk.dll
LoadedModule[82]=F:\FSX\g3d.dll
LoadedModule[83]=F:\FSX\panels.dll
LoadedModule[84]=F:\FSX\multiplayer.dll
LoadedModule[85]=F:\FSX\ui.dll
LoadedModule[86]=F:\FSX\sound.dll
LoadedModule[87]=F:\FSX\sim1.dll
LoadedModule[88]=F:\FSX\simscheduler.dll
LoadedModule[89]=F:\FSX\visualfx.dll
LoadedModule[90]=F:\FSX\window.dll
LoadedModule[91]=F:\FSX\terrain.dll
LoadedModule[92]=F:\FSX\weather.dll
LoadedModule[93]=C:\Windows\system32\DSOUND.dll
LoadedModule[94]=C:\Windows\system32\POWRPROF.dll
LoadedModule[95]=F:\FSX\symmap.dll
LoadedModule[96]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.19061_none_72d6d48d86649709\gdiplus.dll
LoadedModule[97]=C:\Windows\system32\MSIMG32.dll
LoadedModule[98]=F:\FSX\xuipc.dll
LoadedModule[99]=F:\FSX\livingwater.dll
LoadedModule[100]=F:\FSX\fs-traffic.dll
LoadedModule[101]=F:\FSX\gps.dll
LoadedModule[102]=C:\Windows\system32\MSWSOCK.dll
LoadedModule[103]=C:\Windows\system32\SHFOLDER.dll
LoadedModule[104]=C:\PROGRA~2\Raptr\ltc_help32-106568.dll
LoadedModule[105]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[106]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[107]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[108]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[109]=C:\Windows\system32\rsaenh.dll
LoadedModule[110]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[111]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[112]=C:\Windows\system32\wbemcomn.dll
LoadedModule[113]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[114]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[115]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[116]=C:\Windows\system32\NTDSAPI.dll
LoadedModule[117]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL
LoadedModule[118]=C:\Windows\system32\dxgi.dll
LoadedModule[119]=C:\Windows\system32\d3d11.dll
LoadedModule[120]=C:\Windows\system32\aticfx32.dll
LoadedModule[121]=C:\Windows\system32\atiu9pag.dll
LoadedModule[122]=C:\Windows\system32\atiumdag.dll
LoadedModule[123]=C:\Windows\system32\atiumdva.dll
LoadedModule[124]=C:\Windows\system32\D3DCompiler_34.dll
LoadedModule[125]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[126]=C:\Windows\system32\d3d10_1.dll
LoadedModule[127]=C:\Windows\system32\d3d10_1core.dll
LoadedModule[128]=C:\Windows\SysWOW64\dxdiagn.dll
LoadedModule[129]=C:\Windows\SysWOW64\d3d10.dll
LoadedModule[130]=C:\Windows\SysWOW64\d3d10core.dll
LoadedModule[131]=C:\Windows\system32\winbrand.dll
LoadedModule[132]=C:\Windows\system32\WTSAPI32.DLL
LoadedModule[133]=C:\Windows\system32\WINSTA.dll
LoadedModule[134]=C:\Windows\SysWOW64\gameux.dll
LoadedModule[135]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18837_none_41e855142bd5705d\COMCTL32.dll
LoadedModule[136]=C:\Windows\SysWOW64\XmlLite.dll
LoadedModule[137]=C:\Windows\SysWOW64\wer.dll
LoadedModule[138]=C:\Windows\System32\Wpc.dll
LoadedModule[139]=C:\Windows\System32\wevtapi.dll
LoadedModule[140]=C:\Windows\System32\msxml6.dll
LoadedModule[141]=C:\Windows\System32\bcrypt.dll
LoadedModule[142]=C:\Windows\system32\SAMLIB.dll
LoadedModule[143]=C:\Windows\system32\netutils.dll
LoadedModule[144]=F:\FSX\uiautomationcore.dll
LoadedModule[145]=C:\Windows\system32\OLEACC.dll
LoadedModule[146]=C:\Windows\System32\MMDevApi.dll
LoadedModule[147]=C:\Windows\System32\PROPSYS.dll
LoadedModule[148]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[149]=C:\Windows\system32\RICHED20.DLL
LoadedModule[150]=C:\Windows\system32\HID.DLL
LoadedModule[151]=C:\Windows\system32\XInput9_1_0.dll
LoadedModule[152]=C:\Windows\system32\wdmaud.drv
LoadedModule[153]=C:\Windows\system32\ksuser.dll
LoadedModule[154]=C:\Windows\system32\AVRT.dll
LoadedModule[155]=C:\Windows\system32\msacm32.drv
LoadedModule[156]=C:\Windows\system32\midimap.dll
LoadedModule[157]=C:\Windows\system32\dinput.DLL
LoadedModule[158]=C:\Windows\System32\wship6.dll
LoadedModule[159]=C:\Windows\System32\wshtcpip.dll
LoadedModule[160]=F:\FSX\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow.dll
LoadedModule[161]=C:\Windows\system32\Secur32.dll
LoadedModule[162]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll
LoadedModule[163]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[164]=C:\Windows\system32\WINNSI.DLL
LoadedModule[165]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll
LoadedModule[166]=C:\Windows\system32\DNSAPI.dll
LoadedModule[167]=C:\Windows\system32\dhcpcsvc6.DLL
LoadedModule[168]=C:\Windows\System32\netprofm.dll
LoadedModule[169]=C:\Windows\System32\nlaapi.dll
LoadedModule[170]=C:\Windows\system32\rasadhlp.dll
LoadedModule[171]=C:\Windows\System32\npmproxy.dll
LoadedModule[172]=C:\Windows\system32\dhcpcsvc.DLL
LoadedModule[173]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[174]=F:\FSX\ORBX\FTX_NA\FTX_AA_KSFF\Scenery\ObjectFlow_KSFF.dll
LoadedModule[175]=F:\FSX\PMDG\DLLs\PMDG_HUD_interface.dll
LoadedModule[176]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[177]=C:\Windows\system32\MSVCR100.dll
LoadedModule[178]=F:\FSX\Modules\rxpGnsDriver.dll
LoadedModule[179]=F:\FSX\PMDG\DLLs\PMDG_Interface.dll
LoadedModule[180]=F:\FSX\Modules\LeonardoSH.dll
LoadedModule[181]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll
LoadedModule[182]=F:\FSX\FeelThere\Erj\E145XH.dll
LoadedModule[183]=F:\FSX\Aerosoft\Flight Recorder\AS-FlightRecorder.dll
LoadedModule[184]=F:\FSX\IRIS Platinum Series\F-15E Mudhen Driver\IRIS_F15E.dll
LoadedModule[185]=F:\FSX\Modules\VRS_TacPack\VRS_TacPack.dll
LoadedModule[186]=C:\Windows\system32\WINHTTP.dll
LoadedModule[187]=C:\Windows\system32\webio.dll
LoadedModule[188]=C:\Windows\system32\d3dx9_43.dll
LoadedModule[189]=F:\FSX\as_srv\as_btstrp.dll
LoadedModule[190]=C:\Windows\syswow64\PSAPI.DLL
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=DataRequest
State[1].Value=Bucket=471917438/nBucketTable=5/nResponse=1/n
FriendlyEventName=Stopped responding and was closed
ConsentKey=AppHangXProcB1
AppName=Microsoft Flight Simulator®
AppPath=F:\FSX\fsx.exe
ReportDescription=A problem caused this program to stop interacting with Windows.

Apparently my computer never created system restore points so that it is out of the question.

Share this post


Link to post
Share on other sites

I decided to read your OP and I immediately knew what was wrong.  Whenever FSX does not startup to the startup screen, there's a problem in your dll.xml.  You removed FSDT/FlightBeam stuff that uses couatl.  That was the wrong thing to do but you already did it.  Did you remove the AddonManager entry in the dll.xml?  And the couatl entry in the exe.xml?  That's probably why it is not firing up.  If you did (or if you didn't), I would reinstall just one product that uses couatl and the addon manager.  When you do this, the program will install the latest version of the Addon Manager and that is the fix.  Anytime FSX or P3D or FSX-SE does not startup to the startup screen, just download and reinstall the Addon Manager.  If that does not fix the problem (and it will), then there's a corrupted entry in the dll.xml.  The modules in the dll.xml and exe.xml are loaded during startup to the splash screen. 

 

I accidently found the the Addon Manager was the problem a couple of years ago when I could not get FSX to start up. I moved the dll.xml to a temp folder and everything started up.  I then decided to download and reinstall the latest Addon Manager and the problem went away immediately.  Hope this helps.

 

Best regards,

Share this post


Link to post
Share on other sites

here is my Dll

 

<?xml version="1.0" encoding="WINDOWS-1252"?>
 
-<SimBase.Document version="1,0" Type="Launch">
 
<Descr>Launch</Descr>
 
<Filename>dll.xml</Filename>
 
<Disabled>False</Disabled>
 
<Launch.ManualLoad>False</Launch.ManualLoad>
 
 
-<Launch.Addon>
 
<Name>ObjectFlow.dll</Name>
 
<Disabled>False</Disabled>
 
<ManualLoad>False</ManualLoad>
 
<Path>F:\FSX\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow.dll</Path>
 
</Launch.Addon>
 
 
-<Launch.Addon>
 
<Name>ObjectFlow_KSFF.dll</Name>
 
<Disabled>False</Disabled>
 
<ManualLoad>False</ManualLoad>
 
<Path>F:\FSX\ORBX\FTX_NA\FTX_AA_KSFF\Scenery\ObjectFlow_KSFF.dll</Path>
 
</Launch.Addon>
 
 
-<Launch.Addon>
 
<Name>Object Placement Tool</Name>
 
<Disabled>True</Disabled>
 
<ManualLoad>False</ManualLoad>
 
<Path>..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path>
 
</Launch.Addon>
 
 
-<Launch.Addon>
 
<Name>Traffic Toolbox</Name>
 
<Disabled>True</Disabled>
 
<ManualLoad>False</ManualLoad>
 
<Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path>
 
</Launch.Addon>
 
 
-<Launch.Addon>
 
<Name>Visual Effects Tool</Name>
 
<Disabled>True</Disabled>
 
<ManualLoad>False</ManualLoad>
 
<Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path>
 
</Launch.Addon>
 
 
-<Launch.Addon>
 
<Name>PMDG HUD interface</Name>
 
<Disabled>False</Disabled>
 
<Path>PMDG\DLLs\PMDG_HUD_interface.dll</Path>
 
<DllStartName>module_init</DllStartName>
 
<DllStopName>module_deinit</DllStopName>
 
</Launch.Addon>
 
 
-<Launch.Addon>
 
<Name>Reality XP GNS WAAS Hardware</Name>
 
<Disabled>False</Disabled>
 
<ManualLoad>False</ManualLoad>
 
<Path>Modules\rxpGnsDriver.dll</Path>
 
</Launch.Addon>
 
 
-<Launch.Addon>
 
<Name>Level-D Simulations</Name>
 
<Disabled>False</Disabled>
 
<ManualLoad>False</ManualLoad>
 
<Path>Modules\LVLD.dll</Path>
 
</Launch.Addon>
 
 
-<Launch.Addon>
 
<Name>PMDG Interface</Name>
 
<Disabled>False</Disabled>
 
<Path>PMDG\DLLs\PMDG_Interface.dll</Path>
 
<DllStartName>module_init</DllStartName>
 
<DllStopName>module_deinit</DllStopName>
 
</Launch.Addon>
 
 
-<Launch.Addon>
 
<Name>RAASPRO</Name>
 
<Disabled>False</Disabled>
 
<ManualLoad>False</ManualLoad>
 
<Path>.\RAASPRO\RAASPRO.dll</Path>
 
<DllStartName>module_init</DllStartName>
 
<DllStopName>module_deinit</DllStopName>
 
</Launch.Addon>
 
 
-<Launch.Addon>
 
<Name>Fly the Maddog</Name>
 
<Disabled>False</Disabled>
 
<ManualLoad>False</ManualLoad>
 
<Path>F:\FSX\Modules\LeonardoSH.dll</Path>
 
</Launch.Addon>
 
 
-<Launch.Addon>
 
<Name>FeelThere ERJX Helper</Name>
 
<Disabled>False</Disabled>
 
<Path>FeelThere\Erj\E145XH.dll</Path>
 
</Launch.Addon>
 
 
-<Launch.Addon>
 
<Name>Flight Recorder</Name>
 
<Disabled>False</Disabled>
 
<ManualLoad>False</ManualLoad>
 
<Path>Aerosoft\Flight Recorder\AS-FlightRecorder.dll</Path>
 
</Launch.Addon>
 
 
-<Launch.Addon>
 
<Name>IRIS F15E Weapons Manager</Name>
 
<Disabled>False</Disabled>
 
<ManualLoad>False</ManualLoad>
 
<Path>IRIS Platinum Series\F-15E Mudhen Driver\IRIS_F15E.dll</Path>
 
<DllStartName>module_init</DllStartName>
 
<DllStopName>module_deinit</DllStopName>
 
</Launch.Addon>
 
 
-<Launch.Addon>
 
<Name>FSUIPC 4</Name>
 
<Disabled>False</Disabled>
 
<Path>Modules\FSUIPC4.dll</Path>
 
</Launch.Addon>
 
 
-<Launch.Addon>
 
<Name>VRS_TacPack</Name>
 
<Disabled>False</Disabled>
 
<ManualLoad>False</ManualLoad>
 
<Path>Modules\VRS_TacPack\VRS_TacPack.dll</Path>
 
</Launch.Addon>
 
 
-<Launch.Addon>
 
<Name>as_connect</Name>
 
<Disabled>False</Disabled>
 
<Path>as_srv\as_btstrp.dll</Path>
 
</Launch.Addon>
 
</SimBase.Document>
 
my exe file
 
<?xml version="1.0" encoding="windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>exe.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Name>as_btstrp_config_manager</Name>
<Disabled>False</Disabled>
<Path>as_srv\as_btstrp_config_manager.exe</Path>
</Launch.Addon>
</SimBase.Document>
 
 
I did have FB KSFO and KDEN still installed after I had uninstalled my fsdreatmeam addons  which removed the couatl so I uninstalled them as well but still is not starting.  I saw no lines in either about addon manager..etc

I did notice the leveld and RAAS pro and I deleted them both so I removed the entries. I kept getting a RAAS.del error everything fsx started up so I just deleted it from entry thinking that might had fixed it but it still won't start.

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