Hello everyone, Sorry to bother, but I tried to fly the 737 twice over the last couple of days, but CTD on both occasions, with the following error The first box says Smartassembly - TroubleshootingThis feature requires that (smartassembly) is available on this computer Then the dreaded Netframework box... See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text **************System.Runtime.InteropServices.COMException (0xC000014B): Exception from HRESULT: 0xC000014B at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at Microsoft.FlightSimulator.SimConnect.SimConnect.ReceiveDispatch(SignalProcDelegate pfcnSignal) at Microsoft.FlightSimulator.SimConnect.SimConnect.ReceiveMessage() at rexwxengine2.controls.ucLoadAircraftLocation.DefWndProc(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.ContainerControl.WndProc(Message& m) at System.Windows.Forms.UserControl.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies **************mscorlib Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5446 (Win7SP1GDR.050727-5400) CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll----------------------------------------rexwxengine2 Assembly Version: 2.3.2010.38532 Win32 Version: 2.3.2010.1027 CodeBase: file:///C:/Program%20Files%20(x86)/Real%20Environment%20Xtreme%202.0/rexwxengine2.exe----------------------------------------System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5446 (Win7SP1GDR.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll----------------------------------------System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5447 (Win7SP1GDR.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll----------------------------------------System.Drawing Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll----------------------------------------Microsoft.FlightSimulator.SimConnect Assembly Version: 10.0.61259.0 Win32 Version: 10.0.61637.0 (FSX-Xpack.20070926-1421) CodeBase: file:///C:/Windows/assembly/GAC_32/Microsoft.FlightSimulator.SimConnect/10.0.61259.0__31bf3856ad364e35/Microsoft.FlightSimulator.SimConnect.dll----------------------------------------msvcm80 Assembly Version: 8.0.50727.6195 Win32 Version: 8.00.50727.6195 CodeBase: file:///C:/Windows/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a/msvcm80.dll----------------------------------------System.Xml Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll----------------------------------------System.Configuration Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll----------------------------------------System.Data Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll---------------------------------------- ************** JIT Debugging **************To enable just-in-time (JIT) debugging, the .config file for thisapplication or computer (machine.config) must have thejitDebugging value set in the system.windows.forms section.The application must also be compiled with debuggingenabled. For example: <configuration> Strange cause this is only recent I have had a few flights without any issue.. Will post my system specs if required.

Try flying the exact same flight again without the REX weather engine.

Hello Froze again. This time i did a return flight MEL-LST no issue but on decent into MEL froze again. I had REX OFF.

I have done this flight many times and had the CTD before but don't have it now. I took the "just get rid of it" approach and did a complete re-install and it seems to be fine now. I can't help but keep noticing the rexwxengine2 in the error. Are you sure you are using nothing from REX?

The NGX **does not use .NET or smartassembly**. Period. It is literally impossible for the NGX to crash due to either of those things - it's some other app causing the crash. The NGX is pure C++ and a bit of XML, neither of which have anything to do with .NET or smartassembly. Your error logs specifically mention REX, which is a .NET/smartassembly app and is known to cause error windows like that. Please stop blaming the NGX for things it's not responsible for. Do some research about how these error message work. A C++ app cannot give you .NET errors.

The NGX **does not use .NET or smartassembly**. Period. It is literally impossible for the NGX to crash due to either of those things - it's some other app causing the crash. The NGX is pure C++ and a bit of XML, neither of which have anything to do with .NET or smartassembly. Your error logs specifically mention REX, which is a .NET/smartassembly app and is known to cause error windows like that. Please stop blaming the NGX for things it's not responsible for. Do some research about how these error message work. A C++ app cannot give you .NET errors.

Hello, Do you think a NET update would help?

Hello, Do you think a NET update would help?

It is worth a shot, since that's the origin of the error. What OS are you on?

Win 7 64 bit6GB RamI7 960GTX 570

Brent, it all depends on what the application was programmed with. Windows 7 contains all .NET runtimes up through 3.5. 4.0 was released last year and needs to be downloaded separately or through Windows Update. The point though is that an application made with 3.5 won't run on 4.0. 4.0 doesn't contain all previous versions, you have to have what the application actually needs. REX was done with .NET 2.0, so that's definitely already there in Win7.

Brent, it all depends on what the application was programmed with. Windows 7 contains all .NET runtimes up through 3.5. 4.0 was released last year and needs to be downloaded separately or through Windows Update. The point though is that an application made with 3.5 won't run on 4.0. 4.0 doesn't contain all previous versions, you have to have what the application actually needs. REX was done with .NET 2.0, so that's definitely already there in Win7.

No drama Ryan - Thx for the input.Next time FS freezes, I will take a look at the system log. Could be something else if I am not using REX at all. Anyway, may report over the weekend. Brent

Hi Little update - I did download the 14 day trial of smart assembly and it has not frozen - so hopefully this may fix. Also, I believe it may be related to Ultimate Traffic, so if the smart assembly fix does not work, i will look into the procedures on fixing the uiautomationcore.dll file which I am aware some users are having FS CTD by this file. Thats all for this morning.

I am about 60% sure that you have a corrupt SimConnect installation. What has caused the corruption is anyones' guess although it sometimes happens when FSX doesn't shut down properly. I have experienced 'Smart Assembly' errors before, and I use Ultimate traffic. Its true that UT uses Smart Assembly but so do many other developers, so I am not sure that you can point the finger in that direction. Utimate traffic appears to take the blame because it is one of the first add-ons to load and inevitable falls foul of a corrupt Simconnect with a 'smart assembly' error when when it can't load. .REX may have failed in a similar way -i.e tried to load but hit a corrupt Sim Connect (I also use REX) but it doen't mean that REX caused it and Its definitely nothing to do with the NGX. Unfortunately Sim Connect has a reputation in the developer community for being the 'Achiles heel' of FSX and corruption is an all too frequent event. If I am right, you will experience ongoing stabilty problems and CTDs and the faulting module will vary. It will carry on until FSX is unusable unless you fix it. It is possible to run a repair and its worked for me in the past (although on one occasion I had to undertake a complete re- install after manually clearing out the Sim connect entries in the windows directly as an FSX re-install doesn't overwrite the corrupted files (another Achiles heel). This was not easy with 11GB of add ons (thank God I have full backups). Have a look at this threadhttp://forum.avsim.net/topic/323016-smart-assembly-ctd/ This link is also very helpful - it certainly helped me. http://forum.ivao.aero/index.php?topic=95115.0 Somebody has also had succes with reinstalling the C++ 2008 libraries -although I don't understand why. Be wary of the UIAutomation core 'fix' that is being peddled on the internet. In my opinion, there is a lot of snake oi with tihs one, particularly the bit about 'removing the 64bit version from Windows' - BAD MOVE. The problems with this DLL arise because there are different versions for win7 64 bit, win732 bit and Vista32 bit. .FSX needs the 32 bit Vista version (it doesn't know anything about windows 7 because it was developed before Win7 was released) . When FSX loads, it searches the directory structure in sequence for what it needs - it will look in the FSX subdirectory first and if it finds the UIAUTOMATION.DLL in here it will use it, (this is one of the reasons , If you are running a 64 bit Window7 system, it keeps 32 bit applications in a seperate folder called programes X86 - so it can load software with 32bit dlls and not 64 bit dlls which will be in 'programs directory)' . Put the 32 bit vista version of the dll in the FSX root folder and you shouldn't have a problem (you don't need to register it - more disinformation). The assertion that this dll causes other dlls to fail also seems ill-informed to me (I have used this fix it for years with no problems) although I can understsnd how using the wrong version of this dll or fiddling with the dlls in the windows directory in an unifomed way can cause problems. Also, if you are unfortunate enough to have to go through an FSX reinstall and you are running Windows 7, put FSX in a folder other than 'Programs' or ProgramsX86' (if you have not already done so) and you will experience fewer problem. Mine runs on a seperate drive entirely. I hope that this helps you and good luck