Yes it is weird but when I first got my new build going I got my first FSX CTD and WIN 8 automatically set VISTA SP2 compatibility. Makes you wonder what is going on under the covers. Cheers jja

Well, any trick that helps is a good one. So if that one fixed the CTDs for you, it's worth mentioning and one, if having the same problems, should try it. Edited. I just saw that you wrote that Win8 automatically picks that mode.

 

I was wondering. You folks with the running P3D installations. Do the notes from Scarlett also apply to that sim? Or do they largely differ. Now don't tell me P3D doesn't crash. Back then, I saw it. However, I don't recall the log entries and things any more.

 

Just asking because this may also be a P3D guide then. The FSUIPC fix for the g3d.dll crashes is needed too, right?

I mentioned earlier that I think the prime cause is an old FS addon that was maybe upgraded to meet compatibility with FSX but evidently not fully compatible. According to my research, "UI Automation was first available in Windows XP as part of the Microsoft .NET Framework. Although an unmanaged C++ API was also published at that time, the usefulness of client functions was limited because of interoperability issues." For Windows 7, the API has been rewritten in the Component Object Model (COM). FSX was developed for the Vista OS but Vista had not been released until shortly after the release of FSX. It's a system dll and part of the Microsoft.net framework that Microsoft developed to help developers make their products run better. For some in the FSX community, they have failed. I try to keep my system clean of old FS apps and maybe that's why I have not run into problems with this dll (yet!). I would recommend that anyone who has never received this menu crash or had uiautomationcore.dll shown as the faulting module, should keep it out of their FSX folder. Doing a Google search on the uiautomationcore.dll, it appears FSX is the only game, the only computer software product that suffers with this issue so there are some interoperability issues between Vista and Windows 7/8 and FSX (for some). Just another two-cents worth of more info and my thoughts....

 

Best regards,

Jim

Good information Jim. Thanks jja

With hundrens, and if not thousands of users posting topics here in the CTD forum every month about crash to desktop errors, I have decided to compile a list, and guide on the most common CTD errors, and why they happen.

 

Even though I became a member back in 2011, I have been reading this forum for quite awhile, and taking note of a-lot of crash to desktop errors, and have been learning about them ever since!

 

WIth all of us trying every day to improve FSX, I hope this topic will help new-comers understand why FSX is giving them crashes.

 

So, LETS BEGIN!

 

 

