Jim, all the .dds files are in the FSX root texture folder and shown as "SUCCESS"!

 

All the .BMP files cannot be found. I have undertaken a full search of programs and files and they are not there.

 

Can I get the BMP files from anywhere, as I assume this is what is causing the CTD?

 

Thanks

 

Sauviat

All the .BMP files cannot be found. I have undertaken a full search of programs and files and they are not there.

There are not on my system either Sauviat and I have FSX/Acceleration installed. I doubt they were ever installed. Some program though is calling for them to render and they cannot be found. If they were the causes of your crashes, you would only see one "Name Not Found" entry. I definitely do not think these are your problems as you can see the files are replicated by .dds files which replaced .bmp files used for FS9. I would say you might have found your problem if the textures were from the scenery in NY State but these are ocean waves.

 

When I found my cause of my crash, I sat in front of my computer with pencil and paper in hand and whenever I saw a glitch, a long pause, or a stutter, something I thought was abnormal, I wrote down the time shown on my system. Then I went to that minute in the process monitor log and looked at everything being loaded (thousands and thousands of entries) but I was lucky and most of the entries for that minute were from MyTrafficX loading flight plans. I also wanted to know what was loading whenever I got some nasty pauses or long stutters. Never pinned those down but my FSX runs great.

 

If you do not see anything in the minute of the crash (and just that minute), then you should disable the scenery that might be causing it.  I would also suggest just moving your scenery.cfg over to a temporary folder, running FSX again and the default scenery will be loaded.  If the crashes continue then it is not caused by any scenery and you have an installation problem.

 

Best regards,

Moved the Scenery.cfg from the root folder to a temporary folder. However, FSX will not start, as it says the scenery.cfg is missing!!!

 

What about the one in the Roaming folder?

 

Thanks

 

Sauviat

Unchecked everything in Add-on scenery which I installed over a long time that may be associated with the NY area.

 

Ran Process Monitor and at the CTD "NAME COLLISION" came up on this one within the last minute at the end:

 

C:\Users\Martin Parr\AppData\Local\Microsoft\FSX\Shaders\General

 

Thanks

 

Sauviat

 

 

Moved the Scenery.cfg from the root folder to a temporary folder. However, FSX will not start, as it says the scenery.cfg is missing!!!

 

The only way that could happen is if you deleted or moved the one in the same folder as where your fsx.cfg is located.  That one cannot be deleted or moved.  The one located in C:/Program Files/Microsoft/FSX is the working copy of the scenery.cfg.  If you move it out of there, then the one in your Roaming file will be copied to the Program Files location. You can also go into the Scenery Library and disable all of them or download SceneryConfigEditor and run it before you start up fsx.

 

 

 

an Process Monitor and at the CTD "NAME COLLISION" came up on this one within the last minute at the end:
C:\Users\Martin Parr\AppData\Local\Microsoft\FSX\Shaders\General

 

The shaders folder can be deleted if you want.  It is only a temporary file and is rebuilt once you restart FSX.  If there's a Shaders10 (for DX10), that folder can be deleted too and it will be recreated if and when you turn on DX10 Preview.

 

Best regards,

FSX is installed in C:FSX with Scenery.cfg in the root and not in program files.

 

In AppData/Roaming is the FSX.CFG and Scenery.cfg.

 

The one placed in a temp folder was the one from the root directory.

 

I have just placed the scenery.cfg which was in the appdata/roaming folder in a temporary and the same CTD at 100%.

 

Having tried all the options something is amiss!

 

Thanks

 

Sauviat

 

I already have Scenery Config Editor.

Edited February 27, 201511 yr by sauviat

FSX is installed in C:FSX with Scenery.cfg in the root and not in program files.

