Jim Young

See the following link for a temporary solution to this problem - http://forum.avsim.net/topic/452549-r6025-runtime-error-continues-in-v24/
 
Best regards,

This error can be stopped with RAASPRO and FSUIPC modules enabled by making sure "Prompt on Exit" is enabled in the P3D.cfg settings. It will also work with Tessellation on or off. Evidently, RAASPRO is not shutting down properly and enabling the "Prompt on Exit" allows time for the program to properly shut down.
 
This fixes the problem for clean installs of P3D too as something in P3D was not shutting down fast enough. This temporary fix will be placed in the next revision of the AVSIM CTD Guide.
 
Best regards,

You can try uninstalling/reinstalling SP2. You should also move your fsx.cfg to another temporary folder or rename it to fsx.orig and restart fsx and let the config rebuild. This gets rid of evil tweaks that might be in your fsx.cfg that might be causing this problem. It could also be a simconnect issue not being able to communicate in your network.
 
Best regards,

Then you should download and run AppCrashView (see AVSIM CTD Guide for link). There are many reasons for the StackHash/NTDLL crash(es) and they are listed in the AVSIM CTD Guide. One primary cause is My Traffic X 5.4c. The AVSIM CTD Guide is located to the right of this forum under Hot Spots.
 
Best regards,

According to the AVSIM CTD Guide:
 
Visualfx.dll – The visualfx.dll is used to display an FSX effect. An effect needed for an aircraft or scenery may not be located in the Effects folder and, when the effect is called by the program, it cannot be found and FSX crashes. The CTD occurs mostly with aircraft not properly installed and/or the default flight (shown in the [userinterface] Situation= line in your fsx.cfg) may be corrupted when a new default flight is set up. The solution in this case is to rename your fsx.cfg to fsx.orig, restart FSX and let the fsx.cfg rebuild. It has also been fixed by returning the default textures into the main texture folder. This can be done through a backup or conducting a FSX repair installation.
 
Best regards,

Do you have that file reference in your post above - File: D:\FSX\Scenery\0201\scenery\APX21140.bgl ?  That's a default FSX scenery.  Perhaps the file got corrupted somehow and fsx cannot read it.  If it is just GSX, try uninstalling, running FSX at least one time (to make sure that is the problem), then reinstall GSX.  GSX usually does not generate a new scenery cache until fsx is fully loaded.  What is the new scenery you put in the Scenery Library or, what new scenery did you just install?  Sometimes the registry gets corrupted so you should run a registry cleaner such as CCleaner.
 
Best regards,

Nonsense!!  If you have a corrupted dll.xml, FSX may not run.  I have hundreds of examples in the AVSIM CTD Forum to prove my point.  There have been many members who have CTD's but, when they disable a module from running, the crash(es) will stop. 
 
It is a 100% proven fact that fsx will not start up if it is missing Microsoft Visual C++2005 w/sp1.  I do not know why you had to go through the iteration of how and why the MSV would be missing and just let the OP just look in his Add/Remove Programs to see if it was there or not.  It was almost like you were questioning my response. 
 
Best regards,

Take a look at the AVSIM FSX Configuration guide located under Hot Spots to the right of this forum.  Make sure AA and AA are enabled.  Follow the guidance for the Nvidia NI settings to eliminate these anomalies.
 
You might get more information about your problems by checking out Steve's DX10 Fixer Forum located under Commercial Forums here on AVSIM.
 
Best regards,

Most likely a problem with your Acceleration installation.  You can try uninstalling Acceleration (go to Add/Remove Programs and look for FSX and click on uninstall.  It will only uninstall Acceleration).  Run FSX once and see if this fixed the problem.  If not reinstall Acceleration with Admin privileges.  Run FSX again and see if the problem fixed.  If not, remove your Fsx.cfg, restart fsx and let the config rebuild.  If this does not fix the problem, rename your logbook.bin in the My Documents/Fight Simulator X Files and try running FSX again.  There is also a program in the AVSIM Library called FSX Logbook Recovery which will look for errors and fix them.
 
 
 
 
Not sure what you mean here.  You moved FSX to another drive?  If so, that probably is your problem.
 
Best regards,

Never heard of an 8bd1 CTD.  Actually all that was was the signature of the crash which means the crash occurred at memory address 8bd1.
 
I see you have posted the same CTD over at the Aerosoft forum for AirbusX.  I suspect you think the problem is the Airbus.
 
Your problem is your Fsx.cfg.  Delete or rename it, restart FSX and let the config rebuild.  Whenever you have a CTD in FSX the first thing you should suspect is high settings somewhere (could also be in your Display Driver settings or you could have an unstable overclock).  You have high FSX settings.  You must be seeing blurry textures too as you have that nasty tweak Fiber_Frame_Time_Fraction=0.15.  Then you have LOD_Radius at 6.5 and Texture_Max_Load at 2048 and you wonder why your application is hanging?  Whenever you get a CTD, these are the first three items that should be returned to the default.  I would also lower the Autogen from dense to normal.  Since you have a wide screen monitor, then you should indicate this in the Display section of the fsx.cfg to WideViewAspect from False to True.  Check out the AVSIM FSX Configuration Guide for recommended settings.
 
