Depending on the number and size of subs you are using in PI, it may be that windows is running out swap space (Virtual Memory). Note that this is completely distinct from the so-called PI Swap directories.
To verify whether this is happening, open the Windows Task manager and click on the Performance tab. Next click on the Memory section and note the values of the Committed entry. (The values there will be larger than the amount of physical RAM you have installed.) From the Task Manager Options menu, select Always On Top. You should also open a Windows File Explorer window and select Computer or This PC (depending on version of Windows) to see the free space on your drives. Leave both of these windows open.
Now, kick off your PI process of interest and switch to the Windows File Explorer window. You should now see the Windows File Explorer and Task manager windows with PI running behind them. Keep watch on both the free file space and the memory utilization values as PI operates. As PI works, you will note that your memory will fill up more or less completely. When that happens, you will then note that the Committed value of virtual memory starts to grow. At the same time, the free drive space will start to fill up. If you run out of drive space, then PI will either error out or possibly lock up.
At the end of this experiment, you will know more about the source of the problem. If PI dies while there is still free drive space, you may need to both free up drive space and / or increase the size of the Windows Virtual Memory Swap file. This can be done using the Windows Performance Dialog of the Control Panel. If PI messes up before even filling up physical RAM, then something else is going on.
Edited by jdupton, 04 March 2020 - 11:40 PM.