Saw this issue though OpsMgr 2012 R2 console, telling me that all Windows Server 2012 and 2012 R2 servers where reporting this issue every evening when the backup kicked in.
There are a lot of blog posts on the web telling you to disabling the cache on the disks and so on, but this is a default setting i did not want to change. And in my opinion that is a workaround, not a fix.
So working with this issue led me to an known error from VMware: KB2006849
Telling me that this has been solved in a patch from the 27th of january 2015 and later versions.
Version: ESXi 5.5 Patch 4
To verify which version you are running, then look in the vSphere Client under one of your hosts:
Then compare that number with this website:Build number history
If you have a build version before 2403361 (like the above example) – then you need to update your ESX hosts and the VMware tools on the virtual machines.
This solves the issue.
Event id numbers which leads to this issue:
Event ID 50, 57, 137, 140, 157 and 12289