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.

FIX: High Critical Section Contention in MSWSTR10.dll under Stress


View products that this article applies to.

This article was previously published under Q327964

↑ Back to the top


Symptoms

You might experience slow performance or high CPU utilization, or the system may stop responding. If you attach a debugger to the process, or you load a user dump file in a debugger with correct symbol files setup, you might experience high critical section contention. The following is an example:
0:177> !locks 
CritSec MSWSTR10!g_CritSec+0 at 1B64A010 
LockCount 26 
RecursionCount 0 
OwningThread 0 
EntryCount 522d0 
ContentionCount 52373

↑ Back to the top


Resolution

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next MDAC 2.6/2.7 service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. The English version of this 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.
Collapse this tableExpand this table
DateTimeVersionSizeFile name
15-Aug-200208:572.70.9001.16307,200Msadce.dll
15-Aug-200208:572.70.9001.1657,344Msadcf.dll
15-Aug-200208:572.70.9001.16131,072Msadco.dll
15-Aug-200208:572.70.9001.1653,248Msadcs.dll
15-Aug-200208:572.70.9001.16147,456Msadds.dll
15-Aug-200208:572.70.9001.16487,424Msado15.dll
15-Aug-200208:572.70.9001.1653,248Msadrh15.dll
15-Aug-200208:572.70.9001.16180,224Msdaprst.dll
15-Aug-200208:572.70.9001.16110,592Msdarem.dll
15-Aug-200208:572.70.9001.1632,768Msdfmap.dll

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

↑ Back to the top


Keywords: KB327964, kbhotfixserver, kbqfe, kbfix, kbbug

↑ Back to the top

Article Info
Article ID : 327964
Revision : 5
Created on : 10/11/2005
Published on : 10/11/2005
Exists online : False
Views : 432