Hi @Chad
When the worker process exceeds the virtual memory limit, IIS will spin up a new worker process and kill the old one.
I think this is why the connection is reset, and you set the Virtual Memory Limit to 0, which means there is no limit to the virtual memory it can use, so the problem goes away.
If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.