Sign in to follow this  
leak91

HRESULT: 0xC000014B CTD

Recommended Posts

Hi Jim!

 

I did everything you said and keep getting the undhandled exceptions :( I looked at the windows event log and also saw that FSX tries to disable the Desktop Window Manager, maybe its related? Don't really know what to do, since ive disabled UAC and shared all the folders related to FSUIPC and all addons... Anyways, here is both the unhandled exception and the error description that i find in the windows event log right before it logs FSX trying to close the Desktop Window Manager:

 

 

************** 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 FSXWX.Form1.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.Form.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.5485 (Win7SP1GDR.050727-5400)

    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll

----------------------------------------

FSXWX

    Assembly Version: 1.0.0.0

    Win32 Version: 1.0.0.0

    CodeBase: file:///C:/Users/Lyonel%20Aguilar/Desktop/FSX%20stuff/FSXWX/FSXWX.exe

----------------------------------------

System.Windows.Forms

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5491 (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.8686 (QFE.050727-8600)

    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.5495 (Win7SP1GDR.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.Core

    Assembly Version: 3.5.0.0

    Win32 Version: 3.5.30729.5420 built by: Win7SP1

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll

----------------------------------------

System.Configuration

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

----------------------------------------

System.Xml

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5494 (Win7SP1GDR.050727-5400)

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll

----------------------------------------

 

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

 

For example:

 

<configuration>

    <system.windows.forms jitDebugging="true" />

</configuration>

 

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.

 

 

 

Fault bucket 53152480, type 27

Event Name: BEX

Response: Not available

Cab Id: 0

 

Problem signature:

P1: fsx.exe

P2: 10.0.62615.0

P3: 559f9a9a

P4: MSVCR100.dll

P5: 10.0.40219.325

P6: 4df2be1e

P7: 0008af3e

P8: c0000417

P9: 00000000

P10:

 

Attached files:

C:\Users\Lyonel Aguilar\AppData\Local\Temp\WERFAA3.tmp.WERInternalMetadata.xml

C:\Users\Lyonel Aguilar\AppData\Local\Temp\WER64D.tmp.appcompat.txt

C:\Users\Lyonel Aguilar\AppData\Local\Temp\WERBAD.tmp.mdmp

 

These files may be available here:

C:\Users\Lyonel Aguilar\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_b7e0bfec1d0fa7777e37948a9e8d514f9471_061045f4

 

Analysis symbol:

Rechecking for solution: 0

Report Id: b30e3319-b0fb-11e6-9cd7-0025228a2f52

Report Status: 9

 

Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a

Faulting module name: MSVCR100.dll, version: 10.0.40219.325, time stamp: 0x4df2be1e

Exception code: 0xc0000417

Fault offset: 0x0008af3e

Faulting process id: 0x16e4

Faulting application start time: 0x01d244fc232b5fdb

Faulting application path: C:\Steem\steamapps\common\FSX\fsx.exe

Faulting module path: C:\Windows\system32\MSVCR100.dll

Report Id: b30e3319-b0fb-11e6-9cd7-0025228a2f52

 

 

   53152480

   27

   BEX

   Not available

   0 

fsx.exe

   10.0.62615.0

   559f9a9a

   MSVCR100.dll

   10.0.40219.325

   4df2be1e

   c0000417

   0008af3e

   16e4

   01d244fc232b5fdb

   C:\Steem\steamapps\common\FSX\fsx.exe

   C:\Windows\system32\MSVCR100.dll

   b30e3319-b0fb-11e6-9cd7-0025228a2f52

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

I looked at the windows event log and also saw that FSX tries to disable the Desktop Window Manager

 

This is normal and must happen whenever you start up FSX.

 

I would uninstall FSXWX until you get all of your problems fixed as it is not communicating properly with FSX.

 

The faulting module (MSVCR100.dll) belongs to Microsoft Visual C++ Redistributable 2010.  This is installed when you install FSX-SE.  See page 33 of the AVSIM CTD Guide regarding this error and how to fix it.  I would run the Microsoft.net Repair Tool as explained in the AVSIM CTD Guide.

 

You also had Exception Code 0417 which means an illegal parameter was passed to the C++Runtime Function.  You do have Microsoft Visual C++2005 w/SP1 installed right?

 

Hopefully the actions above will fix this issue for you.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

By the way,there are some changes in fsx.cfg that FSXWX recommends in order to e.g have more realistick turbulence effects on the 737NGX and more realistic cloud spread, etc. Should I reverse them when I uninstall FSXWX or can I keep them in order to add some realism? (So that turbulence doesn't for example affect the NGX in a completely exaggerated way)

Share this post


Link to post
Share on other sites

By the way,there are some changes in fsx.cfg that FSXWX recommends in order to e.g have more realistick turbulence effects on the 737NGX and more realistic cloud spread, etc. Should I reverse them when I uninstall FSXWX or can I keep them in order to add some realism? (So that turbulence doesn't for example affect the NGX in a completely exaggerated way)

I have no idea as I do not have that weather program but maybe someone who has it installed here at AVSIM can help you.  For now, I would just comment the items out of your fsx.cfg until you get your crashes fixed.  When you comment something out of the FSX.cfg, just place two slashes // in front of the parameter (i.e., //highmemfix=1). The item will not load.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

So I solved my MSVCR100 problem but got some ndll problem or something (can't remember the exact name, am in the subway on my way to work atm...). I followed the avsim guide and updated my drivers. It's gotten better :-)

Share this post


Link to post
Share on other sites

Sounds good.  The NTDLL.dll error is common.  I am currently getting them constantly myself but with P3D.  I use to get 30-40 fps in FTX/Orbx Southern California.  Suddenly I'm only getting 12 - 13 fps.  If I get rid of all of the modules being loaded by the dll.xml, it relieves the stress on the sim.  If I go to settings and try to change them, the sim freezes up.  So something is horribly amiss and it could be a bug (virus) or something that is constantly running in the background causing my system to use an enormous amount of resources that is needed by the sim. 

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

FYI, I fixed my NTDLL.dll errors.  My FSUIPC.dll was not up-to-date and was not loading properly.  Secondly, my video card drivers were up-to-date but evidently not installed properly.  I reinstalled them with Admin Rights.  My latest FSUIPC log of my flight from KPSP to KLAX shows the following:

 

Minimum frame rate was 9.9 fps, Maximum was 48.4 fps
Minimum available memory recorded was 689Mb
Average frame rate for running time of 2270 secs = 23.9 fps

Maximum AI traffic for session was 192 aircraft
Memory managed: 643 Allocs, 643 Freed

********* FSUIPC Log file closed ***********

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

FYI, I fixed my NTDLL.dll errors.  My FSUIPC.dll was not up-to-date and was not loading properly.  Secondly, my video card drivers were up-to-date but evidently not installed properly.  I reinstalled them with Admin Rights.  My latest FSUIPC log of my flight from KPSP to KLAX shows the following:

 

Minimum frame rate was 9.9 fps, Maximum was 48.4 fpsMinimum available memory recorded was 689Mb

Average frame rate for running time of 2270 secs = 23.9 fpsMaximum AI traffic for session was 192 aircraft

Memory managed: 643 Allocs, 643 Freed

********* FSUIPC Log file closed ***********

 

Best regards,

Jim

HI Jim! Where can you find the latest fsuipc? Been looking for it but I always find the one that's a few years old (maybe that's the one). Which one are you using? (So I can compare when I get on the sim)

 

Regards,

Lyo

Share this post


Link to post
Share on other sites

HI Jim! Where can you find the latest fsuipc? Been looking for it but I always find the one that's a few years old (maybe that's the one). Which one are you using? (So I can compare when I get on the sim)

 

Regards,

Lyo

You can find it here - http://www.schiratti.com/dowson.html.  I actually thought I had the hotfix to the latest version of P3D but did not and that will cause an ntdll.dll error, not all of the time but occasionally.  That's the strange thing about fsx/p3d.  The sims work occasionally even with corrupted or missing modules or high settings or bad tweaks so, when things go bad, you have a difficult time figuring out what caused it.

 

Just a little update to my comments above... there is a major issue in the LAX area that dramatically drops fps and eats VAS like crazy.  I removed FSDT KLAX and used the one that comes with SoCal (or the default that comes with P3D) and it brought down my system just as much.  Leave that area and things are okay.  I think I need to edit the control panel for Orbx SoCal and turn the eye-candy off.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

 

 

You also had Exception Code 0417 which means an illegal parameter was passed to the C++Runtime Function.  You do have Microsoft Visual C++2005 w/SP1 installed right?

 

Hopefully the actions above will fix this issue for you.

 

Best regards,

Jim

 

Hey Jim! I got another MSVCR100 problem, and noticed that the exception code: 0xc0000417 was still there. I reinstalled my microsoft visual c++ 2005 sp1 and also installed the basic version (without sp1). I did this since it was allowed by the installers, as opposed to the other microsoft visuals (which didnt let me install "basic" versions once the sp1 versions were installed). Do you think it was right to do so or that I should only keep the sp1 versions?

 

Best regards,

Lyonel

Share this post


Link to post
Share on other sites

MSVCR100 is used by Dovetail Games and others to make sure FSX-SE was installed correctly.  I know FSDT uses the MSVCR100 too.  In fact many addon developers have been using the MSVCR100 (Microsoft Visual C++2010) to get their product installed properly.  If a product is not installed properly, a C++ runtime error will occur.  Since so many addon developers use Microsoft Visual C++2010, you have to figure out which addon caused your problem.  It could be an airport scenery, an Orbx/FTX scenery, a PMDG aircraft.... well, many products.

 

If you look on page 25, AVSIM CTD Guide, I show you what Microsoft Visuals should be installed and the version numbers.  There's a picture of my add/remove programs.  The version numbers should be the same or higher.  If you have the same or higher version of Microsoft Visual 2005 w/SP1, then you have SP1 installed.  MSV 2005 w/SP1 was required before or after FSX SP2 or Acceleration was installed.  As I stated earlier, this MSV and MSV 2008 should have been installed by Dovetail when you installed FSX-SE.  So I doubt you have a bad installation of your MSV 2005 w/SP1 or a MSV 2010.  One of the many components of MSV 2010 could be corrupted somehow though.  This is why I recommended running the Microsoft.net repair tool shown on page 25/26 of the CTD Guide.

 

The most important thing to look at in an error report such as the Event Viewer or the AppCrashView program is the faulting module.  It provides a clue as to what went wrong.  Do not know why Microsoft did that (provide a clue showing the faulting module and exception codes).  Of course I'm being silly.  They did it on purpose.  Unfortunately, all of the other stuff in a crash report is gobblygook.  A tech sitting at your computer might figure it out but a lot of it shows memory addresses where the fault occurs, etc.

 

As far a determining which addon might be causing your problems, you need to move your fsx.cfg, dll.xml, exe.xml, and scenery.cfg to a temporary directory.  I discuss this on page 10 of the AVSIM CTD Guide.  You can also mess around with the dll.xml (the thingy that loads modules) and disable them, then enable them one by one until the crash reoccurs.  When you move the scenery.cfg to a temporary directory, it is rebuilt by FSX-SE with the default scenery.cfg.  Perhaps one of those FSDT airports is not working properly or one of the Orbx/FTX airports (just guessing as I have no idea what you have installed).  Rebuilding the scenery.cfg gives you a quick idea if it is one of the sceneries.  If it is not one of the sceneries and the crashes still occur, then move your old scenery.cfg back and your add-on scenery will be back.  It is the only way I know of to quickly ascertain what might have caused FSX-SE to crash.

 

There are other simple things you can do too or check.  Many problems are associated with admin privileges.  If you do not have all of the required privileges, FSX-SE may not run properly as some needed component needs a module or file and you do not have access to that needed component.

 

It's all getting close to just starting over.  Uninstall FSX-SE, shutdown and restart your computer, run a registry cleaning program like CCleaner, make sure the folders that held the FSX.cfg and Scenery.cfg are deleted, then reinstall FSX-SE.  Run it at least once before you install an add-on and each time after you install an add-on just to make sure that add-on is running properly.

 

Hope this helps.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

MSVCR100 is used by Dovetail Games and others to make sure FSX-SE was installed correctly.  I know FSDT uses the MSVCR100 too.  In fact many addon developers have been using the MSVCR100 (Microsoft Visual C++2010) to get their product installed properly.  If a product is not installed properly, a C++ runtime error will occur.  Since so many addon developers use Microsoft Visual C++2010, you have to figure out which addon caused your problem.  It could be an airport scenery, an Orbx/FTX scenery, a PMDG aircraft.... well, many products.

 

If you look on page 25, AVSIM CTD Guide, I show you what Microsoft Visuals should be installed and the version numbers.  There's a picture of my add/remove programs.  The version numbers should be the same or higher.  If you have the same or higher version of Microsoft Visual 2005 w/SP1, then you have SP1 installed.  MSV 2005 w/SP1 was required before or after FSX SP2 or Acceleration was installed.  As I stated earlier, this MSV and MSV 2008 should have been installed by Dovetail when you installed FSX-SE.  So I doubt you have a bad installation of your MSV 2005 w/SP1 or a MSV 2010.  One of the many components of MSV 2010 could be corrupted somehow though.  This is why I recommended running the Microsoft.net repair tool shown on page 25/26 of the CTD Guide.

 

The most important thing to look at in an error report such as the Event Viewer or the AppCrashView program is the faulting module.  It provides a clue as to what went wrong.  Do not know why Microsoft did that (provide a clue showing the faulting module and exception codes).  Of course I'm being silly.  They did it on purpose.  Unfortunately, all of the other stuff in a crash report is gobblygook.  A tech sitting at your computer might figure it out but a lot of it shows memory addresses where the fault occurs, etc.

 

As far a determining which addon might be causing your problems, you need to move your fsx.cfg, dll.xml, exe.xml, and scenery.cfg to a temporary directory.  I discuss this on page 10 of the AVSIM CTD Guide.  You can also mess around with the dll.xml (the thingy that loads modules) and disable them, then enable them one by one until the crash reoccurs.  When you move the scenery.cfg to a temporary directory, it is rebuilt by FSX-SE with the default scenery.cfg.  Perhaps one of those FSDT airports is not working properly or one of the Orbx/FTX airports (just guessing as I have no idea what you have installed).  Rebuilding the scenery.cfg gives you a quick idea if it is one of the sceneries.  If it is not one of the sceneries and the crashes still occur, then move your old scenery.cfg back and your add-on scenery will be back.  It is the only way I know of to quickly ascertain what might have caused FSX-SE to crash.

 

There are other simple things you can do too or check.  Many problems are associated with admin privileges.  If you do not have all of the required privileges, FSX-SE may not run properly as some needed component needs a module or file and you do not have access to that needed component.

 

It's all getting close to just starting over.  Uninstall FSX-SE, shutdown and restart your computer, run a registry cleaning program like CCleaner, make sure the folders that held the FSX.cfg and Scenery.cfg are deleted, then reinstall FSX-SE.  Run it at least once before you install an add-on and each time after you install an add-on just to make sure that add-on is running properly.

 

Hope this helps.

 

Best regards,

Jim

Thanks Jim, I'll experiment a bit and see what happens!

MSVCR100 is used by Dovetail Games and others to make sure FSX-SE was installed correctly.  I know FSDT uses the MSVCR100 too.  In fact many addon developers have been using the MSVCR100 (Microsoft Visual C++2010) to get their product installed properly.  If a product is not installed properly, a C++ runtime error will occur.  Since so many addon developers use Microsoft Visual C++2010, you have to figure out which addon caused your problem.  It could be an airport scenery, an Orbx/FTX scenery, a PMDG aircraft.... well, many products.

 

If you look on page 25, AVSIM CTD Guide, I show you what Microsoft Visuals should be installed and the version numbers.  There's a picture of my add/remove programs.  The version numbers should be the same or higher.  If you have the same or higher version of Microsoft Visual 2005 w/SP1, then you have SP1 installed.  MSV 2005 w/SP1 was required before or after FSX SP2 or Acceleration was installed.  As I stated earlier, this MSV and MSV 2008 should have been installed by Dovetail when you installed FSX-SE.  So I doubt you have a bad installation of your MSV 2005 w/SP1 or a MSV 2010.  One of the many components of MSV 2010 could be corrupted somehow though.  This is why I recommended running the Microsoft.net repair tool shown on page 25/26 of the CTD Guide.

 

The most important thing to look at in an error report such as the Event Viewer or the AppCrashView program is the faulting module.  It provides a clue as to what went wrong.  Do not know why Microsoft did that (provide a clue showing the faulting module and exception codes).  Of course I'm being silly.  They did it on purpose.  Unfortunately, all of the other stuff in a crash report is gobblygook.  A tech sitting at your computer might figure it out but a lot of it shows memory addresses where the fault occurs, etc.

 

As far a determining which addon might be causing your problems, you need to move your fsx.cfg, dll.xml, exe.xml, and scenery.cfg to a temporary directory.  I discuss this on page 10 of the AVSIM CTD Guide.  You can also mess around with the dll.xml (the thingy that loads modules) and disable them, then enable them one by one until the crash reoccurs.  When you move the scenery.cfg to a temporary directory, it is rebuilt by FSX-SE with the default scenery.cfg.  Perhaps one of those FSDT airports is not working properly or one of the Orbx/FTX airports (just guessing as I have no idea what you have installed).  Rebuilding the scenery.cfg gives you a quick idea if it is one of the sceneries.  If it is not one of the sceneries and the crashes still occur, then move your old scenery.cfg back and your add-on scenery will be back.  It is the only way I know of to quickly ascertain what might have caused FSX-SE to crash.

 

There are other simple things you can do too or check.  Many problems are associated with admin privileges.  If you do not have all of the required privileges, FSX-SE may not run properly as some needed component needs a module or file and you do not have access to that needed component.

 

It's all getting close to just starting over.  Uninstall FSX-SE, shutdown and restart your computer, run a registry cleaning program like CCleaner, make sure the folders that held the FSX.cfg and Scenery.cfg are deleted, then reinstall FSX-SE.  Run it at least once before you install an add-on and each time after you install an add-on just to make sure that add-on is running properly.

 

Hope this helps.

 

Best regards,

Jim

By the way Jim, I'm pretty sure of which addon is creating the problem. I believe it's fsxwx, since it's always mentioned somewhere in error reports (the one that is not event viewer). It's either that or AI smooth... so I was thinking I'd try to solve it by fixing the module (I did run the repair tool, but yeah...). I'm thinking I might get an earlier version of fsxwx since the newer ones, while still compatible, are only tested in prepared3d..

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this