strider Posted October 29, 2018 Report Posted October 29, 2018 2018-10-28 17:06:45 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000 Quote
Martin_1970 Posted October 29, 2018 Report Posted October 29, 2018 (edited) Hello, i get the CTD with the same log entry, ...often (startet 20 Flights, but could only finish 4, 16 CDT) This is the only entry in the log concerning the CTD: 2018-10-29 17:25:08 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000 No crash_report from X-plane or windows. The crash is more like "someone closes the application" For the question about conflicting plugins: I tested the aircraft on my secondary, clean, xplane installation, and there i get the crashes too Find attached the logfile from the "clean installation" crash. If i could help in finding this bug, please tell me. It is very frustrating to have this really cool aircraft and then it crashes so often Some question to the other guys with CDT issues: When you crash: - Do you have "NEXRAD" activated in the MAP settings of the G1000? - Do you use some kind of dynamic weather, e.g: built in "Match real world conditions" or something like xEnviro, FS_Global_Real_Weather or something else what changes the weather? - Do you have the G1000 weather radar activated? I have the feeling the bug could be located in the weather change, but i´m not sure (have to do more tests...) regards, Martin edit: during writing this post, another crash in my "unclean" installation happened, and i got a debug.log this time. Hope this helps Log.txt debug.log Log_plugins.txt Edited October 29, 2018 by Martin_1970 Quote
docpan Posted October 29, 2018 Report Posted October 29, 2018 I have the same error: 2018-10-29 21:04:40 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000 several times... Quote
skiselkov Posted October 29, 2018 Report Posted October 29, 2018 That just means some other plugin has called the SetUnhandledExceptionFilter function and replaced the crash handler function of the TBM with their own. This crash handler function is used by the TBM avionics to generate debug traces so we can debug issues. Without a debug trace, there's nothing we can do. This is caused by one of your plugins. If you can recreate the issue, please try removing other plugins besides Gizmo from the plugins folder (e.g. by moving them to another location temporarily). If you then cause the sim to crash, it should produce a usable stack trace that we can use to debug the issue. Quote
Martin_1970 Posted October 30, 2018 Report Posted October 30, 2018 (edited) Hi, sorry for repeating my post but: I tried it on a clean xplane installation, this means there are no other plugins. And i get the CTD there too. How can i produce / where to find the stack trace ? Update: Crashed again on the clean installation logfile added. You can see there are no other plungins installed than yours. Log.txt Edited October 30, 2018 by Martin_1970 added log 1 Quote
mcritzman Posted October 30, 2018 Report Posted October 30, 2018 17 hours ago, docpan said: I have the same error: 2018-10-29 21:04:40 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000 several times... + 1 for that same error. Log 10.29.18 CTD.txt Quote
Floater Posted October 31, 2018 Report Posted October 31, 2018 First CTD since I own the TBM Log.txt Quote
Tassierob Posted October 31, 2018 Report Posted October 31, 2018 2 hours ago, Floater said: First CTD since I own the TBM Log.txt Interesting. It is exactly the same error I had when it crashed on me. Were you by chance playing with the G1000 while in the air? That is when mine happened. Quote
Floater Posted October 31, 2018 Report Posted October 31, 2018 (edited) Nope. Just lined up in EGLC and moved the throttle the first centimeters to set T/O thrust. Ps. rebooted X-Plane and done the same flight without any problem Edited October 31, 2018 by Floater Quote
wodyfox Posted October 31, 2018 Report Posted October 31, 2018 Yesterday also had my 1st CTD. I was at FL260 and changing something in the G1000. Forgot to save the log. Quote
stolowski Posted October 31, 2018 Report Posted October 31, 2018 @skiselkovI think no plugins, including TBM, should install global signal/error (SIGSEGV?) handlers and expect them to work in a reliable manner, it goes beyond any promises made by X-Plane SDK, and is generally true for any software where plugins (dynamic libraries) are used to extend base functionality. I think this crash report from clean XP installation proves it - it can very well be X-Plane itself resetting the handler for whatever reason. By the way, XP generates crash reports for Visual Studio in Output/crashreports directory, I wonder if they could be useful if TBM plugins were compiled with debug symbols? On 10/30/2018 at 9:00 AM, Martin_1970 said: Hi, sorry for repeating my post but: I tried it on a clean xplane installation, this means there are no other plugins. And i get the CTD there too. How can i produce / where to find the stack trace ? Update: Crashed again on the clean installation logfile added. You can see there are no other plungins installed than yours. Log.txt Quote
Martin_1970 Posted October 31, 2018 Report Posted October 31, 2018 Hi, thanks for the reply. As this kind of crash even doesn´t create a report in /output/crah_reports and even windows itself doesn´t report something like "...has stopped working" i think i can only wait and hope for the best. I aggree with you it could also be a problem of X-plane itself, maybe you use a feature, no other aircraft used before? who knows. As some other user have similar CTD (but a little bit different) with some more information / backtrace, maybe this CTD is fixed if you could fix the other CDT. I hope so, because i can´t use the aircraft in this state. I hope for 1.0.9 Quote
hb-hez Posted October 31, 2018 Report Posted October 31, 2018 clean install, same plugins as Martin_1970, just had a CTD: 2018-10-31 21:23:13 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000 Quote
Martin_1970 Posted October 31, 2018 Report Posted October 31, 2018 Hi, i found a way, to reproduce another CTD: 0:01:23.082 D/ATC: Validating altitude for p=1 (N01XP): filed: 36000 usable_rte_dist: 438.638519 maxDescent: 109000 maxAlt: 109000 minAlt: 36000 chosen_alt: 36000 0:01:23.082 D/ATC: p=1 (N01XP): Cleared IFR 0:01:23.082 D/ATC: p=1 (N01XP): Squawk 4701 0:01:23.199 D/ATC: p=1 (N01XP): Taxi (23 points issued) G64: 83.507: Plugin Disabled. 0:01:25.808 D/ATC: p=2 (N02XP): Fly Heading: 214 0:01:25.808 D/ATC: p=2 (N02XP): Maintain 1998ft G64: 87.298: Boot Count: 3 G64: 89.920: Plugin Enabled. G64: 98.897: Boot Count: 4 G64: 101.511: Run: OnKickStart.. 2018-10-31 22:39:44 TBM900[except.c:171]: Caught EXCEPTION_ACCESS_VIOLATION Backtrace is: 0 00007FF978E4BCF0 C:\WINDOWS\System32\KERNELBASE.dll+ebcf0 () 1 00007FF97BE02717 C:\WINDOWS\SYSTEM32\ntdll.dll+a2717 () 2 00007FF97BDEAB36 C:\WINDOWS\SYSTEM32\ntdll.dll+8ab36 () 3 00007FF97BDFED2D C:\WINDOWS\SYSTEM32\ntdll.dll+9ed2d () 4 00007FF97BD66C86 C:\WINDOWS\SYSTEM32\ntdll.dll+6c86 () 5 00007FF97BDFDC5E C:\WINDOWS\SYSTEM32\ntdll.dll+9dc5e () 6 00007FF63FC15467 D:\X-Plane 11\X-Plane.exe+ef5467 () 7 00007FF63F6F4A6E D:\X-Plane 11\X-Plane.exe+9d4a6e () 8 00007FF63F6F6FE0 D:\X-Plane 11\X-Plane.exe+9d6fe0 () 9 00007FF96DCD158A D:\X-Plane 11\Resources\plugins\XPLM_64.dll+1158a () 10 00007FF9556BFED6 D:\X-Plane 11\Resources\plugins\Gizmo64.plugin\64\win.xpl+1fed6 () 11 00007FF9556C3B6E D:\X-Plane 11\Resources\plugins\Gizmo64.plugin\64\win.xpl+23b6e () 12 00007FF96DCD0C4D D:\X-Plane 11\Resources\plugins\XPLM_64.dll+10c4d () 13 00007FF96F9A3095 D:\X-Plane 11\Resources\plugins\PluginAdmin\64\win.xpl+3095 () 14 00007FF96FAE9CEA D:\X-Plane 11\Resources\plugins\XPWidgets_64.dll+9cea () 15 00007FF96FAE1873 D:\X-Plane 11\Resources\plugins\XPWidgets_64.dll+1873 () 16 00007FF96FAE7865 D:\X-Plane 11\Resources\plugins\XPWidgets_64.dll+7865 () 17 00007FF96DCC6675 D:\X-Plane 11\Resources\plugins\XPLM_64.dll+6675 () 18 00007FF63F77B110 D:\X-Plane 11\X-Plane.exe+a5b110 () 19 00007FF63F1B7D9A D:\X-Plane 11\X-Plane.exe+497d9a () 20 00007FF63FA0C903 D:\X-Plane 11\X-Plane.exe+cec903 () 21 00007FF97A706CC1 C:\WINDOWS\System32\USER32.dll+16cc1 () 22 00007FF97A70688B C:\WINDOWS\System32\USER32.dll+1688b () 23 00007FF9635D8BC1 C:\WINDOWS\SYSTEM32\OPENGL32.dll+38bc1 () 24 00007FF97A706CC1 C:\WINDOWS\System32\USER32.dll+16cc1 () 25 00007FF97A706693 C:\WINDOWS\System32\USER32.dll+16693 () 26 00007FF63FA0B23B D:\X-Plane 11\X-Plane.exe+ceb23b () 27 00007FF63EE5B41C D:\X-Plane 11\X-Plane.exe+13b41c () 28 00007FF63FBF38C7 D:\X-Plane 11\X-Plane.exe+ed38c7 () 29 00007FF97A643034 C:\WINDOWS\System32\KERNEL32.DLL+13034 () 30 00007FF97BDD1461 C:\WINDOWS\SYSTEM32\ntdll.dll+71461 () I can reproduce this easy with deactivating gizmo plugin and reactivating it (sometimes this must be done twice). Attached the complete log.file (x-plane clean installation) Log.txt Sometimes i get also a CTD wehen i choose "reboot scripts" from the gizmo plugin menue, or combination with the en-/disable of the plugin. And a small voice in my head say's, the other CTD (those without trace / debug information) are also related to gizmo... I wanted to try a flight without active gizmo plugin, but the license check seems not to be only on start, it seems to be permanent. What happens, if the license server is not available (e.g. instable internet connection) while i´m flying? regards, Martin Quote
sd_flyer Posted November 1, 2018 Report Posted November 1, 2018 11.30b1 same error TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000 Log.txt Quote
seth Posted November 1, 2018 Report Posted November 1, 2018 same here 2018-11-01 16:08:16 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000 Quote
russell458 Posted December 31, 2018 Report Posted December 31, 2018 2018-12-30 23:53:01 TBM900[except.c:171]: Caught EXCEPTION_ACCESS_VIOLATION Backtrace is: 0 00007FFF4234BCF0 C:\WINDOWS\System32\KERNELBASE.dll+ebcf0 () 1 00007FFF459D3167 C:\WINDOWS\SYSTEM32\ntdll.dll+a3167 () 2 00007FFF459BB5E6 C:\WINDOWS\SYSTEM32\ntdll.dll+8b5e6 () 3 00007FFF459CF7DD C:\WINDOWS\SYSTEM32\ntdll.dll+9f7dd () 4 00007FFF4593D856 C:\WINDOWS\SYSTEM32\ntdll.dll+d856 () 5 00007FFF459CE70E C:\WINDOWS\SYSTEM32\ntdll.dll+9e70e () 6 00007FF6441360C7 C:\SteamLibrary\steamapps\common\X-Plane 11\X-Plane.exe+f060c7 () 7 00007FF643638827 C:\SteamLibrary\steamapps\common\X-Plane 11\X-Plane.exe+408827 () 8 00007FF6436376DE C:\SteamLibrary\steamapps\common\X-Plane 11\X-Plane.exe+4076de () 9 00007FF64365466A C:\SteamLibrary\steamapps\common\X-Plane 11\X-Plane.exe+42466a () 10 00007FF64368A38B C:\SteamLibrary\steamapps\common\X-Plane 11\X-Plane.exe+45a38b () 11 00007FFF444A3034 C:\WINDOWS\System32\KERNEL32.DLL+13034 () 12 00007FFF459A3691 C:\WINDOWS\SYSTEM32\ntdll.dll+73691 () TBM900_Log.txt Log.txt Quote
Goran_M Posted December 31, 2018 Report Posted December 31, 2018 1 hour ago, russell458 said: 2018-12-30 23:53:01 TBM900[except.c:171]: Caught EXCEPTION_ACCESS_VIOLATION Backtrace is: 0 00007FFF4234BCF0 C:\WINDOWS\System32\KERNELBASE.dll+ebcf0 () 1 00007FFF459D3167 C:\WINDOWS\SYSTEM32\ntdll.dll+a3167 () 2 00007FFF459BB5E6 C:\WINDOWS\SYSTEM32\ntdll.dll+8b5e6 () 3 00007FFF459CF7DD C:\WINDOWS\SYSTEM32\ntdll.dll+9f7dd () 4 00007FFF4593D856 C:\WINDOWS\SYSTEM32\ntdll.dll+d856 () 5 00007FFF459CE70E C:\WINDOWS\SYSTEM32\ntdll.dll+9e70e () 6 00007FF6441360C7 C:\SteamLibrary\steamapps\common\X-Plane 11\X-Plane.exe+f060c7 () 7 00007FF643638827 C:\SteamLibrary\steamapps\common\X-Plane 11\X-Plane.exe+408827 () 8 00007FF6436376DE C:\SteamLibrary\steamapps\common\X-Plane 11\X-Plane.exe+4076de () 9 00007FF64365466A C:\SteamLibrary\steamapps\common\X-Plane 11\X-Plane.exe+42466a () 10 00007FF64368A38B C:\SteamLibrary\steamapps\common\X-Plane 11\X-Plane.exe+45a38b () 11 00007FFF444A3034 C:\WINDOWS\System32\KERNEL32.DLL+13034 () 12 00007FFF459A3691 C:\WINDOWS\SYSTEM32\ntdll.dll+73691 () TBM900_Log.txt Log.txt Could you submit this to Laminar as a bug report. The backtrace points to X-Plane itself crashing. (The Windows and X-Plane references) Quote
jcbak Posted December 31, 2018 Report Posted December 31, 2018 I had a CTD while descending using FLC.....TBM900[except.c:171]: Caught EXCEPTION_ACCESS_VIOLATION. Have no idea what that means. Quote
wsando1 Posted December 31, 2018 Report Posted December 31, 2018 Do you have AI aircraft enabled? I've been plagued with CTD's which had similar in the Log files, but have now found stability by removing AI Aircraft, specifically World Traffic AI from the Xplane AI Airplane menu. Even with all plug-ins removed including World Traffic, I had the maximum number of World Traffic AI still defined within the AI menu (out of sight, out of mind). With the AI removed I have improved stability significantly. The World Traffic plugin otherwise works fine, but I no longer get the World Traffic AI drawn on the G1000. I'm doing more testing now with default AI and again with World Traffic AI but in fewer aircraft defined within the menu. May not be relevant in your case but thought I'd share my experience. Quote
sd_flyer Posted January 1, 2019 Report Posted January 1, 2019 and now something completely different CTD with TerraMaxx.. and issue that presumably have been fixed "License challenge failed; TerraMaxx disabled." and crash Log.txt Quote
xplanebobby Posted January 1, 2019 Report Posted January 1, 2019 i bet this has something to do with this gizmo thing...because now all of the sudden this exact same crash procedure happens to me in the jar330, i fly this thing for 2 years now and never got any problems with xplane crashing, but since installing this bird...my xplane crashes all the time... Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.