Q. Your Windows Server 2003 System event log reports many 'PerfOS event ID: 2001 - Unable to get interrupt information from system' errors?

When your Windows Server 2003 has more than 32 processors, the System event log reports many:

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

This behavior will occur if any 32-bit application uses the NtQuerySystemInformation function to determine the number of available processors. Because there are more than 32 processors available, the PerOS event is logged each time that the NtQuerySystemInformation function is used.

This behavior has been corrected and will be available in Windows Server 2003 SP2 (Service SP2ack 2), by setting the LogErrorToFile Value Name to 0:

1. Open a CMD.exe window.

2. Type the following command and press Enter:

<b>reg add HKLM\SYSTEM\CurrentControlSet\Services\PerfOS\Performance /V LogErrorToFile /T REG_DWORD /F /D 0</b>


Please or Register to post comments.

IT/Dev Connections

Las Vegas
September 30th - October 4th

Paul ThurottYou'll have the opportunity to experience:
• The Microsoft
Technology Roadmap
• Office 365 Implementation
• Hyper-V Optimizing
• Windows 8 Deployment
and much more!

Come See Paul Thurrott & Rod Trent in Person!

Early Registration Now Open

Upcoming Training

Mastering System Center 2012

During over 6 hours of training you can join John Savill from your computer as he will walk you through the key components and capabilities of System Center 2012, what’s involved in using the components, and the benefit they can bring to your environment.

Register Now

Current Issue

May 2013 - The NameTranslate object is useful when you need to translate Active Directory object names between different formats, but it's awkward to use from PowerShell. Here's a PowerShell script that eliminates the awkwardness.

CURRENT ISSUE / ARCHIVE / SUBSCRIBE

Windows Forums

Get answers to questions, share tips, and engage with the Windows Community in our Forums.