Archived

This topic is now archived and is closed to further replies.

theskyisthelimit

Objectflow FTX modules causes crash to desktop when alt tabbing?

Recommended Posts

I have reason to believe that the modules related to objectflow from FTX are causing FSX to crash to the desktop if you alt tab or alt enter and switch to desktop.. If i remove these entries, I dont experience the crash.

 

The event viewer on my windows 8 x64 box show errors related to d3dl.dll however (fsx crash dumps).

I've tried running FSX both as "administrator" and in normal mode to no avail..

 

Has anyone else ran into this and knows what could be causing it to crash related to the ftx modules?

 

Thanks in advance

Share this post


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

The event viewer on my windows 8 x64 box show errors related to d3dl.dll however (fsx crash dumps).

 

The d3d9.dll in the FSX main folder is related to the ENB Series. If you have this addon installed, it's causing your crashes. It's a common crash and I removed it from my FSX a long time ago. Many have gotten it to work and have nothing but total praise for the addon. To get rid of the crashes, delete the d3d9.dll from the main FSX folder. Also delete enb.ini or you'll get even more crashes.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

The d3d9.dll in the FSX main folder is related to the ENB Series. If you have this addon installed, it's causing your crashes. It's a common crash and I removed it from my FSX a long time ago. Many have gotten it to work and have nothing but total praise for the addon. To get rid of the crashes, delete the d3d9.dll from the main FSX folder. Also delete enb.ini or you'll get even more crashes.

 

Best regards,

Jim

 

Thanks for that.. however, it didnt turn out to be this (so far).. I dont have that series.. i didnt have d3d9.dll in the main fsx folder.. the event log showed it in system32.. so i copied it to the fsx folder instead.. renabled the objectflow entries and thus far i can alt tab multiple times without fail (so far)..

Share this post


Link to post
Share on other sites

Good to hear you might have fixed the problem. Never heard of this type of 'repair'. The d3d9.dll is related to DirectX. You might want to run a dxdiag with your Run command and check to make sure there are no problems.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Good to hear you might have fixed the problem. Never heard of this type of 'repair'. The d3d9.dll is related to DirectX. You might want to run a dxdiag with your Run command and check to make sure there are no problems.

 

Best regards,

Jim

 

Actually my issue transformed itself..

 

While the original situation is fixed.. It seems that now if i directly load a saved flight off the harddrive then alt tab in and out it crashes with ntdll.dll error.. if i open that same file after first opening fsx no issues..

 

Trying to figure out why this may be currently.

Share this post


Link to post
Share on other sites

Most likely this is a memory issue. The ntdl.dll is related to that. Alt/tab takes up a lot of resources for any game, not just FSX. Instead of alt/tabbing, I would alt/enter to go from windowed mode to full screen and vice-versa. Remember FSX can only 'see' 4 GB's at the most. Any other memory you have installed is used for the system functions.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Most likely this is a memory issue. The ntdl.dll is related to that. Alt/tab takes up a lot of resources for any game, not just FSX. Instead of alt/tabbing, I would alt/enter to go from windowed mode to full screen and vice-versa. Remember FSX can only 'see' 4 GB's at the most. Any other memory you have installed is used for the system functions.

 

Best regards,

Jim

 

It does the same if you use alt-enter or alt-tab..

 

I'd think similar, except for the fact i can load the same saved flight after first launching fsx directly, then loading the same flight.. no issues alt tabbing or entering. Only when i launch from the file explorer, the flight, do i run into this issue.

Share this post


Link to post
Share on other sites

I think i solved my issue.. ok well not solved, but figured out what the cause was.

 

It turned out that the fsuipc entry in the dll.xml file was causing ctd when alt tab/alt enter, after having launched a saved flight directly from the hdd. I removed the addon entry and i can alt tab multiple times on multiple loads no issues. I'm running v4.8x of FSUIPC as of this moment.

Share this post


Link to post
Share on other sites

Flight One has a nice utility that checks your dll.xml and repairs it http://www.flight1.c...sp?page=library. You can also reorder the items within the dll.xml. Hard to believe the FSUIPC.dll entry caused the problem but at least it's fixed.

 

Best regards,

Jim

 

Thanks for that tool tip.. i tried the tool.. for some reason it only showed about 4 sections when there were quite a bit more. Havent dived in deep enough to figure out why just yet.

Share this post


Link to post
Share on other sites

You have to click on Extract Sections and select no to open the current dll.xml. If you say yes, it will just open the default dll.xml.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

I started having issues again.. so this time i wiped the machine and went clean install.. all to a separate partition/drive..

 

Unfortunately i'm back in the same boat..

 

So far installed:

UTX, GEX, Orbx Au areas and FTX PNW.. Anytime i do an alt enter it will immediately crash.. with ntdll.dll.. if i dont put d3d9.dll in the fsx directory it will crash with the d3d9.dll error.

 

