I have been experiencing CTDs with NGX SP1 when a FSX menu action is selected. Through troubleshooting process, I have isolated one possible cause. After testing with and without GoFlight ver 2.03 installed, I was able to tie the CTD on selection of the FSX meun to installation of ver 2.03. The CTDs began occuring about the same time that I upgraded to ver 2.03 at the end of October.Question: Those who are experiencing CTD when FSX menus are selected, do you have GoFlight software installed. Is it ver 2.03? Once again, on multple cycles with and without ver 2.03 installed, I've been able to tie the CTD and installation of this ver together as a possible culprit.I'm going to go back to ver 2.02 to see if this resolves the issue.Thanks,Rich Boll

Follow up:Installed GoFlight ver 2.02. Repeated test that resulted in CTD with ver 2.03. No CTDs occured with FSX menu selections, specificly Add-On>FSUPIC menu with GofFlight ver 2.02Rich

Replacing the UIAutomationCore.dll file doesn't work then?

I'm using 2.0.0.1 with no problems so I'm hesitant to install the new update. Has anyone sent a message to GoFlight about this problem?Frank

Frank,If I recall correctly, I was using ver 2.01 when I first installed NGX back when it was released in August. I had no problems with the GoFlight software until I installed ver 2.03 around Nov 1st. After that, I couldn't fly NGX without experiencing a crash when tried to access one of the FSX menus. I should note that the problem involved the FSX Controls menu after I made a change to a joystick assignment and also when I clicked to open the FSX>Addon>FSUIPC menus. When I selected the FSUIPC menu, the CTD was immediate. With the Controls menu, it was upon exit. The faulting modules where Windows 7 system modules like USER32.DLL, dinput.DLL, or ntdll.dll.While researching each of these DLLs, I found out that the dinput.dll is related to HID devices like joysticks. That lead me to investigate joystick & controller issues, which is how I discoverd the link with GoFlight 2.03 to the CDTs.I have sent an email to GoFlight concerning this issue. I am waiting for a response.Thanks,Rich

I often have the same problem (CTD when accessing FSX menus), however I don't have GoFlight nor any other S/W that interacts with FSX or NGX. The problem is not consistent: it sometimes happens, sometimes not. Usually I am trying to save a flight while still on the ground, such as when ready to taxi. I have noticed that if I pause the flight before accessing the menu, it almost always crash. It also happens if I am trying to access the weather od look at the map. Anyone else have this problem?Gaétan

My story with GF and crash when hitting menu? UIAutomationCore.DLL.This is W7 x64? If Yes, please search for UIAutomationCore.DLL from Vista OS. It should have approx 150kB. Just drop it to the FSX root folder and open/close menus for ~15-20 times (my orginal UIAutomationCore crashed after ~15 times accessing the menus).

My story with GF and crash when hitting menu? UIAutomationCore.DLL.This is W7 x64? If Yes, please search for UIAutomationCore.DLL from Vista OS. It should have approx 150kB. Just drop it to the FSX root folder and open/close menus for ~15-20 times (my orginal UIAutomationCore crashed after ~15 times accessing the menus).

+1

Found and resolved the problem, but in my case it had nothing to do with UIAutomationCore.DLL. First I found that the UIAutomationCore.DLL in my FSX folder WAS the Vista file (6.0.5840.16386). I also found that I had a different UIAutomationCore.DLL file in C:WindowsSystem32 (6.1.7600.16385), which is normal since my OS is Win 7 32-bits. I kept searching until I found someone who suggested looking in the Event Viewer to find out exactly which module causes the crash. I did, and found the faulty module was nvd3dum.dll, NOT UIAutomationCore.DLL. Now, this nvd3dum.dll is tied to the nVidia driver. So I went into the Device Manager and updated the driver. This solved the problem! I since have accessed all parts of the menus (about 20 times), both in pause and running mode, and no more CTD!So the problem had nothing to do with the PMDG B737-NGX (although it might have triggered it because it is so demanding), nor even with FSX. It was caused by an outdated or defective graphics card driver.Nevertheless, thanks to both Bartłomiej and Howard for steering me in the right direction. I hope that by posting this it will help others who run into the same problem.Gaétan

Glad you sorted it out Gaétan