This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
GTN750Xi shows only black screen in all aircraft
#1
In all the aircraft using  GTN750NXi I see the correct bezel and knobs but a black screen.  I am a long time user of the TDS GTN stuff.  The A2A Comanche, JPL 152 and Cessna 414AW were both working perfectly with the TDS 750 the last time I flew them - probably just after New Years.

I've attached a screen shot of the WASM debugger
[Image: JPL-C152-GTNXi-750.jpg]

 TDS GPS manager says I am current at version 1.0.3.7 for the sim and 3.6.4.0 for the trainer.

When in the sim/Dev Mode I see that two TDS packages are mounted and registered:
tds-gtnxi-gauge (version 1.0.11) and tds-gtnxi-jpl_c152 (0.1.0 ). Here 

Here is the log from the TDS module during a flight with the JPL C152 and a black GTNXi750 screen:
[19/01/2024 15:00:05.670 00002578 INFO] TDSGTNXiFlightSimEXE.exe version 1.0.3.7
[19/01/2024 15:00:06.034 00004f50 INFO] Got Version: 9
[19/01/2024 15:00:06.036 00004f50 INFO] GTNProxy::Open Services DLL Version: 1.0.3.7
[19/01/2024 15:00:16.453 00004f50 ERROR] ^^^ GTNProxy::Open Error starting process C:\ProgramData\Garmin\Trainers\GTI\Production\GTI__GTN_Xi__20_30\app-20.30.8\bin\GTN_Simulator.exe
[19/01/2024 15:00:16.453 00004f50 ERROR] Error closing program: 299
[19/01/2024 15:36:16.257 00000e08 INFO] Received Simconnect Quit
[19/01/2024 15:36:16.377 00000e08 INFO] Closing program automatically with MSFS
[19/01/2024 15:36:16.475 00002578 INFO] Ending EXE Process

Here the TDS GPS Manager log and the .exe log:
[20/01/2024 17:13:01.853 0000275c INFO] TDSGPSManager.exe version 1.0.1.0
[20/01/2024 17:13:01.854 0000275c INFO] MSFS Double Install: 0
[20/01/2024 17:13:01.854 0000275c INFO] MSFS Community Folder: 1 and I:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\Packages\Community\
[20/01/2024 17:13:01.855 0000275c INFO] MSFS LocalState Folder: 1 and C:\Users\svmir\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\
[20/01/2024 17:13:01.855 0000275c INFO] MSFS TDS GTNXI Gauge Folder: 1 and C:\Users\svmir\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\TDS-GTNXi-Gauge\work\
[20/01/2024 17:13:01.856 0000275c INFO] MSFS LocalCache Folder: 1 and C:\Users\svmir\AppData\Roaming\Microsoft Flight Simulator
[20/01/2024 17:13:01.856 0000275c INFO] Set CDD: 1 at path: C:\Users\svmir\AppData\Local\Temp\TDS\Temporary\
[20/01/2024 17:13:01.857 0000275c INFO] Set CID: 1 at path: C:\ProgramData\TDS\Trainers\
[20/01/2024 17:17:06.990 0000275c INFO] Exiting WinMain

[20/01/2024 17:09:42.439 00006388 INFO] TDSGTNServices.dll version 1.0.3.7
[20/01/2024 17:11:18.129 00006388 INFO] Ending Process

ALL my test flights are with NO addons except those necessary for A2A, Navigraph, Flow Pro, FSLTL
Reply
#2
Hello,

Which antivirus are you using?
Reply
#3
(01-21-2024, 10:07 AM)adminOwner2 Wrote: Hello,

Which antivirus are you using?

NO antivirus is running
Reply
#4
Photo 
[Image: PC12.jpg]

[Image: PC12-1.jpg]




I have exactly the same problem.
I use the Microsoft Defender Firewall and have switched it off. Unfortunately without success.

I have done the following until then

Uninstalled and reinstalled TDS + Garmin
Checked TDS with other airplanes and helicopters (same problem)
The latest version is installed.

Now I don't know what to do.
I hope to find a solution here.


Attached Files Thumbnail(s)
       
Reply
#5
I uninstalled the Garmin Trainer app, deleted all files and folders associated with Garmin Trainer or TDS, and deleted all registery enteries (Win 11) for Garmin Trainer or TDS.


I then reinstalled Garmin Trainer and the instruments for single and multi engine recip, and turbo prop.

The trainer works perfectly in offliner/simulated data mode.

Here is the log of the install:

[21/01/2024 13:22:46.926 00002458 INFO] TDSGPSManager.exe version 1.0.1.0
[21/01/2024 13:22:46.927 00002458 INFO] MSFS Double Install: 0
[21/01/2024 13:22:46.927 00002458 INFO] MSFS Community Folder: 1 and I:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\Packages\Community\
[21/01/2024 13:22:46.927 00002458 INFO] MSFS LocalState Folder: 1 and C:\Users\svmir\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\
[21/01/2024 13:22:46.928 00002458 INFO] MSFS TDS GTNXI Gauge Folder: 1 and C:\Users\svmir\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\TDS-GTNXi-Gauge\work\
[21/01/2024 13:22:46.928 00002458 INFO] MSFS LocalCache Folder: 1 and C:\Users\svmir\AppData\Roaming\Microsoft Flight Simulator
[21/01/2024 13:22:46.929 00002458 INFO] Set CDD: 1 at path: C:\Users\svmir\AppData\Local\Temp\TDS\Temporary\
[21/01/2024 13:22:46.930 00002458 INFO] Set CID: 1 at path: C:\ProgramData\TDS\Trainers\
[21/01/2024 13:27:03.759 00002458 INFO] Exiting WinMain

I then started MSFS with only the A2A PA24, the Flysimware 414aw, and the jpllogistics C 152 as aircraft to use.  The community folder also had the tds-gtnxi-gauge folder and the tds-gtnxi-JPL_C152 folder.

The sim started normally and I saw the TDS display during the loading.  

The GTN750NXi bezel and knobs appear in all three aircraft but the screen remains blank/black.

Here is the .exe log for this session of the flight simulator:

[21/01/2024 13:58:54.649 00001c18 INFO] TDSGTNXiFlightSimEXE.exe version 1.0.3.7
[21/01/2024 13:58:55.009 00002abc INFO] Got Version: 9
[21/01/2024 13:58:55.011 00002abc INFO] GTNProxy::Open Services DLL Version: 1.0.3.7
[21/01/2024 13:59:05.518 00002abc ERROR] ^^^ GTNProxy::Open Error starting process C:\ProgramData\Garmin\Trainers\GTI\Production\GTI__GTN_Xi__20_30\app-20.30.8\bin\GTN_Simulator.exe
[21/01/2024 13:59:05.518 00002abc ERROR] Error closing program: 299
[21/01/2024 14:07:07.410 0000499c INFO] Received Simconnect Quit
[21/01/2024 14:07:07.534 0000499c INFO] Closing program automatically with MSFS
[21/01/2024 14:07:07.631 00001c18 INFO] Ending EXE Process

When I go try to execute the app at: 
C:\ProgramData\Garmin\Trainers\GTI\Production\GTI__GTN_Xi__20_30\app-20.30.8\bin\GTN_Simulator.exe 

I see the same bezel and knobs as in MSFS.  If I click on the home button I get the message: 
GTN Xi Series Trainer has stopped working

GTN_Simulator.exe has a Digest algorithm of sha256 and Timestamp of Monday, January 23, 2023 05:05:58 PM with a file version of 20.30.8.0 with date modified of 1/21/24 1:25PM



You can see in the following image that the wasm files for the gauge are loaded properly.


Attached Files Thumbnail(s)
   
Reply
#6
Here is the wer report for the last crash when trying to execute GTN_Simulator.exe

Version=1
EventType=BEX
EventTime=133503402366819609
ReportType=2
Consent=1
UploadTime=133503402370658955
ReportStatus=268435456
ReportIdentifier=dc98a0fd-de6f-4879-8ee5-f74ebef8ceff
IntegratorReportIdentifier=442a9191-cb6e-4311-9771-a3e8cfa0902b
Wow64Host=34404
Wow64Guest=332
NsAppName=GTN_Simulator.exe
OriginalFilename=gtn_simulator.exe
AppSessionGuid=0000094c-0001-01d0-068f-221aa34cda01
TargetAppId=W:00062e8d9962b82335ec9e6f988c1a7961e400000904!00004f0d6aa2b6c2a5241176be0770c32cd3ebb770fe!gtn_simulator.exe
TargetAppVer=2023//01//23:22:04:28!d4c701!gtn_simulator.exe
BootId=4294967295
TargetAsId=3209
IsFatal=1
EtwNonCollectReason=1
Response.BucketId=40a8e80df20fbbdc7583b7acc0c96836
Response.BucketTable=5
Response.LegacyBucketId=1550284649342265398
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=GTN_Simulator.exe
Sig[1].Name=Application Version
Sig[1].Value=20.30.8.0
Sig[2].Name=Application Timestamp
Sig[2].Value=63cf046c
Sig[3].Name=Fault Module Name
Sig[3].Value=StackHash_76a1
Sig[4].Name=Fault Module Version
Sig[4].Value=0.0.0.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=00000000
Sig[6].Name=Exception Offset
Sig[6].Value=PCH_8F_FROM_unknown+0x00000000
Sig[7].Name=Exception Code
Sig[7].Value=c0000005
Sig[8].Name=Exception Data
Sig[8].Value=00000008
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.22621.2.0.0.768.101
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=76a1
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=76a173c26a6dc2e3cd83ac8fd9f8bdb9
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=7b3f
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=7b3f634c955ac91fe3f1e745337a968a
UI[2]=C:\ProgramData\Garmin\Trainers\GTI\Production\GTI__GTN_Xi__20_30\app-20.30.8\bin\GTN_Simulator.exe
UI[3]=GTN Xi Series Trainer has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\ProgramData\Garmin\Trainers\GTI\Production\GTI__GTN_Xi__20_30\app-20.30.8\bin\GTN_Simulator.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\System32\KERNEL32.DLL
LoadedModule[3]=C:\Program Files\Avast Software\Avast\x86\aswhook.dll
LoadedModule[4]=C:\WINDOWS\System32\KERNELBASE.dll
LoadedModule[5]=C:\WINDOWS\System32\USER32.dll
LoadedModule[6]=C:\WINDOWS\System32\win32u.dll
LoadedModule[7]=C:\WINDOWS\System32\GDI32.dll
LoadedModule[8]=C:\WINDOWS\System32\gdi32full.dll
LoadedModule[9]=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule[10]=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule[11]=C:\WINDOWS\System32\COMDLG32.dll
LoadedModule[12]=C:\WINDOWS\System32\combase.dll
LoadedModule[13]=C:\WINDOWS\System32\RPCRT4.dll
LoadedModule[14]=C:\WINDOWS\System32\shcore.dll
LoadedModule[15]=C:\WINDOWS\System32\SHLWAPI.dll
LoadedModule[16]=C:\WINDOWS\System32\msvcrt.dll
LoadedModule[17]=C:\WINDOWS\System32\SHELL32.dll
LoadedModule[18]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.22621.2506_none_fbe8e1f07808be9b\COMCTL32.dll
LoadedModule[19]=C:\WINDOWS\System32\ADVAPI32.dll
LoadedModule[20]=C:\WINDOWS\System32\sechost.dll
LoadedModule[21]=C:\WINDOWS\System32\bcrypt.dll
LoadedModule[22]=C:\ProgramData\Garmin\Trainers\GTI\Production\GTI__GTN_Xi__20_30\app-20.30.8\bin\KRNL.dll
LoadedModule[23]=C:\WINDOWS\SYSTEM32\d3d9.dll
LoadedModule[24]=C:\WINDOWS\SYSTEM32\dwmapi.dll
LoadedModule[25]=C:\WINDOWS\System32\WS2_32.dll
LoadedModule[26]=C:\WINDOWS\SYSTEM32\dxcore.dll
LoadedModule[27]=C:\WINDOWS\System32\ole32.dll
LoadedModule[28]=C:\WINDOWS\SYSTEM32\VERSION.dll
LoadedModule[29]=C:\WINDOWS\SYSTEM32\WINMM.dll
LoadedModule[30]=C:\ProgramData\Garmin\Trainers\GTI\Production\GTI__GTN_Xi__20_30\app-20.30.8\bin\libEGL.dll
LoadedModule[31]=C:\ProgramData\Garmin\Trainers\GTI\Production\GTI__GTN_Xi__20_30\app-20.30.8\bin\libGLESv2.dll
LoadedModule[32]=C:\WINDOWS\SYSTEM32\dxgi.dll
LoadedModule[33]=C:\WINDOWS\System32\IMM32.DLL
LoadedModule[34]=C:\Program Files (x86)\Steam\gameoverlayrenderer.dll
LoadedModule[35]=C:\WINDOWS\System32\OLEAUT32.dll
LoadedModule[36]=C:\WINDOWS\System32\PSAPI.DLL
LoadedModule[37]=C:\WINDOWS\SYSTEM32\CFGMGR32.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=22621
OsInfo[3].Key=ubr
OsInfo[3].Value=3007
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1033
OsInfo[7].Key=geoid
OsInfo[7].Value=244
OsInfo[8].Key=sku
OsInfo[8].Value=101
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=768
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=222502828
OsInfo[15].Key=osinsty
OsInfo[15].Value=3
OsInfo[16].Key=iever
OsInfo[16].Value=11.1.22621.0-11.0.1000
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=32628
OsInfo[19].Key=svolsz
OsInfo[19].Value=931
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=220506
OsInfo[22].Key=bldtm
OsInfo[22].Value=1250
OsInfo[23].Key=bldbrch
OsInfo[23].Value=ni_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.22621.3007.amd64fre.ni_release.220506-1250
OsInfo[30].Key=buildflightid
OsInfo[30].Value=34D37308-CE0A-4B7A-9470-B29C3D96D2F8.1
OsInfo[31].Key=edition
OsInfo[31].Value=Core
OsInfo[32].Key=ring
OsInfo[32].Value=Retail
OsInfo[33].Key=expid
OsInfo[33].Value=RS:1A31E,MD:283BAEF,ME:25762F0,ME:27B9BC4,FX:12AAB778,ME:28279A6,FX:12C81320
OsInfo[34].Key=fconid
OsInfo[34].Value=18299130,0,2,0;19193644,0,2,0;19193777,0,2,0;19194292,0,2,0;19195476,0,2,0;19638787,0,2,0;23531064,2,2,0;23562335,2,2,0;23563673,2,2,0;32862274,0,2,1;35409375,0,2,0;35681102,0,1,0;36803287,0,2,1;36803295,0,2,0;36803303,0,2,1;38277973,0,1,0;38859191,0,2,1;39263329,1,2,0;39281392,0,2,0;40025975,0,1,0;40616880,0,1,0;40883769,0,1,0;40981503,0,1,0;41135193,0,1,1;41137130,0,1,0;41342175,0,1,1;41655236,0,2,1;41772259,0,2,1;41799415,0,2,1;42052423,0,2,0;42105254,0,2,1;43133808,1,2,1;43169616,0,1,0;43203978,0,2,1;43572857,0,2,1;43772553,0,1,0;43844371,0,1,1;43978769,0,1,1;43998261,0,2,1;44325080,0,1,0;44521793,0,1,0;44552141,0,1,0;45113694,0,2,1;45185354,0,2,0;45786062,0,2,1;45991456,0,1,1;46251949,0,2,0;46551074,0,1,1;46557400,0,1,1;46604216,0,2,1;46619189,0,2,1;46717502,0,0,0;48057519,0,2,1
OsInfo[35].Key=containerid
OsInfo[36].Key=containertype
OsInfo[37].Key=edu
OsInfo[37].Value=0
OsInfo[38].Key=servicinginprogress
OsInfo[38].Value=0
OsInfo[39].Key=featureupdatependingreboot
OsInfo[39].Value=0
FriendlyEventName=Stopped working
ConsentKey=BEX
AppName=GTN Xi Series Trainer
AppPath=C:\ProgramData\Garmin\Trainers\GTI\Production\GTI__GTN_Xi__20_30\app-20.30.8\bin\GTN_Simulator.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=2646FDCA373E1B5F1C1F712A28C11F9C
MetadataHash=2077150156
Reply
#7
Hello,

We have seen this error message only with Avast/AVG antivirus software. There is no need to keep on looking for other log files/sources as the problem is clearly stated in the TDSGTNXiExeLog.txt

In addition, the standalone GTN Simulator.exe is not designed to be executed externally, which is why it would not work/display a crash error message.
At this point, the only test that is relevant is this: with MSFS closed, start the TDS GTNXi from the desktop shortcut and click on the GTN750Xi button, please check if the screen lights up.

Since the TDS GTNXi has worked well in the past, most likely a software got installed that is interfering with it, let's try to remember which software got installed and work from there. As we have said above, this exact error has been seen with AVG/Avast.

For the sake of this conversation, we recommend continuing it via email: support@tdssim.com
Reply
#8
You are correct - I had turned off (off until I turn back on) all AVAST shields and firewall and used Task Manager to ensure they were not running. The error still occurred.

I then disabled AVAST ransomware shield, email guardian, remote access shield. I also created exceptions in AVAST to not perform any security checks on the three drives I use for MSFS.

Now the TDS software works perfectly.

I will have to work on figuring out which AVAST task is the problem.

Why does no other MSFS addon, of which I have many dozens, have a similar problem as your software does with AVAST?
Reply
#9
(01-23-2024, 03:11 AM)TacomaSailor Wrote: Why does no other MSFS addon, of which I have many dozens, have a similar problem as your software does with AVAST?

Or, why is AVAST the only virus scanner that has a problem with this software? Dodgy
Reply
#10
We see that AVAST/AVG have the tendency to inject themselves into running processes, which would result in a performance loss as well as disrupting normal process usage.
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)