Topics

APCC app crash when parking mount (Mach1) - event viewer details #APCC


Rodolphe
 

Hello
Yesterday evening I experienced a mount crash; when SGP command issued to park the mount at the end of the session, apparently APCC crashed.
SGP log and Windows event viewer follow below.
Please let me now if more details are needed.
Thanks

SGP Log at the time of event:
  • [09/09/20 04:53:17.438][DEBUG][Main Thread][SQ;PK;] Monitoring system shutdown...
  • [09/09/20 04:53:17.439][DEBUG][Main Thread][SQ;PK;] SequenceEnds complete...
  • [09/09/20 04:53:17.439][DEBUG][Sequence Thread][SQ;PK;] Restoring system standby state...
  • [09/09/20 04:53:20.303][DEBUG][Main Thread][PK;] PopulateDataModel:  Transferring view to the data model...
  • [09/09/20 04:53:20.325][DEBUG][MF Update Thread][PK;] Performing serialize...
  • [09/09/20 04:58:26.183][DEBUG][Telescope Thread][PK;] ASCOM Telescope: Error in ParkTel! : Object reference not set to an instance of an object.
  •    at r7.cf(String& A_0)
  • [09/09/20 04:58:26.183][ERROR][Telescope Thread][PK;] Error parking telescope: Error in Parking Telescope! See logs.
  • [09/09/20 04:58:26.184][INFO][Telescope Thread][PK;] Attempting to emergency stop mount and observatory...
  • [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] ASCOM Telescope: Setting tracking state to False
  • [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] ASCOM Telescope: Cannot set tracking state, not supported by scope...
  • [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] Attempting to stop PHD2 guiding...
  • [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] Checking PHD2 state...
  • [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] PHD2 GetPhdStatus - Pre-Wait : Stopped
  • [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] Sending to PHD2:
  • {"method": "get_app_state", "id": 1001}
  •  
  • [09/09/20 04:58:26.284][DEBUG][Telescope Thread][PK;] PHD2 GetPhdStatus - Post-Wait: Stopped
  • [09/09/20 04:58:26.284][DEBUG][Telescope Thread][PK;] PHD2 Guider is already stopped.
  • [09/09/20 04:58:26.284][DEBUG][Telescope Thread][PK;] Autoguider (PHD2) stopped Successfully
  • [09/09/20 04:58:26.284][DEBUG][Telescope Thread][NONE] SGM_TELESCOPE_PARK message complete...
  • [09/09/20 04:58:26.284][DEBUG][Telescope Thread][NONE] Telescope thread is IDLE...


Here are the details from the Windows event viewer:


Log Name:      Application
Source:        Application Error
Date:          09-Sep-20 4:57:42 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      NUC_Astro
Description:
Faulting application name: AstroPhysicsCommandCenter.exe, version: 1.8.3.0, time stamp: 0x5ed3b195
Faulting module name: ntdll.dll, version: 10.0.19041.423, time stamp: 0x6e329152
Exception code: 0xc00000fd
Fault offset: 0x00075027
Faulting process id: 0x1f38
Faulting application start time: 0x01d6860dfbb3abca
Faulting application path: C:\Program Files (x86)\Astro-Physics\APCC Standard\AstroPhysicsCommandCenter.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: b1ab35bb-1ce7-4ea4-9e53-49dad106c709
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2020-09-09T02:57:42.5982470Z" />
    <EventRecordID>6374</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>NUC_Astro</Computer>
    <Security />
  </System>
  <EventData>
    <Data>AstroPhysicsCommandCenter.exe</Data>
    <Data>1.8.3.0</Data>
    <Data>5ed3b195</Data>
    <Data>ntdll.dll</Data>
    <Data>10.0.19041.423</Data>
    <Data>6e329152</Data>
    <Data>c00000fd</Data>
    <Data>00075027</Data>
    <Data>1f38</Data>
    <Data>01d6860dfbb3abca</Data>
    <Data>C:\Program Files (x86)\Astro-Physics\APCC Standard\AstroPhysicsCommandCenter.exe</Data>
    <Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
    <Data>b1ab35bb-1ce7-4ea4-9e53-49dad106c709</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>


Ray Gralak
 

Hi Rodolphe,

Faulting module name: ntdll.dll, version: 10.0.19041.423, time stamp: 0x6e329152
Your info indicates the crash occurred in ntdll.dll, an operating system DLL, which means it is not actually APCC that caused the crash.

