Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, January 19, 2012 4:51 PM
I'm running Hyper-V 6.0.6002.18005 over Windows Server 2008 R2 on a DELL PowerEdge 2900. Intel Xeon X5460.
The server restarts twice a day. Here's the event log entries:
**************************************************
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.274.10
Locale ID: 2058
Additional information about the problem:
BCCode: 7f
BCP1: 0000000000000008
BCP2: 0000000080050031
BCP3: 00000000000006F8
BCP4: FFFFF8000182E152
OS Version: 6_0_6002
Service Pack: 2_0
Product: 274_3
Files that help describe the problem:
C:\Windows\Minidump\Mini011012-01.dmp
C:\Users\administrator.INSYS\AppData\Local\Temp\2\WER-5286234-0.sysdata.xml
C:\Users\administrator.INSYS\AppData\Local\Temp\2\WERD52A.tmp.version.txt
Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409
******************************************
Error, Source: VMSMP, EventID: 26
NIC driver on 'xxxxx - xxxxxxx' cannot load because it is incompatible with the server virtualization stack. Server version 2 Client version 196610 (VMID A72B85B4-8A73-4291-BCDA-B311BE21B369).
*****************************************
Error, Source: storvsp, EventID: 5
A storage device in ''xxxxx - xxxxxxx' cannot load because it is incompatible with the server virtualization stack. Server version 2.0 Client version 4.2 (VMID A72B85B4-8A73-4291-BCDA-B311BE21B369).
*****************************************
Error, Source: vmbus, EventID: 2
The parent partition uses a different VMBus version. You need to Install a matching VMBus version in this guest installation.
*****************************************
Here's what I've tried:
-Disabling C states on registry using the command reg add HKLM\System\CurrentControlSet\Control\Processor /v Capabilities /t REG_DWORD /d 0x0007e066 According to http://support.microsoft.com/kb/975530/en
-Use hotfix KB975530 and KB950050 with no results as I'm receiving the following error: "The update does not apply to your system"
-Installed recent updates.
-Update to last drivers version. Including BIOS firmware.
Bluescreen restarts continues.
All replies (11)
Thursday, January 19, 2012 5:19 PM
I'm not entirely clear on whether the host or a guest is doing this?
Point 1: The error indicates that the host OS and Hyper-V Role have been updated but the guests have not. Re-install Integration Services on the guests to get the host and guest's setup aligned again.
Can you post the *.DMP file to your SkyDrive public and let me know where it is. We can analyze it to see what it says.
EDIT: Please disable Intel TurboBoost in the BIOS.
Philip Elder SBS MVP Blog: http://blog.mpecsinc.ca
Thursday, January 19, 2012 5:24 PM
I think you just got the answer to your question. Since you have incompatible hardware it happens.
******************************************
Error, Source: VMSMP, EventID: 26
NIC driver on 'xxxxx - xxxxxxx' cannot load because it is incompatible with the server virtualization stack. Server version 2 Client version 196610 (VMID A72B85B4-8A73-4291-BCDA-B311BE21B369).
*****************************************
Error, Source: storvsp, EventID: 5
A storage device in ''xxxxx - xxxxxxx' cannot load because it is incompatible with the server virtualization stack. Server version 2.0 Client version 4.2 (VMID A72B85B4-8A73-4291-BCDA-B311BE21B369).
*****************************************
Error, Source: vmbus, EventID: 2
The parent partition uses a different VMBus version. You need to Install a matching VMBus version in this guest installation.
*****************************************
Just do a search here http://www.windowsservercatalog.com/ then click the Hype-V link on the left. You will see that only PowerEdge 2900 III (in the 2900 series) is compatible with Hyper-V.
Adrian Costea - MCP, MCTS, MCSA 2003, MCITP: Windows 7
My Blog: www.vkernel.ro/blog
Friday, January 20, 2012 12:47 AM
Thanks for your assistance Philip.
Host OS is the one that is rebooting, consecuently guest OS also get restarted. I was looking for the *.DMP file on the server but there's no *.DMP file where it should be (%SystemRoot%\MEMORY.DMP). I've enable the Show hidden files and folders and disabled Hide extensions for known file types and Hide protected operating systems files.
I don't know if the server is not generating this file or if I'm not looking in the correct folder. If that's the case, hope you can help me to locate it.
I also tried to re-install Integration Services but it was not possible. It generates an error: An error has ocurred: Unable to launch one of the update programs.
I'll proceed to disable Intel Turbo Boost in BIOS. Then I'll reply the results.
Friday, January 20, 2012 12:56 AM
• In Dell OpenManage Server Administrator, go to System/Auto Recovery
• Change the “Action on Hung Operating System Detection” setting to None
Please note that this may cause your server to hang instead of restarting, be sure you have physical access to the console first or a configured working iDRAC in case you need to do a shutdown to clear the hanged state.
We had a couple of Dell servers with similiar behaviour, seemed to be fixed after 2008 R2 SP1 installation.
EDIT: While you are in the OpenManage Administrators, check your hardware logs for failing devices that could explain the crashes.
Friday, January 20, 2012 1:18 AM
Click Start --> Right click Computer and click Properties --> Advanced System Settings --> UAC --> Startup and Recovery Settings button --> Write debugging information: Small memory dump (256 KB).
Change that. If and when the problem happens again you can get the BSOD info from it via %windir%\MiniDump\.dmp.
Philip Elder SBS MVP Blog: http://blog.mpecsinc.ca
Monday, January 23, 2012 7:43 PM
Thanks Adrian Costea for your reply. I've reviewed the system revision and mine is III.
Monday, January 23, 2012 7:54 PM
Thanks for your support Trana00. Looking for events on Dell Open Manage Server Administration, i found the error: "System Software event: OS Stop sensor, run-time critical stop was asserted" on Hardware Registry. Those errors started a week after Hyper-V was installed.
All Hardware diagnostics on the Open Manage Server Administrator are ok, including Procesors. About SP1, this server has SP2 installed.
Tuesday, January 24, 2012 8:52 PM
Hi Philip,
I've just uploaded the DMP file into my skydrive. Here's the sharing link.
Thursday, January 26, 2012 3:16 PM
Jorge,
I am on a large project that has kept me tied down. My apologies for the delay in getting back. Will do as soon as I have a bit of time.
Philip Elder SBS MVP Blog: http://blog.mpecsinc.ca
Thursday, January 26, 2012 4:01 PM
I took a minute! :)
Make sure your NIC drivers and management software are up to date. Find out of there are any firmware updates for the NICs as well.
KB search: http://support.microsoft.com/search/default.aspx?query=NETIO.SYS
EDIT: Disable TOE, RSS, and other advanced networking features on those NICs too.
Philip Elder SBS MVP Blog: http://blog.mpecsinc.ca
Tuesday, January 31, 2012 9:49 AM
any updates?Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.