Simlink crash on startup

Hello,

I’ve replied to another topic about this, but maybe it wasn’t the right thing to do, so here goes.
Simlink silently crashes on startup, leaving a dump file. No Simlink logs are created.
Here is a sample from Windows’ event log:

Nom de l’application défaillante NavigraphSimlink.exe, version : 1.1.21.329, horodatage : 0x60623430
Nom du module défaillant : Qt5Widgets.dll, version : 5.12.3.0, horodatage : 0x5cac5778
Code d’exception : 0xc0000005
Décalage d’erreur : 0x0000000000100d5f
ID du processus défaillant : 0x324c
Heure de début de l’application défaillante : 0x01d7320e7d320dd4
Chemin d’accès de l’application défaillante : C:\Program Files\Navigraph\Simlink\NavigraphSimlink.exe
Chemin d’accès du module défaillant: C:\Program Files\Navigraph\Simlink\Qt5Widgets.dll
ID de rapport : 324ae097-899a-42fa-8796-3a4fdf4a8c53
Nom complet du package défaillant :
ID de l’application relative au package défaillant :slight_smile:

And here is the relevant part from the dump:

ExceptionAddress: 00007ff9312d0d5f (Qt5Widgets!QComboBox::setCurrentIndex+0x000000000000000f)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000008
Attempt to read from address 0000000000000008

I am running Windows 10 20H2 10.0.19041.1. I have not used Simlink on this computer before, but previous versions had worked pretty well on the previous setup. I’ve tried the usual steps (run as admin, disable A/V, even installed on a different disk) but nothing helped.

I’d of course be willing to try various debugging steps in order to help solve this problem.
Thanks a lot and best regards
Romain

Hi there,
I’ve got the exact same problem with 1.1.21.0329: already completely deinstalled and reinstalled, to no avail. Nothing appears in the systray, ever. No logs are created either.
This is a brand new computer, so I can’t say it has worked before. However, the symptoms are identical to OP’s.
Thanks for your help

Windows’ event log reports this:

Nom de l’application défaillante NavigraphSimlink.exe, version : 1.1.21.329, horodatage : 0x60623430
Nom du module défaillant : Qt5Widgets.dll, version : 5.12.3.0, horodatage : 0x5cac5778
Code d’exception : 0xc0000005
Décalage d’erreur : 0x0000000000100d5f
ID du processus défaillant : 0x324c
Heure de début de l’application défaillante : 0x01d7320e7d320dd4
Chemin d’accès de l’application défaillante : C:\Program Files\Navigraph\Simlink\NavigraphSimlink.exe
Chemin d’accès du module défaillant: C:\Program Files\Navigraph\Simlink\Qt5Widgets.dll
ID de rapport : 324ae097-899a-42fa-8796-3a4fdf4a8c53
Nom complet du package défaillant :
ID de l’application relative au package défaillant :

Regards
Romain

I’ve briefly opened the dump:

ExceptionAddress: 00007ff9312d0d5f (Qt5Widgets!QComboBox::setCurrentIndex+0x000000000000000f)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000008
Attempt to read from address 0000000000000008

Now why would this fail in some cases and not in others, I don’t know yet.
This is on W10 with the latest updates (ie . 20H2 10.0.19041.1), nothing special about the setup. I’ve tried the usual steps (run as admin, disable A/V, even installed on a different disk) but nothing helped.

Cheers

Romain

Hi Romain,

Welcome.

Not that I think it is an issue, but I show the latest Windows 10 build as 19042.928, so I suggest you update.

Please disable your Antivirus and firewall

Please use only Windows Programs and Features to uninstall Simlink:

image

If they exist delete directories
c:\Users\username\AppData\Roaming\Navigraph\Simlink and c:\Program Files\Navigraph\Simlink.

Then download and install Simlink .

Please let us know how you get on.

Cheers
Ian

Hi Ian,

Well when I posted, I had just performed a full update, so indeed, I don’t think it would matter, all the more as the error seems to come from Qt5.

I had already performed all of the troubleshooting steps you mention prior to posting, sorry if that wasn’t clear enough, but it did not help at all.

Looking forward to your reply,
Cheers
Romain

Hi again,
For what it’s worth, I’m running W10 19042.928 now and it hasn’t help one bit :wink:

Cheers
Romain

Hi Ian,

I haven’t heard from you in a week and I don’t know what to make of it. Is the problem being investigated with no result so far, or has it gone under the radar? What can I do to help?
Cheers
Romain

Hi Romain,

We have been investigating. Our Simlink developer will be in touch soon.

Cheers
Ian

Hi Ian,

Good to hear, thanks for the feedback!

Cheers
Romain

Hi Romain,

We have some health issues, which will delay our response.

Thank you for your patience.

Cheers
Ian

Hi Ian,

Understood, sorry to hear that. Take care!
Cheers
Romain

Hi Romain,

I believe this is now resolved - was an incorrect string in .settings file?

Please confirm and I shall mark as resolved.

Cheers
Ian

Hi,

This i resolved.

Br
Lasse

Lasse Törnqvist
V. Gösbäcksvägen 7
393 65 Kalmar
070-554 04 35

Hi Ian,

I never edited the .settings file, so I would say it got corrupt more than “incorrect”. I guess that’s for you to investigate further.

As a side note, requesting access to the user’s computer for something as simple as deleting a config file is overkill :slight_smile:

Cheers
Romain

Hi Romain,

I wasn’t implying you edited it. We have taken steps to ensure the file doesn’t get corrupted.

The time taken to resolve your issue suggested remote access was the next step. Glad it is resolved.

Cheers
Ian

Hi Ian,

Don’t take this the wrong way, but the “time taken” was just me waiting for someone to get in touch. I’m sure you were looking into it on your end in the meantime. But from my perspective, it just looked as if the first step to resolve this was “please give us access to your computer”, when removing a corrupt file was all that was needed. This is what I call overkill, and I’m sure you can understand that :wink:

Cheers
Romain

Hi Romain,

Sure, Glad is is resolved

Happy flying.

Ian

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.