October 3, 20178 yr Author I am so sorry and I thank you for your help! But the error is still there, and i think we are very close to solution! The reason is, that under C:\ProgramData\Garmin\GNS Trainer Data\GNS more and more data is written: sys_nand0 sys_nandc If I delete the sys_nandc the error is gone, but all data are lost. Next time I start the P3D another is sys_nandc created. best regards
October 3, 20178 yr Hi, these files are created one per device type (530/430) / unit number (1 / 2) and this is normal. The device routes, settings, user waypoints are stored in these files. Maybe there is something with this folder which is not right on your system? You might want to try changing this folder path like explained p16 of the User's Manual. 1) Create a folder where these will be stored, say in "My Documents" something like: "C:\Users\[name]\Documents\Reality XP\GNS Simulation\" 2) Set/Add the environment variable "GNSAPPDATA" with the value "C:\Users\[name]\Documents\Reality XP\GNS Simulation\" (without the quotes) 3) Start your simulator, open an aircraft with the GNS, check it creates the corresponding "sys_nand#" file in the new folder.
October 5, 20178 yr Author On Tuesday, October 03, 2017 at 1:17 PM, RXP said: Maybe there is something with this folder which is not right on your system? I do not believe that in the meantime, but it could be testing if it is really necessary. The following is much more important: When the file sys_nand0 is deleted under C:\Program Files (x86)\Garmin\GNS Trainer\GNS , the sequence of the error changes. The following error message appears in the RealityXP log: 17/10/05 06:23:28.555 04840 - ] # rxpGnsSim64.dll version 2.3.2.0 17/10/05 06:24:43.807 10608 WARN ] copy: Der angegebene Pfadname ist ungültig., code: 000000a1 17/10/05 06:24:44.159 10608 WARN ] with: C:\ProgramData\Garmin\GNS Trainer Data\GNS\sys_nandc For this, the simulator (in the moment) can be opened and closed without a crash, even though the following error message is displayed under Windows: Protokollname: Application Quelle: Application Error Datum: 05.10.2017 08:25:36 Ereignis-ID: 1000 Aufgabenkategorie:(100) Ebene: Fehler Schlüsselwörter:Klassisch Benutzer: Nicht zutreffend Computer: ASUS Beschreibung: Name der fehlerhaften Anwendung: G530SIM.exe, Version: 0.0.0.0, Zeitstempel: 0x4bff0a69 Name des fehlerhaften Moduls: unknown, Version: 0.0.0.0, Zeitstempel: 0x00000000 Ausnahmecode: 0xc000041d Fehleroffset: 0x6028c1ed ID des fehlerhaften Prozesses: 0x2980 Startzeit der fehlerhaften Anwendung: 0x01d33da2b7264e74 Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Garmin\GNS Trainer\GNS\G530SIM.exe Pfad des fehlerhaften Moduls: unknown Berichtskennung: 94df7336-32f6-420c-a0a1-63c102545f54 Vollständiger Name des fehlerhaften Pakets: Anwendungs-ID, die relativ zum fehlerhaften Paket ist: Ereignis-XML: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-10-05T06:25:36.262848500Z" /> <EventRecordID>4618</EventRecordID> <Channel>Application</Channel> <Computer>ASUS</Computer> <Security /> </System> <EventData> <Data>G530SIM.exe</Data> <Data>0.0.0.0</Data> <Data>4bff0a69</Data> <Data>unknown</Data> <Data>0.0.0.0</Data> <Data>00000000</Data> <Data>c000041d</Data> <Data>6028c1ed</Data> <Data>2980</Data> <Data>01d33da2b7264e74</Data> <Data>C:\Program Files (x86)\Garmin\GNS Trainer\GNS\G530SIM.exe</Data> <Data>unknown</Data> <Data>94df7336-32f6-420c-a0a1-63c102545f54</Data> <Data> </Data> <Data> </Data> </EventData> </Event> It always begins with the error shown above in green and then the P3Dv4 crashes, if the file sys_nand0 under C:\Program Files (x86)\Garmin\GNS Trainer\GNS is not deleted, these errors follow: a) Protokollname: Application Quelle: .NET Runtime Datum: 05.10.2017 08:22:33 Ereignis-ID: 1026 Aufgabenkategorie:Keine Ebene: Fehler Schlüsselwörter:Klassisch Benutzer: Nicht zutreffend Computer: ASUS Beschreibung: Anwendung: Prepar3D.exe Frameworkversion: v4.0.30319 Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet. Ausnahmeinformationen: Ausnahmecode c0000005, Ausnahmeadresse 0000000000000000 Stapel: Ereignis-XML: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name=".NET Runtime" /> <EventID Qualifiers="0">1026</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-10-05T06:22:33.008115300Z" /> <EventRecordID>4609</EventRecordID> <Channel>Application</Channel> <Computer>ASUS</Computer> <Security /> </System> <EventData> <Data>Anwendung: Prepar3D.exe Frameworkversion: v4.0.30319 Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet. Ausnahmeinformationen: Ausnahmecode c0000005, Ausnahmeadresse 0000000000000000 Stapel: </Data> </EventData> </Event> b) Protokollname: Application Quelle: Application Error Datum: 05.10.2017 08:22:33 Ereignis-ID: 1000 Aufgabenkategorie:(100) Ebene: Fehler Schlüsselwörter:Klassisch Benutzer: Nicht zutreffend Computer: ASUS Beschreibung: Name der fehlerhaften Anwendung: Prepar3D.exe, Version: 4.0.28.21686, Zeitstempel: 0x594a7255 Name des fehlerhaften Moduls: unknown, Version: 0.0.0.0, Zeitstempel: 0x00000000 Ausnahmecode: 0xc0000005 Fehleroffset: 0x0000000000000000 ID des fehlerhaften Prozesses: 0x1798 Startzeit der fehlerhaften Anwendung: 0x01d33da1f0be8a73 Pfad der fehlerhaften Anwendung: C:\P3D\Prepar3D.exe Pfad des fehlerhaften Moduls: unknown Berichtskennung: 4370d7e8-bc5d-4ae4-bdcb-489dd55dc2a3 Vollständiger Name des fehlerhaften Pakets: Anwendungs-ID, die relativ zum fehlerhaften Paket ist: Ereignis-XML: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-10-05T06:22:33.181905000Z" /> <EventRecordID>4610</EventRecordID> <Channel>Application</Channel> <Computer>ASUS</Computer> <Security /> </System> <EventData> <Data>Prepar3D.exe</Data> <Data>4.0.28.21686</Data> <Data>594a7255</Data> <Data>unknown</Data> <Data>0.0.0.0</Data> <Data>00000000</Data> <Data>c0000005</Data> <Data>0000000000000000</Data> <Data>1798</Data> <Data>01d33da1f0be8a73</Data> <Data>C:\P3D\Prepar3D.exe</Data> <Data>unknown</Data> <Data>4370d7e8-bc5d-4ae4-bdcb-489dd55dc2a3</Data> <Data> </Data> <Data> </Data> </EventData> </Event> Otherwise, this error chain never occurs. Do we go on with it? best regards
October 5, 20178 yr Thank you for the additional logs and information. I'm yet to understand why P3D4 is failing on its own just because of this file though. Nevertheless, the RXP GNS V2 log file in the first case clearly says it has failed to find the source file ("sys_nand0") to copy from, but it works because you already have the local device copy on the drive ("sys_nandc"). 10 hours ago, SebastianStorb said: On October 3, 2017 at 7:17 AM, RXP said: Maybe there is something with this folder which is not right on your system? I do not believe that in the meantime, but it could be testing if it is really necessary. Can you please try this out? This will help us eliminate or confirm probable causes. Please make sure to use the latest v2.3.3 as well:
October 6, 20178 yr Hi Sebastian, By any chance do you have the SimConnect files installed? Including the Microsoft ESP SimConnect.msi. If not they are found in: \Prepar3D v4\redist\Interface\ESPv1 SimConnect.msi \Prepar3D v4\redist\Interface\FSX-RTM\retail\lib SimConnect.msi \Prepar3D v4\redist\Interface\FSX-SP1\retail\lib SimConnect.msi \Prepar3D v4\redist\Interface\FSX-SP2-XPACK\retail\lib SimConnect.msi
October 6, 20178 yr Author 16 hours ago, bills511 said: By any chance do you have the SimConnect files installed? Including the Microsoft ESP SimConnect.msi. Thank you very much for your advise! No - Bevore (09.09.2017) I had only one installed: But after installing today, rebooting and reinstalling RealityXP I have the same RealityXP errors. The .NET Runtime error comes only one time since i can see up till now. THANK U - Did I install enough now?
October 6, 20178 yr Author On Thursday, October 05, 2017 at 7:38 PM, RXP said: Can you please try this out? I tried: but no success. The GNS error is still there! On Thursday, October 05, 2017 at 8:51 AM, SebastianStorb said: G530SIM.exe, shows the same error logs!
October 6, 20178 yr Author On Thursday, October 05, 2017 at 7:38 PM, RXP said: Please make sure to use the latest v2.3.3 as well: Yes i uninstalled, rebooted and installed the new version. Sorry - did not help! :-(
October 6, 20178 yr Author Q1) Is it ok, that the Garmin Trainer can not be empowerd, if you open it without P3D? I can open it, update the required data under WFDEprdct.exe. But i is not possible to empower it with the left upper know. "Press the Power/COM vomume knop to power on the unit. The other knobs (i.g. HDG or SPEED) can be used. BUT the MASTER Switch is offline. Q2) Could it be, that i have the problems, because of having a single GNS430 installation (and did not buy both GNS430 & GNS530)? Was it tested with a single version computer?
October 6, 20178 yr 1) Yes this is normal and expected. 2) Are you trying to load a panel with a 530 although you've only purchased the 430?
October 6, 20178 yr Author 1 hour ago, RXP said: 2) Are you trying to load a panel with a 530 although you've only purchased the 430? No
October 7, 20178 yr 7 hours ago, SebastianStorb said: Could it be, that i have the problems, because of having a single GNS430 installation (and did not buy both GNS430 & GNS530)? Was it tested with a single version computer? Than I don't understand your question. Can you please explain further?
October 7, 20178 yr Author 6 hours ago, RXP said: Can you please explain further? My fear is that the software runs only error-free, if both program parts (GNS 430 AND GNS 530) were installed.
October 7, 20178 yr Hi, let me first thank you again for your endurance with this issue. Like you can read, we are trying to find out the root cause. The software is fine with either or both installed, hopefully! Otherwise this forum would be flooded with similar reports. In effect, being the only report of its kind leads me to favour the idea there is something in your system making our GNS V2 trigger these events like you've reported. It might be our GNS V2 is not doing well under some configuration which you'd be the only one to have, or, there is something inherently wrongly installed/configured on your system on it own. We've eliminated 'German' as a system language, other customers are from Germany too. We're eliminated anti-virus programs. We've eliminated GNS V2 installation problems, all files seem installed properly. We've NOT eliminated other modules/gauge though, which needs you to ensure you can run a genuine FS installation, no other add-ons, using only a default aircraft, but I doubt this is the root cause. The only thing strikingly different is your Windows system is installed and running from a different drive than the GNS V2 trainer. If I reming correctly, your Windows is on say 'D' and your GNS V2 is on 'C'. Maybe you might want to try installing the GNS trainer to your system drive instead and see if this has any effect? After reviewing all code which is surrounding what the logs are saying, this might be a possibility but this would have to be tested to be sure.
October 7, 20178 yr Some confusion on my part but Windows is installed on D drive? But GNS V2 is installed on C drive? Is the GNS installer creating these folders? C:\Program Files (x86), C:\ProgramData, C:\Users\[name]\Documents. I agree with Jean-Luc. Install GNS on the same drive as windows. Otherwise, I have never heard of windows on a drive other than the C drive. I know that's another topic.
Archived
This topic is now archived and is closed to further replies.