I am having issues that started causing real problems for me after the last couple of updates.

 

Just for a start though, PC is generally stable few CTD's within FSX / P3D3 / P3D4 but no more than I would expect within the platform(s) - this issue aside 99% of flights I would expect to complete without any issue whatsoever in the case of p3d4 I can fly PMDG NGX / 777 without issue, occurs with any bird GTN equipped (always solo GTN750). Should also say no other software / game has caused a complete lock like this on my system.

 

Initially this issue started with the F1 GTN in P3D3, occasional random complete system lock (mouse freeze, no keyboard response power on/off only option), a pain but liveable with(ish). Moving over to P3D4 and it wasn't - lucky to get 1 minute before complete lock, again I'm not doing anything specific (can even be in external view). Unusable, but any aircraft without GTN works 100% fine. Support from F1 was useless so swapped to RXP. At this point I thought the issue had completely cleared up, although had extremely rare lock-up (perhaps once a month with at least a few flights a day). With the later versions this has increased to the point where it is more likely than to occur, again non GTN equipped aircraft do not suffer.

 

Appreciate any help you can give to try and sort this out.

 

Regards,

 

G

Hi,

It would help having more of your system specs to get started with (CPU, RAM, Video Driver, VRAM, OS)

A total system lockup usually occur only if a low-level component is failing (hardware or software). In your case I'd venture to check the video card and its drivers first and foremost.

I'd cross check any thermal issue, or wear and tear. You might want to try running a benchmark on your video card, like the infamous 'furmark':

https://geeks3d.com/furmark/

It provides tons of internal data from your video card and it also pushes the video card to its maximum, enough to detect a power/thermal issue (not sure it can detect a VRAM module issue though).

19 minutes ago, RXP said:

It would help having more of your system specs to get started with (CPU, RAM, Video Driver, VRAM, OS)

A total system lockup usually occur only if a low-level component is failing (hardware or software). In your case I'd venture to check the video card and its drivers first and foremost.

I'd cross check any thermal issue, or wear and tear. You might want to try running a benchmark on your video card, like the infamous 'furmark':

https://geeks3d.com/furmark/

It provides tons of internal data from your video card and it also pushes the video card to its maximum, enough to detect a power/thermal issue (not sure it can detect a VRAM module issue though).

Sorry, missed that out:: i7-930, 12Gb, GTX970, 4Gb VRAM, Win10 ...

 

Will run furmark and see what that does....

G

49 minutes ago, Gazzareth said:

Will run furmark and see what that does....

 

