Symptoms. Under high load with 16 or more processors and many I/O failures, Windows 8.1 or Windows Server 2012 R2 virtual machines crash, which is caused by Stop error in vhdmp.sys. Resolution. To resolve this issue, install update 2919355.

When you access a shared virtual hard disk file (.vhdx) through a redirector and a time-out error or network error is returned to VHDMP.sys, you may receive a Stop error that looks something like this:

When you try to interact with a virtual hard disk (VHD) file by using a tool such as Hyper-V Manager, Storage Manager, or Diskpart, you receive the following error message: Title: Virtual Disk Manager. Description: A Virtual Disk Provider for the specified file was not found.

Symptoms. Under high load with 16 or more processors and many I/O failures, Windows 8.1 or Windows Server 2012 R2 virtual machines crash, which is caused by Stop error in vhdmp.sys. Resolution. To resolve this issue, install update 2919355.

When you use shared virtual hard disk (.vhdx) files on a Windows Server 2012 R2 computer, Windows OS may experience memory leak. For every IO issued by svhdxflt, VHDMP believes that there is an Activity ID.

Symptoms. When you remove a virtual disk device (VHD or VHDx file) in Windows 8.1 or Windows Server 2012 R2, extraneous log entries that resemble the following are created: Log Name: System. Source: disk. Date: <Date><Time>.

You have the Hyper-V server role installed on the cluster nodes. You create virtual machines on one cluster node, and you configure the virtual machines as cluster resources. You create multiple Cluster Shared Volume (CSV) resources and create one Virtual Hard Disk (VHD) file in each CSV.

When you run a Windows Server 2012 R2 virtual machine in Windows Azure, the event log may fill with many event ID 129 events. Event 129 is logged when I/O requests are dropped because of time-out issues.

Fixes an issue in which you cannot create a virtual hard disk on a remote server share in Windows 8.1, Windows Server 2012 R2, Windows 8, or Windows Server 2012. This issue occurs if the SMB Service does not support resiliency.

Ultimately, this may cause the Physical Disk resource to either not come online or take a long time to come online on the new node. Therefore, virtual machines that have VHD files on the Cluster Shared Volume may crash.