Symptoms of crash
- CPU allowance of the guest VM is on 100% (seen from host)
- high memory demand - always higher than satisfied), no disk activity or queue
- sometimes it is possible to move the mouse or switch the window, but not to launch new app
These are common to dozens of "crashes" we have observed at our facility during last two months. Note that the Veeam (together with its storage) is on virtual, not physical server.
If you see this symptoms and attribute them to the ReFS, I would suggest to force stop the machine immediately.
We have been trying to wait, even few days if the situation will recover, but it won't. Instead, long-term guest VM troubles led its time service to behave in a crazy way - sometimes shifting time to hours and even a few months to the future. This is something that guest or host were not able to repair. Wrong dates caused lot of other strange things, i.e. bad traces saved to SQL database, so our Veeam backup scheduler stopped to behave correctly since (our case #02063994).
After a force restart the machine sometimes get in troubles again immediately. We have ended the troubles by starting the machine and
a) lightly shutting down the machine just after windows booted, if it allowed to do so (if not, than hard shutdown and again)
b) waiting few hours after start, to recover (worked only sometimes for us)
Hope this info save you some time.
little OT: thanks for the MSFT ticket advices, we are NGO so the SA is maybe crippled of support benefit because of that.