TBM Crash Windows 10 XPlane 11.41

[Gregg Seipp]

Log attached

Log.txt

[Goran_M]

What an unusual crash.  However, it's not the TBM causing it, although it looks like it got caught up in the middle of it and maybe had a part in it.  I know it references the TBM just before the backtrace, due to the TBM reading the terrain and scenery data, but it looks like it was flying over corrupt scenery (underlined, enlarged and italicized). 

0:32:27.810 I/DSF: Warning for missing scenery file: +26-096
0:32:27.857 I/DSF: Warning for missing scenery file: +27-096
0:32:28.094 I/SCN: DSF load time: 203266 for file Custom Scenery/Global Forests/Earth nav data/+20-100/+28-096.dsf (0 tris, 0 skipped for 0.0 m^2)
0:32:28.192 I/SCN: DSF load time: 96178 for file Custom Scenery/Global Airports/Earth nav data/+20-100/+28-096.dsf (0 tris, 0 skipped for 0.0 m^2)
0:32:28.251 I/SCN: DSF load time: 5659 for file Custom Scenery/EXT_texas_lights/Earth nav data/+20-100/+28-096.dsf (0 tris, 0 skipped for 0.0 m^2)
0:32:28.538 I/SCN: DSF load time: 268950 for file G:\Ortho4XP1.3\yOrtho4XP_Overlays/Earth nav data/+20-100/+28-096.dsf (0 tris, 0 skipped for 0.0 m^2)
0:32:30.798 I/SCN: DSF load time: 2215221 for file Custom Scenery/zOrtho4XP_+28-096/Earth nav data/+20-100/+28-096.dsf (206724 tris, 16 skipped for -6.4 m^2)

Then the crash was actually caused by a graphics issue that had something to do with the scenery (the gpu driver going crazy).

0 00007FFEB2BD7D60 C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_27303a6ab0e36ec9\nvoglv64.dll+0000000000C67D60 ()
1 00007FFEB2C9E3E3 C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_27303a6ab0e36ec9\nvoglv64.dll+0000000000D2E3E3 ()
2 00007FFEB2C8F6C7 C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_27303a6ab0e36ec9\nvoglv64.dll+0000000000D1F6C7 ()
3 00007FFEB2C90A05 C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_27303a6ab0e36ec9\nvoglv64.dll+0000000000D20A05 ()
4 00007FFEB282308A C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_27303a6ab0e36ec9\nvoglv64.dll+00000000008B308A ()
5 00007FFEB28116DC C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_27303a6ab0e36ec9\nvoglv64.dll+00000000008A16DC ()
6 00007FFEB2812FBF C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_27303a6ab0e36ec9\nvoglv64.dll+00000000008A2FBF ()
7 00007FFEB2812CBA C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_27303a6ab0e36ec9\nvoglv64.dll+00000000008A2CBA ()
8 00007FFEB2A90C98 C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_27303a6ab0e36ec9\nvoglv64.dll+0000000000B20C98 ()

Then finally Windows itself crashing X-Plane.

9 00007FFF39187BD4 C:\WINDOWS\System32\KERNEL32.DLL+0000000000017BD4 ()
10 00007FFF3A64CED1 C:\WINDOWS\SYSTEM32\ntdll.dll+000000000006CED1 ()

If you can fly over the same area again, with the TBM, and it crashes again, it's almost definitely the scenery.  If this happens, try moving the scenery out of your custom scenery folder, and trying to fly over it again.  If it doesn't crash, then it's a 100% certainty the scenery is the cause.

(Hope this makes sense).

 

Edited January 8, 2020 by Goran_M

[Gregg Seipp]

37 minutes ago, Goran_M said:

What an unusual crash.  However, it's not the TBM causing it, although it looks like it got caught up in the middle of it and maybe had a part in it.  I know it references the TBM just before the backtrace, due to the TBM reading the terrain and scenery data, but it looks like it was flying over corrupt scenery (underlined, enlarged and italicized). 

0:32:27.810 I/DSF: Warning for missing scenery file: +26-096
0:32:27.857 I/DSF: Warning for missing scenery file: +27-096
0:32:28.094 I/SCN: DSF load time: 203266 for file Custom Scenery/Global Forests/Earth nav data/+20-100/+28-096.dsf (0 tris, 0 skipped for 0.0 m^2)
0:32:28.192 I/SCN: DSF load time: 96178 for file Custom Scenery/Global Airports/Earth nav data/+20-100/+28-096.dsf (0 tris, 0 skipped for 0.0 m^2)
0:32:28.251 I/SCN: DSF load time: 5659 for file Custom Scenery/EXT_texas_lights/Earth nav data/+20-100/+28-096.dsf (0 tris, 0 skipped for 0.0 m^2)
0:32:28.538 I/SCN: DSF load time: 268950 for file G:\Ortho4XP1.3\yOrtho4XP_Overlays/Earth nav data/+20-100/+28-096.dsf (0 tris, 0 skipped for 0.0 m^2)
0:32:30.798 I/SCN: DSF load time: 2215221 for file Custom Scenery/zOrtho4XP_+28-096/Earth nav data/+20-100/+28-096.dsf (206724 tris, 16 skipped for -6.4 m^2)

Then the crash was actually caused by a graphics issue that had something to do with the scenery (the gpu driver going crazy).

0 00007FFEB2BD7D60 C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_27303a6ab0e36ec9\nvoglv64.dll+0000000000C67D60 ()
1 00007FFEB2C9E3E3 C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_27303a6ab0e36ec9\nvoglv64.dll+0000000000D2E3E3 ()
2 00007FFEB2C8F6C7 C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_27303a6ab0e36ec9\nvoglv64.dll+0000000000D1F6C7 ()
3 00007FFEB2C90A05 C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_27303a6ab0e36ec9\nvoglv64.dll+0000000000D20A05 ()
4 00007FFEB282308A C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_27303a6ab0e36ec9\nvoglv64.dll+00000000008B308A ()
5 00007FFEB28116DC C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_27303a6ab0e36ec9\nvoglv64.dll+00000000008A16DC ()
6 00007FFEB2812FBF C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_27303a6ab0e36ec9\nvoglv64.dll+00000000008A2FBF ()
7 00007FFEB2812CBA C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_27303a6ab0e36ec9\nvoglv64.dll+00000000008A2CBA ()
8 00007FFEB2A90C98 C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_27303a6ab0e36ec9\nvoglv64.dll+0000000000B20C98 ()

Then finally Windows itself crashing X-Plane.

9 00007FFF39187BD4 C:\WINDOWS\System32\KERNEL32.DLL+0000000000017BD4 ()
10 00007FFF3A64CED1 C:\WINDOWS\SYSTEM32\ntdll.dll+000000000006CED1 ()

If you can fly over the same area again, with the TBM, and it crashes again, it's almost definitely the scenery.  If this happens, try moving the scenery out of your custom scenery folder, and trying to fly over it again.  If it doesn't crash, then it's a 100% certainty the scenery is the cause.

(Hope this makes sense).

 

Yeah, I'm not sure if it's related to those two missing ortho tiles or not.  There are a number of folks having issues...not just with the TBM.  I'm trying to track it down.  Seems to be related to OpenGL on the Nvidea drivrs.  Tried several drivers.  It's all guesswork but the common theme I've been thinking about is FXAA.  Not sure...and you really can never be sure.