Thats an interesting, and complex issue!

FWIW, I have run Exp in complex setups (numerous serial connections, numerous UDP and TCP network connections, reading/writing via DLL from 3rd party (mine) apps etc) and run for days on end without any issues. I actually do a full system reboot every 2-3 days, maybe unnecessarily, to prevent any possible  system interruptions cause by any source (windows/expedition/3rd party apps/virtual serial port drivers etc) - since these usually occur at the least convenient time.

So, only trying to think of anything out of the ordinary that you might be experienceing:

- Windows version and level? i.e. Home/Pro etc - I always use Pro
- User profile has Administrator permissions?
- Odd folder read/write permissions in data dir? Witnessed in the past Windows config where permissions were not properly provisioned
- Running Exp as Administrator?
- Default installation locations?
- Windows firewall/defender or any other 3rd party security apps? - I never use 3rd party
- Assume latest version of Exp?
- PC RAM? - for me these days minimum 32GB
- SSD or HDD?
- USB-serial or USB-ethernet adapters? If yes, standard drivers?
- Tried an Exp system restore?
- Are you migrating settings/files from/to? LIke Marks.xml, states, stripcharts, user config files, *.reg settings, etc etc?

 

 

Roma wrote:

Thank you for the ideas and the questions, here are the details below:

- was Windows 10 and Windows 11, Pro or higher. I was using Windows Remote Desktop to connect to PC from a deck tablet, not always, the problem exists without RDP
- the user profile does have admin permissions, however Expedition is starting in "normal" mode without explicit elevation to admin privileges. I was thinking it would ask for admin permissions if they are needed
- odd permissions on folders are unlikely, because it was on different PCs, with just standard installation, no fancy folders
- yes, default installation locations
- just windows defender
- the latest version at the time of the race, as I mentioned in the previous post, I've seen that multiple times over past few years
- RAM was usually 16Gb. I can try with 32GB, however I doubt how it would help with CMap - that version is 32 bit, it is not supposed to care about anything more than 4Gb. in your experience with 32Gb, how much does Expedition use?
- always SSD
- adapters activesense NGX-1 or NGW-1, standard drivers, yes
- Expedition system restore? haven't tried, do you recommend trying it next time?
- I did migrate some settings sometimes, not always, mostly marks if I was preparing the route at home before the race.

- any considerations about GPU (graphical card)? 

• I'd try always setting Exp to run with admin privileges. I do this as standard.
• Not sure it is Maps Manager causing the issue as a 32-bit app
• The more memory the better - I use as much as I can get on any machine. Irrespective of what Exp will use, I have had struggles with 32-bit/16GB machines when, for example larger grib files are loaded and pushing times back/fwd. I'm not suggesting that the machine is running out of memory etc, just that it could be a contributor.
• On that note I regularly 'flush' out of Exp older grib files.
• Can't comment specifically on GPU, but have a review here: https://www.expeditionmarine.com/resources.html#gpu
• I'm assuming your NGX/NGW are USB devices? Personally I'm not a fan of depending on these as a primary data input (cannot qualify with evidence etc), nor am I suggesting that these are the cause of issues, but if you have an alternative method of connection would be worth trying.

Exp system restore
• Is a PITA to build Exp from the ground up, but have had success in the past when something odd is happening. i.e. my home machine would not run Simulator which was only resolved with a full Exp Sys restore of registry settings.