Windows guest operating systems that are using virtual disks on non-local datastores might experience unexpected blue screens.
This issue occurs when the responses from the storage array take longer than the guest operating system expects to wait. The default disk timeout period in Windows is too short to handle the longer delays that can occur in a SAN, NFS, or iSCSI environment, and a blue screen error is the result of exceeding this timeout.
To resolve this issue, increase the disk timeout to 60 seconds in the Windows virtual machines by editing the Windows registry.
Note: This solution is applicable only to versions before 3.0.2. VMware Tools installations after this automatically modifies this value.
To increase the disk timeout value:
- In the registry, go to HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/Disk.
- Right-click and select Edit/Add value.
- Set the value name to TimeOutValue.
- Set the data type to REG_DWORD.
- Set the data to 0x03chex (or60decimal).
- Reboot the virtual machine.
Note:
- Contact your Storage vendor to confirm whether a specific TimeOutValue setting is identified for your particular environment.
- Increasing this disk timeout setting does not affect the performance of the guest operating system or virtual machine under normal operating conditions, but you must verify how the applications you are running in the guest operating system handle disk access delays.
- To accommodate transient events, VMware Tools increases the SCSI disk timeout to 60 seconds.
Additional Information
For translated versions of this article, see: