When software that uses Transport Driver Interface (TDI) drivers, such as some antivirus software, is installed on a Windows Server 2008 system or on Windows Vista Service Pack 1 (SP1) system, the handle count of the system process keeps increasing. This problem occurs if the Windows Server 2008 system or the Windows Vista Service Pack 1 (SP1) system is running on a computer that has multiple processors. If this issue occurs for some time, the computer begins to run out of system resources. Therefore, any new automatic file distribution (AFD) connection to this computer fails.

Additionally, the following problems may occur if the computer is a domain controller:

• User authentication fails
• Sysvol replication fails
• One of the following Netlogon events occurs:
  • Netlogon event 5775
  • Netlogon event 5792
  • Netlogon event 5792
  • Netlogon event 5719

For example, the following is a sample event when Netlogon event 5775 occurs:

Log Name: System
Source: NETLOGON
Event ID: 5775
Level: Error
Keywords: Classic
Description:
The dynamic deletion of the DNS record '. 600 IN SRV 0 100 389 .' failed on the following DNS server:
DNS server IP address: 
Returned Response Code (RCODE): 5
Returned Status Code: 10055
USER ACTION
To prevent remote computers from connecting unnecessarily to the domain controller, delete the record manually or troubleshoot the failure to dynamically delete the record. To learn more about debugging DNS, see Help and Support Center.

ADDITIONAL DATA
Error Value: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. 

When you are running Windows Vista or Windows Server 2008 on a computer that has more than 8 logical processors, the Windows Experience Index rating is unavailable in the system properties. Additionally, when you run the WinSAT command (Winsat.exe), the command exits with a fatal error message. For example, you receive the following error message when you run a WinSAT CPU -Encryption command:

Error: The WinSAT XML does not adhere to the schema.

This problem occurs on a computer that has more than 8 logical processors. For example, you have a computer that has two quad-core processors and hyper-threading is enabled for these processors. In this example, you have 16 logical processors because hyper-threading makes each core appear as two logical processors to the operating system.

A hotfix is available for Windows Vista-based computers and Windows Server 2008-based computers that have more than 32 logical processors. This hotfix corrects a logic that is used to determine affinity masks.

Consider the following scenario. You are running Windows Vista or Windows Server 2008 on a computer that has multi-core processors. A driver on the computer calls the MmProbeAndLockPages routine asynchronously. In this scenario, data corruption may occur.

This problem occurs randomly. It typically occurs when the following conditions are true:

• The computer has some graphics processing devices installed.
• You are running a graphics-intensive application.

When this problem occurs, the system or the application may crash. The actual symptoms vary, depending on the specific drivers that are installed on the computer.

Use multiple processors at boot time to speed the boot process! Keep reading →

Consider the following scenario:

• You have a computer that uses a multicore processor. The number of the cores on a socket is not a power of 2. For example, the computer has a 6-core processor.
• You install an x86-based version of Windows Server 2008 or an x86-based version of Windows Vista on the computer.

In this scenario, you experience the following problems:

• When you check the number of processors in some user interfaces, such as in Task Manager, the number that is displayed is lower than the actual number.
• Performance of the computer is lower than expected.

Note: These problems occur only on an x86-based version of Windows Server 2008 and on an x86-based version of Windows Vista.

Consider the following scenario:

• On a multiprocessor system, you encode a multi-bitrate (MBR) video by using one of the following:
  • Windows Media Encoder 9 Series
  • An application that is based on the Windows Media Format SDK

You compress the video by using one of the following:

• The Windows Media Video v9 codec
• The Windows Media Video 9 Advanced Profile codec

On a multiprocessor computer that is running Windows Vista, the Rasdial API may free the same memory two times. When this problem occurs, the dial-up application stops responding (hangs).

Consider the following scenario:

• You have a Windows Vista-based computer that has multiple processors, such as a dual-core processor. Or, the computer has a hyperthreading-enabled processor.
• You run a program that uses the waveOutWrite function.

In this scenario, the waveOutWrite function returns the following error message:

MMSYSERR_NODRIVER

The waveOutWrite function continues to return this error message until you exit the program. Additionally, audio playback does not work as expected when you run the program.

On an Intel Ultra Mobile Platform-based computer that is running Windows Vista, the Windows System Assessment tool (Winsat.exe) displays incorrect processor information. Therefore, the Windows Experience Index score is lower than the actual score.

Note: The code name for Intel Ultra Mobile Platform is “McCaslin.”

For example, you open a command prompt by using an administrator account. Then, you run the WinSAT.exe –v command at the command prompt. The processor cache size that appears in the command output is not consistent with the processor cache size that is described in the processor’s product documentation.