Microsoft Knowledge Base Email Alertz

A computer that is running an x64-based version of Windows Server 2008 stops responding

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 980081 - Last Review: April 27, 2010 - Revision: 4.0

Stress tests may cause a Windows Server 2008 system that has the Hyper-V role installed to hang

Hotfix download is availableHotfix Download Available
View and request hotfix downloads

On This Page

SYMPTOMS

When you perform stress tests on a Windows Server 2008 system that has the Hyper-V role installed, the system may stop responding or hang.

CAUSE

A thread on one processor owns a network device interface specification (NDIS) Read lock or Write lock. This thread waits for a spinlock. However, a thread on a second processor owns the spinlock, and this thread waits for the same NDIS Read lock or Write lock that is owned by the thread on the first processor. This creates a deadlock situation. Therefore the computer stops responding.

RESOLUTION

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, your computer must be running Windows Server 2008 Service Pack 2 (SP2). For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
968849  (http://kbalertz.com/Feedback.aspx?kbNumber=968849/ ) How to obtain the latest service pack for Windows Server 2008

Restart requirement

You may have to restart the computer after you install this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 file information notes
  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    Collapse this tableExpand this table
    VersionProductSR_LevelService branch
    6.0.600 2 . 22xxxWindows Vista and Windows Server 2008SP2LDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Hvax64.exe6.0.6002.22337651,26412-Feb-201012:03x64
Hvboot.sys6.0.6002.22337108,42412-Feb-201015:04x64
Hvix64.exe6.0.6002.22337672,25612-Feb-201012:03x64
Virtualization.events.xmlNot Applicable1,38403-Apr-200920:56Not Applicable
Vmsntfy.dll6.0.6002.2233762,46412-Feb-201012:11x64
Vmswitch.sys6.0.6002.22337250,88012-Feb-201012:11x64

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

This issue is caused by a deadlock in the Vmswitch.sys driver. Thevmswitch!VmsCdpCopyPortInfo function is called on the switch lock, and then takes the network adapter lock and port lock. The correct order here is first the network adapter lock, then the switch lock, and finally the port lock. This issue was fixed in Windows 7. For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684  (http://kbalertz.com/Feedback.aspx?kbNumber=824684/ ) Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Server 2008

Additional files for all supported x64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Amd64_microsoft-hyper-v-drivers_31bf3856ad364e35_6.0.6002.22337_none_c7a6ffbcc629ebf8.manifestNot Applicable9,21612-Feb-201016:13Not Applicable
Amd64_wvms_pp.inf_31bf3856ad364e35_6.0.6002.22337_none_c15ad954c015be80.manifestNot Applicable6,17912-Feb-201016:15Not Applicable
Package_for_kb980081_sc_1~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable2,14316-Feb-201001:56Not Applicable
Package_for_kb980081_sc~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43116-Feb-201001:56Not Applicable
Package_for_kb980081_server_1~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable2,14716-Feb-201001:56Not Applicable
Package_for_kb980081_server~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43816-Feb-201001:56Not Applicable

APPLIES TO
  • Windows Server 2008 Datacenter
  • Windows Server 2008 Enterprise
  • Windows Server 2008 Standard
  • Windows Web Server 2008
  • Windows Server 2008 Foundation
Keywords: 
kbqfe kbhotfixserver kbsurveynew kbautohotfix kbexpertiseinter kbbug kbfix KB980081
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate