Hi Ed.

As a user of the SkyX and a series 1 MX myself it is difficult to think of anything that ACP, the Bisque ASCOM driver or MaxIm could do that would cause TheSyX to crash, this has to be something specific to the Paramount, Windows or TheSkyX.

The logs show that the last instruction before the problem was to start an exposure, are you using the Paramount Versa Plate USB ports to connect to the camera?

If so, disconnect all USB devices that are using the Versa Plate USB ports and run USB cables direct.

I have had so many problems with the internal USB cables that run from the MKS5000 control board up to the Versa Plate outlets that I stopped using them.
It's conceivable that a problem with those internal USB cables and connections to the devices, or the devices themselves, can break the control link between the Paramount and TheSkyX, causing TheSkyX to quit while leaving the mount still tracking since they all use the same internal hub on the Paramount control board.

A further issue may occur when running additional through-the-mount cabling on the Paramount as there is just insufficient room in the RA axis of the MX and eventually the cables becoming tangled in the RA axis and pull the internal USB cables partially out of their sockets on the MKS5000 board, which also can cause the Paramount to TheSkyX USB link to fail and TheSkyX to crash.

If this applies to your mount then drop the front of the MKS5000 tray and check that both the through-the-mount Versa Plate internal USB cables are still firmly pressed into their respective sockets at the left-front of the MKS5000 board.
From memory I think the sockets used for the Versa Plate USB outlets on the MKS board are USB0 and USB1 while socket USB2 is left empty.

Besides the above you might be a little behind with the Windows updates, there were two major updates on my Windows 10 Pro system this week, .NET 3.5-4.8 as well as the usual Windows quality updates and several Windows Defender signature and engine updates (which I haven't bothered listing separately):

KB5009543 Quality update 2022-01 for Windows 10 platform 21H2.
KB5008876 .NET 3.5-4.8 update 2022-01 for Windows 10 platform 21H2.

My Windows 10 PRO platform 21H2 is now at build 19044.1466.

It's possible your computer was trying to install either of the above updates and that caused the issue, check for updates manually.

Recheck also that your dedicated Windows Power-Plan for the observatory computer has retained the correct settings for USB sleep.
Here is a link to a document I wrote a few years ago on the Diffraction Limited forum that details how to create a bespoke Power-Plan in Windows:

https://forum.diffractionlimited.com...ate-1909.6546/

Lastly, check in MaxIm's own logs to see if anything else was reported from the camera(s) before TheSkyX crashed that might help point down the exact sequence of events (such as loss of communication, USB errors etc).

That's all I can think of at the moment, if I have any other ideas I'll come back to the thread later.

William.