I'm not sure how relevant this will be now as you've probably resolved the issue but I wanted to add my experience in case it helps someone else.
I have a similar setup here that I admin. Windows 10 Pro box with 8Gb or ram (upgrading to 24 tomorrow). This box houses the company file as well as a local install of QB Enterprise Mfg and Wholesale 23 for the remote users to connect to it via an remote desktop VM session. Several of the other users in the physical office also connect to this box with local installs of the same software on their computers as they need to provide updates to records or input data.
With all that in mind, from time to time I kept having the same issues I have seen on this page. Often it would hard lock and silent crash to the desktop. Sometimes it would throw an abort error. I narrowed it down to the Sleep Timer being set on the host box to 20 minutes. I turned this off and it basically resolved all my issues. Then, a month or so later, they came back. Turn out that when I ran the Windows Updater on the host computer, the updates it installed reset that sleep timer back to 20 minutes. I had to go back and turn it off again. Problems solved for now again. I'm guessing the host computer going into sleep mode is severing the network connections to it.
This probably won't help those who use it in single user mode on a local install but I'd wager that if you step away from your computer for X amount of time equal to or greater than whatever your computers sleep timer is that when you get back it might cause problems there as well. Just something worth testing I guess.
