We experienced an issue with a newly built Hyper-V 2012 R2 server running on Windows Server 2012 R2 Datacentre edition with all the latest critical and security and critical as of 23/06/2015. The server was built, setup with a number of virtual machines and ran without issues for a period of approximately 1 month. After approximately 1 month, the server started blue screening on a regular basis, no changes had been made to the Hyper-V Host.
The Hyper-V Host was setup on a Dell PowerEdge R730XD with 192GB of memory.
The Blue Screen error was: KERNEL_SECURITY_CHECK_FAILURE
The cause of the crash as per the original error was from the NT Kernel (ntoskrnl.exe).
We opened a support case with Microsoft to get the full memory dump analysed. After the memory dump was analysed, we were advised it was a known bug in Windows Server 2012 R2 identified 14th of April 2015. They pointed us at KB3055343 which resolves a issue with Windows that can cause inconsistent network interface data on the system.
After downloading and installing KB3055343 the issue was resolved.
https://support.microsoft.com/kb/3055343
The Hyper-V Host was setup on a Dell PowerEdge R730XD with 192GB of memory.
The Blue Screen error was: KERNEL_SECURITY_CHECK_FAILURE
The cause of the crash as per the original error was from the NT Kernel (ntoskrnl.exe).
We opened a support case with Microsoft to get the full memory dump analysed. After the memory dump was analysed, we were advised it was a known bug in Windows Server 2012 R2 identified 14th of April 2015. They pointed us at KB3055343 which resolves a issue with Windows that can cause inconsistent network interface data on the system.
After downloading and installing KB3055343 the issue was resolved.
https://support.microsoft.com/kb/3055343
This is dummy text. It is not meant to be read. Accordingly, it is difficult to figure out when to end it. But then, this is dummy text. It is not meant to be read. Period.
ConversionConversion EmoticonEmoticon