gavoon1 19 Posted January 31, 2016 Report Share Posted January 31, 2016 So after to talking to you guys I did a flight in the airbus and everything was fine. Today I downloaded ENB SERIES linked from cedarjet youtubes chanel. Fsx loaded up fine the when I clicked fly now: the loading doesnt even start it just crashes... I uninstalled ENB.. and looked through my FSX root folder and found 10 crash files... FSX_62615_crash....mdmp etc.. Any ideas? Gavin Link to post Share on other sites
wain 879 Posted February 1, 2016 Report Share Posted February 1, 2016 Was everything fine after you uninstalled ENB? Link to post Share on other sites
The Ben 0 Posted February 1, 2016 Report Share Posted February 1, 2016 That happens when you have game boosters installed like "Razer Cortex". Make sure you uninstall them first. Link to post Share on other sites
gavoon1 19 Posted February 1, 2016 Author Report Share Posted February 1, 2016 Nope it doesn't work still. I uninstalled ENB. It still crashes once I click fly now it just goes black and the white loading box never starts loading after 4 seconds it crashes. Should I re-install FSX. One guy to me to delete the logbook.bin in my FSX folder. ( cant find that ) gAVIN Link to post Share on other sites
The Ben 0 Posted February 1, 2016 Report Share Posted February 1, 2016 Look for "dxgi.dll" or "d3d9.dll" in your fsx folder, if you find it, delete it. Link to post Share on other sites
MyPC8MyBrain 273 Posted February 1, 2016 Report Share Posted February 1, 2016 can you post the content of your dll.xml and exe.xml please? Link to post Share on other sites
gavoon1 19 Posted February 2, 2016 Author Report Share Posted February 2, 2016 1. EXE: <?xml version="1.0" encoding="WINDOWS-1252"?> -<SimBase.Document version="1,0" Type="Launch"> <Descr>Launch</Descr> <Filename>EXE.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>True</Launch.ManualLoad> -<Launch.Addon> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Name>Addon Application</Name> <Path>C:\MyPath\Addon.exe</Path> <CommandLine/> <NewConsole>True</NewConsole> </Launch.Addon> </SimBase.Document> ( 1. is from FSX/SDK/ Core utilities kit/sim connect SDK/ config/ 2. EXE: <?xml version="1.0" encoding="WINDOWS-1252"?> Fsx/ config data/ App data/ 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>Visual Effects Tool</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path> </Launch.Addon> </SimBase.Document> 2.<?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>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> </SimBase.Document Does that mean anything to you? Cause If I re-intall FSX SE that should fix the issue.. But I will have to re-intsall all the Addons. Any Ideas? 1 Link to post Share on other sites
stu7708 244 Posted February 2, 2016 Report Share Posted February 2, 2016 I don't think those will tell us anything Gavin. The versions of dll.xml and exe.xml we need to look at are located in your user profile. Look in this folder. C:\Users\YOUR USERNAME\AppData\Roaming\Microsoft\FSX or possibly FSX-SE at the end. Also, it could help to see if there are any error reports in the Windows Application Log connected to the crash. Not 100% sure on how to get to those in Windows 8 though.. in Win 7 and Win 10 they are accessed by Right Clicking on Computer in the Explorer and clicking Manage. From there it's going to be a bit of a shot in the dark for me as I'm running a Swedish version of Windows, so I'm not up to speed on the English vocabulary. My guess is that it is Logs - Windows Logs - Applications. See the image below. Step one is to navigate to the appropriate log using the tool structure to the left, use the icons as a guide since this one is in swedish. I'm pretty sure the order is the same on an Windows installation using the English Language Pack. Once the log file for Applications is loaded scroll through the list for any posts with a red circle and the text Error in the first column, or check for "Application Error" in the Source column. In the first row of text in the description you'll find the application that was the source of the error, and if you are lucky there will also be a reference to a .dll-file associated with the crash. 1 Link to post Share on other sites
MyPC8MyBrain 273 Posted February 2, 2016 Report Share Posted February 2, 2016 Thank you Mikael, FYI accessing the log on 8 is the same as on 7 or 10 anywhere you see "my computer" icon; right click and select manage, Link to post Share on other sites
stu7708 244 Posted February 2, 2016 Report Share Posted February 2, 2016 Good to know Chris! And I should possibly also have added that the "AppData"-folder is hidden by default, so to be able to see that you will need to set windows to show hidden folders and files. Could anyone with an English installation of Windows possibly help with how to enable that in case Gavin needs it! 1 Link to post Share on other sites
gavoon1 19 Posted February 2, 2016 Author Report Share Posted February 2, 2016 Ahaha You guys are probably laughing very hard and righlty so! <?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>Addon Manager</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>bglmanx.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>VistaMare Core</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>VistaMare\ViMaCoreX.dll</Path> </Launch.Addon> -<Launch.Addon> <Name>FS Recorder</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\Program Files (x86)\FS Recorder for FSX\FSRecorder_FSX.dll</Path> </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>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> </SimBase.Document> This DLL. xml document is in my APPDATA FSX SE folder. <?xml version="1.0" encoding="WINDOWS-1252"?> -<SimBase.Document version="1,0" Type="Launch"> <Descr>Launch</Descr> <Filename>EXE.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> -<Launch.Addon> <Name>Couatl</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>fsdreamteam\couatl\couatl.exe</Path> </Launch.Addon> -<Launch.Addon> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Name>Addon Application</Name> <Path>C:\MyPath\Addon.exe</Path> <CommandLine/> <NewConsole>True</NewConsole> </Launch.Addon> -<Launch.Addon> <Name>EZdok camera addon</Name> <Disabled>False</Disabled> <Path>C:\Program Files (x86)\EZCA\EZCA.exe</Path> </Launch.Addon> </SimBase.Document> Thats my addon launch that wont help.... Faulting application name: EZCA.exe, version: 1.1.8.6, time stamp: 0x2a425e19Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000Exception code: 0xc0000005Fault offset: 0xff080000Faulting process id: 0xf44Faulting application start time: 0x01d14358cec93884Faulting application path: C:\Program Files (x86)\EZCA\EZCA.exeFaulting module path: unknownReport Id: 1429a4bc-af4c-11e5-8318-f0795965aac0Faulting package full name: EZDOK cant be the issue cause even when I disable ezdok it still crashes Is this what you want? Gavin 1 Link to post Share on other sites
MyPC8MyBrain 273 Posted February 2, 2016 Report Share Posted February 2, 2016 we're loughing with you here's your EXE.XML code, replace your old with this <?xml version="1.0" encoding="WINDOWS-1252"?> <SimBase.Document version="1,0" Type="Launch"> <Descr>Launch</Descr> <Filename>EXE.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>Couatl</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>fsdreamteam\couatl\couatl.exe</Path> </Launch.Addon> <Launch.Addon> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Name>Addon Application</Name> <Path>C:\MyPath\Addon.exe</Path> <CommandLine/> <NewConsole>True</NewConsole> </Launch.Addon> </SimBase.Document> to compare; below is your old EXE.XML,i stripped out "EZdok camera addon" entry <?xml version="1.0" encoding="WINDOWS-1252"?> <SimBase.Document version="1,0" Type="Launch"> <Descr>Launch</Descr> <Filename>EXE.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>Couatl</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>fsdreamteam\couatl\couatl.exe</Path> </Launch.Addon> <Launch.Addon> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Name>Addon Application</Name> <Path>C:\MyPath\Addon.exe</Path> <CommandLine/> <NewConsole>True</NewConsole> </Launch.Addon> <Launch.Addon> <Name>EZdok camera addon</Name> <Disabled>False</Disabled> <Path>C:\Program Files (x86)\EZCA\EZCA.exe</Path> </Launch.Addon> </SimBase.Document> Link to post Share on other sites
gavoon1 19 Posted February 2, 2016 Author Report Share Posted February 2, 2016 So replace the tope thing with my old DLL. XML in my APPDATA/ FSX SE folder? I just want to make sure I am doing the right thing. Gavin Link to post Share on other sites
stu7708 244 Posted February 3, 2016 Report Share Posted February 3, 2016 Since there is a mention of EZCA.exe in your log-files that's a good place to start, although I think Chris had a slight brain fart.. Just replace every mention of DLL.xml in his last post with EXE.xml Also remember to make a backup of your original exe.xml before you start to have something to roll back on in case of failure... Also, do you know what this bit in the EXE.xml is referring to? <Launch.Addon> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Name>Addon Application</Name> <Path>C:\MyPath\Addon.exe</Path> <CommandLine/> <NewConsole>True</NewConsole> </Launch.Addon> Never seen that one before. 1 Link to post Share on other sites
MyPC8MyBrain 273 Posted February 3, 2016 Report Share Posted February 3, 2016 I think Chris had a slight brain fart.. Oops... two tiny mistakes in the description above the code fixed; the code snippet itself was/is fine , i wondering about that strange entry too; since its disabled it’s not likely to effecting this condition, Link to post Share on other sites
stu7708 244 Posted February 3, 2016 Report Share Posted February 3, 2016 I think Chris had a slight brain fart.. Oops... two tiny mistakes in the description above the code fixed; the code snippet itself was/is fine , i wondering about that strange entry too; since its disabled it’s not likely to effecting this condition, Ahh.. missed that the Disabled tag was set to TRUE 1 Link to post Share on other sites
gavoon1 19 Posted February 4, 2016 Author Report Share Posted February 4, 2016 What this going to do? Is this: <?xml version="1.0" encoding="WINDOWS-1252"?><SimBase.Document version="1,0" Type="Launch"><Descr>Launch</Descr><Filename>EXE.xml</Filename><Disabled>False</Disabled><Launch.ManualLoad>False</Launch.ManualLoad><Launch.Addon><Name>Couatl</Name><Disabled>False</Disabled><ManualLoad>False</ManualLoad><Path>fsdreamteam\couatl\couatl.exe</Path></Launch.Addon><Launch.Addon><Disabled>True</Disabled><ManualLoad>False</ManualLoad><Name>Addon Application</Name><Path>C:\MyPath\Addon.exe</Path><CommandLine/><NewConsole>True</NewConsole></Launch.Addon></SimBase.Document> I put this in my EXE.XML or DLL.XML. I will try this ( if its right ) But lets say I decide to re-install FSX SE tmr, and that doesnt work does that mean my drivers need to be updated cause last time I checked ( not long ago ) they where fine. But if the re-installation doesnt work what could I do. I just want to know my options in that case. I would un-install before re-installing FSX SE through steam obviously and then check to see if it still crashes when I click FLY NOW". If it works I will install my addons and make sure its a clean installation. I hope to get flying for the weekend, If its not fixed by then I dont know what to do. Thanks- gavin Link to post Share on other sites
MyPC8MyBrain 273 Posted February 4, 2016 Report Share Posted February 4, 2016 replace EXE.XML content; save and run FSX, Link to post Share on other sites
gavoon1 19 Posted February 4, 2016 Author Report Share Posted February 4, 2016 That didnt work... I will try plan b re-install FSX. Thanks agin Gavin. Ps let you know if It doesnt work, we can further troobleshoot. I wont open a new topic Gavin Link to post Share on other sites
gavoon1 19 Posted February 5, 2016 Author Report Share Posted February 5, 2016 RESOLVED for now.. I re-installed it everything is working except I can use my mouse in ezdok to look around.Worked in past, but that now abig deal. " Less tweekin', more flyin" Gavin Link to post Share on other sites
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now