Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/925104

From BetaArchive Wiki

Article ID: 925104

Article Last Modified on 3/28/2007



APPLIES TO

  • Microsoft Windows Server 2003, 64-Bit Datacenter Edition
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
  • Microsoft Windows Server 2003, Datacenter x64 Edition
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server 2003, Enterprise x64 Edition



Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry


SYMPTOMS

When you use a Microsoft Windows Server 2003-based computer that has more than 32 processors, you may notice that many events are reported in the System log that resemble the following:

Event logged:
===============
PerfOS event ID: 2001 - "Unable to get interrupt information from system."

CAUSE

This problem occurs because one or more 32-bit applications have used the NtQuerySystemInformation function in order to determine the number of processors that are available for the computer. If more than 32 processors are available, the PerfOS event is logged every time that the NtQuerySystemInformation function is used.

RESOLUTION

Windows Server 2003-based computers that are running Service Pack 2 (SP2)

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

This problem was addressed in Windows Server 2003 Service Pack 2 (SP2). You do not have to download a hotfix to resolve this problem. However, some Windows registry information is missing. To resolve this problem, you must modify the Windows registry. To do this, follow these steps:

  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PerfOS\Performance

  3. In the Edit menu, point to New, click DWORD Value, type LogErrorToFile, and then press ENTER.
  4. Double-click LogErrorToFile, type 0, and then click OK.

    Note When you set the LogErrorToFile value to 0, PerfOS events are no longer logged in the System log. You can enable logging again by setting this value to 1.

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

889100 How to obtain the latest service pack for Windows Server 2003


Hotfix information

Windows Server 2003-based computers that are running Service Pack 1 (SP1) or earlier versions

When you install this hotfix on computers that are running Service Pack 1 (SP1) or earlier versions, you do not have to modify the registry to resolve this problem.

Prerequisites

There are no prerequisites for installing this hotfix.

Restart requirement

You must restart your computer after you apply this hotfix.

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.

Windows Server 2003, Itanium-based computers that are running SP1 or earlier versions

File name File version File size Date Time Platform SP requirement Service branch
Perfos.dll 5.2.3790.2794 57,344 16-Sep-2006 14:28 IA-64 SP1 SP1QFE
Wperfos.dll 5.2.3790.2794 27,136 16-Sep-2006 14:28 x86 SP1 WOW
Updspapi.dll 6.2.29.0 638,688 16-Sep-2006 14:39 IA-64 None Not Applicable

Windows Server 2003, x64-based computers that are running SP1 or earlier versions

File name File version File size Date Time Platform SP requirement Service branch
Perfos.dll 5.2.3790.2794 32,256 16-Sep-2006 14:28 x64 SP1 SP1QFE
Wperfos.dll 5.2.3790.2794 27,136 16-Sep-2006 14:28 x86 SP1 WOW
Updspapi.dll 6.2.29.0 462,048 16-Sep-2006 14:39 x64 None Not Applicable

Windows Server 2003, x86-based computers that are running SP1 or earlier versions

File name File version File size Date Time Platform
Perfos.dll 5.2.3790.2794 27,136 16-Sep-2006 12:50 x86
Updspapi.dll 6.2.29.0 371,424 12-Oct-2005 23:13 x86


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.

MORE INFORMATION

For more information, 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


Keywords: kbwinserv2003sp2fix kbexpertiseinter kbexpertiseadvanced kbwinserv2003presp2fix kbprb kbfix kbhotfixserver kbqfe kbpubtypekc KB925104