June 17, 201213 yr Found this: http://answers.microsoft.com/en-us/windows/forum/windows_other-gaming/whilt-playing-flight-sim-fsx-received-error-net/3f4d8949-09d3-4135-ab66-e09316a34b91 and this from firehawk44 :"The exception code 14b indicates your system is under a lot of strain and using too many computer resources. FSX, with sliders set high can do this, even moderately high depending on what you are flying and where you are flying. REX Overdrive can also be a real killer for systems like yours and mine. Personally I'm going to wait to install anything "REX" until I update my system. It does look like an awesome program though! If you have the real weather systems running on your computer, FSX may work for a bit but will eventually crash or turn into a slide show as the real weather programs, even the default, can bring a mediocre system down to its knees and the latest and greatest systems working much harder than usual after awhile. This is why I very rarely use real weather especially if I'm using commercial payware aircraft or flying into areas that have photoscenery. Smart Assembly is an error belonging to the dotnet framework. You should have Version 4.0 installed (check your list of installed programs)and, if not, update the program. If you do have it installed, it evidently did not install correctly. Just goto the dotnet website and download the latest version and reinstall it (you may have to uninstall the one sitting on your system first). It fixed the Smart Assembly error for someone else here on AVSIM by reinstalling Version 4.0 and it should work for you too. I would also uninstall REX and see if the error occurs again. Via Google, most of the people who got the 14b exception error blamed it on REX and it turned out to be too much for their system. Hope this helps!EDIT: Forgot to add that according to Google, the exception code 14b is also related to an old version of the dotnet framework." Try searching here in AvSim or at Google using the line "exception from hresult:0xc000014b". You will get many hits. Joe Brown
June 17, 201213 yr Never mind, It looked like a C000148 not C00014B on my screen, so the link I had won't help you sorry!! Thanks Tom My Youtube Videos! http://www.youtube.com/user/tf51d
June 17, 201213 yr I still think that's a .net framework issue... I'd install 3.5 and 4.0 3.5 - http://www.microsoft.com/en-us/download/details.aspx?id=21 4.0 - http://www.microsoft.com/en-us/download/details.aspx?id=17851 | My Liveries | FAA ZMP | PPL ASEL | | Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |
June 17, 201213 yr Author I uninstalled all of my framework and then installed 4.0 and i haven't gotten the error since then. I'll see how it goes cause I just randomly would get the error. Jerad Burns
Create an account or sign in to comment