You are currently offline, waiting for your internet to reconnect

"0x000000BE" Stop error when you install Windows Vista or Windows Server 2008 if more than two AMD Bulldozer-based 16-core processors are installed

Not sure if this is the right fix? We've added this issue to our memory dump diagnostic which can confirm.
Consider the following scenario:
  • You have a computer that has more than two AMD Bulldozer-based 16-core processors.
  • You try to install Windows Vista or Windows Server 2008 on the computer.
In this scenario, you receive the following Stop error message in the installation process:
STOP 0x000000BE ( parameter1 , parameter2 , parameter3 , parameter4 )

  • The parameters in this Stop error message may vary, depending on the configuration of the computer.
  • Not all 0x000000BE Stop errors are caused by this issue.
  • You can install Windows Vista or Windows Server 2008 successfully on the computer if you limit the processor to use less than 48 cores.

    For example, the installation succeeds when two AMD Bulldozer processors (32 cores) are installed. However, the installation fails when three AMD Bulldozer processors (48 cores) are installed.
  • You may also receive this Stop error message if you extend the computer to more than two AMD Bulldozer-based 16-core processors after you install Windows Vista or Windows Server 2008.
This issue occurs because of a logic error when the operating system selects an ideal processor for a thread.

When the operating system uses the incorrect logic, the operating system selects a nonexistent processor. Therefore, you receive a Stop error message.
To resolve this issue, install the following hotfix package on the affected computer. Depending on the current state of the system you have a number of options for implementing the patch.

Option 1: System is bug checking due to the installation of an additional Processor. We can temporally limit the number of processors to allow the system to boot successfully and apply the hotfix.
  1. Power-on or restart the effected computer
  2. During the initial boot process press the “Space bar” to access the Windows Boot Manager and then press the F10 key
  3. Edit the current boot options (i.e. /NOEXECUTE=OPTOUT) to include the NUMPROC switch to limit the number of processors to a lower value. Please note that yours may be slightly different. We want to just add the NUMPROC switch to the end of the list. For instance;


    Note: This is a onetime change and will only be used for the current boot process. Upon concurrent rebooted this change will be omitted.
  4. Press the “Enter Key” to submit the change.
  5. Continue with the normal boot process and log onto the system with an account which has administrative credentials.
  6. Download, extract and install the Hot Fix package which will to update the kernel.
  7. When prompted to reboot select “Yes”

