I have just purchased my version of Level D 767 for FSX. I operate this on the following system:1. AMD Phenom II processor2. 6 GB of RAM3. Saphhire 5670 1GB DDR5 graphics card4. Gigabyte MB with built-in sound card5. Windows 7 - 32 bit6. FSX with Acceleration Eddition7. FSX installed in the default MS games folder8. I always run FSX in windowed modeThe CTD happens with the Level D 767 sometimes as soon as the airplane loads, and ALWAYS as soon I click on the GROUND REQUESTS sub-menu.I read a lot about the UIAUTOMATIONCORE.DLL solution, and I tried it several times with several technics, but nothing worked.I ran the EVENT VIEWER tool, and I found out that the generated report is always the same with both kinds of CTDs. Below is the copies report:Log Name: ApplicationSource: Application ErrorDate: 4/28/2011 12:38:08 AMEvent ID: 1000Task Category: (100)Level: ErrorKeywords: ClassicUser: N/AComputer: islam-PC2Description:Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdadbException code: 0xc0000374Fault offset: 0x000c283bFaulting process id: 0x6a8Faulting application start time: 0x01cc0576fde6021fFaulting application path: C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\fsx.exeFaulting module path: C:\Windows\SYSTEM32\ntdll.dllReport Id: 75ac11ef-716a-11e0-be52-1c6f65a6dab2As you can see guys, the faulting module name is: ntdll.dll, version: 6.1.7600.16385.SO.... Any one has a clue now on what can I do???Thank you very much.Islam

Crashes related to ntdll.dll are extremely hard to troubleshoot, since every piece of software on your machine is using it one way or another (including Windows and drivers).Therefore, I suggest a process of elimination…I assume you are not over-clocking any of your hardware.Since you are running Windows 7, ensure Windows UAC is disabled.Make sure you install the latest Sound and Video drivers.Suggest you load default B737 and fly in default scenery. That should be a stable scenario.If that works, you can then go-back to using Level-D 767 to see if you can re-produce the issue.Gerald R.http://www.multicrewxp.com

AFAIK the uiautomationcore.dll bug is for the 64-bit version of Win 7 (please correct me if I'm wrong), but in any case it only cures menu access CTDs and right-button-click CTDs after the twentieth time, so any mouse-triggered CTD that happens the the very first few time you use the mouse is by definition not a uiautomationcore CTD.Make sure you also have the latest version of your MB Chip Drivers, usually downloadable from your MB manufacturer's web site, as well as all the updates to .NET installed.+1 on speedbrid's recommendation to start with a bare-bones version of FSX to make sure you have a stable install.Cheers,- jahman.

Thank you guys very much for your help. I will double check for the drivers, but please tell me what exactly is the so called UAC?

Thank you guys very much for your help. I will double check for the drivers, but please tell me what exactly is the so called UAC?

User Access Controls. Hit the Start button and type User Access Controls in the search box and then look up at the top of the menu and you'll see links to the controls.Best regards,Jim

Islam,I am a long time user of the LDS767 with FSX. In addition to the suggestions that other have given you. I might add a couple of others here. First this CTD can be caused by many situations. When I experienced this it was due to multiple accesses of the menu's in FSX. Some folks have suggested that if you select the menu option more than 20 times in a flight, FSX will crash and give you that fatal error. Now, I only do it to load programs "once" and that is it. If you go to multiple outside views like spot etc, remember that these count against that 20 number. With the LDS 767 if you resize the various panels and they exceed your graphic card capabilities this too can cause a ntdll.dll error. Crashing FSX with the ntdll.dll fault is a well known problem that MS should have fixed, but with the dissolved of ACES that won't happen with FSX. Hopefully FLIGHT won't have this issue. For now, I would just limit my accesses to the menu function to less than 20 clicks.Bob

Thank you very much Bob and Jim. Actually after several days of going nuts, finally I guess - thanks to Allah - that I am on my short finals for the cure!I have collected some knowledge from fooling around the forums and support teams, that I'd like to share with you guys here, just in case someone can use it.There are several kinds of CTDs that I've read about for FSX generally and Level D 767 specifically:1. If your CTD is happening because of multiple use of menus, then you probably should go for installing the "UIautomationcore.dll" file in the root FSX folder. This file can be downloaded from here: http://www.mediafire.com/?mik2mlqdz1w2. If your CTD is happening at certain occasions like accessing the GROUND menu of 767, or as soon as the airplane loads, then run the event viewer after the CTD, and find the exception code:2-1: If the exception code is something near "000005", then you probably should disable your DEP.2-2: If the exception code is something near "0000374", like mine, then - and I don't know why - you probably should uninstall MS Office package from your system!!!

I have just purchased my version of Level D 767 for FSX. I operate this on the following system:1. AMD Phenom II processor2. 6 GB of RAM3. Saphhire 5670 1GB DDR5 graphics card4. Gigabyte MB with built-in sound card5. Windows 7 - 32 bit6. FSX with Acceleration Eddition7. FSX installed in the default MS games folder8. I always run FSX in windowed mode The CTD happens with the Level D 767 sometimes as soon as the airplane loads, and ALWAYS as soon I click on the GROUND REQUESTS sub-menu. I read a lot about the UIAUTOMATIONCORE.DLL solution, and I tried it several times with several technics, but nothing worked. I ran the EVENT VIEWER tool, and I found out that the generated report is always the same with both kinds of CTDs. Below is the copies report: Log Name: ApplicationSource: Application ErrorDate: 4/28/2011 12:38:08 AMEvent ID: 1000Task Category: (100)Level: ErrorKeywords: ClassicUser: N/AComputer: islam-PC2Description:Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdadbException code: 0xc0000374Fault offset: 0x000c283bFaulting process id: 0x6a8Faulting application start time: 0x01cc0576fde6021fFaulting application path: C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\fsx.exeFaulting module path: C:\Windows\SYSTEM32\ntdll.dllReport Id: 75ac11ef-716a-11e0-be52-1c6f65a6dab2As you can see guys, the faulting module name is: ntdll.dll, version: 6.1.7600.16385.SO.... Any one has a clue now on what can I do??? Yes, get rid of that name.Thank you very much.Islam