Some eagle-eyed MVPs reported that Microsoft has issued a rollup-update for Windows Server 2008 R2 Hyper-V.¬† Microsoft is recommending the installation of the rollup update to avoid the described issues.¬† You’ll not that the affect CPUs in issue 1 and 3 are Intel CPUs.¬†¬†The¬†update¬†rolls up 3 updates into one installer:
Issue 1 – KB975530
When a computer has one or more Intel CPUs code-named Nehalem installed, you receive the following Stop error message:
0×00000101 ( parameter1 , 0000000000000000, parameter3 , 000000000000000c) CLOCK_WATCHDOG_TIMEOUT
Note The Nehalem CPU for a server is from the Intel Xeon processor 5500 series and for a client computer is from the Intel Core-i processor series.
Issue 2 – KB974909
Consider the following scenario:
- You run a virtual machine (VM) on the computer.
- You use a network adapter on the VM to access a network.
- You establish many concurrent network connections. Or, there is heavy outgoing network traffic.
- In this scenario, the network connection on the VM may be lost. Additionally, the network adapter is disabled.
- Note: You have to restart the VM to recover from this issue.
Issue 3 – KB981791
When a computer has an Intel Westmere processor, you receive an error message that resembles the following:
STOP: 0x0000001a ( Parameter1 , Parameter2 , Parameter3 , Parameter4 ) MEMORY_MANAGEMENT
Credit: Artem Pronichkin, MVP
This blog post is the property of Aidan Finn (@joe_elway / http://www.aidanfinn.com) and may not be reused in any manner without prior consent of Aidan Finn. You may quote one paragraph from this blog post if you link to the original blog post.
No related posts.