0.00
...
·
 |
|---|
|
Last night Nina just stopped running. My last 3 lines in the log file are 2024-09-15T04:20:37.3747|INFO|ImageSaveController.cs|DoWork|97|Successfully saved file at C:\Users\Brian Watson\Documents\N.I.N.A\2024-09-14\LIGHT\Beehive Cluster_2024-09-15_04-19-31__GAIN-400_60.00.cr2. Duration Total: 00:00:02.7054780; BeforeSave: 00:00:00.0002686; BeforeFinalizeImageSaved: 00:00:02.6988006; FinalizeSaveTime: 00:00:00.0064080 2024-09-15T04:20:38.9477|INFO|ImageSolver.cs|Solve|54|Platesolve successful: Coordinates: RA: 08:40:23; Dec: 19° 39' 55"; Epoch: J2000 2024-09-15T04:20:38.9478|INFO|CenterAfterDriftTrigger.cs|PlatesolvingImageFollower_PropertyChanged|189|Drift: 0.1980992113481068 / 1.3 arc minutes Any ideas? If it exits unexpectedly it doesn't seem to give any message the next time it starts up. |
6.06
...
·
·
1
like
|
|---|
| Generally if the NINA log does not show the reason it is caused by some lower level crash of the process. Look in the windows Application and System event logs (run the event viewer) and see what occurred around those times. Typical causes can be hardware failures, memory errors, bugs in .net, etc., but any clues will likely be there. If it isn't obvious the cause, I recommend putting that event viewer entry(s) on discord for the developers to see. |
|
0.00
...
·
|
|---|
| Thanks. I will look into that. |
0.90
...
·
|
|---|
| Was this just after a meridian flip or a slew? Sometimes cables catch and the USB data results in NINA crashing. You may want to look at your connections, especially if you have a USB hub. Power interruptions to your devices are also a primary suspect. I had problems with the Pegasus Astro hub by using the improper connection that caused input power issues. |
|
6.06
...
·
|
|---|
|
If you actually have crashes (where there's no log entry just event viewer) caused by USB problems, it may be useful to share with the developers. Most such errors are captured and show up as disconnects of devices in the logs. They (I am not one) work pretty hard to intercept errors like that and log them, as to many users the cryptic messages in the event viewer are not a lot of help (often to seasoned developers they are not either, Microsoft being Microsoft). Not suggesting they don't happen, just that it's nice if they can fix to be more user friendly if so. Terminology -- if NINA intercepts an error and can log it, and the NINA window goes away, it's not considered a crash. It may be a really bad error and not continue working right, but for developers crash means the whole program terminated and disappeared, and at best your only sign is a blank screen and event log entries. |
3.81
...
·
|
|---|
|
Brian, this just happened to me recently. It was corrupt system files embedded in Windows 11. I wish I could remember the dos command that I used, but it was given to me by my IT guy at work. I ran it and I did a repair. I also ran a low level disc check and repair on my storage drives. That seemed to have fixed the problem. Windows 11 was restarting due to these errors and Nina never logged the reboot either. So I had to go into system events in windows and there I matched up the times of my last image and the random restart. best of luck! Tom |
|
0.00
...
·
|
|---|
Charles Bradshaw: No, at 4am I had restarted because of dslr camera connection. It had taken 20 minutes worth of 1 minute pictures. I suspect the camera possibly disconnected (another issue to be figured out) but usually Nina handles that fine. This is the first time I have experienced Nina just up and quitting. I'll see if it happens again. |
|
0.90
...
·
|
|---|
Brian Watson:Charles Bradshaw: It looks as if your sequence did a slew because" "2024-09-15T04:20:38.9477|INFO|ImageSolver.cs|Solve|54|Platesolve successful: Coordinates: RA: 08:40:23; Dec: 19° 39' 55"; Epoch: J2000 2024-09-15T04:20:38.9478|INFO|CenterAfterDriftTrigger.cs|PlatesolvingImageFollower_PropertyChanged|189|Drift: 0.1980992113481068 / 1.3 arc minutes" The center after drift trigger suggests you were off target enough to re-slew to re-center. I've found that this most often happens to me if I have a cable drag. Look at your guiding log to see if your stars were not round or guiding failed. This can also cause your DSLR to disconnet. |
|
0.00
...
·
|
|---|
|
“Look in the windows Application and System event logs (run the event viewer) and see what occurred around those times.” I see the following. This may be a one up fluke but it might mean something to someone. Log Name: Application Source: .NET Runtime Date: 2024-09-15 4:20:39 AM Event ID: 1026 Task Category: None Level: Error Keywords: Classic User: N/A Computer: JBWAstroRig1 Description: Application: NINA.exe CoreCLR Version: 8.0.624.26715 .NET Version: 8.0.6 Description: The process was terminated due to an unhandled exception. Exception Info: exception code c0000005, exception address 00007FFB448D1B82 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name=".NET Runtime" /> <EventID Qualifiers="0">1026</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2024-09-15T08:20:39.8378549Z" /> <EventRecordID>5793</EventRecordID> <Correlation /> <Execution ProcessID="8124" ThreadID="0" /> <Channel>Application</Channel> <Computer>JBWAstroRig1</Computer> <Security /> </System> <EventData> <Data>Application: NINA.exe CoreCLR Version: 8.0.624.26715 .NET Version: 8.0.6 Description: The process was terminated due to an unhandled exception. Exception Info: exception code c0000005, exception address 00007FFB448D1B82 </Data> </EventData> </Event> then Log Name: Application Source: Application Error Date: 2024-09-15 4:20:40 AM Event ID: 1000 Task Category: Application Crashing Events Level: Error Keywords: Classic User: N/A Computer: JBWAstroRig1 Description: Faulting application name: NINA.exe, version: 3.1.1.9001, time stamp: 0x66470000 Faulting module name: wpfgfx_cor3.dll, version: 8.0.624.26906, time stamp: 0x664acc71 Exception code: 0xc0000005 Fault offset: 0x0000000000061b82 Faulting process id: 0x%9 Faulting application start time: 0x%10 Faulting application path: %11 Faulting module path: %12 Report Id: %13 Faulting package full name: %14 Faulting package-relative application ID: %15 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" EventSourceName="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2024-09-15T08:20:40.9376288Z" /> <EventRecordID>5794</EventRecordID> <Correlation /> <Execution ProcessID="7908" ThreadID="0" /> <Channel>Application</Channel> <Computer>JBWAstroRig1</Computer> <Security /> </System> <EventData> <Data>NINA.exe</Data> <Data>3.1.1.9001</Data> <Data>66470000</Data> <Data>wpfgfx_cor3.dll</Data> <Data>8.0.624.26906</Data> <Data>664acc71</Data> <Data>c0000005</Data> <Data>0000000000061b82</Data> </EventData> </Event> |
|
6.06
...
·
·
1
like
|
|---|
| The developers mostly hang out on Discord, if you want to post there. Maybe one will show up here. All I can tell you is it appears screen-update related and buried in .net. Might be a bug, might be something in your screen drivers (including RDP drivers if remote). But that's the sort of info they would need to see if it rings any bells. |
