Thank you for your post MickyHunt!

I went ahead and pushed this thread out through our Twitter page to try and capture a broader audience! Can't wait to see other users responses!

When you say migrated, did you spin up a new 2012 R2 VM and then do the Sage CRE migration upgrade from there? 

I've got 13.1 on a Server 2012 R2 VM but it is a Gen 1 instance, and no similar issues to report. This instance is from a migration upgrade from 9.8 U8 on a Server 2008 R2 VM.

What shows in the logs of the VM and the Hypervisor? What are the details of the crash reports?

Edit to add: are you backing up to a network share or to another attached VHDX?

Thanks Brian. I did spin up a w2012 R2 VM and used the sage migration tool to migrate from a physical w2003 server. I was running out of time so I spun up a W2012 Gen 1 VM and then migrated again. No issues this round. All is running well and closed the year without issue on 14.1 U2. Logs were not reporting anything except abnormal issues. Had our San Vendor  run the dump through an analysis tool and he seemed to think it was pointing to a resource issue. Increasing memory or processors did not help. My feeling is that it is related to using a Gen 2 VM. As far as the backup was concerned it was to the same vhdx that the data

Not a fan of R2, so many of the great features of 2012 deprecated and mixed ver2 and 1 vm's don't play well....  Migrated 9.8 to 13.1 using 2012 vm's no issues and new years eve upgraded to 14.1 no issues on 2012 hyper-v.

Brian sorry got cut off. Backup target was the same VHDX that the company data is on. I actually copied a 5GB file to the same vhdx drive and then copied that file to multiple folders on the same vhdx without issue. Only had the issue using the file tools backup for the company data. Anyway all is good now and my takeaway is to use one Gen 1 VM for Sage for now.

thanks.

Thanks for the input Michael. I did spin up a W2012 Gen 1 VM and migrated. All seems to be running well now.