Windows potentially is out of date, or corrupted. It also could be your system memory could have had an error (one or more bits changed).

1. Which version of Windows are you running? (run from a command prompt: "WinVer")

2. Run cmd.exe "as administrator", then check your O/S by typing "sfc.exe /scannow"

3. Run Windows update and apply all updates.

4. Find and download a memory checker to determine if there is a problem with memory on your system. If there is a problem, you should try reseating your dynamic RAM modules.

5. Many of the links with ntdll.dll crashes suggest to try unregistering and re-registering the ntdll.dll. For example:

https://answers.microsoft.com/en-us/windows/forum/all/faulting-module-name-ntdlldll/82a80b07-6d81-40f7-8aa6-b11f00098480

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Rodolphe
Sent: Wednesday, September 9, 2020 12:37 AM
To: main@ap-gto.groups.io
Subject: [ap-gto] APCC app crash when parking mount (Mach1) - event viewer details #APCC

Hello
Yesterday evening I experienced a mount crash; when SGP command issued to park the mount at the end of the
session, apparently APCC crashed.
SGP log and Windows event viewer follow below.
Please let me now if more details are needed.
Thanks

SGP Log at the time of event:

* [09/09/20 04:53:17.438][DEBUG][Main Thread][SQ;PK;] Monitoring system shutdown...
* [09/09/20 04:53:17.439][DEBUG][Main Thread][SQ;PK;] SequenceEnds complete...
* [09/09/20 04:53:17.439][DEBUG][Sequence Thread][SQ;PK;] Restoring system standby state...
* [09/09/20 04:53:20.303][DEBUG][Main Thread][PK;] PopulateDataModel: Transferring view to the data
model...
* [09/09/20 04:53:20.325][DEBUG][MF Update Thread][PK;] Performing serialize...
* [09/09/20 04:58:26.183][DEBUG][Telescope Thread][PK;] ASCOM Telescope: Error in ParkTel! : Object
reference not set to an instance of an object.
* at r7.cf(String& A_0)
* [09/09/20 04:58:26.183][ERROR][Telescope Thread][PK;] Error parking telescope: Error in Parking
Telescope! See logs.
* [09/09/20 04:58:26.184][INFO][Telescope Thread][PK;] Attempting to emergency stop mount and
observatory...
* [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] ASCOM Telescope: Setting tracking state to
False
* [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] ASCOM Telescope: Cannot set tracking state,
not supported by scope...
* [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] Attempting to stop PHD2 guiding...
* [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] Checking PHD2 state...
* [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] PHD2 GetPhdStatus - Pre-Wait : Stopped
* [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] Sending to PHD2:
* {"method": "get_app_state", "id": 1001}
*
* [09/09/20 04:58:26.284][DEBUG][Telescope Thread][PK;] PHD2 GetPhdStatus - Post-Wait: Stopped
* [09/09/20 04:58:26.284][DEBUG][Telescope Thread][PK;] PHD2 Guider is already stopped.
* [09/09/20 04:58:26.284][DEBUG][Telescope Thread][PK;] Autoguider (PHD2) stopped Successfully
* [09/09/20 04:58:26.284][DEBUG][Telescope Thread][NONE] SGM_TELESCOPE_PARK message
complete...
* [09/09/20 04:58:26.284][DEBUG][Telescope Thread][NONE] Telescope thread is IDLE...



Here are the details from the Windows event viewer:


Log Name: Application
Source: Application Error
Date: 09-Sep-20 4:57:42 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: NUC_Astro
Description:
Faulting application name: AstroPhysicsCommandCenter.exe, version: 1.8.3.0, time stamp: 0x5ed3b195
Faulting module name: ntdll.dll, version: 10.0.19041.423, time stamp: 0x6e329152
Exception code: 0xc00000fd
Fault offset: 0x00075027
Faulting process id: 0x1f38
Faulting application start time: 0x01d6860dfbb3abca
Faulting application path: C:\Program Files (x86)\Astro-Physics\APCC Standard\AstroPhysicsCommandCenter.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: b1ab35bb-1ce7-4ea4-9e53-49dad106c709
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-09-09T02:57:42.5982470Z" />
<EventRecordID>6374</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>NUC_Astro</Computer>
<Security />
</System>
<EventData>
<Data>AstroPhysicsCommandCenter.exe</Data>
<Data>1.8.3.0</Data>
<Data>5ed3b195</Data>
<Data>ntdll.dll</Data>
<Data>10.0.19041.423</Data>
<Data>6e329152</Data>
<Data>c00000fd</Data>
<Data>00075027</Data>
<Data>1f38</Data>
<Data>01d6860dfbb3abca</Data>
<Data>C:\Program Files (x86)\Astro-Physics\APCC Standard\AstroPhysicsCommandCenter.exe</Data>
<Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
<Data>b1ab35bb-1ce7-4ea4-9e53-49dad106c709</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>


