Hello,

 

Lately i've been getting this .NET Framework error everytime i try to do a flight, 0xC000014B.

I looked in event viewer, this is what i got:

 

Process ID: 153c

Start Time: 01cfc48043983f46

Termination Time: 169

Application Path: D:\FSX\fsx.exe

Report Id: fe3c3963-3075-11e4-8639-dcdcfe3671ee

 

I have gotten 3 of these errors today alone, on a fresh copy of both windows and fsx.

I re-formatted my computer to fix this issue, but it's still here.

 

Earlier it said in the event viewer that the crash was caused by panels.dll.

 

 

I have tried the .net framework verification tool, Fsxsave, and also disabled the IVAO MTL, without any luck.

Does anyone know how to fix this problem?

 

 

Kim.

 

Does anyone know how to fix this problem?

Exception from HRESULT: 0xc000014B error - The 0xc000014B is a "broken pipe" exception. A pipe is a communication channel between two applications (such as FSX and an addon program like ASN or OPUS). SimConnect offers addons the possibility to use pipes to communication with FSX. A "broken pipe" is a situation where one of the pipes no longer exists, while the other tries to communicate using the pipe. A typical scenario would be fsx crashing and then ASN or OPUS tried to use the pipe (communications channel) and the “pipe” was broken. The 014B exception would then occur.

 

Best regards,

Exception from HRESULT: 0xc000014B error - The 0xc000014B is a "broken pipe" exception. A pipe is a communication channel between two applications (such as FSX and an addon program like ASN or OPUS). SimConnect offers addons the possibility to use pipes to communication with FSX. A "broken pipe" is a situation where one of the pipes no longer exists, while the other tries to communicate using the pipe. A typical scenario would be fsx crashing and then ASN or OPUS tried to use the pipe (communications channel) and the “pipe” was broken. The 014B exception would then occur.

 

Best regards,

Thanks for your answer, 

Do you have any suggestions to how i fix this problem?

Thanks for your answer, 

Do you have any suggestions to how i fix this problem?

When there's a communications problem (simconnect is the communicator), there is probably a sharing issue. You can try right clicking the main fsx folder and select Properties. Once open, click on the Share tab and see if the folder is being shared. If not, click on Advanced options and click on Share. The sharing should include all sub-folders but you want to make sure by going to another folder under the main fsx folder and make sure that folder is shared too. You need to make sure you do the same thing for all of the folders that have FSX addons so those textures, those modules, can communicate with FSX too.

 

Here's a link to the process with pictures which may help you if you are having problems - http://www.pcadvisor.co.uk/how-to/windows/3434911/how-share-folders-without-homegroups-in-windows-7/ .

 

As stated in the AVSIM CTD Guide, you may have to take ownership of the files too. Here's a link to that subject and how to download the neat tool that makes it easy to take ownership so that you have full control over your computer and not your computer has full control over you - http://www.addictivetips.com/windows-tips/windows-7-access-denied-permission-ownership/ .

 

Make sure port 445 is open. If File and Printer Sharing is enabled, this port will automatically be enabled and open. See this link for further information - http://windows.microsoft.com/en-us/windows-vista/enable-file-and-printer-sharing .

 

Hope this helps.

 

Best regards,

When there's a communications problem (simconnect is the communicator), there is probably a sharing issue. You can try right clicking the main fsx folder and select Properties. Once open, click on the Share tab and see if the folder is being shared. If not, click on Advanced options and click on Share. The sharing should include all sub-folders but you want to make sure by going to another folder under the main fsx folder and make sure that folder is shared too. You need to make sure you do the same thing for all of the folders that have FSX addons so those textures, those modules, can communicate with FSX too.

 

Here's a link to the process with pictures which may help you if you are having problems - http://www.pcadvisor.co.uk/how-to/windows/3434911/how-share-folders-without-homegroups-in-windows-7/ .

 

As stated in the AVSIM CTD Guide, you may have to take ownership of the files too. Here's a link to that subject and how to download the neat tool that makes it easy to take ownership so that you have full control over your computer and not your computer has full control over you - http://www.addictivetips.com/windows-tips/windows-7-access-denied-permission-ownership/ .

 

Make sure port 445 is open. If File and Printer Sharing is enabled, this port will automatically be enabled and open. See this link for further information - http://windows.microsoft.com/en-us/windows-vista/enable-file-and-printer-sharing .

 

Hope this helps.

 

Best regards,

Thank you again.

I just did some testing, and fsx ran without any problems, without vPilot and Acars running. So i guess the problem has to come from one of those programs.

Thank you again.

I just did some testing, and fsx ran without any problems, without vPilot and Acars running. So i guess the problem has to come from one of those programs.

Scratch that, did some more testing, running each of those two programs individually, still crashed both times. It also crashed with another aircraft. 

I have no idea what to do about this, and i don't understand why this is happening on a fresh copy of fsx.

I have no idea what to do about this, and i don't understand why this is happening on a fresh copy of fsx.

Your problem is with communications between fsx and programs that use simconnect (as I stated above). It has nothing to do with an aircraft or FSX. Study the instructions for installing VPilot and/or ACARS with emphasis on simconnect connections. If you are networking on another PC, make sure simconnect is installed there too. Whenever you install addons like VPilot and ACARS you take major risks on whether they will work properly or not. Most do not work out of the box and you need to do a lot of configuring. I have seen a lot of problems reported here with VPilot. Here's one - http://forum.avsim.net/topic/447885-ctd-vpilot/ . I don't even know if this guy got it worked out or not. He was starting to get different types of errors and lost focus on the VPilot crash. Hopefully you have visited the VPilot forums to see if anyone else has reported crashes with VPilot similar to yours - http://www1.metacraft.com/VRC/forums/viewforum.php?f=23 . Looks like they have an excellent troubleshooting guide too. There are several different ACARS addons so not sure which one you have installed. Some of these addons require the latest FSUIPC too as bugs are found in communications between that module and FSX addons.

 

For panels.dll error, most people have fixed this by loading the default Cessna first and then your aircraft.

 

Best regards,