Missing Exchange Writer + Missing System Writer + Specific services crashing regulary + Hyper-V VM

I have some strange errors on multiple Server 2012 R2 Virtual Machines (Hyper-V hosts).

• Missing VSS writers on startup: System Writer and Exchange Writer.

I have scoured the net for possible solutions, including the hotfixes, but they are not applicable to my case. If I restart the services responsible for those two writers, the writers are there. However, they dissapear after a while.

• few very specific services are crashing very regulary (and are being recovered)

The COM+ Event System service terminated unexpectedly.

The Windows Font Cache Service service terminated unexpectedly

The Network List Service service terminated unexpectedly

The Network Store Interface Service service terminated unexpectedly

On average they have done this '50 times'

My guess is that they make the 2 other writers dissapear. These services are all hosted in the same svchost.exe I think. Because at the same time, this error can be seen in the application log:

Faulting application name: svchost.exe, version: 6.3.9600.17415, time stamp: 0x54504177
Faulting module name: regsvc.dll_unloaded, version: 6.3.9600.17415, time stamp: 0x54504293
Exception code: 0xc0000005
Fault offset: 0x000000000000318b
Faulting process id: 0xa818
Faulting application start time: 0x01d12c0f3318f052
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: regsvc.dll

There are no other events of note in the application log.

I have checked: regkey permissions on vss key and I have already done the takeown fix on the winsxs folder.
Visual Studio is not installed on this server.

Only happens on VM hosts (generation 2) - Server 2012 R2 servers.

Anyone has a clue? I'm baffled and I've already wasted hours on possible solutions.

I can confirm now that the problem was with one of the services that was hosted inside the svchost.

After giving every service a seperate process to run in, only the Windows Time Service kept crashing. The VSS writers are back and I have successfully backed-up the affected server for 4 days in a row. This is an absolute first.

Now all that remains is finding out why the time service keeps crashing, but this is low priority.

The VSS writers were affected because Exchange Store service is dependent on the Network Store Interface Service. It crashes and restarts, the store service keeps running properly but the crash is enough to disrupt the VSS service.