Ray Gralak
 

Rodolphe,

Also, can you use APCC's log zipper to zip your logs and place them in the files section, or post a link to a dropbox or other folder?

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Rodolphe
Sent: Wednesday, September 9, 2020 12:37 AM
To: main@ap-gto.groups.io
Subject: [ap-gto] APCC app crash when parking mount (Mach1) - event viewer details #APCC

Hello
Yesterday evening I experienced a mount crash; when SGP command issued to park the mount at the end of the
session, apparently APCC crashed.
SGP log and Windows event viewer follow below.
Please let me now if more details are needed.
Thanks

SGP Log at the time of event:

* [09/09/20 04:53:17.438][DEBUG][Main Thread][SQ;PK;] Monitoring system shutdown...
* [09/09/20 04:53:17.439][DEBUG][Main Thread][SQ;PK;] SequenceEnds complete...
* [09/09/20 04:53:17.439][DEBUG][Sequence Thread][SQ;PK;] Restoring system standby state...
* [09/09/20 04:53:20.303][DEBUG][Main Thread][PK;] PopulateDataModel: Transferring view to the data
model...
* [09/09/20 04:53:20.325][DEBUG][MF Update Thread][PK;] Performing serialize...
* [09/09/20 04:58:26.183][DEBUG][Telescope Thread][PK;] ASCOM Telescope: Error in ParkTel! : Object
reference not set to an instance of an object.
* at r7.cf(String& A_0)
* [09/09/20 04:58:26.183][ERROR][Telescope Thread][PK;] Error parking telescope: Error in Parking
Telescope! See logs.
* [09/09/20 04:58:26.184][INFO][Telescope Thread][PK;] Attempting to emergency stop mount and
observatory...
* [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] ASCOM Telescope: Setting tracking state to
False
* [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] ASCOM Telescope: Cannot set tracking state,
not supported by scope...
* [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] Attempting to stop PHD2 guiding...
* [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] Checking PHD2 state...
* [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] PHD2 GetPhdStatus - Pre-Wait : Stopped
* [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] Sending to PHD2:
* {"method": "get_app_state", "id": 1001}
*
* [09/09/20 04:58:26.284][DEBUG][Telescope Thread][PK;] PHD2 GetPhdStatus - Post-Wait: Stopped
* [09/09/20 04:58:26.284][DEBUG][Telescope Thread][PK;] PHD2 Guider is already stopped.
* [09/09/20 04:58:26.284][DEBUG][Telescope Thread][PK;] Autoguider (PHD2) stopped Successfully
* [09/09/20 04:58:26.284][DEBUG][Telescope Thread][NONE] SGM_TELESCOPE_PARK message
complete...
* [09/09/20 04:58:26.284][DEBUG][Telescope Thread][NONE] Telescope thread is IDLE...



Here are the details from the Windows event viewer:


Log Name: Application
Source: Application Error
Date: 09-Sep-20 4:57:42 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: NUC_Astro
Description:
Faulting application name: AstroPhysicsCommandCenter.exe, version: 1.8.3.0, time stamp: 0x5ed3b195
Faulting module name: ntdll.dll, version: 10.0.19041.423, time stamp: 0x6e329152
Exception code: 0xc00000fd
Fault offset: 0x00075027
Faulting process id: 0x1f38
Faulting application start time: 0x01d6860dfbb3abca
Faulting application path: C:\Program Files (x86)\Astro-Physics\APCC Standard\AstroPhysicsCommandCenter.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: b1ab35bb-1ce7-4ea4-9e53-49dad106c709
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-09-09T02:57:42.5982470Z" />
<EventRecordID>6374</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>NUC_Astro</Computer>
<Security />
</System>
<EventData>
<Data>AstroPhysicsCommandCenter.exe</Data>
<Data>1.8.3.0</Data>
<Data>5ed3b195</Data>
<Data>ntdll.dll</Data>
<Data>10.0.19041.423</Data>
<Data>6e329152</Data>
<Data>c00000fd</Data>
<Data>00075027</Data>
<Data>1f38</Data>
<Data>01d6860dfbb3abca</Data>
<Data>C:\Program Files (x86)\Astro-Physics\APCC Standard\AstroPhysicsCommandCenter.exe</Data>
<Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
<Data>b1ab35bb-1ce7-4ea4-9e53-49dad106c709</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>


