Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Stop error on a Windows Server 2008-based terminal server when the server is running under a heavy load: "0x0000000A"

View products that this article applies to.


When a Windows Server 2008-based terminal server is running under a heavy load for a long time (about eight hours), an error occurs in the memory manager. In this situation, you receive the following Stop error message:
STOP: 0x0000000A (parameter1, parameter2, parameter3, parameter4)
When this issue occurs, all user sessions on the server fail. In this situation, you must restart the server.

↑ Back to the top


This issue occurs because of a race condition that is triggered when the memory manager deals with certain kinds of images. Specifically, a thread in one terminal server session searches for an entry in the Viphook.dll file. At the same time, a thread in another terminal server session deletes this entry. Because of this synchronization issue, the first thread returns a value of NULL.

↑ Back to the top


Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the �Hotfix Request� page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.


To apply this hotfix, the computer must be running one of the following operating systems:
  • Windows Server 2008
  • Windows Vista Service Pack 1 (SP1)

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

To use this hotfix, you do not have to make any changes to the registry.

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 2008 and Windows Vista SP1, x86-based versions
File nameFile versionFile sizeDateTimePlatform
Package_1_for_kb951149~31bf3856ad364e35~x86~~ applicable1,77730-Apr-200817:14Not applicable
Package_2_for_kb951149~31bf3856ad364e35~x86~~ applicable1,94430-Apr-200817:14Not applicable
Package_3_for_kb951149~31bf3856ad364e35~x86~~ applicable1,78230-Apr-200817:14Not applicable
Package_4_for_kb951149~31bf3856ad364e35~x86~~ applicable1,78230-Apr-200817:14Not applicable
Package_for_kb951149_client_1~31bf3856ad364e35~x86~~ applicable1,36730-Apr-200817:14Not applicable
Package_for_kb951149_client~31bf3856ad364e35~x86~~ applicable1,43130-Apr-200817:14Not applicable
Package_for_kb951149_sc_0~31bf3856ad364e35~x86~~ applicable1,42130-Apr-200817:14Not applicable
Package_for_kb951149_sc~31bf3856ad364e35~x86~~ applicable1,42330-Apr-200817:14Not applicable
Package_for_kb951149_server_0~31bf3856ad364e35~x86~~ applicable1,42530-Apr-200817:14Not applicable
Package_for_kb951149_server~31bf3856ad364e35~x86~~ applicable1,43130-Apr-200817:14Not applicable
Package_for_kb951149_winpesrv_0~31bf3856ad364e35~x86~~ applicable1,42230-Apr-200817:14Not applicable
Package_for_kb951149_winpesrv~31bf3856ad364e35~x86~~ applicable1,42930-Apr-200817:14Not applicable
X86_8787e7ee511dde00a6197061728d0054_31bf3856ad364e35_6.0.6001.22169_none_883c00dd9adbd137.manifestNot applicable69730-Apr-200817:14Not applicable
X86_microsoft-windows-os-kernel_31bf3856ad364e35_6.0.6001.22169_none_6c82217dcd693de7.manifestNot applicable17,80630-Apr-200806:24Not applicable
Ntkrnlpa.exe6.0.6001.221693,601,46430-Apr-200805:39Not applicable
Ntoskrnl.exe6.0.6001.221693,549,24030-Apr-200805:39Not applicable
Windows Server 2008 and Windows Vista SP1, x64-based versions
File nameFile versionFile sizeDateTimePlatform
Amd64_076f98de89d41b26ae5a52e135562863_31bf3856ad364e35_6.0.6001.22169_none_df5e571d3e227436.manifestNot applicable70130-Apr-200817:14Not applicable
Amd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.0.6001.22169_none_c8a0bd0185c6af1d.manifestNot applicable16,51230-Apr-200808:21Not applicable
Package_1_for_kb951149~31bf3856ad364e35~amd64~~ applicable1,78730-Apr-200817:14Not applicable
Package_2_for_kb951149~31bf3856ad364e35~amd64~~ applicable1,95630-Apr-200817:14Not applicable
Package_3_for_kb951149~31bf3856ad364e35~amd64~~ applicable1,79230-Apr-200817:14Not applicable
Package_4_for_kb951149~31bf3856ad364e35~amd64~~ applicable1,79230-Apr-200817:14Not applicable
Package_for_kb951149_client_1~31bf3856ad364e35~amd64~~ applicable1,37530-Apr-200817:14Not applicable
Package_for_kb951149_client~31bf3856ad364e35~amd64~~ applicable1,43930-Apr-200817:14Not applicable
Package_for_kb951149_sc_0~31bf3856ad364e35~amd64~~ applicable1,42930-Apr-200817:14Not applicable
Package_for_kb951149_sc~31bf3856ad364e35~amd64~~ applicable1,43130-Apr-200817:14Not applicable
Package_for_kb951149_server_0~31bf3856ad364e35~amd64~~ applicable1,43330-Apr-200817:14Not applicable
Package_for_kb951149_server~31bf3856ad364e35~amd64~~ applicable1,43930-Apr-200817:14Not applicable
Package_for_kb951149_winpesrv_0~31bf3856ad364e35~amd64~~ applicable1,43030-Apr-200817:14Not applicable
Package_for_kb951149_winpesrv~31bf3856ad364e35~amd64~~ applicable1,43730-Apr-200817:14Not applicable
Windows Server 2008, Itanium-based versions
File nameFile versionFile sizeDateTimePlatform
Ia64_777bfc00e3a8b97d8ce87eced5378809_31bf3856ad364e35_6.0.6001.22169_none_9a7eabf64b7fbf25.manifestNot applicable69930-Apr-200817:14Not applicable
Ia64_microsoft-windows-os-kernel_31bf3856ad364e35_6.0.6001.22169_none_6c83c573cd6746e3.manifestNot applicable16,81930-Apr-200810:29Not applicable
Package_1_for_kb951149~31bf3856ad364e35~ia64~~ applicable1,78230-Apr-200817:14Not applicable
Package_2_for_kb951149~31bf3856ad364e35~ia64~~ applicable1,78730-Apr-200817:14Not applicable
Package_3_for_kb951149~31bf3856ad364e35~ia64~~ applicable1,78730-Apr-200817:14Not applicable
Package_for_kb951149_sc_0~31bf3856ad364e35~ia64~~ applicable1,42530-Apr-200817:14Not applicable
Package_for_kb951149_sc~31bf3856ad364e35~ia64~~ applicable1,42630-Apr-200817:14Not applicable
Package_for_kb951149_server_0~31bf3856ad364e35~ia64~~ applicable1,42930-Apr-200817:14Not applicable
Package_for_kb951149_server~31bf3856ad364e35~ia64~~ applicable1,43430-Apr-200817:14Not applicable
Package_for_kb951149_winpesrv_0~31bf3856ad364e35~ia64~~ applicable1,42630-Apr-200817:14Not applicable
Package_for_kb951149_winpesrv~31bf3856ad364e35~ia64~~ applicable1,43330-Apr-200817:14Not applicable

↑ Back to the top


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

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

↑ Back to the top

Keywords: kbautohotfix, kbexpertiseadvanced, kbfix, kbqfe, KB951149

↑ Back to the top

Article Info
Article ID : 951149
Revision : 2
Created on : 10/8/2011
Published on : 10/8/2011
Exists online : False
Views : 384