+- Forums (https://www.fsxwx.com/mybb)
+-- Forum: Categories (https://www.fsxwx.com/mybb/forumdisplay.php?fid=3)
+--- Forum: Discussions (https://www.fsxwx.com/mybb/forumdisplay.php?fid=5)
+--- Thread: Microsoft .NET Framework unhandled exception (/showthread.php?tid=80)
Microsoft .NET Framework unhandled exception - bashope - 2016-03-28
Hi there,
Lately I've been getting a lot of Microsoft .NET Framework unhandled exceptions. It has been preventing me from successfully completing flights :(
I'll paste the log here hoping it might help. Thanks a lot. This is my favorite weather engine.
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 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.8670 (QFE.050727-8600)
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:///F:/Bruno/Downloads/Flying/Utils/FSXWX/FSXWX.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
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.8670 (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.8681 (QFE.050727-8600)
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.9193
Win32 Version: 8.00.50727.9193
CodeBase: file:///C:/WINDOWS/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9193_none_d09188224426efcd/msvcm80.dll
----------------------------------------
System.Core
Assembly Version: 3.5.0.0
Win32 Version: 3.5.30729.8693 built by: QFE
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.8670 (QFE.050727-8600)
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.8679 (QFE.050727-8600)
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.
Microsoft .NET Framework unhandled exception - fsxwx - 2016-03-29
Thanks for reporting. There was a similiar crash reported recently and I will certainly try to trace this problem.
Sorry for not having a direct answer or solution...
Anyway: Can you give some details when, where and under what circumstances you experienced the crash? It would be really insightful to reproduce such a crash myself.
Microsoft .NET Framework unhandled exception - bashope - 2016-03-30
Don't thank me, I'm the one who should thank you. This weather engine is THE BEST. And I'm trying it right now at LPMA, very strong gusts tonight yahooo :)
Unfortunately there's not a lot more information I can give you about it... It happened a couple of times already (with 1.5.3, not with 1.5.4 yet). Flying online on IVAP and with the TAV virtual airline ACARS (TAPLog).
This is the only configuration where it has crashed yet.
If it happens again I'll post the log again and advise on the configuration.
Maybe you could include in the executable an option to create some verbose logging that could help in these situations?
Cheers!! Thanks again.
Microsoft .NET Framework unhandled exception - toggernet - 2016-03-31
Probably not the same cause, but I get .NET crashes (listing various FSX modules) when another CPU/HDD intensive program is running at the same time as FSX or if I've left my power plan on anything other than 100% min and max processor state (turbo CPU), and also when my HDD is heavily fragmented. Quad core 4.4ghz i5 4690K, GeForce GTX 760 2GB
Microsoft .NET Framework unhandled exception - bashope - 2016-04-07
And again :(
Flying from GCLP to LPMA. Connected to IVAO but not to TAPv acars.
I hope this helps!
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 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.8670 (QFE.050727-8600)
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:///F:/Bruno/Downloads/Flying/Utils/FSXWX/FSXWX.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
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.8670 (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.8681 (QFE.050727-8600)
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.9193
Win32 Version: 8.00.50727.9193
CodeBase: file:///C:/WINDOWS/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9193_none_d09188224426efcd/msvcm80.dll
----------------------------------------
System.Core
Assembly Version: 3.5.0.0
Win32 Version: 3.5.30729.8693 built by: QFE
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.8670 (QFE.050727-8600)
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.8679 (QFE.050727-8600)
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.
Microsoft .NET Framework unhandled exception - bashope - 2016-04-20
Happened yet again last night... at the end of a 3 hour flight :( Very frustrating.
Do the logs help at all? Should I keep providing them or is it useless at this point?
Thank you!!
PS: I'm very excited about the new simulators from dovetail. I have pre-ordered Flight School. 64 bit, directx 11, and they have a partnership with ORBX. I have a feeling they are well positioned to be the new "de facto" flying simulator. If they partner with aerosoft as well, game over :)
Cheers!
Microsoft .NET Framework unhandled exception - bashope - 2016-04-23
Ok, I have news.
It looks like it might be completely unrelated to FSXWX. A friend of mine advised me that it could be because of the file UIAutomationcore.dll.
There's a fix somewhere on "da web". Just google it. So far, it looks like this fixed it for me. I just wanted to share in case someone else is having similar trouble.
Cheers!
Microsoft .NET Framework unhandled exception - fsxwx - 2016-04-24
bashope Wrote:Do the logs help at all?Yes and no. They give a hint, but they don't reveal the culprit. Thanks anyway!
FSX has a a million reasons to crash ... ;-) And everytime the Simconnect connection is lost/crashes, it brings down FSXWX, too.
Indeed, the UIAutomationcore.dll is one reason for FSX to crash. As a matter fact, I also used an alternative version all the time.
I really hope that this is the solution for your troubles. Let me known if another crash will occur that could be related to FSXWX.
Microsoft .NET Framework unhandled exception - toggernet - 2016-04-25
Disabling problem reporting seems to help as well (the popup that shows an application needs to close / looking for solution, when it crashes).
Control Panel\All Control Panel Items\Action Center\Problem Reporting Settings > Never check
The popup still appears but if you ignore it, it normally stops showing the "crashed" dimmed background after a few seconds and returns to normal.
Also clicking continue instead of quit on the ms.net crashed popup appears to help, but othertimes it needs a reboot.
.....................
I've tested this again with problem reporting enabled and it appears that this makes "crashes" unrecoverable! , its looking for a solution and forces FSX to close, period.
With problem reporting disabled, whilst the popup still appears (removable via registry edits - Google it) if you ignore it, FSX recovers in a few seconds and doesn't need to close.
"So it looks like in most cases (on my system at least) FSX hasn't actually crashed, its windows that thinks its crashed (like its timed out too early running a piece of code, FSX being CPU hungry) then has no solution, so forces closure."
Microsoft .NET Framework unhandled exception - emolina - 2017-03-28
Just a quick data point. I've just installed fsxwx for the first time and had this problem.
I fixed it by changing the 'time' option to 'current'.
Microsoft .NET Framework unhandled exception - collique - 2018-11-17
emolina Wrote:Just a quick data point. I've just installed fsxwx for the first time and had this problem.
I fixed it by changing the 'time' option to 'current'.
Thanks emolina
Microsoft .NET Framework unhandled exception - flyboy - 2019-04-24
Try changing you time from SIM to CURRENT. This worked for me. This is a fantastic app for weather generation. I find it quite realistic and promote it at every opportunity. I am using FSX on Windows 10
Microsoft .NET Framework unhandled exception - sagarks201 - 2020-05-10
I started getting the same error on version 1.6.1 on FSX when using the current time and both my sim the fsxwx will crash 2 :30 hrs into the flight