Dsamain.exe process crashes when AD LDS instance raises an exception in Windows 8.1 or Windows Server 2012 R2

This article describes an issue that occurs on a Windows 8.1 or Windows Server 2012 R2-based computer that has the Active Directory Lightweight Directory Services (AD LDS) server role installed. A hotfix is available to fix this issue. The hotfix has a prerequisite.
When this issue occurs, an event ID 1011 with the following information is raised in the Application Event log:

Log Name: Application
Source: Windows Error Reporting
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: dsamain.exe
P2: 6.3.9600.16384
P3: 5215f6df
P4: ntdsai.dll
P5: 6.3.9600.16517
P6: 52d9619c
P7: c0000005
P8: 000000000007a087

Hotfix information
Important If you install a language pack after you install this hotfix, you must reinstall this hotfix. Therefore, we recommend that you install any language packs that you need before you install this hotfix. For more information, see Add language packs to Windows.

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that's described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there's a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section doesn't appear, submit a request to Microsoft Customer Service and Support to get 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 don't 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: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you don't see your language, it's because a hotfix isn't available for that language.


To apply this hotfix, you must have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows 8.1 or Windows Server 2012 R2.

Registry information

To use the hotfix in this package, you don't have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix doesn't replace a previously released hotfix.

File information

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 8.1 and Windows Server 2012 R2 file information and notes

Important Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that's listed under "Windows 8.1/Windows Server 2012 R2" 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, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.3.960 0.16 xxxWindows 8.1 and Windows Server 2012 R2RTMGDR
    6.3.960 0.17xxxWindows 8.1 and Windows Server 2012 R2RTMGDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes aren't listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 8.1
File nameFile versionFile sizeDateTimePlatform
Active directory diagnostics.xmlNot applicable11,52918-Jun-201312:21Not applicable
Ntdsctr.hNot applicable19,67518-Jun-201312:21Not applicable
Ntdsctrs.iniNot applicable55,53618-Jun-201312:22Not applicable
Report.ad.xmlNot applicable167,99118-Jun-201312:21Not applicable
Rules.ad.xmlNot applicable33,91118-Jun-201312:21Not applicable
For all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Active directory diagnostics.xmlNot applicable11,52918-Jun-201314:46Not applicable
Ntdsctr.hNot applicable19,67518-Jun-201314:45Not applicable
Ntdsctrs.iniNot applicable55,53618-Jun-201314:46Not applicable
Report.ad.xmlNot applicable167,99118-Jun-201314:46Not applicable
Rules.ad.xmlNot applicable33,91118-Jun-201314:46Not applicable

Additional file information

Additional file information for Windows 8.1 and for Windows Server 2012 R2
Additional files for all supported x86-based versions of Windows 8.1
File propertyValue
File nameX86_bdb07ec6d5e584f235c2ba7ff323143f_31bf3856ad364e35_6.3.9600.17994_none_5e5108f03de1c102.manifest
File versionNot applicable
File size716
Date (UTC)24-Jul-2015
Time (UTC)08:47
PlatformNot applicable
File nameX86_microsoft-windows-d..services-core-files_31bf3856ad364e35_6.3.9600.17994_none_24801be6429de1bb.manifest
File versionNot applicable
File size11,809
Date (UTC)24-Jul-2015
Time (UTC)08:50
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2
File propertyValue
File nameAmd64_d3b2d66079595c62644acfa3ae9e1924_31bf3856ad364e35_6.3.9600.17994_none_774d29adf249aaf0.manifest
File versionNot applicable
File size720
Date (UTC)24-Jul-2015
Time (UTC)08:47
PlatformNot applicable
File nameAmd64_microsoft-windows-d..services-core-files_31bf3856ad364e35_6.3.9600.17994_none_809eb769fafb52f1.manifest
File versionNot applicable
File size11,813
Date (UTC)24-Jul-2015
Time (UTC)08:47
PlatformNot applicable
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More information
The issue occurs during a topology check by the knowledge consistency checker (KCC) to create the spanning tree algorithm.

During this process, Dsamain.exe references a NULL pointer, and the exception is raised.
See the terminology that Microsoft uses to describe software updates.

Article ID: 3080777 - Last Review: 09/08/2015 21:24:00 - Revision: 1.0

Windows Server 2012 R2 Datacenter, Windows Server 2012 R2 Standard, Windows Server 2012 R2 Essentials, Windows Server 2012 R2 Foundation, Windows 8.1 Enterprise, Windows 8.1 Pro, Windows 8.1

  • kbqfe kbsurveynew kbfix kbautohotfix kbhotfixserver kbexpertiseinter KB3080777