Best regards,

Some have fixed this problem by pausing FSX just before lowering the speed to normal.  You can try pausing after you have lowered the sim rate too.  You are using a lot of system resources when you increase the sim rate and this allows the sim to "catch up".  I heard a long time ago that there were issues with the 16x's rate but cannot find it now.  As I recall the Microsoft developers were recommending a speed no higher than 8x's.  If you have a lot of other things running in the background, like real weather, atc, an AI program, using a commercial aircraft from Aerosoft or PMDG, flying over commercial scenery and not the default, then this only increases the chances for something like this to happen.  High FSX settings and a bad tweak like BufferPools will do it too.  You should look at your Event Viewer to see if there are any events showing these freezes and if there was a module that caused it.  AppCrashView can probably pick it up too especially if you received a message that FSX has to close and they are looking for a fix.  You can get more details of these two programs in the AVSIM CTD Guide (see pinned topic in this forum).
 
Best regards,

A bad tweak?  A high setting?  If you deleted your Fsx.cfg and let it rebuild and not change any of the display settings (except resolution), does the problem still exist?  Bad tweaks, high settings are the cause of all low FPS with textures rendering very slowly.  We install fsx/acceleration, run fsx and the fps are extremely high (with my system I was getting fps over 300!!).  Then we start adding things and the fps start to plunge.  We try tweaks to make it go faster but those do not always work.  Slowly but surely, FSX is verrrrrry slow.  So you have to balance eye-candy with the technology and that's not easy.  AVSIM has a great configuration guide (see link in my signature) that should provide some good balanced settings.  AVSIM does not recommend tweaks though but has some suggestions in case you want to try them. 
 
Do you run an AI commercial addon program?  Do not see that in your list and many people own AI programs or install a freeware version. 
 
If you set your REX4 scenery to 4096 HD or even 2048 HD textures, that will create problems but we are talking about individual products.  It's very difficult to give you advice (other than the above) when we have no idea what settings you have employed for your addons.
 
That's my 2-cents worth.  Good luck in getting your problem fixed.
 
Best regards,

Do not install the uiautomationcore.dll  Causes more problems than it helps.  Just look at all the posts here in the CTD Forum that shows a crash report with the uiautomationcore.dll module loading.  Individuals removed it and the crashes stopped in many cases.  I fortunately have the evidence, the proof-positive evidence that the uiautomationcore.dll does not prevent all FSX crashes.  You are one more example as you DID have the uiautomationcore.dll installed (see loaded module 134 in OP).
 
Your crash was caused by your ATI driver.  A known crash.  The following topic might help - http://forum.avsim.net/topic/423624-amd-139-tutorial-get-fsx-working-again/.  In addition, it appears you have a very old driver and maybe all you need to do is update it.
 
Best regards,

I think the best solution would be to use the FSX internal flight plan program.  Once set up you can print out the Nav Log.
 
Best regards,

I would remove the UIAutomationcore.dll from the main FSX folder as many with Windows 8 have fixed their crashes by removing this module. .

Best regards,

This is a known problem with the latest ATI driver.  See this recent post here in the CTD Forum - http://forum.avsim.net/topic/423624-amd-139-tutorial-get-fsx-working-again/.  There are posts about this problem in the DX10 Forum too.
 
Graphic blurs are common in FSX and mostly caused by one or more of your fsx settings set too high.  Your graphics card is struggling to render the texture in time.  This is even if you have high fps as fsx is more dependent on the CPU than the GPU.  Maybe limiting your fps might help but then you'll probably run into more problems.
 
Hope this helps.  Welcome to the AVSIM Forums!
 
Best regards,
Jim

Glad you were able to resolve the problem.  You didn't say but I assume reinstalling FSUIPC fixed the g3d.dll error?
 
Best regards,
Jim

This will happen when you have a lot of programs running in the background.  This is why I use Scenery Config Editor, a utility where I can activate/deactivate scenery before I even start up FSX.  I have mainly photoscenery installed and, if I have it all activated in the Scenery Library, it will all load even if I'm not going there in my flight plan.  This brings a system with a lot of photoscenery down to its knees.  So, if you are running fsx and hear a lot of commotion going on with your SSD/HDD's, then that's what is happening.  In the scenario I just described, I can make a black screen where the aircraft should be spinning 100% of the time if I have all of my scenery enabled.  It will also happen when you select an aircraft and then immediately go to select your starting location.  You'll have to wait for about 15 minutes before the black screen goes away and you can see your aircraft spinning and you can now go in and select the beginning location of your flight. 
 
I don't know what kind of system you have.  I have a very powerful Haswell i7 4770K system.
 
You might want to also look in your Event Viewer/Administrative Events and see what problems your computer is experiencing.
 
You can also download and run AppCrashView and see if any crashes were reported recently.
 
I have also seen where IE10 will bring down FSX if you have IE10 loaded in the background, especially if you have several Tabs open.
 
Hope this helps.
 
Best regards,
Jim

Even better!  Your ATI video card drivers caused your crash.  A lot of people who own an ATI Video card are seeing this crash.  See this post for possible resolution - http://forum.avsim.net/topic/423624-amd-139-tutorial-get-fsx-working-again/.
 
Best regards,
Jim

Problem fixed!  Ever since I started this topic back on July 29th, I've had to hit the F5 (Refresh) button to refresh every page I visited.  Quite frustrating to say the least.  I finally found the fix (this is for all versions of Internet Explorer):
 
Click on F12.  This will bring up the Developer's Console at the bottom of the page.
 
Click on Cache and select "Always Refresh from Server".
 
I'm still trying to figure out why this wasn't set up automatically for me.  Very few other members here at AVSIM have this issue with their IE browsers.
 
Best regards,

That's normal.  NVIDIA is telling you (via their 3D Drivers) what is incompatible when you run the sim in 3d.
 
Best regards,
Jim

You had a KERNEL_DATA_INPAGE_ERROR which indicates Windows could not read a file from the disk that is supposed to be there. It may indicate the hard disk has bad sectors, hardware (disk, controller, memory) issues, a virus infection or a bug in a device driver.
 
Scan your system for any corrupted system files - http://pcsupport.about.com/od/toolsofthetrade/ht/sfc-scannow.htm.
 
Did you just install a new SSD or other piece of hardware?  That should be the first suspect.
 
Check your disks for errors - Go to Windows Explorer and right click on your C drive and click on Properties.  Click on the Tools tab and then Error-checking.  Do this for every HDD installed.
 
You have SSD's so do not defragment them.  If you have a HDD, then you can defragment that HD.
 
Your page file could be corrupted.   Click on the Start button and type virtual in the search box then look up in the menu and click on How to change the size of virtual memory.  Follow those directions.  Once there, turn off (click on None) for each HDD and reboot.  Once restarted, go back into the virtual memory (page file) settings and click on System Managed Size for all HDD's.
 
Download and run freeware driver cleaner software.  It will show you if you have any drivers out of date.  If you want the program to update the drivers for you, then you will have to purchase and register the software.  You can also look at what drivers are outdated and go to Google or Bing and search for the driver, download it, and install the updated driver(s). 
 
Hope this helps.
 
Best regards,

Thanks for posting your AppCrashView results in a new post.  It makes things easier.  Your crash was caused by your ATI video card driver.  Uninstall/reinstall the driver.  Make sure you have the latest drivers for your video card - http://support.amd.com/us/gpudownload/Pages/index.aspx.
 
I would also remove the uiautomationcore.dll from your main fsx folder as it is obviously not fixing your crash(es).  Place it in a temporary folder until this problem is fixed.  Then, if you want, you can move it back.
 
You might want to scan your system too for any corrupted drivers as something might have gotten corrupted when you removed the uiautomationcore.dll's from your system folders and then replaced them - http://pcsupport.about.com/od/toolsofthetrade/ht/sfc-scannow.htm.
 
Best regards,

You have a very powerful system for FSX.  In fact my old system was the i7 2600K w/the GTX 680.  You just have to be careful how you tweak it and how you set your fsx and video card settings.  With your system I would use the following guide - http://www.simforums.com/forums/drivers-nv-inspector-fsxcfg-complete-guide_topic36586.html.  Be careful if you employ the BufferPool tweak (even the one in the guide in the link I just provided).  On the system you have now, I didn't tweak at all except that I raised the LOD_Radius and reset the Texture_Max_Load.  Just remember, if you are flying a 777 or an Airbus, you won't be able to see much at FL 100 and above.  Up there you want some pretty clouds, a nice VC, and a nice wingview.  A lot of people, including me, increase their FPS and rendering by changing the resolution.  I hit the minus key a couple of times in the PMDG 777 VC, and four times at wingview and all external views.  This provides a more realistic rendering of your flightsim.  It's amazing how many more fps you can get just by doing this little trick.  I use a lot of photoscenery and it really works great with that.  It should work with other scenery too.  Moving all of your sliders to the max is the worse thing you can do to fsx.  It may work okay a couple of times but eventually it is going to bite you and you'll be visiting this forum frequently for answers.
 
Best regards,

What do you have?  FSX Deluxe and that's it?  Or do you have Acceleration too.  Or maybe you had FSX, SP1 and SP2 installed.  If you had SP2 installed then you need to reinstall or do a repair with SP1 and SP2 too.  If you had Acceleration, you need to repair that too.
 
Best regards,
Jim