Never seen an error like that, but in your wgserv directory look for .out or .err files and they will have a ton info about the crash and track it down better.
well you could run the shutdown command with the reboot flag, But you will need to set WG to run as a service so it starts back up. Also might have to do an auto-login to get the service to kick on.
Once it grows it does not shrink. In windows 95 days I kinda remember 8G being a limit, but your past that so memory might be shit. My bbs is only running on a 4G drive, but it is full.
If you do backups that will make it grow. Also your log files can be pretty large so look at those to trim space.
Don't disable, just cleanup now and then. I once a year go thru and delete any backups on the host over a year, and clean down my mud logs. My bbs logs I rotate daily so I can parse smaller files, and these are sent to my network storage.
My backup system is a little redundant and bullet proof, I lost my board a few times to vm crashes. So now I back the mud files daily and they are moved off to my network storage, it rotates out all logs and create blank ones at cleanup. Then I also do VM level backups that are pushed to my network storage and keeps three days worth, then it pushes those to my host. My host is backed up nightly to the cloud. I do not want to loose the board again!