Hi that was copid from the internet -

You must have administrative credentials to run regedit.exe.

I followed this link http://support.microsoft.com/kb/318785

 

and in the registry edit its there even the x86

in C programes microsoft.net in that folder there is only this - redislist (name of the folder) i go into it and theres 2 files called (AssemblyList_4_client.xml) and (AssemblyList_4_extended.xml)

 

 

in C programes microsoft.net in that folder there is only this - redislist (name of the folder) i go into it and theres 2 files called (AssemblyList_4_client.xml) and (AssemblyList_4_extended.xml)

 

So, they are not installed properly if the various versions are not shown in C:\Windows (not programs)\Microsoft.net\Framework(x86).  In the Framework folder you should have the Version 2.0, then a folder for 3.5, then a folder for 4.0, etc.

 

I need to emphasize that the proper versions of dotnet are installed when you install FSX, Acceleration, and each addon.  You might mess up your installation when you reinstall Windows, then, to save time you decide to move the whole FSX folder into the new installation without running the installation programs.  Then run the FSX Registry Repair program.  That may work for a while with no problems but eventually you will run into a problem as FSX addons look for a certain version of dotnet.  If it doesn't find it, crash!

 

Best regards,

ok i found the folder looking in the wrong place lol your message above highlighted it. right what am i looking for so much in here

i have all those folders?

 

 

right what am i looking for so much in here
i have all those folders?

 

That's correct.  Most likely you do and you can move on to another possible solution.  The faulting module in your crash report is showing that something is not installed properly or a file/module is not communicating properly with your FSX installation due to sharing conflicts.  If a file is not being shared because you have so much security placed on your system, then FSX cannot call that module or texture or file and process it.  What was the last program you installed before the crash(es) began?  In your investigation of your crash, you need to disable modules in your dll.xml as shown in the AVSIM CTD Guide -

 

Disable modules in dll.xml – Sometimes a module you have installed is corrupted.  You can check to see if any modules are the cause of your crashes by disabling all modules (except the first one).  Change the parameter False in the line <Disabled>False</Disabled> to True.  If the problem is fixed, then enable each module one by one until the culprit is found.

 

You might have a bad scenery addon and you should disable your addon scenery as advised in the AVSIM CTD Guide -

 

Disable Add-on Scenery – If you have a crash and the cause is unknown, disable all your add-on scenery in the Scenery Library, run FSX and see if this fixes the problem.  If it does, then the problem is associated with one or more of your add-on sceneries. To find the offending scenery, enable your add-ons 3-4 at a time until the CTD returns.

 

Another possible fix to your problem is to rebuild your fsx.cfg as suggested in the AVSIM CTD Guide -

 

Rebuild the FSX.cfg – Many CTD’s can be fixed by renaming your FSX.cfg to Fsx.orig, restarting FSX and letting the fsx.cfg rebuild.  It has been said that rebuilding your fsx.cfg will is about the same as uninstalling/reinstalling FSX.

 

Many have been very successful in fixing their FSX problems by rebuilding their facilities/scenery indexes and shader folder.  AVSIM provides great guidance on how to accomplish this function -

 

Delete/Rebuild your Facilities/Scenery Indexes and Shader Folders – Periodically delete your Facilities/Scenery Indexes located in Program Data/Microsoft/FSX.  Delete the Facilities and Scenery folders.  Delete the Shader folders located in AppData/ (your user name)/Local/Microsoft/FSX/Shader10 and Shader folders. When you restart FSX, these folders will be rebuilt.  It has been known to fix some CTD’s. 

 

Since the type of crash you had was a BEX (Buffer_Exception_Overrun) you could have a problem with a USB port.  A lot of individuals do not update their USB drivers that fix computer bugs.  They think Windows Update will do it for them - LOL.  As shown in the excellent AVSIM CTD Guide, you should also update your drivers -

 

Update Drivers – Microsoft does an excellent job providing updates for Windows and some drivers, such as for your keyboard, mouse, and video card.  But they do not find updates for drivers required for computer system stability.  Usually, the manufacturer of your computer, like Dell or Hewlett Packard will provide you updates for some of the hardware installed on your computer.  You should also download and run a program that will scan your computer for updated drivers.  These drivers will be updates for your CPU, your motherboard, USB ports, SSD’s, HDD’s, printers, etc.  There are several commercial developers who have programs that will scan your system.  Just use the Internet search engines, Google or Bing for Drivers or Driver Updates and you will get a list of programs you can download and run.  The programs are freeware but, when drivers are found to be out-of-date, they will ask you to pay a small registration fee to download and install the updates for you.  You can either pay or you can get the name of the out-of-date driver from the list provided by the driver scanner program and then go to Google/Bing and search for the updated driver. Once found, you can download and install the driver yourself.  Manufacturers constantly update drivers when they find issues with previous versions and it is one of the best things you can do to help maintain system stability.

 

Sometimes FSX users will have several Windows open and this increases the changes for having memory issues.  As indicated in the AVSIM CTD Guide, you should increase the heap limitation -

 

Increase Heap Limitation – There is a problem sometimes with Windows 7 users when too many Windows are open.  This may cause an out-of-memory (OOM) crash.  It is caused because of the desktop heap limitation.  Here is the link to the Microsoft Fix-It program that will increase your desktop heap limitation: http://support.microsoft.com/kb/947246. (Thanks to B247NG)

 

So there are a lot of things you can do to troubleshoot your problem.  Your problem could be anything and you are in control of your computer and you need to start investigating to see if you can find a solution.  I wish I could say exactly what is causing your crashes without you going through an investigation but there are just too many variables.

 

Hope this helps.

 

Best regards,

Nothing recently and it was all working fine! I've disabled DEP and got a new uiautomation thing aswell? Its not crashed since buddy fingers crossed do you think DEP had something to do with it? I'll take all your advice onboard cheers.

Has the exception code on my crash got to do with it? C00000D?

One other thing you mention to install fsx out of the default c programs x86 but i've installed it on that folder, now you recommended me to download that take ownership for fsx is this as just as good as placing it outside of the default folder? Basically i wont need to re-install fsx because of this download?

 

 

One other thing you mention to install fsx out of the default c programs x86 but i've installed it on that folder

 

I've never recommended that.  In fact I have had my fsx installation in the default programs x86 folder forever and have never had any problems.  I did turn off UAC though and made sure my fsx was being shared.

 

Best regards,

Right ok think i've done everything possible to have fsx shared your advice and others etc!