Joe Zeglinski
 

Hi Ray,
 
    FYI. To your point #4, no need to find one. Recall that there is a Windows provided off-line memory test – under START->ADMINISTRATIVE TOOLS –> “Windows Memory Diagnostic”.
 
    The user can run a single pass which would take something like 20 minutes depending on memory size, or change the on-screen  option for multiple reruns, perhaps for hours, until (maybe) a failure finally comes up, due to maybe a memory module  or case temperature heat. The results of the run will pop up shortly after the program reboots Windows, and will also be found inside the Notifications icon.
 
Joe Z.
 

From: Ray Gralak
Sent: Wednesday, September 9, 2020 9:31 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC app crash when parking mount (Mach1) - event viewer details #APCC
 
Hi Rodolphe,

> Faulting module name: ntdll.dll, version: 10.0.19041.423, time stamp: 0x6e329152

Your info indicates the crash occurred in ntdll.dll, an operating system DLL, which means it is not actually APCC that caused the crash.

Windows potentially is out of date, or corrupted. It also could be your system memory could have had an error (one or more bits changed).

1. Which version of Windows are you running? (run from a command prompt: "WinVer")

2. Run cmd.exe "as administrator", then check your O/S by typing "sfc.exe /scannow"

3. Run Windows update and apply all updates.

4. Find and download a memory checker to determine if there is a problem with memory on your system. If there is a problem, you should try reseating your dynamic RAM modules.

5. Many of the links with ntdll.dll crashes suggest to try unregistering and re-registering the ntdll.dll. For example:

https://answers.microsoft.com/en-us/windows/forum/all/faulting-module-name-ntdlldll/82a80b07-6d81-40f7-8aa6-b11f00098480

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


Rodolphe
 

Hi Ray
Many thanks for the feedback. I'm running Win10, latest version, systematically updated with the windows updates.
I've just launched a mem check, will report if any issues there.
Will also post the zipped logs on a shared folder, once the PC accepts to log me in!
Thanks
KR
Rodolphe


Rodolphe
 

Here's the link to the logs:
https://1drv.ms/u/s!AvO2KZoP803hor9FwEhPAYzmsSjwzw?e=8VN42W
Mem diag didn't return any errors.
Version is 2004 (build 19041.508)
O/S check reported a minor bluetooth driver error, fixed it, and a second run after rebooting didn't find further errors.
I won't tinker with ntdll.dll at this point, until I see more issues popping up like that one above.
Thanks
Rodolphe


Ray Gralak
 

Hi Rodolphe,

Looking at your logs, you seem to have switched between connections a few times. For example, COM3 to COM4, to Ethernet, and back to COM4. Are you have problems with connections, or just trying different connection methods?

COM4 looks like it uses a Prolific chip, which is known to have some issues compared to devices that use FTDI chips. I'm not sure if that caused this problem, but the ntdll.dll crash seemed to happen during a transmit.

I suggest you do a web search to see if there are any problems reported on the specific USB/serial converter you are using. Maybe also check if there is a driver update for the USB/Serial converter.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Rodolphe
Sent: Thursday, September 10, 2020 1:56 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC app crash when parking mount (Mach1) - event viewer details #APCC

Here's the link to the logs:
https://1drv.ms/u/s!AvO2KZoP803hor9FwEhPAYzmsSjwzw?e=8VN42W
Mem diag didn't return any errors.
Version is 2004 (build 19041.508)
O/S check reported a minor bluetooth driver error, fixed it, and a second run after rebooting didn't find further
errors.
I won't tinker with ntdll.dll at this point, until I see more issues popping up like that one above.
Thanks
Rodolphe


Rodolphe
 

Hi Ray
Thanks for your investigation.
Correct, I tried different options to stabilize the connection to CP4 and finally settled with Ethernet.
Last night, I had an 8-hour continuous session without any comm error, this is perfect.
issue closed!
Kind regards
Rodolphe