I've tried disabling utx and taking out portions of the dll.xml (and tried the tool).. to me, once again, it seems that some part of the dll.xml is causing the crash, possibly the dll's related to au and objectflow (just a guess so far).

 

I've tried removing fsx.cfg and rebuilding it (same result).

I also reran the directx setup just to be safe, with no success on a fix.

 

Looking at the debug info, it seems to be related to an access violation.

 

**I can confirm that if i take out all objectflow entries from the dll.xml file, then it never seems to crash on an alt enter, thus far anyway

Share this post


Link to post
Share on other sites

to add to this, the d3d9.dll i'm running (via system32) is fairly new:

Version 6.2.9200.16384 dated 7/25/2012 (and the directx 10 dll's are present in the system32 directory, though as of now i'm not using dx10 with fsx, but i am with other games)

Share this post


Link to post
Share on other sites

Do you have the ENB Series mod installed? It places the d3d9.dll into the main fsx folder. For many people, this will create a crash 100% of the time with ntdl.dll as the faulting module. There is a d3d9.dll that comes with Windows and that should be left in the Windows/system32 folder. If you installed the ENB series, you will have to remove the d3d9.dll in the main fsx folder PLUS the enb.ini. If you just remove the d3d9.dll and leave the enb.ini in the folder, you will get a crash. It is highly unlikely any FTX texture, scenery, object caused your crash as this would be reported by everyone. I have almost every FTX scenery and no problems. If you have the enb series module, you'll need to search fsx to see if anyone can give you a link to the one that works. I removed it soon after getting it due to all the crashes.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Do you have the ENB Series mod installed? It places the d3d9.dll into the main fsx folder. For many people, this will create a crash 100% of the time with ntdl.dll as the faulting module. There is a d3d9.dll that comes with Windows and that should be left in the Windows/system32 folder. If you installed the ENB series, you will have to remove the d3d9.dll in the main fsx folder PLUS the enb.ini. If you just remove the d3d9.dll and leave the enb.ini in the folder, you will get a crash. It is highly unlikely any FTX texture, scenery, object caused your crash as this would be reported by everyone. I have almost every FTX scenery and no problems. If you have the enb series module, you'll need to search fsx to see if anyone can give you a link to the one that works. I removed it soon after getting it due to all the crashes.

 

Best regards,

Jim

 

Unfortunately i dont have that mod (though i had found others with that issue with enb in my searches for poss. solutions).. at this point i dont have d3d9.dll in the fsx directory.. so it will crash on d3d9.dll.. if d3d9.dll is put in there, then yeah i end up with ntdll.dll crashes as the source.

Share this post


Link to post
Share on other sites

so it will crash on d3d9.dll.. if d3d9.dll is put in there

 

There should be no d3d9.dll in your fsx folder and I apologize as we went over this earlier in this discussion. Been busy. Forgot what we had done.

 

**I can confirm that if i take out all objectflow entries from the dll.xml file, then it never seems to crash on an alt enter, thus far anyway

 

Have you tried uninstalling the objectflow related sceneries then reinstalling? Your dll.xml could be corrupted. If you go into FTX Central and disable FTX sceneries and go to the default, does the crash still occur?

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

There should be no d3d9.dll in your fsx folder and I apologize as we went over this earlier in this discussion. Been busy. Forgot what we had done.

 

 

 

Have you tried uninstalling the objectflow related sceneries then reinstalling? Your dll.xml could be corrupted. If you go into FTX Central and disable FTX sceneries and go to the default, does the crash still occur?

 

Best regards,

Jim

 

Yeah, I dont have the d3d9.dll in there, let me rephrase, because before the way i worded it sounded confusing i think:

 

if d3d9.dll is in fsx i get crashes related to ntdll.dll.. if d3d9.dll is removed and only in sys32, then the crash is related to d3d9.dll.

 

So far, all i've done is remove the entries from dll.xml for objectflow (all is fine then).. I ran the dll.xml tool check, it said it appeared fine on the check button anyway.

 

As far as "uninstalling orbx sceneries", there doesnt appear to be an easy way to uninstall.. no entries in add/remove.. but what i have done is gone into ftx central and set it to default mode, this mode crashes as well.

 

I could try deleting the existing dll.xml and create another one pasting in one objectflow entry to see what that does.

 

No change on deleting the xml and recreating, unfortunately.

Share this post


Link to post
Share on other sites

Here are my dll.xml entries. They should be the same as yours as FTX will not allow any of their sceneries to be moved to another HDD.

 

<Launch.Addon>

<Name>ObjectFlow_W16.dll</Name>

<Disabled>False</Disabled>

<ManualLoad>False</ManualLoad>

<Path>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ORBX\FTX_NA\FTX_AA_W16\scenery\ObjectFlow_W16.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>ObjectFlow_KJAC.dll</Name>

<Disabled>False</Disabled>

<ManualLoad>False</ManualLoad>

<Path>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ORBX\FTX_NA\FTX_AA_KJAC\Scenery\ObjectFlow_KJAC.dll</Path>