The scenery.cfg in the hidden appdata/roaming folder with the fsx.cfg is not a working scenery.cfg. It cannot be modified in any way. When fsx was first released several years ago, we asked one of the developers about it and they told us to leave it and do not modify it in any way.  So, if you modified it or changed the date it was created, this is probably why fsx will not start up when you remove the working scenery.cfg (which must be located in the Program Files/Microsoft/FSX folder.  That location cannot be modified.  So now we are slowly finding out why you are having so many crashes.

 

The SceneryConfigEditor will look for the working scenery.cfg when you first load it up.  If the scenery.cfg is not in the correct folder, it will not find it automatically.  You would have to go to the menu and locate it yourself each time.

 

Best regards,

Sherlock Young is on the case!

 

This is what I have found, thus far.

 

Scenery Config Editor has in the Text Editor the list of Areas, etc. I.e. [General], [Arear.001], [Area.002] through to [Area.251].

 

The Properties give the File name and tree as "C:\ProgramData\Microsoft\FSX\NewScenery.cfg" In that folder the file is dated 27/02/2015 22.52, which is the last time I tried to run FSX. However, also in that folder is OldScenery.cfg with the same date but 20.06 and scenery.cfg with the same date and time as OldScenery.cfg.

 

I have now placed the abovementioned scenery.cfg into a Temporary Folder and loading up FSX....Ah, Failed to open file C:\ProgramData\Microsoft\FSX\Scenery!

 

The only difference I have noticed so far is that you say Program Files\Microsoft\FSX and my actual installation, by using the C;\FSX installation route states ProgramData\Microsoft\FSX.

 

I now placed NewScenery.cfg into the Temporary folder and again started up FSX , but it failed to start. The Scenery Config Editor properties now shows "C:\ProgramData\Microsoft\FSX\Scenery.cfg". In the C:\ProgramData\Microsoft\FSX folder it shows scenery.cfg 27/02/2015 20.06 and OldScenery.cfg 28/02/2015 10.53.

 

Have now closed down and reopened the Scenery Config Editor and now there is another NewScenery.cfg in the C:\ProgramData\Microsoft\FSX.

 

Restarting FSX and see that NewScenery.cfg has disappeared from C:\ProgramData\Microsoft\FSX. FSX failed to start. Both OldScenery.cfg and scenery.cfg have the same date and time.

 

I note that there is also a Scenery.cfg.bak in the C:\ProgramData\Microsoft\FSX folder. Now, I have never used a .bak as I use the protocol .old if I make any changes, etc, This Scenery.cfg.bak is dated 13/09/2014 13.55. As I keep in date order any download for FS9/FSX by scenery, aircraft, helicopter I see there was a download called CYYJ_606 on  13/09/2014 13.57. However, this scenery is for CYYJ on the other side of North America and would not surely interfere with NY!

 

Ok I am now placing the scenery.cfg in the temporary folder and remove the extension .bak from the back up. Again, having attempted to start up FSX, it failed again!

 

Are there any other options?

 

Thanks

 

Sauviat

I disabled CYYJ in add-on scenery, but FSX continued to fail in the NY area.

 

I have now started at Martha's Vineyard and started up Process Monitor. Heading in the general direction towards NY City and about 15 miles east of KBID FSX failed.

 

From the time of failure working backwards, the first result is PATH NOT FOUND for C:\Scenery\Global\Texture and the .CAB extension. There was one other occurrence within the same minute prior to these two.

 

Thanks

 

Sauviat

Have now closed down and reopened the Scenery Config Editor and now there is another NewScenery.cfg in the C:\ProgramData\Microsoft\FSX.

You need to get rid of NewScenery.cfg (and oldscenery.cfg). Open up SceneryConfigEditor and click on Edit and then Preferences. Uncheck "Follow the New Scenery Convention". This way, your scenery.cfg will be the only thingy SceneryConfigEditor sees and edits. I was using the NewScenery convention too for some time and finally realized, the newscenery.cfg was being edited and not the scenery.cfg. It's all very confusing as you have indicated in your last post.

 

I have never heard of FSX not starting up because of a problem with the scenery.cfg. If it is not the the ProgramData folder, FSX will copy the one in the folder with fsx.cfg to the ProgramData folder and you'll have the basic default scenery.cfg again. If it is corrupted, you'll see error messages like "Area115 cannot be found" but, if you hit OK, it will continue on and fsx will start up. So, there is something else that is stopping FSX to start up. As indicated in the AVSIM CTD Guide one of the reasons why FSX will not start up is caused by a FSDT or FlightBeam airport. All you have to do is go on line to FSDT and download the latest AddonManager and run it again. That will fix that problem. If it still does not start up, then there is something else but it cannot be caused by the scenery.cfg. If you move the scenery.cfg to a temporary directory, it should be rebuilt by the file in the Roaming directory (if it is still there). If there is no scenery.cfg in your Roaming directory (in the same folder with fsx.cfg), then the scenery.cfg cannot be rebuilt and fsx will probably not start. I have never tried that as I have never heard of anyone deleting the scenery.cfg in the Roaming directory.

 

OldScenery.cfg is named by a scenery program they installed. They modified your scenery.cfg during installation and made a backup. Same goes with Scenery.cfg.bak. These files, as well as NewScenery.cfg, can safely be deleted.

 

The CYYJ scenery should not interfere with any of your NY State scenery. You are correct.

 

If there is a problem with your scenery.cfg, it will be shown in the SceneryConfigEditor but, again, an error will not prevent fsx from starting up.

 

Have you moved your fsx.cfg to a temporary folder and let the fsx.cfg rebuild? The problem could be in your fsx.cfg. For instance, if you have the tweak BufferPools (you know, the one that causes instability in many systems), it could prevent your computer from starting up if the parameters are incorrect. They say that rebuilding your fsx.cfg is the same as reinstalling FSX. It fixes so many problems because people like to tweak and they screw up the tweaks.

 

Best regards,

From the time of failure working backwards, the first result is PATH NOT FOUND for C:\Scenery\Global\Texture and the .CAB extension. There was one other occurrence within the same minute prior to these two.

I probably should not have told you about the Process Monitor as PATH NOT FOUND is a very common error in the report and means nothing. It's what is loading at the exact time of the crash is that is important. If you ran process monitor normally and it showed every process happening on your computer, you would see thousands and thousands of PATH NOT FOUND. All it means is that the process could not find the path in the registry which is very, very common. A lot of programs do not put the path into the registry but the program code tells the program to look in C:/scenery/world/scenery and you will find the texture or the .cab that needs to be rendered right now.  The process monitor also looks in the system registry for the entry too as that usually is faster.  This is how software programs like FSDT airports can find the location of FSX.  They look in the registry first.

 

We need to get back to your OP.  In your OP the crash report says the ntdll.dll caused the crash.  AVSIM did the leg work for you and searched the Internet, all of the flight simulation websites, every post in AVSIM looking for reasons why the ntdll.dll shows up as the faulting module in a crash report.  Here is what it says on Page 14:

 

NTDLL.dll – Several possibilities as follows:

• Quote from Microsoft Techs – “Heap metadata can become corrupted and it has been identified by Microsoft as one of the most common causes of application failures.  When an application crash shows the faulting module as ntdll.dll along with the Memory Access Violation (0xc0000005), then Windows places the application on a watch list and, if the application crashes at least four times or more in an hour, the fault tolerant heap service will configure the application to use the fault tolerant heap service in the future” (Source - Chapter 10, Memory Management, Windows Internals, Part 2: Covering Windows Server 2008 R2 and Windows 7 by Mark E. Russinovich, David A Solomon, and Alex Ionescu).  The service is part of the Security Center service so you need to make sure this service is turned on.  If the ntdll.dll is placed on the watch list, this information will be shown in the Event Viewer (Admin Events).  See also Increase Heap Limitation in the Actions to Take to Prevent Crashes section of this guide.
• MyTrafficX version 5.4c is installed. It is believed to be caused by an AI scheduling programming error. Go back to the 5.4b version or make sure no external AI program schedule is activated (i.e., the 2012 or 2013 Schedules on the developers website).  The default schedule appears to be okay for most. Check the developers support forums for updated information and possible bug fixes.
• System overheats or you have wrong timings/voltages set for your installed RAM or CPU voltage. You might be able to fix by returning your BIOS to Optimized Defaults or lowering your overclock by one point from say, 4.4GHz to 4.3GHz.
• Remove the UIAutomationcore.dll from the main FSX folder, if installed.
• Check your dll.xml for duplicate entries or any corruption.  Some have fixed the NTDLL.dll CTD by removing duplicate entries and/or old software entries where the software is no longer on your system.
• Disable User Access Controls (UAC) (see the section above for more information).
• Update hardware drivers for your computer (especially on new computer systems) (see Driver Update information in this guide).

I remember clearly the one time I got this frustrating ntdll.dll error it took some time to find a solution until I looked in the dll.xml and saw duplicate PMDG entries and entries for software I had uninstalled some time ago.  I removed them and immediately the ntdll.dll errors went away.  Go figure!!  Now, don't get centered on this as the cause of your problem, it is just one of the possibilities.  This is why I recommended in the CTD Guide that one should move their dll.xml, their exe.xml, their fsx.cfg, their scenery.cfg all over to a temporary directory and restart fsx.  You are now back to the default configuration.  Then you should move them back one at a time until the error pops up again.  In your case I would just move the scenery.cfg back to its proper folder.  Then you will not have a dll.xml or exe.xml.  Does the crash still occur?  If not, then there is an entry in the dll.xml or exe.xml that is corrupted (the dll.xml and exe.xml are not rebuilt if removed).  A corrupted dll.xml is a cause for fsx not to start up.  Here's more information about the dll.xml and how to troubleshoot - http://support.precisionmanuals.com/kb/a92/dll_xml-information-and-troubleshooting.aspx.

 

Hope this helps.  I wish there was a solution like change the following parameter in FSX to 10 and your problems would all be fixed but there is no simple solution to ntdll.dll errors (except that hundreds here in this forum have been successful by removing the uiautomationcore.dll from their main fsx folder.  I think they put in a 64 bit version and it should be a 32 bit version or they are putting in the latest version found.  Not a good idea).

 

Best regards,

I have done these actions:

 

" Uncheck "Follow the New Scenery Convention"".

 

"OldScenery.cfg is named by a scenery program they installed. They modified your scenery.cfg during installation and made a backup. Same goes with Scenery.cfg.bak. These files, as well as NewScenery.cfg, can safely be deleted".

 

"Removed Scenery.cfg to a temporary folder".

 

Restarted FSX and yes the Scenery.cfg rebuilt itself! FSX started at KTEB, no issues for start up

 

Where have all my add-on sceneries gone to for the whole of FSX?

 

Looking also in the Scenery Config Editor, they are not there also! Have I got to re-install them from square one?

 

Thanks

 

Sauviat

 

 

Where have all my add-on sceneries gone to for the whole of FSX?
Looking also in the Scenery Config Editor, they are not there also! Have I got to re-install them from square one?

 

You now have the default scenery.cfg that is loading and fsx is starting up.  That's good.  You have two options.  Open up the Scenery.cfg that you moved to a temporary folder and copy all of your addon scenery (should be down to Propeller Objects).  Open up your new scenery.cfg and paste the addon scenery and then click on Save.  This option will require fixing the Areas/Layers (which can be done by the SceneryConfigEditor). 

 

The second option is the best option.  Open up SceneryConfigEditor and click on Add Area then go to the folder which contains your first addon scenery.  Add it to scenery, click on Save, and then run FSX and go fly to make sure that area is not causing you crashes.  Then, do the same thing by adding another scenery to the scenery.cfg.  If you have a lot like me and you are confident they are not causing you problems, then go to the SceneryConfigEditor and add those.  If you have any Orbx scenery, those are only added via their utility.  You cannot mess with those.

 

Best regards,

Want to add that still this is not going to fix your ntdll.dll error in NY State.

 

Best regards,

Phew! I replaced the add-ons still not starting in the NY area.

 

Then I removed the UIAutomationcore.dll and still not starting.

 

Below is the dll.xml, but no idea if there is something there that should not be:

 

<?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>C:\Microsoft Flight Simulator X\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow.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>FSUIPC 4</Name>

 

<Disabled>False</Disabled>

 

<Path>Modules\FSUIPC4.dll</Path>

 

</Launch.Addon>

 

 

-<Launch.Addon>

 

<Name>SquawkBox Transponder</Name>

 

<Disabled>False</Disabled>

 

<ManualLoad>False</ManualLoad>

 

<Path>C:\SquawkBox\sbtrans10.dll</Path>

 

</Launch.Addon>

 

 

-<Launch.Addon>

 

<Name>SquawkBox AI Control</Name>

 

<Disabled>False</Disabled>

 

<ManualLoad>False</ManualLoad>

 

<Path>C:\SquawkBox\sbaicontrol10.dll</Path>

 

</Launch.Addon>

 

 

-<Launch.Addon>

 

<Name>SquawkBox Internal Version</Name>

 

<Disabled>False</Disabled>

 

<ManualLoad>False</ManualLoad>

 

<Path>C:\Program Files (x86)\SquawkBox\sbmod10.dll</Path>

 

</Launch.Addon>

 

</SimBase.Document>

 

Thanks

 

Sauviat

 

 

-
Object Placement Tool
True
False
..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll.addon>
-
Traffic Toolbox
True
False
..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll.addon>
-
Visual Effects Tool
True
False
..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll.addon>

 

Not sure why you have these entries.  Are you developing software for FSX?  These tools in the FSX Software Development Kit (SDK) would help.

 

Otherwise I do not see a problem with your dll.xml.  I see no duplicates.

 

SquawkBox has been known to cause a lot of problems in FSX (your can search this forum).

 

Best regards,