First post.  Not a windows expert.   3rd year Rookie.
Setup: Toughbook CF31, latest windows 10 and latest expedition, (garmin gps, heading, AIS, ...) N2000 through actisense NGT-1 USB w/updated firmware and drivers + (old ockam T1 wind (good wand and new card), bsp, depth) serial with tripp-lite keyspan serial/USB converter.  Compute TWD, TWA, TWS in expedition, and push out info to garmin mast/cockpit displays.  Worked solid all last season, ran 24hrs+ (never crashed).

This season day one/two on the water ended yesterday.  Latest version of Windows 10, latest Expedition version.  Same connections, fired up on CF31, running, info from both sides (garmin n2000 and ockam serial) showing up (raw streams on both), then a series of unexpected Expedition shut downs (every 5-10 min random)  Strip Chart stays running).  Day 2  on water same thing, but after the 4th or 5th shutdown it managed to stay up for a couple hours.

** Then tried newer CF54 (more RAM and SSD), up to date Win 10 and latest Expedition.  Same crashes/shutdowns but almost immediately.  Played around and found it was the serial/tripp-lite input causing the shutdown.  Would run clean with just n2000 input, or with no inputs, but plugin that ockam/serial.USB converter cable and down immediately.  Then eventually really broke it, and expedition would start and immediately shutdown.  Took home, tried to reload, no joy, but stumbled over the system restore app, and deleted display states and deleted all registry, and the program runs again.

I am pretty sure when I plug back in on the boat it will repeat.

Any ideas out there or similar experience? 

Only real changes this year were latest Win 10, latest Expedition, and the second computer (CF54) which seems more sensitive than the CF31, but both crash. And from I could figure it was the ockam/serial input causing the issues.