We have seen this issue mainly caused by a race condition in the Hyper-V, all you require to do is to have SP1 installed and install the appropriate hotfix
We have seen this issue mainly caused by a race condition in the Hyper-V, all you require to do is to have SP1 installed and install the appropriate hotfix