Crashing during Live Stack
Posted: Wed Apr 29, 2026 10:21 pm
I'm in the process of setting up a second rig. I have an older (2023) Beelink mini computer running SC v4.1.12529 and a newer (2025) Beelink mini running SC v4.1.14265, both under Windows 11 Pro.
The old system: Beelink AMD Ryzen 7 5700U, 16 GB RAM, 932 GB SSD, Windows 11 Pro 25H2
The new system: Beelink AMD Ryzen 7 5825U, 32 GB RAM, 477 GB DDS, Windows 11 Pro 25H2
The older system runs like a champ, but the newer one has intermittent issues. I have built an observatory in the backyard with the rigs on adjacent piers. I control the rigs from inside the house over Windows RDP. The internet to the house is over wifi, but it is very fast. The old and new rigs do everything I expect them to do, but when running DSO Live Stack, the new one has problems.
I'll have started up in the late afternoon, connected via RDP, and run my calibration frames. I get a live view with the camera looping, waiting for dark. The camera (ASI2600MC) is cool and ready to go. I start ASIMOUNT for my AM5 mount and PHD2 for guiding. I use the GOTO Catalog to pull up a target and do an autofocus run. Then I start Live Stack. It may run for an hour or more without incident, or it may crash after one or two light frames. I have found no pattern as to how long it will run before crashing.
When it crashes, this is the behavior: I'm monitoring the Live Stack from inside the house. Everything looks normal. Then the camera exposure bar stops updating, and I notice that the screen is frozen. RDP says it's having trouble connecting and eventually gives up. I reconnect by RDP. Normally, it has stored the password and connects without asking for a password, but when this happens, it asks for a password. When I connect, SC, PHD2, and ASIMOUNT have all stopped running. It's as if the computer has restarted or logged out. When I restart SC, the camera has warmed up.
I have multiple ASI2600MCs that I have tried, and I have swapped out USB cables and power supplies. The only constant that I have found is that the old computer with old software runs fine, and the new computer with new software has the problem, but only during Live Stack. It runs dark frame captures and sequences fine. I'm attaching a log file from a recent run. As far as I am able to make out, everything looks fine. It just stops in the middle of a light frame capture with no error message. The PHD2 log also just seems to stop.
I'm not sure whether this is problem with this particular version of SC or whether it is a Windows problem. In the attached log file SC has started a capture with no report of finishing it, but according to the time stamp, the light frame was saved after that last log entry. At the same time as the timestamp of the last light frame, the Windows System log records a critical error: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Would it be advisable to load onto the new computer the same version of SC that is working on the old one? This might tell me whether the problem is with the version or with the computer.
The old system: Beelink AMD Ryzen 7 5700U, 16 GB RAM, 932 GB SSD, Windows 11 Pro 25H2
The new system: Beelink AMD Ryzen 7 5825U, 32 GB RAM, 477 GB DDS, Windows 11 Pro 25H2
The older system runs like a champ, but the newer one has intermittent issues. I have built an observatory in the backyard with the rigs on adjacent piers. I control the rigs from inside the house over Windows RDP. The internet to the house is over wifi, but it is very fast. The old and new rigs do everything I expect them to do, but when running DSO Live Stack, the new one has problems.
I'll have started up in the late afternoon, connected via RDP, and run my calibration frames. I get a live view with the camera looping, waiting for dark. The camera (ASI2600MC) is cool and ready to go. I start ASIMOUNT for my AM5 mount and PHD2 for guiding. I use the GOTO Catalog to pull up a target and do an autofocus run. Then I start Live Stack. It may run for an hour or more without incident, or it may crash after one or two light frames. I have found no pattern as to how long it will run before crashing.
When it crashes, this is the behavior: I'm monitoring the Live Stack from inside the house. Everything looks normal. Then the camera exposure bar stops updating, and I notice that the screen is frozen. RDP says it's having trouble connecting and eventually gives up. I reconnect by RDP. Normally, it has stored the password and connects without asking for a password, but when this happens, it asks for a password. When I connect, SC, PHD2, and ASIMOUNT have all stopped running. It's as if the computer has restarted or logged out. When I restart SC, the camera has warmed up.
I have multiple ASI2600MCs that I have tried, and I have swapped out USB cables and power supplies. The only constant that I have found is that the old computer with old software runs fine, and the new computer with new software has the problem, but only during Live Stack. It runs dark frame captures and sequences fine. I'm attaching a log file from a recent run. As far as I am able to make out, everything looks fine. It just stops in the middle of a light frame capture with no error message. The PHD2 log also just seems to stop.
I'm not sure whether this is problem with this particular version of SC or whether it is a Windows problem. In the attached log file SC has started a capture with no report of finishing it, but according to the time stamp, the light frame was saved after that last log entry. At the same time as the timestamp of the last light frame, the Windows System log records a critical error: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Would it be advisable to load onto the new computer the same version of SC that is working on the old one? This might tell me whether the problem is with the version or with the computer.