This is a known issue affecting ESXi 5.0 and 5.1, Please see the following VMware kb for more information.
Please get VMware support to confirm there is no underlying storage contention in your environment
In vCenter go to the datastore where the VM resides on and rescan the datastore, this resolved this issue.