When you print on Windows Vista-based or Windows Server 2008-based computers that have hyper threading technology, the print process exits unexpectedly (crashes) under heavy stress.

Note: This issue occurs mainly on multiprocessor computers and on multicore computers.

Consider the following scenario:

• You have a multiprocessor computer that is running Windows XP, Windows Server 2003, or Windows Vista.
• You resume the computer from hibernation (S4).

In this scenario, the computer stops responding on a black screen.

On a multiprocessor computer that is running Windows Vista or Windows Server 2008, when you try to transfer requests to a specific endpoint on a USB device, the requests are not transferred over the USB bus in the order in which they are submitted to the Windows USB driver stack.

This issue usually occurs when some requests contain zero-byte packets.

Consider the following scenario:

• Windows Server 2008 or a Windows Vista SP1 is running in a virtual machine.
• The computer that is running the virtual machine has multiple processors.

In this scenario, the virtual machine may restart unexpectedly. Additionally, you may receive the following Stop error code:

0×000000BE

On a multiprocessor computer that is running Windows Vista or Windows Server 2008, a network connectivity failure occurs randomly when you run certain utilities, such as the Remote Shell (Rsh.exe) utility or the Remote Copy (Rcp.exe) utility. This problem occurs if a network application is using the same four-tuple (server IP address, server port, client IP address, and client port) every time that the utility reconnects a TCP session in a TCP TIME-WAIT delay period.

For example, consider the following scenario:

• On the Windows XP-based computer, the Remote Shell service is installed.
• On the Windows Vista-based computer that has multiple processors, the Remote Shell utility (Rsh.exe) is installed.
• You use the Remote Shell utility on the Windows Vista-based computer to access the Windows XP-based computer.
• The Remote Shell utility commands continue to run one after another for several minutes.

In this scenario, the Remote Shell utility may fail. Additionally, you may receive an error message that resembles the following:

Windows XP computer name: Operation timed out

Consider the following scenario:

• You have a computer that is running Windows Vista Service Pack 1 (SP1) or Windows Server 2008.
• The computer has multiple processors installed.
• You restart the computer.

In this scenario, the computer may stop responding at the Windows Start screen.

When you start a multiprocessor portable computer that runs Windows Vista, you may receive the following Stop error message:

STOP: 0×0000007E (parameter1, parameter2, parameter3, parameter4)
NETIO.SYS

This problem typically occurs after a driver for a third-party network adapter is installed.

Notes:

• The parameters in this Stop error message vary, depending on the configuration of the computer.
• Not all “0×0000007E” Stop error messages are caused by this problem.

Consider the following scenario:

• You have a multiprocessor computer that is running Windows Vista or Windows XP.
• The computer has exactly 32 processors.
• You resume the computer from hibernation (S4).

In this scenario, the computer stops responding on a black screen.