Ran burn in test for 30  minutes, no issues. Then did a benchmark, no problem (https://gpuscore.top/furmark/show.php?id=52246)...

 

15 minutes of CPU Burner - no issues, peak temp 83C ...

 

G

 

 

This sounds fine.

I've noticed you're not using the latest NVidia Driver nor the latest Windows version.

• Latest NVidia should be 445.87 (you have 441.41)
• Latest Windows should be at least 18363.778 (you have 18362)

The NVidia driver is potentially a culprit for this kind of problems and I doubt Win10 in itself would cause this but this is still possible.

I'll update and see if it makes any odds, I don't really expect it to, since it's been ongoing for so long through so many versions, but will see what happens....

 

G

If through all these versions you've used the same NVidia drivers... you never know!

1 minute ago, RXP said:

If through all these versions you've used the same NVidia drivers... you never know!

Lol no, it's been quite a while, might even have been across a couple of graphics cards....

 

G

Sorry to say made no odds, updated both drivers and windows. Still same result - hard lock !! 😞

In this case 12000ft, not touching GTN at time....

G

Ok.

If the problem is with the GTN itself, we might get a chance to get an information about the error with the following:

1. Locate one of the aircraft folder you'll fly with
2. Open the RealityXP.GTN.ini file found there with notepad.exe
3. If you're trying with the GTN 750 unit#1, locate the line:
   
   [GTN_750_1]
    
4. Add the following lines right below
   
   [GTN_750_1]
   LogTrainer = 5
   DebugValue = 1

These are documented in the RXP GTN User's Manual p26 for more info.

Next time you run it might have the time to output useful information to the rxpGtnSim.dll.log file.

3 minutes ago, RXP said:

Ok.

If the problem is with the GTN itself, we might get a chance to get an information about the error with the following:

1. Locate one of the aircraft folder you'll fly with
2. Open the RealityXP.GTN.ini file found there with notepad.exe
3. If you're trying with the GTN 750 unit#1, locate the line:
   
   [GTN_750_1]
    
4. Add the following lines right below
   
   [GTN_750_1]
   LogTrainer = 5
   DebugValue = 1

These are documented in the RXP GTN User's Manual p26 for more info.

Next time you run it might have the time to output useful information to the rxpGtnSim.dll.log file.

 

Already set the logvalue to 7 to try, here you go::::

Seems like lots of "Fails" - not sure if they are terminal or just because its simulated!!

 

G

 

20/04/23 21:15:39.674 13068 -    ] # rxpGtnSim64.dll version 2.5.24.0
20/04/23 21:15:39.673 13068 INFO ] 
20/04/23 21:16:54.550 06580 INFO ] GTN 750.1 - TRAINER 6623
20/04/23 21:16:54.629 06580 INFO ] C:\Program Files (x86)\Garmin\Trainers\Packages\GTN\Bin
20/04/23 21:16:54.729 06580 INFO ] C:\Program Files (x86)\Garmin\Trainers\Packages\GTN\data
20/04/23 21:16:54.775 06580 INFO ] C:\ProgramData\Garmin\Trainers\Databases
20/04/23 21:16:54.831 06580 INFO ] C:\ProgramData\Garmin\Trainers\GTN\nonvol
20/04/23 21:17:00.395 06580 WARN ] GTN 750.1 process is running as-admin
20/04/23 21:17:02.326 06580 INFO ] using: %LOCAL_APPDATA%\CrashRpt\UnsentCrashReports\GTN Trainer_6.62.3.0RXP
20/04/23 21:24:27.482 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(559) (null)
20/04/23 21:24:27.691 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(4041) Error -14 writing reg tag header when creating tags in registry file /mnt/sys_nand0/reg_lvl_d.reg
20/04/23 21:24:27.704 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3883) Error -16 writing tags to new registry file /mnt/sys_nand0/reg_lvl_d.reg
20/04/23 21:24:27.926 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_SYS_CNFG_XPDR_1
20/04/23 21:24:28.004 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_SYS_CNFG_XPDR_2
20/04/23 21:24:28.031 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_TCAS_XPDR_CTRL
20/04/23 21:24:28.167 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_XPDR_TEST_AIRB
20/04/23 21:24:28.206 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_SYS_CNFG_XPDR_1
20/04/23 21:24:28.220 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_SYS_CNFG_XPDR_1
20/04/23 21:24:28.239 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_SYS_CNFG_XPDR_1
20/04/23 21:24:28.256 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_SYS_CNFG_XPDR_1
20/04/23 21:24:28.474 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_WX_REQ_DATA
20/04/23 21:24:28.511 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_IOP_TEMPERATURE_DATA
20/04/23 21:24:28.693 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_MAX_SPD
20/04/23 21:24:28.714 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_PVT_STATE_ALT
20/04/23 21:24:28.731 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_PVT_STATE_POSN
20/04/23 21:24:28.812 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_SP_DB_XFER_ENB
20/04/23 21:24:29.202 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_CNXT_FPL_IMPORT_ENB
20/04/23 21:24:29.219 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_CNXT_DB_UPLOAD_ENB
20/04/23 21:24:29.238 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_CNXT_XM_AUDIO_CNTRL
20/04/23 21:24:29.252 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_CNXT_GSR65_MSG_CNTRL
20/04/23 21:24:29.271 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_CNXT_GSR56_PHN_CNTRL
20/04/23 21:24:29.328 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_SIM_TOW
20/04/23 21:24:29.509 06580 INFO ] GFX Debug: enabled.
20/04/23 21:24:29.929 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_UART_DATA_RECORD
20/04/23 21:24:29.980 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_ARNC429_DATA_RECORD
20/04/23 21:24:30.004 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_SCHD_MSG_TIME
20/04/23 21:24:30.034 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_GWX_WATCH_ENABLED
20/04/23 21:24:30.062 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_GWX_TGT_ALRT_ENABLED
20/04/23 21:24:30.079 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_DFLT_INTL_CODE
20/04/23 21:24:30.982 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_ADB_DB_HDR
20/04/23 21:24:31.012 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_DB_ACTV_STATE_AVTN
20/04/23 21:24:31.026 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_SYS_CNFG_XPDR_1
20/04/23 21:24:31.059 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_SYS_CNFG_XPDR_1
20/04/23 21:24:31.084 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_SYS_CNFG_XPDR_1
20/04/23 21:24:31.103 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_DB_ACTV_STATE_BMAP
20/04/23 21:24:31.117 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_DB_ACTV_STATE_SFTX
20/04/23 21:24:31.149 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_DB_ACTV_STATE_OBST
20/04/23 21:24:31.230 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_SIM_WAAS_INTEG
20/04/23 21:24:31.280 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_IRID_PHONE_CNFG
20/04/23 21:24:31.319 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_DB_ACTV_STATE_APDR
20/04/23 21:24:31.358 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_DB_ACTV_STATE_FC
20/04/23 21:25:50.523 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_ARSPC_GRP_NAME_IDX_0
20/04/23 21:26:08.228 06580 WARN ] FAIL: 00 ..\..\lib\acl\kernel\reg\reg_intf.c(3777) REG_TAG_SAR_NO_UNLK_CNT
 

Hi,

The error is related to a corruption in your non volatile memory files.

One reason is a crash in the past when the trainer was trying to quit. Another one is because you've updated the garmin Trainer and from one version to the next it failed to also update its internal data as it is saved in the non volatile memory.

The only way to solve this is to delete the non volatile memory files and let the trainer rebuild them anew.

These are the files documented in the RXP GTN User's Manual "Device Embedded Memory" chapter.

PS: once done and you've validated it works, don't forget to delete the 2 'debug settings' lines from your ini file!

Edited April 24, 20206 yr by RXP

 

OK will give that a try and see if it makes a difference. 

 

Thanks,

 

G

Unfortunately not, well - removed errors from the log (new file is clear of errors), but still locks up exactly the same..... 😞

In the last case, had just taken off without even bothering to program a plan....

 

G

Did you backup your original panel.cfg file?  One with no GTN?  Why not try going back to it and fly and see if you are getting lockups without the GTN.  Of course before you do that make a copy of your current panel.cfg that has the GTN......