A Stop error occurs when you profile an application in Visual Studio 2008 SP1 on a computer that uses an AMD processor and has Hyper-V enabled

Article translations Article translations
Article ID: 969873 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

You enable a Hyper-V role on a computer that uses an AMD processor. On the computer or on a virtual machine that is created by Hyper-V, you profile an application by using a sampling method in Microsoft Visual Studio 2008 Service Pack 1 (SP1). In this situation, the operating system crashes, and a series of Stop errors occurs. The first Stop error in the series is 0x0000004A.

CAUSE

This issue occurs because Visual Studio 2008 SP1 does not detect Hyper-V. Because of this behavior, Visual Studio 2008 SP1 does not recognize that it is running in a virtual environment. Therefore, the profiler tries to use physical hardware that does not exist in the virtual environment. For example, the profiler tries to use a performance monitor unit (also known as PMU).

RESOLUTION

Hotfix information

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

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must have Visual Studio 2008 SP1 installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply the hotfix if no instance of Visual Studio is being used.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
VSPerfMon.exe9.0.30729.4491179,53616-Feb-201003:33:06 PM
VSPMsg.dll9.0.30729.4491101,70416-Feb-201003:33:06 PM
VSPMsgui.dll9.0.30729.449194,54416-Feb-201003:33:06 PM

WORKAROUND

To work around this issue, disable the virtualization support in BIOS, and then remove the Hyper-V role from the operating system.

STATUS

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

MORE INFORMATION

After you install this hotfix, Visual Studio 2008 SP1 can detect Hyper-V. When you repeat the behavior that is described in the “Symptoms” section, you receive an explicit error message.

Properties

Article ID: 969873 - Last Review: October 7, 2011 - Revision: 2.0
APPLIES TO
  • Microsoft Visual Studio 2008 Service Pack 1
Keywords: 
kbexpertiseadvanced kbsurveynew kbqfe KB969873

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com