Option 2: The operating system is not installed and installation fails. For this option we need to integrate the hotfix package on to the media that is used for the installation image of Windows Server 2008. To do this, follow these steps:
  1. Download all the necessary files and tools. To do this, follow these steps:
    1. Install the Windows 7 OEM Preinstallation Kit (OPK). The Windows 7 tools can be used to service Windows Server 2008 and Windows Vista images.
    2. Request and extract the hotfix package to the package update folder on the computer by doing the following;

      a. Request and download the hotfix to the computer

      b. Run the Hotfix to extract the installation .msu file to C:\Test\Updates directory.

      c. Open an elevated command prompt and change directory to C:\Test\Updates

      d. Run the following command to extract the contents of the .msu file.

      Expand -f:* Windows6.0-KB2563727-x64.msu c:\test\updates
    3. Copy the Install.wim file from the Windows Server 2008 installation media (i.e. x:\Sources) to the computer. For example, copy the Install.wim file to the folder C:\Test\Images.

      Note: Be sure to clear the read-only protection flag from the copy of Install.wim by right-clicking on the file, select properties clear check box next to Read –only and click OK

  2. Add the hotfix to a Windows Server 2008 image Install.wim file. To do this, follow these steps:
    1. Click Start, click All Programs, click Windows OPK, right-click Deployment Tools Command Prompt, and then click Run as administrator.
    2. At the command prompt, retrieve the name or the index number for the image that you want to change. To do this, type the following command, and then press Enter:

      Dism /Get-WIMInfo /WimFile:C:\test\images\install.wim
    3. Notice the index number or the name of the Windows Server 2008 image to which you will add the hotfix.

      ----- for example -----

      E:\Test\Updates>Dism /Get-WIMInfo /WimFile:c:\test\images\install.wim

      Deployment Image Servicing and Management tool

      Version: 6.1.7600.16385

      Details for image : e:\test\images\install.wim

      Index : 1

      Name : Windows Longhorn SERVERSTANDARD

      Description : Windows Longhorn SERVERSTANDARD

      Size : 9,514,856,643 bytes

      Index : 2

      Name : Windows Longhorn SERVERENTERPRISE

      Description : Windows Longhorn SERVERENTERPRISE

      Size : 9,524,736,456 bytes

      Index : 3

      Name : Windows Longhorn SERVERDATACENTER

      Description : Windows Longhorn SERVERDATACENTER

      Size : 9,523,944,197 bytes

      Index : 4

      Name : Windows Longhorn SERVERSTANDARDCORE

      Description : Windows Longhorn SERVERSTANDARDCORE

      Size : 2,854,434,578 bytes

      Index : 5

      Name : Windows Longhorn SERVERENTERPRISECORE

      Description : Windows Longhorn SERVERENTERPRISECORE

      Size : 2,865,043,006 bytes

      Index : 6

      Name : Windows Longhorn SERVERDATACENTERCORE

      Description : Windows Longhorn SERVERDATACENTERCORE

      Size : 2,864,646,247 bytes

      The operation completed successfully.


    In this case we are interested in index 2, SERVERENTERPRISE.

    1. Create an offline target image folder (C:\Test\Offline) which will be used to mount the image and install the hotfix package. In the command window type the following command without the quotes.

      “MD C:\Test\Offline”

      Note: You must create the C:\Test\Offline folder before you mount the image.
    2. Use a DISM command to mount the image by using the index number or the name that you noticed in step 2C:

      Dism /Mount-Wim /WimFile:C:\test\images\install.wim /Index:2 /MountDir:C:\test\offline
    3. Add the hotfix package to the mounted install.wim file. At the command prompt, type the following command, and then press Enter.

      Dism /Image:C:\test\offline /Add-Package /PackagePath:C:\test\updates\
    4. At the command prompt, type the following command to commit the changes and unmount the image, and then press Enter:

      Dism /Unmount-WIM /MountDir:C:\test\offline /Commit

  3. Prepare the Windows Server 2008 installation media by doing the following:
    1. Make a folder named DVD, and then copy the contents of the Windows Server 2008 setup DVD to the DVD folder. For example, you can use the following commands:

      md \dvd
      xcopy X:\*.* \dvd /e

      Note: In these commands, the X represents the letter of the DVD drive.
    2. Copy the modified Install.wim files to the DVD folder on the hard disk:

      copy C:\test\images\install.wim \dvd\sources
    3. Instead of modifying the Boot.wim file it is easier to modify the bcdstore of the installation media. To modify the bdcstore open and elevated command prompt and run the following command:

      “bcdedit /store c:\dvd\boot\bcd /set {default} numproc 16”

  4. Next build an updated bootable DVD image. You can use the oscdimg command to create an International Standards Organization (ISO) file of the DVD folder and to make the image a UEFI-bootable image. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

    947024 How to create an ISO image for UEFI platforms for a Windows PE CD-ROM for Windows Server 2008
    1. Open an elevated command window
    2. Change the directory to the location of the OSCDIMG.EXE
    3. Run the following command to create the bootable DVD image ISO file

      Oscdimg -m -o -u2 -udfver102 -bootdata:2#p0,e,bC:\Windows\Boot\DVD\PCAT\,e,bC:\Windows\Boot\DVD\EFI\en-US\efisys.bin C:\DVD C:\x64_2k8r2.iso

      Note: you need to use the correct OSCDIMG.EXE for the platform you are building the DVD on -- e.g., x64, x86 32-bit, etc.b For Example:

      "c:\Program Files\Windows OPK\Tools\amd64\oscdimg.exe" -m -o -u2 -udfver102 \


      be:\Windows\Boot\DVD\EFI\en-US\efisys.bin e:\DVD e:\x64_2k8r2.iso

      OSCDIMG 2.55 CD-ROM and DVD-ROM Premastering Utility

      Copyright (C) Microsoft, 1993-2007. All rights reserved.

      Licensed only for producing Microsoft authorized content.

      Scanning source tree (500 files in 14 directories)

      Scanning source tree complete (787 files in 248 directories)

      Computing directory information complete

      Image file is 2806284288 bytes (before optimization)

      Writing 787 files in 248 directories to e:\x64_2k8r2.iso

      100% complete

      Storage optimization saved 126 files, 25073664 bytes (1% of image)

      After optimization, image file is 2783588352 bytes

      Space saved because of embedding, sparseness or optimization = 25073664


  5. After you finished creating the image successfully, burn the update image to a DVD and use for the installation of Windows Server 2008. For information with regards to services a Windows Vista or Windows Server 2008 image, please see the following TechNet reference;

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 this specific problem.

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, submit a request to 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: 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.


To apply this hotfix, you must be running one of the following operating systems:
  • Windows Vista Service Pack 2 (SP2)
  • Windows Server 2008 Service Pack 2 (SP2)
For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:
935791 How to obtain the latest Windows Vista service pack
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 How to obtain the latest service pack for Windows Server 2008

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English 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 Vista and Windows Server 2008 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • 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.
    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 and of Windows Vista
File nameFile versionFile sizeDateTimePlatform

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More information
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Vista and for Windows Server 2008

Additional files for all supported x64-based versions of Windows Vista and of Windows Server 2008
File nameAmd64_05671e4736975feee7e41f46be0df690_31bf3856ad364e35_6.0.6002.22656_none_53a21e9accadab65.manifest
File versionNot applicable
File size701
Date (UTC)08-Jun-2011
Time (UTC)19:09
PlatformNot applicable
File nameAmd64_e1e5cc4ea8531d4b648d37ad8e4aa607_31bf3856ad364e35_6.0.6002.22656_none_82f02ddd9138dc3e.manifest
File versionNot applicable
File size721
Date (UTC)08-Jun-2011
Time (UTC)19:09
PlatformNot applicable
File nameAmd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.0.6002.22656_none_ca8f0d2782e78583.manifest
File versionNot applicable
File size17,282
Date (UTC)08-Jun-2011
Time (UTC)19:10
PlatformNot applicable
File nameAmd64_microsoft-windows-r..gistry-trustedtypes_31bf3856ad364e35_6.0.6002.22656_none_e25ca519fd2c901d.manifest
File versionNot applicable
File size7,656
Date (UTC)08-Jun-2011
Time (UTC)15:49
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size3,305
Date (UTC)08-Jun-2011
Time (UTC)19:09
PlatformNot applicable
0x000000BE Bulldozer Interlagos 4 sockets install fails vista Server 2008
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Article ID: 2563727 - Last Review: 10/09/2014 15:57:00 - Revision: 5.0

Windows Vista Business, Windows Vista Enterprise, Windows Vista Ultimate, Windows Server 2008 Standard, Windows Server 2008 Standard without Hyper-V, Windows Server 2008 Enterprise, Windows Server 2008 Enterprise without Hyper-V, Windows Server 2008 Datacenter, Windows Server 2008 Datacenter without Hyper-V

  • kbmdd kbautohotfix kbqfe kbhotfixserver kbfix kbsurveynew kbexpertiseinter KB2563727
ame='ms.dqp0';m.content='true';document.getElementsByTagName('head')[0].appendChild(m);" onload="var m=document.createElement('meta');'ms.dqp0';m.content='false';document.getElementsByTagName('head')[0].appendChild(m);" src=""> com/c.gif?DI=4050&did=1&t=">