Hi,

 

I'm slowly moving from FS2004 to FSX and finally caught this error with PMDG NGX. I remember that it was extensive discussion about this module, but I cannot recall if there some agreement about...

 

1) what version of the module to use

2) where this module should be placed.

 

The link to the most reliable version of the module would be much appreciated.

 

Thanks

Dmitriy

http://forum.avsim.net/topic/368927-ui-automationdll/. There are several other posts in this forum regarding this crash and procedures on how to fix it. As I always state, I doubt it will work though. It's a hit and miss 'fix'. Works for some. Doesn't for most. Uiautomationcore.dll is part of the dotnet framework and you need versions 1 thru 4 installed as they are not backward compatible. If you do not have the proper version installed, the 737NGX will not work properly. However, PMDG does install the proper version when you install it. But, if you moved the installation from one computer to another an error could occur. The PMDG 737NGX needs the latest version of MS Visuals C++.

 

Best regards,

Jim

Jim,

 

PMDG has been installed properly as well as other C++ libraries, Please take a look

It looks like you are missing several... Perhaps if you run Windows update? I did not go to the MSV website and download these packages. They were installed with FSX addons and FSX. The 64 bit versions are not required for FSX.

 

 

It also looks like you might be missing several MS dotnet framework files. Versions 1-4 are required. PMDG installs the required MSV and dotnet software to run their addon. I recommend you uninstall the aircraft and reinstall it. Make sure UAC is turned off and any anti-virus program temporarily disabled too. The Memory_Access_Violation exception code 0xc0000005 indicates settings for FSX set too high or your page file (virtual memory) is not set to 'system managed size'. I have found that FSX likes 'system managed size' the best.

 

Best regards,

Jim

UAC = off. I've using this since the first day of Vista,

High settings i FSX?...Hmmmm, I'm still testing around with LOD 4.5 and Texture_Max_Load_1046, and "zero" autogen.

Memory is also system managed that is set by default.

 

Actually, I want to reach the stability of the system before OC, therefore it's not in my interest to push an envelope with my PC.

 

Anyway, I will continue testing and report back if the problem will arise.

 

Thank you Jim.

 

PS. How to you "read" the error codes? Any valid documentation about that?

How to you "read" the error codes? Any valid documentation about that?

 

Google/Bing is your friend :friends:

 

When I find a faulting module such as uiautomationcore.dll in the Event Viewer I simply Google 'uiautomationcore.dll error fsx'. I'll find hundreds of posts throughout the flight sim community and then pass it on to you.

 

I also Google 'Exception Code 0xc0000005' and I'll find out all kinds of details about this code (and then pass it on to you). Since I know for a fact uiautomationcore.dll is part of the MS dotnet framework, I'll also recommend updating and making sure you have all the required versions installed. Each developer uses a different version and none are backward compatible. With Google/Bing you can enter the whole error message you get when your system crashed and you'll find thousands who have had similar problems and possible solutions. No two systems are alike so what works on their system does not necessarily work on yours. I use Google frequently to correct any errors that pop up in my Event Viewer. I'll type the whole error message and will always find a solution that others have found. It's like having a computer tech sitting next to you and telling you what's wrong and this is how to fix it.

 

Hope this helps.

 

Best regards,

Jim

Jim,

 

Could you please post the links to all of the dotnet packages. I don't even know the official names of this packages.

 

Thanks

Dmitriy

Actually, the exception code .....0005 can be related to literally anything, not only to memory in BIOS (too wide definition), My BIOS setting are set to default.

 

See this about ATI.

 

Hardware-specific graphics issues

 

ATI

 

On computers that use an ATI video card, you may experience the following issues:

• Use of the ATI Radeon X1800 CrossFire Edition video card may cause the screen to flicker or to appear black.
  
• The game runs slowly.
  
• A fatal error occurs when you start the game. The error message indicates the following information:
  Problem signature
  Problem Event Name: APPCRASH
  Application Name: fsx.exe
  Application Version: 10.0.61637.0
  Application Timestamp: 46fadb14
  Fault Module Name: atiumdag.dll
  Fault Module Version: 7.14.10.523
  Fault Module Timestamp: 46c10882
  Exception Code: c0000005
  Exception Offset: 0004e060
  OS Version: 6.0.6001.2.1.0.768.3
  Locale ID: 1033
  

To resolve these issues, visit the following ATI Technologies Inc. Web site to download the latest driver for your specific video card:

 

http://support.microsoft.com/kb/925722

0005 can be related to literally anything, not only to memory in BIOS (too wide definition), My BIOS setting are set to default.

 

I have stated that several times here on AVSIM. That's why I usually state there's no magic bullet to most FSX crashes. But it IS related to memory. When FSX was running, it was calling a module (atiumdag.dll) but couldn't because of a Memory_Access_Violation. System drivers can also cause crashes if a driver for a video card or sound card are corrupted or missing. 98% of all the crashes in FSX have the exception code 0xc0000005. It's almost impossible to pinpoint the cause of the crash if no faulting module is shown. In your case, the ATI module was the faulting module and that gives you a hint as to what caused the crash. Here's an excellent explanation of the Memory_Access_Violation error - http://www.updatexp.com/0xC0000005.html.

 

Could you please post the links to all of the dotnet packages. I don't even know the official names of this packages.

 

Here's a link to one package - http://www.microsoft.com/en-us/download/details.aspx?id=19. Links to the other packages are listed at the bottom of the page of the link I provided.

 

Best regards,

Jim

I But it IS related to memory. When FSX was running, it was calling a module (atiumdag.dll) but couldn't because of a Memory_Access_Violation.

 

So, it's about the memory - what can be done on my side if my PC is 2 weeks old (custom assembling by Microcenter) and BIOS settings are default. Change RAM? What if it won't work? Seems like endless game.

 

PS. The last screen isn't mine. It's taken from Microsoft website for illustrative purposes.

So, it's about the memory - what can be done on my side if my PC is 2 weeks old (custom assembling by Microcenter) and BIOS settings are default. Change RAM? What if it won't work? Seems like endless game.

 

Like I said, it's complicated. There are so many causes and your system memory is just one really tiny possibility. There is no 'magic bullet' to fix your problem. You have to investigate. That's why I always ask to see what's in the Event Viewer (which you provided right away). It's the first step into the investigation. Maybe your settings in FSX are set too high. FSX can only see so much memory and not much above 4GB and that's with a 64 bit system. In a 32 bit system, fsx can only see 3GB. For proof of this, read the article by the computer guru in the FS community, NickN, about memory settings - http://www.simforums.com/forums/topic29041.html. FSX cannot run with max settings without subsequent issues. You have a very nice system but it cannot run fsx at the max. What did you install just before the crashes (for fsx or any application on your computer)? Perhaps that's causing the problem. Do a Google search for: faulting module uiautomationcore.dll fsx. There are hundreds of individuals who have received the same error and maybe you'll see a commonality and a possible solution. Unfortunately I have run out of ideas. Hopefully you can find more possibilities by Googling as suggested above.

 

Best regards,

Jim