We ran a test on one of our freshly installed Hyper-V Server 2008 R2 servers to see if we ran into this issue.
- Intel Server System SR1630HGP 1U
- Intel Server Board S3420GPLC integrated
- Intel Xeon Processor X3450
- 16GB Kingston ECC
- Intel RS2BL080 6Gbps SAS 2nd Generation PCI-E
- 3x 450GB Seagate 15K RPM SAS in RAID 5
- Intel RAID Smart Battery for the RAID controller
The server has only been up and running about 24 hours. We have been running some stress tests along with some test VM installs and backup restores as Hyper-V guests.
This is the Crash Analyzer Wizard’s results (DaRT MDOP product):
So, after a relatively short period of use the problem has reared its head.
- Our previous post: Hyper-V On Nehalem CPUs Error – CLOCK_WATCHDOG_TIMEOUT Critical Hotfix.
It looks as though the hotfix is an absolute must for any Technician’s Thumb Drive and a required install on any server that will utilize Hyper-V on Intel Xeon Processor 3400 and 5500 series CPUs!
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book