I am very impressed with this (didn't want to copy the whole original message again). When I migrate to FSX I will keep this in hand should I run into any problems. Outstanding job Scarlett.

I guess this is great but on my Windows 7 (64) system I am not able to match the guide. I have gotten a couple of blue screens lately with Power_Driver_State_Failure; Stop 0x0000009F. I need to open Control Panel, Administrative Tools to get to Event Viewer. When I open Event Viewer there is no next level choice named Application. I can find Application under Windows Logs, but I find nothing there that is related to Fault Module Name and/or Exception Code.

 

Can someone further enlighten me?

I would recommend that anyone who has never received this menu crash or had uiautomationcore.dll shown as the faulting module, should keep it out of their FSX folder. Doing a Google search on the uiautomationcore.dll, it appears FSX is the only game, the only computer software product that suffers with this issue so there are some interoperability issues between Vista and Windows 7/8 and FSX (for some). Just another two-cents worth of more info and my thoughts....

 

An excellent way of putting it, Jim and applicable to many "magic" FSX fixes. Don't fix it if it ain't broken.

 

That said, and while this is exactly the route I (almost always) take with my system, after I'd CTD'ed with uiautomationcore.dll issues numerous times I grabbed the Vista version and stuck it in the FSX root folder. It's been well over a year since I finally did so and haven't had a uiautomationcore.dll crash since.

 

I honestly believe that some of problems experienced with the fix come from dubious copies of the Vista version from equally dubious sources. At the time, I pulled mine from an existing Vista 64 installation.

 

Scott

I honestly believe that some of problems experienced with the fix come from dubious copies of the Vista version from equally dubious sources. At the time, I pulled mine from an existing Vista 64 installation.

 

Thanks Scott. I'm a little concerned about your last sentence though. You have the 32 bit uiautomationcore.dll from Vista installed don't you? Not the 64 bit as FSX is a 32 bit application running in a 64 bit OS environment. It only accepts 32 bit stuff. Just wanted to make sure. It's really strange why I have never had the need to install the uiautomationcore.dll into my FSX folder and have had very few crashes over the past 6 plus years. I did try it when the g3d.dll ctd started happening to almost everyone but it did not fix that CTD. I never run my computer with all settings or most of them at max. I think that has something to do with it as the uiautomationcore.dll is related to memory management.

 

Best regards,

Jim

I guess this is great but on my Windows 7 (64) system I am not able to match the guide. I have gotten a couple of blue screens lately with Power_Driver_State_Failure; Stop 0x0000009F. I need to open Control Panel, Administrative Tools to get to Event Viewer. When I open Event Viewer there is no next level choice named Application. I can find Application under Windows Logs, but I find nothing there that is related to Fault Module Name and/or Exception Code.

 

Can someone further enlighten me?

 

Sorry, I didn't include bluescreens, because there can be so many different reasons why a 'bluescreen' happens. In your case, post a topic in the CTD forum to prevent this topic from becoming a topic with endless replies.

Scarlett--appreciate that you took the time to do this, but there are some material errors that need addressing here.

 

Exception Code

 

Fault Module Name is the self explanatory. This is the DLL that was loaded before the Application crashed. 90% of crashes can be identifyed and solved with these.

 

Exception Code basically gives us a big clue on why it happened. For example, and exception of 0x0000005, means FSX had a MEMORY_ACCESS_VIOLATION. Which means FSX crashed because FSX was seaching for a file, and could not find it.

 

No, first of all I think you mean the 0xC0000005 exception, which is the dreaded MEMORY_ACCESS_VIOLATION. It has nothing to do with file access--it means that a program has attempted to access memory at an address that is not allowed. The most common causes on a stable PC are null or otherwise bad pointer references, memory buffer overruns, and other programming issues. Often a program works but does not gracefully handle bad data when it appears--MSFS's unruly behavior when a bad texture is encountered is but one of too many examples. An unstable overclock or some bad RAM can also cause this by corrupting a memory address being loaded into a CPU address register. But the memory exception violation is usually a programming and/or bad data issue, or a sign of system instability--but not a file system fault at all.

 

MSVCR80.DLL is part of the Miscrosoft Visual C++ 2005 Redistrabutable package, and crashes from MSVCR80.DLL usually means there is an error in the installation. Others have reported crashes with this DLL with certain aircraft, such as the Airbus X extended.

 

I strongly disagree that crashes in this, or any other MS kernel or library module "usually" indicate an installation error. Usually NOT. The significance of the faulting module is purely identification of the module containing the instruction that tripped the fault. Often--usually, in fact--an error with the MC Visual C++ runtime identified as the faulting module is caused by another program passing out-of-bounds or nonsensical parameters to one of the functions in the library. I can easily write code to cause a crash in a particular library module outside of my own program by calling one of its library functions with a null/bad pointer, for example. The aforementioned Airbus X Extended had/has easily duplicated bugs that will cause a memory exception in MSVCRT80.dll in a perfectly good installation. I don't want to see people spring-loaded to messing around with their operating system when this error occurs, because there is a lot of potential to cause greater harm when they do--especially when following the advice of some of the snake-oil solutions floating like landmines out in the internet wilderness (like manually tinkering with Windows side-by-side libraries, for example).

 

Terrain.DLL CTD usually has two main causes. First, and most common; FSX sliders are way too high. You are using too many system recources for your system to handle, and it is crashing. The second cause is a faulty installation of a scenery. Because of the exception code, (0x000005), FSX is calling for a texture or scenery item, and cannot find it.

 

I think it is more likely caused by a corrupt scenery bgl or texture than a missing one--FSX can and does handle missing textures without crashing. There's an fsx.cfg setting that'll display a label where every missing texture is encountered, in fact--if you enable it you might be surprised how many textures are missing in your day-to-day operations. You can also trigger a fault in this or another dll if you set Bufferpools to 0 and then overrun the video frame buffer by sending data faster than the video card can process it, i.e. having the sliders set too high. But that kind of crash isn't caused simply by setting sliders too high--it's caused by first intentionally defeating FSX's designed video buffer management process (BP=0) and then overwhelming it. If you take a stock FSX install and max every slider, you may only get 3 fps, but it won't CTD.

 

FIX: ATC.DLL have been reported due to an unstable overclock. Overheading while playing FSX can cause this issue. Look into the settings and core temperatures in your bios to make sure it's stable. If the crash is occurring in complex scenery areas, try turning down your FSX settings to put less stress on your system.

 

An unstable OC can cause errors in just about any module, as can overheating. But these sorts of instabilities are not consistent--if you are seeing a crash in the same module at the same addresses, it's a software issue or bad RAM. If you're seeing errors in assorted modules in addition to blue-screen crashes, I'd suspect CPU or motherboard component overheating. If the errors are all video system related, perhaps an overheating, underpowered, or failing video card.

 

Last, on the uiautomationcore.dll issue--it seems clear from my testing here that FSX has a proven incompatibility with the Win 7 version of this system dll. As Ryan previously described, I can force a crash with a base install of FSX on my Win 7 machine in short order just by opening/closing menus. Adding a copy of the Vista version of the dll to the FSX base directory--the dll that FSX was designed to operate with--solves that problem. And I've never resolved a subsequent CTD issue by removing it.

 

It's always good to have a place to start with tackling the nefarious CTD problem...but I have to caution against too cookie-cutter an approach, and especially against making assumptions early about having a system problem as the cause. In my experience, poorly-written software is the most common cause of these problems, and when they start cropping up the first thing I ask myself is "what software changes have I made recently?" I also keep a running log of every change I make to my FSX machine to aid in that troubleshooting.

 

Regards

I used to get the uiautomation.dll error on my old vista 32bit PC until I placed the file directly in

C:\fsx Just got a brand new pc win 7 home premium fsx gold edition installed

Only added one add on fspassengers which involves a lot of use of the menus and the crashes started occurring straight away . Copied the uiautomation.dll from my old pc across to the new one and in 4 weeks have not had a uiautomation.dll crash since. But maybe fspassengers needs this file ?

I appreciate may not work for others but has cured this particular error for me, don't you just love pc's!

 

 

MSVCR80.DLL- Most commonly paired with Exception Code 0x000000d

 

MSVCR80.DLL is part of the Miscrosoft Visual C++ 2005 Redistrabutable package, and crashes from MSVCR80.DLL usually means there is an error in the installation. Others have reported crashes with this DLL with certain aircraft, such as the Airbus X extended.

 

As a developer I encounter this one quite often when i overlook something in my code.

 

First of all, there is a very high (or should i say low value) area in memory (ranging from NULL(a redefinition of 0) to something that looks like 0xcdcdcdcdcd and possibly greater) that is reserved i presume for dynamic memory allocation and other windows operating stuff. I normally see it assigned to an object or variable just before it is initialized or just after i call the C++ delete statement before i assign a NULL value to a pointer. However i have noticed that with the above dll installed, if i get a 0xC0000005 exception it can be tricky to track down the actual dll involved because it lists the MSVCR80.DLL as the fault and not my gauge and the memory address is usually not NULL. Its only when i get a NULL pointer error that the actual module is identified.

 

Bottom line is its normally a case of a developer forgetting to initialize something properly(so it never gets assigned a place in memory) and then trying to use it or deleting it before being certain that it is actually no longer in use (common cause of CTDs on shutdown). It generally makes things a bit difficult for us devs to try and track down.

Scarlett--appreciate that you took the time to do this, but there are some material errors that need addressing here.

 

 

 

No, first of all I think you mean the 0xC0000005 exception, which is the dreaded MEMORY_ACCESS_VIOLATION. It has nothing to do with file access--it means that a program has attempted to access memory at an address that is not allowed. The most common causes on a stable PC are null or otherwise bad pointer references, memory buffer overruns, and other programming issues. Often a program works but does not gracefully handle bad data when it appears--MSFS's unruly behavior when a bad texture is encountered is but one of too many examples. An unstable overclock or some bad RAM can also cause this by corrupting a memory address being loaded into a CPU address register. But the memory exception violation is usually a programming and/or bad data issue, or a sign of system instability--but not a file system fault at all.

 

 

 

I strongly disagree that crashes in this, or any other MS kernel or library module "usually" indicate an installation error. Usually NOT. The significance of the faulting module is purely identification of the module containing the instruction that tripped the fault. Often--usually, in fact--an error with the MC Visual C++ runtime identified as the faulting module is caused by another program passing out-of-bounds or nonsensical parameters to one of the functions in the library. I can easily write code to cause a crash in a particular library module outside of my own program by calling one of its library functions with a null/bad pointer, for example. The aforementioned Airbus X Extended had/has easily duplicated bugs that will cause a memory exception in MSVCRT80.dll in a perfectly good installation. I don't want to see people spring-loaded to messing around with their operating system when this error occurs, because there is a lot of potential to cause greater harm when they do--especially when following the advice of some of the snake-oil solutions floating like landmines out in the internet wilderness (like manually tinkering with Windows side-by-side libraries, for example).

 

 

 

I think it is more likely caused by a corrupt scenery bgl or texture than a missing one--FSX can and does handle missing textures without crashing. There's an fsx.cfg setting that'll display a label where every missing texture is encountered, in fact--if you enable it you might be surprised how many textures are missing in your day-to-day operations. You can also trigger a fault in this or another dll if you set Bufferpools to 0 and then overrun the video frame buffer by sending data faster than the video card can process it, i.e. having the sliders set too high. But that kind of crash isn't caused simply by setting sliders too high--it's caused by first intentionally defeating FSX's designed video buffer management process (BP=0) and then overwhelming it. If you take a stock FSX install and max every slider, you may only get 3 fps, but it won't CTD.

 

 

 

An unstable OC can cause errors in just about any module, as can overheating. But these sorts of instabilities are not consistent--if you are seeing a crash in the same module at the same addresses, it's a software issue or bad RAM. If you're seeing errors in assorted modules in addition to blue-screen crashes, I'd suspect CPU or motherboard component overheating. If the errors are all video system related, perhaps an overheating, underpowered, or failing video card.

 

Last, on the uiautomationcore.dll issue--it seems clear from my testing here that FSX has a proven incompatibility with the Win 7 version of this system dll. As Ryan previously described, I can force a crash with a base install of FSX on my Win 7 machine in short order just by opening/closing menus. Adding a copy of the Vista version of the dll to the FSX base directory--the dll that FSX was designed to operate with--solves that problem. And I've never resolved a subsequent CTD issue by removing it.

 

It's always good to have a place to start with tackling the nefarious CTD problem...but I have to caution against too cookie-cutter an approach, and especially against making assumptions early about having a system problem as the cause. In my experience, poorly-written software is the most common cause of these problems, and when they start cropping up the first thing I ask myself is "what software changes have I made recently?" I also keep a running log of every change I make to my FSX machine to aid in that troubleshooting.

 

Regards

 

Thank you for your contribution. I wish that you had permission to edit this topic to make it better, because my only wish for this topic is to be as accurate as possible.

 

I don't have the time to read everything you said, but thank you for reading and helping anybody else.

Bottom line is its normally a case of a developer forgetting to initialize something properly

 

This might be true but I think it might also be the case of a wrong version installed on your system. FSX was developed with MSV 2005 but Acceleration was developed with MSV 2005 SP1. Unfortunately, Microsoft did not get the SP1 updated included when Acceleration was released. Therefore, everyone should be upgrading their MSV2005 to include SP1 (V 8.0.50727.6195). So, if you ever get a CTD, this is one of the first things you should look for. I do not know what MSV was used by the developers of AirbusX Extended but it could have been MSV 2010 or later. Normally, the installation software will look for the proper version and install the proper MSV if not found on the system. I recently reinstalled FSX/Acceleration and several addons and one of them installed MSV 2008 and 2010. Microsoft Visuals are not backward compatible so, just having only the latest installed on your system will cause problems. I think a lot of people are making mistakes by copying their FSX installation over to a new OS installation and then running a registry repair like the one from Flight1 which will make sure your registry knows where FSX is installed. In this case, the proper MSV will not be installed and FSX will crash and maybe throw up the MSVCR80.dll as the fault as it cannot be found on the system.

 

Totally a lot of possibilities but we might be able to reduce some by educating people on the proper installation of FSX/Acceleration and the addons. I appreciate your input as it adds another thing members need to think about when they get this CTD.

 

Best regards,

Jim

I don't have the time to read everything you said

 

You ought to go back and study them, Scarlett. Bob's and Jonathan's posts have been the best things I've ever read on CTDs. Thanks, guys.

 

Hook