After running WINDBG application, log file provided the following information near the end:

ModLoad: 1ccc0000 1d95e000 C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_3f9eae06dd582000\ig9icd32.dll
ModLoad: 5d360000 5d36f000 C:\WINDOWS\SysWOW64\resourcepolicyclient.dll
ModLoad: 79030000 7905c000 C:\WINDOWS\System32\DriverStore\FileRepository\nvdmwi.inf_amd64_ea069416c21f849f\nvdlist.dll
(5f2c.5594): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=0019d658 ebx=1a7e81e8 ecx=00000000 edx=00000000 esi=00000000 edi=76553240
eip=00000000 esp=0019d604 ebp=0019df60 iopl=0 nv up ei pl zr na pe nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00210246
00000000 ?? ???

Note, that lines 1 and 3 mentioned loading of DLL files. Both of these DLL files are specific to the computer's graphic card. Then on line 4 there was an Access violation. 

Next, review AutoPIPE's Log files, 

2021-06-24 21:26:21.993363: <info> INITAP: setup recently used models list.
2021-06-24 21:26:21.993363: <info> INITAP: Initialize form/panel/command windows.
2021-06-24 21:26:22.013309: <info> c_InitGraphicsFromHwnd: Initialize GFW graphics from passed window handle

The last line entered was directly related to graphics.

Next, review Event viewer log files.

If you see the error marked in red in above screenshot which says "Faulting module path: C:\Windows\System32\DriverStore\FileRepository\nvdmwi.inf_amd64_3ba7366d8c5113d7\nvoglv32.dll"
The line entered was directly related to graphics card.

Based on these 3 pieces of information, the issue must be related to the computer's graphic card settings. 

Workaround:

Make sure that NVIDIA's graphic card is updated regularly. 

See WIKI here for suggested NVIDIA's graphic card settings. 

After making some modifications to the NVIDIA's graphic card settings, AutoPIPE started without issue.