Your Windows Server 2003 computer may experience an access violation in Svchost.exe when it becomes extremely low on resources

Article translations Article translations
Article ID: 829994 - View products that this article applies to.
Expand all | Collapse all

On This Page


When your Windows Server 2003 computer becomes extremely low on resources, your computer may experience an access violation in Svchost.exe. When this problem occurs, your computer may unexpectedly shut down and then restart, or it may stop responding.

The problem that is described in this article is characterized by the following call stack:
2: kd> kb50
ChildEBP RetAddr  Args to Child
01b3f8e4 7531b4d6 01b3f8fc 0f1097e0 0f3b0490 0xffffffff
01b3f958 7531d656 0d831b10 03811830 0f1097e0 wbemcore!CComplexProjectionSink::Project+0x41
01b3f97c 75312f53 03811818 00000012 00000012 wbemcore!CComplexProjectionSink::Indicate+0x44
01b3f9b8 58b82230 037fe848 00000012 002b1678 wbemcore!CDecoratingSink::Indicate+0x13d
01b3f9d4 75588d7b 02b87888 00000012 0f0fee18 wmiprvsd!CInterceptor_IWbemObjectSink::Indicate+0x44
01b3fa18 75588ff5 00000012 0401def8 01b3fa6c FastProx!CSinkStubBuffer::XSinkStublet::Indicate_Stub+0xae
01b3fa28 77268ae0 026e62ac 02ac8754 0401def8 FastProx!CSinkStubBuffer::XSinkStublet::Invoke+0x1a
01b3fa6c 77268a8a 02ac8754 02a983a0 04093038 ole32!SyncStubInvoke+0x33
01b3fab4 77179c54 02ac8754 04027c88 026e62ac ole32!StubInvoke+0xa5
01b3fb8c 77179b79 0401def8 00000000 026e62ac ole32!CCtxComChnl::ContextInvoke+0xe3
01b3fba8 772689c2 02ac8754 00000001 026e62ac ole32!MTAInvoke+0x18
01b3fbd8 77268872 02ac8700 0401def8 026e62ac ole32!AppInvoke+0x9a
01b3fc94 77d696b4 e904549a 23c48428 01b3fcec ole32!ComInvokeWithLockAndIPID+0x29f
01b3fca4 77268d92 00000001 00000000 02a98388 USER32!___PchSym_ <PERF> (USER32+0x696b4)
01b3fcec 77c57307 00000004 02a98388 0013ec20 ole32!ThreadInvoke+0x1de
01b3fd20 77c571c9 77268c40 0013ec20 01b3fdf8 RPCRT4!DispatchToStubInCNoAvrf+0x38
01b3fd74 77c57289 00000000 00000000 77166a58 RPCRT4!RPC_INTERFACE::DispatchToStubWorker+0x112
01b3fd98 77c60291 0013ec20 00000000 77166a58 RPCRT4!RPC_INTERFACE::DispatchToStub+0xa1
01b3fdc8 77c852d1 0013ec20 0013ebd8 00000000 RPCRT4!RPC_INTERFACE::DispatchToStubWithObject+0xb3
01b3fe04 77c5a76a 0013e9b8 000a2ca8 000ef430 RPCRT4!LRPC_SCALL::DealWithRequestMessage+0x2dd
01b3fe28 77c57bf1 000a2ce0 01b3fe40 0013e9b8 RPCRT4!LRPC_ADDRESS::DealWithLRPCRequest+0x16b
01b3ff8c 77c696a9 77c695f1 000a2ca8 00000000 RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x423
01b3ff90 77c695f1 000a2ca8 00000000 00000000 RPCRT4!RecvLotsaCallsWrapper+0x9
01b3ffb0 77c696d7 0008a4d8 77e4a990 03ff2e68 RPCRT4!BaseCachedThreadRoutine+0x9c
01b3ffb8 77e4a990 03ff2e68 00000000 00000000 RPCRT4!ThreadStartRoutine+0x17
01b3ffec 00000000 77c696c0 03ff2e68 00000000 kernel32!BaseThreadStart+0x34


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.


No prerequisites are required.

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later) 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 tool in Control Panel.

Windows Server 2003 32-bit versions

Date         Time   Version            Size    File name
01-Oct-2003  08:13  5.2.3790.89       467,968  Wbemcore.dll 

Windows Server 2003 64-bit Edition

Date         Time   Version            Size    File name        Platform
01-Oct-2003  08:01  5.2.3790.89     1,724,416  Wbemcore.dll     IA-64


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


For additional 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


Article ID: 829994 - Last Review: July 25, 2007 - Revision: 2.10
  • Microsoft Windows Server 2003, Web Edition
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise x64 Edition
kbautohotfix kbhotfixserver kbqfe kbbug kbfix kbqfe kbwinserv2003presp1fix KB829994

Give Feedback


Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from