When you connect to a computer that is running Windows Server 2008 R2, Windows 7, Windows Vista or Windows Server 2008 by using the RDP protocol, the computer stops responding or you receive the following Stop error message:

STOP: 0x0000007F (0×0000008, parameter2, parameter3, parameter4)

Notes:

• The parameters in this Stop error message may vary, depending on the configuration of the computer. However, the first parameter is always 0×0000008.
• Not all “0x0000007F” Stop errors are caused by this issue.

For example, you have deployed a Microsoft Virtual Desktop Infrastructure (VDI) environment in a network. You log on to a virtual machine that is running Windows Server 2008 R2, Windows 7, Windows Vista or Windows Server 2008 in the VDI environment. In this situation, the virtual machine stops responding or you receive the Stop error message.

Consider the following scenario:

• You install Microsoft Message Queuing (also known as MSMQ) 4.0 on a computer that is running Windows Vista or Windows Server 2008.
• You create a transactional Message Queuing queue on the computer.
• You run a client application that performs a transactional remote receive on the queue by using the exclusive access mode.

In this scenario, the client application intermittently receives an error message that resembles the following:

Access denied

Note: This issue occurs even after you restart the application.

A computer that is running an x64-based version of Windows Vista Service Pack 2 (SP2) or of Windows Server 2008 SP2 crashes when you do one of the following:

• Restart the computer
• Restart the computer and then access the computer immediately by using Remote Desktop Protocol (RDP)

When this issue occurs, you receive the following Stop error message:

STOP: 0x0000001E : (ffffffffc0000005, fffff8000253254e, 0, ffffffffffffffff)
KMODE_EXCEPTION_NOT_HANDLED

Assume that you run a Windows Management Instrumentation (WMI) command to set a value in the Win32_ComputerSystem?WMI class on a computer that is running one of the following operating systems:

• Windows Vista
• Windows Server 2008
• Windows 7
• Windows Server 2008 R2

For example, you use administrative credentials to run the following command:
Wmic computersystem where name=”%computername%” set AutomaticManagedPagefile=False
In this situation, the value of the TimezonekeyName registry entry is changed to a null value.

Note: The TimezonekeyName registry entry is located in the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TimeZoneInformation

Consider the following scenario in a domain environment:

• You have a computer that is running Windows Server 2008 R2, Windows 7, Windows Server 2008 or Windows Vista.
• You use the Group Policy Management Console snap-in (Gpmc.msc) to connect to a domain controller from another domain.
• You create a Group Policy object (GPO). Then, you enable and configure the Item-level targeting option of the Group Policy preference setting for this GPO in the Gpmc.msc snap-in.
• In the Targeting Editor dialog box, you click New Item to select Computer Name or Security Group as the new item-level targeting item.
• You click the ellipsis button (…) to open an item-level targeting object picker dialog box.

In this scenario, the object picker dialog box shows an incomplete enterprise structure. The object picker dialog box only shows the domain in which the Gpmc.msc is started. The object picker dialog box does not show the domain in which you configure the Group Policy object. Because of this issue, users can only select objects in the same domain as the computer.

Assume that you run an application that uses the Windows Filtering Platform API for several minutes on a computer that is running one of the following operating systems:

• Windows 7
• Windows Server 2008 R2
• Windows Server 2008
• Windows Vista

In this situation, the computer stops responding and there is no network activity. To recover from this issue, you have to perform a hard restart.

Consider the following scenario:

• You use the Robocopy.exe utility to copy or backup files on a computer that is running Windows Vista or Windows Server 2008.
• The names of the files contain East Asian characters, for example Japanese characters.

In this scenario, some files may not be copied and the Robocopy.exe utility does not report an error.
Here is a sample scenario:

• You have the following two files on a computer that is running Windows Vista or Windows Server 2008.
  • ?.txt (“chouon” character)
  • ?.txt (“em dash” character)
  • -.txt (“en dash” character)
• You try to copy these files to a destination folder by using the Robocopy.exe utility.

In this scenario, the Robocopy.exe utility incorrectly believes that their file names are identical and only one of the files is copied. Additionally, no error is reported.

Consider the following scenario:

• You join a computer that is running Windows Server 2008 or Windows Vista to a network.
• The network is configured to use Internet Protocol security (IPsec) network address translation traversal (NAT-T) security.
• You use IPsec to communicate with another computer in the network.

In this scenario, you randomly receive a Stop error message that resembles the following, and then the computer restarts:

STOP 0x000000C2 (parameter1, parameter2, parameter3, parameter4)

Notes:

• This Stop error describes a BAD_POOL_CALLER issue.
• The four parameters in this error message vary, depending on the configuration of the computer.
• Not all “0x000000C2″ Stop errors are caused by this issue.

Assume that you run a service which queries the Win32_StartupCommand Windows Management Instrumentation (WMI) class on a computer that is running Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2.

In this situation, all loaded user profiles occasionally cannot be unloaded successfully after the WMI query is finished. If the number of unloaded user profiles keeps increasing, the system resources may be exhausted. For example, the virtual address control block (VACB) may be exhausted.

Here is a sample scenario:

• You run a service on a computer that is running Windows Server 2008.
• The service queries the Win32_QuickFixEngineering WMI class first.
• The service then queries the Win32_StartupCommand WMI class.

In this scenario, all loaded user profiles cannot be unloaded. If you open the HKEY_USERS registry subtree by using an administrator account, you find that the user profiles are still loaded.

Note: You can obtain more information about the loaded user profiles from the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

You schedule a task on a computer that is running Windows Vista or Windows Server 2008. However, the scheduled task is forcibly canceled by the TaskEng.exe process. Additionally, the following events are logged:

Event ID: 330
Source: Microsoft-Windows-TaskScheduler
Message: Task Scheduler stopped the instance name instance of task task name as request by user user name.

Event ID: 111
Source: Microsoft-Windows-TaskScheduler
Message: Task Scheduler terminated the instance name instance of the task name task.