</Launch.Addon>

 

If FSX is still crashing even with ftx disabled and the default enabled, then it cannot be a FTX problem. There's something else. Look in your main fsx folder and look for a .ini (initiator) type file. It sounds like something is calling for the d3d9.dll and it cannot find it. The only way I know of that could cause this to happen is if you still have the enb.ini in the fsx folder.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Here are my dll.xml entries. They should be the same as yours as FTX will not allow any of their sceneries to be moved to another HDD.

 

<Launch.Addon>

<Name>ObjectFlow_W16.dll</Name>

<Disabled>False</Disabled>

<ManualLoad>False</ManualLoad>

<Path>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ORBX\FTX_NA\FTX_AA_W16\scenery\ObjectFlow_W16.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>ObjectFlow_KJAC.dll</Name>

<Disabled>False</Disabled>

<ManualLoad>False</ManualLoad>

<Path>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ORBX\FTX_NA\FTX_AA_KJAC\Scenery\ObjectFlow_KJAC.dll</Path>

</Launch.Addon>

 

If FSX is still crashing even with ftx disabled and the default enabled, then it cannot be a FTX problem. There's something else. Look in your main fsx folder and look for a .ini (initiator) type file. It sounds like something is calling for the d3d9.dll and it cannot find it. The only way I know of that could cause this to happen is if you still have the enb.ini in the fsx folder.

 

Best regards,

Jim

 

Ftx cant go on another drive or just may not work right?

 

I installed fsx to my O partion.. so everything is O:\program files (x86) etc..

So by default when i installed ftx it went to O.. my entries in my dll.xml point to O:\path

 

I dont have enb so i doubt its enb ini related, though ill poke around in the folder to look for others.

 

 

I just assumed since i can remove the ftx entries and everything is fine, that it must be ftx related.

 

Ftx cant go on another drive or just may not work right?

 

I installed fsx to my O partion.. so everything is O:\program files (x86) etc..

So by default when i installed ftx it went to O.. my entries in my dll.xml point to O:\path

 

I dont have enb so i doubt its enb ini related, though ill poke around in the folder to look for others.

 

 

I just assumed since i can remove the ftx entries and everything is fine, that it must be ftx related.

 

Only 1 ini in the fsx directory.. a 2007 mpc file.. the only other change to the fsx folder i did, was moving the uiautomationcore.dll file into here.

Share this post


Link to post
Share on other sites

Ftx cant go on another drive or just may not work right?

 

No it just has to be installed on the same drive as FSX so you are okay. Have you tried checking for corrupt system files by running sfc /scannow? Perhaps that d3d9.dll is corrupt. Are there any other dll.xml files in the folder (that were renamed?). Some of the programs I install back up my dll.xml before they modify the original. You might try renaming the current one to dll.xml.orig then rename one of the backups to dll.xml and see if that fixes things.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

No it just has to be installed on the same drive as FSX so you are okay. Have you tried checking for corrupt system files by running sfc /scannow? Perhaps that d3d9.dll is corrupt. Are there any other dll.xml files in the folder (that were renamed?). Some of the programs I install back up my dll.xml before they modify the original. You might try renaming the current one to dll.xml.orig then rename one of the backups to dll.xml and see if that fixes things.

 

Best regards,

 

i havent tried sfc but i may.. i tried the original dll.xml and also deleting it and letting orbx recreate it, no luck either.

 

I may end up sticking in another harddrive for the OS and start clean just for a test, one thing at a time, till i find something that breaks it.

 

 

Jim

Share this post


Link to post
Share on other sites

i tried the original dll.xml and also deleting it and letting orbx recreate it, no luck either.

 

You cannot delete the dll.xml and let it rebuild. It won't do that. Only the FSX.cfg will rebuild if you delete it.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

You cannot delete the dll.xml and let it rebuild. It won't do that. Only the FSX.cfg will rebuild if you delete it.

 

Best regards,

Jim

 

Strange, at least in my case it did recreate it.

Share this post


Link to post
Share on other sites

I just renamed my dll.xml. Ran FSX and fsx ran great but no new dll.xml was rebuilt. It's impossible as the entries are installed with each addon installation program and FSX has no way of knowing what you installed when you start it up. Think this must be your problem. On a personal note, deleting the dll.xml got rid of the StackHash error I have been getting everytime I shut down FSX. The problem must be somewhere in the dll.xml.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

I just renamed my dll.xml. Ran FSX and fsx ran great but no new dll.xml was rebuilt. It's impossible as the entries are installed with each addon installation program and FSX has no way of knowing what you installed when you start it up. Think this must be your problem. On a personal note, deleting the dll.xml got rid of the StackHash error I have been getting everytime I shut down FSX. The problem must be somewhere in the dll.xml.

 

Best regards,

Jim

 

Ahh... but by rebuild, i actually meant when i ran an airport setup from orbx.. it recreated the base dll.xml file.. not fsx itself.

Share this post


Link to post
Share on other sites