TBM 1.1.6 causing x-plane to crash.

[neilrich3]

Having installed the new version 1.1.6 using the installer/uninstaller, when opening x-plane and having selected the TBM, once x-plane has completed loading...all I get is a pale grey screen and the FPS drops from >50 to about 7, program no longer responding.

Have attempted a number of install using the installer/uninstaller, using windows 10 pro, log attached.

Many thanks in anticipation.

Log.txt

[Goran_M]

Try the usual.  Remove all plugins except Gizmo, reload and see what happens.  Please post back the results, then we can go further.

[silakka]

Had this exact same error now after updating from previous version with a very similar log.txt. What fixed it for me was removing the TBM900 folder from the X-plane 11/Output folder and do a full reinstall. Obviously be cautious it will fully reset the plane and history and starts again with tutorial. Not the ideal solution...

[neilrich3]

Have removed all plugins except Gizmo and attempted another install....unfortunately no change.

Shall attempt silakka's suggestion.

Many thanks

[silakka]

Well seems this was a short-lived success. After flying couple of legs with the plane without issues, I quit X-plane. Now that I tried starting up again I'm back to the CTD issue. I reach the screen which says the last flight wasn't completed (kinda was, continuing from same spot as last time) and then X-plane just closes without error. Have tried removing all plugins and still same, log attached.

Log.txt

[Ravonmith]

Same for me, purchased today. Install- First start ctd. Restart - several plugins deleted, no chance at all. Reinstalled the bird and it worked for 2 flights. After restart of x plane and the question - restore position yes or no, either way just ctd. Only chance is to reinstall several times before each flight. Which sucks.

 

In most cases it says System.32 Error/ kernel  etc. Seems to be the multi thread issue of the tbm 900 which many people had. 

 

[Goran_M]

Are you running more than 1 monitor by any chance?

[Ravonmith]

Unfortunarly no. ;(

Just one screen, 1080 gtx, i5 6500k, all on SSD. Win 10. Warthog. Track ir or oculus all disabled and plugged out.

If the log file does help you guys can provide it too.

I own almost all other study level planes. No ctd at all. Had no ctd before for 9 weeks. 

 

[Goran_M]

A system 32 error is a windows error. Open your log file and scroll to the end. You should find s backtrack. If the last several lines are pointing to your windows files, then it’s something in windows. Some people have reported the TBM running fine after running a scan disk and repairing windows files. Can you try this and see what happens. 

[ZE1011]

I have triple monitors, latest xplane version and updated drivers. Trying sfc scan now. Only had this problem after update to 1.1.6, CTD when starting a flight

 

2019-03-11 19:39:23 TBM900[except.c:171]: Caught EXCEPTION_ACCESS_VIOLATION
Backtrace is:
0 00007FFA42AA669C C:\WINDOWS\System32\KERNELBASE.dll+8669c ()
1 00007FFA45DB80CB C:\WINDOWS\SYSTEM32\ntdll.dll+a80cb ()
2 00007FFA45D9FD36 C:\WINDOWS\SYSTEM32\ntdll.dll+8fd36 ()
3 00007FFA45DB468F C:\WINDOWS\SYSTEM32\ntdll.dll+a468f ()
4 00007FFA45D14BEF C:\WINDOWS\SYSTEM32\ntdll.dll+4bef ()
5 00007FFA45DB33FE C:\WINDOWS\SYSTEM32\ntdll.dll+a33fe ()
6 00000000758F2EC0 C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_7a8e74171e1b8492\nvoglv64.dll+bd2ec0 ()

 

edit sfc scan found no errors

Edited March 11, 2019 by ZE1011

[Hoekstes]

Got a CTD 10 miles after takeoff on Vatsim when I tried opening the checklist on the MFD.

[Goran_M]

2 hours ago, ZE1011 said:

I have triple monitors, latest xplane version and updated drivers. Trying sfc scan now. Only had this problem after update to 1.1.6, CTD when starting a flight

 

2019-03-11 19:39:23 TBM900[except.c:171]: Caught EXCEPTION_ACCESS_VIOLATION
Backtrace is:
0 00007FFA42AA669C C:\WINDOWS\System32\KERNELBASE.dll+8669c ()
1 00007FFA45DB80CB C:\WINDOWS\SYSTEM32\ntdll.dll+a80cb ()
2 00007FFA45D9FD36 C:\WINDOWS\SYSTEM32\ntdll.dll+8fd36 ()
3 00007FFA45DB468F C:\WINDOWS\SYSTEM32\ntdll.dll+a468f ()
4 00007FFA45D14BEF C:\WINDOWS\SYSTEM32\ntdll.dll+4bef ()
5 00007FFA45DB33FE C:\WINDOWS\SYSTEM32\ntdll.dll+a33fe ()
6 00000000758F2EC0 C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_7a8e74171e1b8492\nvoglv64.dll+bd2ec0 ()

 

edit sfc scan found no errors

The end of what you posted shows a GPU driver crash.

C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_7a8e74171e1b8492\nvoglv64.dll+bd2ec0 ()

This is likely due to the 3 monitor setup.  Did you run 3 monitors prior to this update?

1 hour ago, Hoekstes said:

Got a CTD 10 miles after takeoff on Vatsim when I tried opening the checklist on the MFD.

Please post log.txt file immediately after the crash. 

[Ravonmith]

Today i have reinstalled the game, the plane and repaired Windows via admin command console in both mentioned ways, normal scan  and online Image repair.  deleted all registrierty issues, etc.

The first start always works. But next time the sim and plane is loaded and you have to decide yes or no for replace it will Crash again. The ctd with the system32 error is alwys in the backtrace.

BUT if you delete the tbm output folder it works like a charme. Or you start or stop at the exact same gate. No questions, no ctd!!!!

Please investigate!

Since no, and i repeat no other plane causes this, its not systemrelated.

Even the leminar statet in their last dev blog THIS case. Plugins causing crashes where the plugin will not be refeared but arethe reason why.

[ZE1011]

Hi,

I highly doubt this is a GPU driver issue as it works without problems with every other aircraft freeware and payware and also with photoshop etc. Yes I ran the same config before the update. Can you release a roll back as the last version was much better.

[Goran_M]

1 hour ago, ZE1011 said:

Hi,

I highly doubt this is a GPU driver issue as it works without problems with every other aircraft freeware and payware and also with photoshop etc. Yes I ran the same config before the update. Can you release a roll back as the last version was much better.

The TBM code and systems are extremely complex.  Many things have been done that have never been done before in X-Plane.  There are systems inside the TBM working outside of the sim, in their own environment.  So in saying that, it is impossible to compare it to freeware add ons and most, if not all payware.  

As far as the driver issue, it's not my opinion...it's a fact.  The GPU driver is crashing.  The log file is telling us this.  It is very likely, to the point of it being a certainty, something in the TBM code and the multi monitor setup is causing this, but we don't know if it's ONLY this or a combination of something in Laminar AND the TBM and the multi monitor setup, or Laminar, the TBM and the shaders being used for the rain and ice, or all the above PLUS the type of GPU.  Add to this the plethora of system configurations in the PC's of our customers, and you're looking at too many variables to isolate it in a short time frame.  Which is why we always need log files. 

We're still investigating, so for the time being, when it comes to a crash involving the GPU, we're advising everyone to avoid running the TBM on more than 2 screens.  In the vast majority of cases, this temporarily solves the problem.  

As far as a rollback, that's not possible.   I've told everyone, via these forums, over the last few months, to PLEASE make a backup of the TBM and/or X-Plane just in case something goes wrong.  I don't know how X-Aviation handles the rollback process, and why they don't have one, so you are more than welcome to send in an email and ask.

 

[ZE1011]

Ok well ill wait for you to fix it and it will have to sit in the hanger until then. 

[fog]

On 3/11/2019 at 10:28 PM, Goran_M said:

The end of what you posted shows a GPU driver crash.

C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_7a8e74171e1b8492\nvoglv64.dll+bd2ec0 ()

This is likely due to the 3 monitor setup.  Did you run 3 monitors prior to this update?

Please post log.txt file immediately after the crash. 

Hi Goran!

Attached is a fresh log file. I got the exact same error as ZE1011. Crash only happends in triple monitor. Running single monitor without issues.

Freddy

Log.txt

[McShiggity Pilot]

Mine crashes everytime too. Its in the hangar until repairs are done. Not a hppy customer.

[Goran_M]

On 3/13/2019 at 6:57 PM, fog said:

Hi Goran!

Attached is a fresh log file. I got the exact same error as ZE1011. Crash only happends in triple monitor. Running single monitor without issues.

Freddy

Log.txt

You should be able to run 2 monitors.  Triple monitor issue is getting looked into.

25 minutes ago, McShiggity Pilot said:

Mine crashes everytime too. Its in the hangar until repairs are done. Not a hppy customer.

A log.txt file will be helpful.  Most people are having no issues.  I may be able to fix a problem you are having.

Just a footnote.  If your installation is crashing, and you're not sure of what it is, feel free to start a new thread.

[Ned]

I have had the 900 crash twice today. The first log tx error said the crash was caused bu Sky Max Pro, so I disabled SMP and reloaded the 900. All systems good on a flight to KCLT at 22,000 when suddenly another crash.Attaching log.txt which says crash was caused by Open GPWS by Saso Kiselov. I don't know if this is an internal system working in the 900 or what but it is not a plugin I have nor am familiar with.

Log.txt

TBM900_Log.txt

[LKN]

Oh noooooo!

I started to be in trust with the last update to begin my world tour, no problem so far, no CTD from CYQB to California, I flew around Vegas and Cali during the last three days, and now I have the same issue???!

TBM900[except.c:171]: Caught EXCEPTION_ACCESS_VIOLATION
Backtrace is:
0 00007FF9225A1D32 C:\Windows\system32\KERNELBASE.dll+e1d32 ()
1 00007FF924FEF1B3 C:\Windows\SYSTEM32\ntdll.dll+9f1b3 ()
2 00007FF924FD1E26 C:\Windows\SYSTEM32\ntdll.dll+81e26 ()
3 00007FF924FE349D C:\Windows\SYSTEM32\ntdll.dll+9349d ()
4 00007FF924FA48D7 C:\Windows\SYSTEM32\ntdll.dll+548d7 ()
5 00007FF924FE262A C:\Windows\SYSTEM32\ntdll.dll+9262a ()
6 0000000053DE89F0 C:\Windows\SYSTEM32\nvoglv64.DLL+bc89f0 ()

First time that one!

I think I'm gonna do my world tour by bus! Kidding but frustrating

Only one monitor, I didn't add any plugin or scenery, didn't change anything but updated the last version of my favorite bird some days ago... No CTD from other addon engine weather and aircrafts. Do I need to send my log txt knwowing that I don't have any apparent issue with scenes or else? so don't know what to do guys?

How can I elect this bird to make a world tour this way? ... I have long legs to fly to go back in France across lands and seas that I don't want to get back on my desk after two hours in the air, u know what I mean....

Thank you

Edited March 15, 2019 by LKN

[LKN]

KLAS/KLAX I had hopes but until it happened again....

I give up till there is a fix or something tired of CTD which kill immersion and fun, just had an other back to the desk after one hour of flying, guess where?

in final at KLAX!

In final Captains, that is so ennoying and frustrating!

It's not to argue or something but I have no CTD with nothing else so it can't come from plugins, aircrafts or scene etc imo!  but that's just how I feel things that I share softly here... It's difficult to enjoy if it's to get a CTD like the Damocles sword above the airplane...

Hopefully we may have a stable product soon because it's a very great one...

So... no world tour with the TBM my bird is now sleeping in my hangar, under perfusion waiting for medecine,  please Doctors!

Edited March 15, 2019 by LKN

[nsblue]

I'm having the same issue.  X-Plane 11.32 crashes when loading the TBM-900.  I also have a triple monitor setup.   Guess I'll just wait patiently like others for a fix.

Awesome aircraft though and thanks,

Dean

[nilian]

Suffering from the same problem like in the starting post of this thread, I did some anaylzes.

The error message I've got in the log file had the following pattern:

...

2019-03-10 10:41:08 TBM900[libsvs.c:3744]: assertion "!(__builtin_choose_expr ( __builtin_types_compatible_p (__typeof__ ((rev_dir_v).x), double), __isnan((rev_dir_v).x), __builtin_choose_expr ( __builtin_types_compatible_p (__typeof__ ((rev_dir_v).x), float), __isnanf((rev_dir_v).x), __builtin_choose_expr ( __builtin_types_compatible_p (__typeof__ ((rev_dir_v).x), long double), __isnanl((rev_dir_v).x), (__builtin_trap(),(rev_dir_v).x)))))" failed: 
Backtrace is:
0 000000008010FA50 C:\Users\Neil\Desktop\X-Plane 11\Aircraft\X-Aviation\TBM-900\plugins\systems\win_x64\systems.xpl+11fa50 (pathway_cache_refresh+6d0)
1 0000000080112147 C:\Users\Neil\Desktop\X-Plane 11\Aircraft\X-Aviation\TBM-900\plugins\systems\win_x64\systems.xpl+122147 (libsvs_render+6e7)
2 0000000080031557 C:\Users\Neil\Desktop\X-Plane 11\Aircraft\X-Aviation\TBM-900\plugins\systems\win_x64\systems.xpl+41557 (draw_cb+17b7)
3 00007FFF1E9F4FE4 C:\Users\Neil\Desktop\X-Plane 11\Resources\plugins\XPLM_64.dll+4fe4 ()
4 00007FFF1E9F6039 C:\Users\Neil\Desktop\X-Plane 11\Resources\plugins\XPLM_64.dll+6039 ()
5 00007FF671755BDE C:\Users\Neil\Desktop\X-Plane 11\X-Plane.exe+a25bde ()
6 00007FF6716A7955 C:\Users\Neil\Desktop\X-Plane 11\X-Plane.exe+977955 ()
7 00007FF67166CE73 C:\Users\Neil\Desktop\X-Plane 11\X-Plane.exe+93ce73 ()
8 00007FF67166D494 C:\Users\Neil\Desktop\X-Plane 11\X-Plane.exe+93d494 ()
9 00007FF6717894D3 C:\Users\Neil\Desktop\X-Plane 11\X-Plane.exe+a594d3 ()
10 00007FF670E08B12 C:\Users\Neil\Desktop\X-Plane 11\X-Plane.exe+d8b12 ()
11 00007FF671194B6A C:\Users\Neil\Desktop\X-Plane 11\X-Plane.exe+464b6a ()
12 00007FF671A01587 C:\Users\Neil\Desktop\X-Plane 11\X-Plane.exe+cd1587 ()
13 00007FF670E0C18C C:\Users\Neil\Desktop\X-Plane 11\X-Plane.exe+dc18c ()
14 00007FF671C20387 C:\Users\Neil\Desktop\X-Plane 11\X-Plane.exe+ef0387 ()
15 00007FFF2F183DC4 C:\WINDOWS\System32\KERNEL32.DLL+13dc4 ()
16 00007FFF31603691 C:\WINDOWS\SYSTEM32\ntdll.dll+73691 ()

...

When testing the TBM with a clean X-Plane installation there were no problems at all, everything went smooth.
At the end the reason for my crashes was XPUIPC 2.0.4.8. When I use version 2.0.4.7 the crashes are gone so far.

Please be aware that the current version 2.0.5.9 of XPUIPC will break the IXEX737 (Throttles are not controllable anymore) .

Best regards,

Daniel

Edited March 16, 2019 by nilian
typo

[Goran_M]

4 hours ago, nilian said:

When testing the TBM with a clean X-Plane installation there were no problems at all, everything went smooth.
At the end the reason for my crashes was XPUIPC 2.0.4.8. When I use version 2.0.4.7 the crashes are gone so far.

Please be aware that the current version 2.0.5.9 of XPUIPC will break the IXEX737 (Throttles are not controllable anymore) .

Best regards,

Daniel

Thanks for letting everyone know.  Much appreciated