UuidCreate API takes a long time to process a call and eventually times out in Windows Server 2008 SP2

Symptoms

Consider the following scenario:

  • You have a Windows Server 2008 Service Pack 2 (SP2)-based computer that has multiple processors.

  • CPU usage on one or more processors is high.

  • An application that runs at low priority calls the UuidCreate function.

In this scenario, the UuidCreate API takes a long time to process the call. Eventually, the process times out.

Cause

This issue occurs because of high CPU usage. When the UuidCreate function calls some other functions, the UuidCreate function takes a long time to return the UuidCreate API .

Resolution

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 the problem described in this article. 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 website:

http://support.microsoft.com/contactus/?ws=supportNote 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.

Prerequisites

To apply this hotfix, you must be running Windows Server 2008 SP2.

For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

968849How to obtain the latest service pack for Windows Server 2008

Registry information

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

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Server 2008 file information notesImportant Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.

    Version

    Product

    SR_Level

    Service branch

    6.0.600
    2.
    23xxx

    Windows Server 2008

    SP2

    LDR

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2008

File name

File version

File size

Date

Time

Platform

Ksecdd.sys

6.0.6002.23105

440,680

07-May-2013

23:09

x86

Lsasrv.dll

6.0.6002.23106

1,260,032

08-May-2013

03:12

x86

Lsasrv.mof

Not applicable

13,780

09-Sep-2011

11:41

Not applicable

Lsass.exe

6.0.6002.23106

9,728

08-May-2013

01:46

x86

Secur32.dll

6.0.6002.23106

72,704

08-May-2013

03:13

x86

Wdigest.dll

6.0.6002.23106

175,616

08-May-2013

03:13

x86

Msv1_0.dll

6.0.6002.23106

218,624

08-May-2013

03:13

x86

Schannel.dll

6.0.6002.23106

279,552

08-May-2013

03:13

x86

For all supported x64-based versions of Windows Server 2008

File name

File version

File size

Date

Time

Platform

Ksecdd.sys

6.0.6002.23105

517,480

07-May-2013

22:55

x64

Lsasrv.dll

6.0.6002.23106

1,690,624

08-May-2013

03:44

x64

Lsasrv.mof

Not applicable

13,780

15-Nov-2011

15:19

Not applicable

Lsass.exe

6.0.6002.23106

11,264

08-May-2013

02:11

x64

Secur32.dll

6.0.6002.23106

94,720

08-May-2013

03:47

x64

Wdigest.dll

6.0.6002.23106

205,824

08-May-2013

03:48

x64

Msv1_0.dll

6.0.6002.23106

269,312

08-May-2013

03:45

x64

Schannel.dll

6.0.6002.23106

348,160

08-May-2013

03:47

x64

Lsasrv.mof

Not applicable

13,780

09-Sep-2011

11:41

Not applicable

Secur32.dll

6.0.6002.23106

77,312

08-May-2013

03:14

x86

Wdigest.dll

6.0.6002.23106

175,616

08-May-2013

03:13

x86

Msv1_0.dll

6.0.6002.23106

218,624

08-May-2013

03:13

x86

Schannel.dll

6.0.6002.23106

279,552

08-May-2013

03:13

x86

For all supported IA-64-based versions of Windows Server 2008

File name

File version

File size

Date

Time

Platform

Ksecdd.sys

6.0.6002.23105

1,030,504

07-May-2013

22:49

IA-64

Lsasrv.dll

6.0.6002.23106

3,262,464

08-May-2013

02:20

IA-64

Lsasrv.mof

Not applicable

13,780

15-Mar-2011

05:54

Not applicable

Lsass.exe

6.0.6002.23106

17,920

08-May-2013

01:10

IA-64

Secur32.dll

6.0.6002.23106

202,752

08-May-2013

02:22

IA-64

Wdigest.dll

6.0.6002.23106

483,328

08-May-2013

02:23

IA-64

Msv1_0.dll

6.0.6002.23106

570,368

08-May-2013

02:21

IA-64

Schannel.dll

6.0.6002.23106

812,032

08-May-2013

02:22

IA-64

Lsasrv.mof

Not applicable

13,780

09-Sep-2011

11:41

Not applicable

Secur32.dll

6.0.6002.23106

77,312

08-May-2013

03:14

x86

Wdigest.dll

6.0.6002.23106

175,616

08-May-2013

03:13

x86

Msv1_0.dll

6.0.6002.23106

218,624

08-May-2013

03:13

x86

Schannel.dll

6.0.6002.23106

279,552

08-May-2013

03:13

x86


Status

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

More Information

For more information about the UuidCreate function, go to the following Microsoft website:

General information about the UuidCreate functionFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×