Active Directory intermittent error

50% of the time I reboot my server I get an "Active Directory is rebuilding
indices" message followed by an Active Directory error as described in
knowledge base article:

http://support.microsoft.com/?id=258062

There's no need for me to re-boot into DS Restore mode as a straight re-boot
into normal mode still brings up the same re-building message, and the
machine boots normally, and everything appears to work as it should. Event
log entries for a typical reboot follow:

Event Type: Information
Event Source: NTDS ISAM
Event Category: General
Event ID: 102
Date: 20/06/2005
Time: 00:22:24
User: N/A
Computer: MONTGOMERY
Description:
NTDS (768) NTDSA: The database engine started a new instance (0).

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: NTDS ISAM
Event Category: Logging/Recovery
Event ID: 477
Date: 20/06/2005
Time: 00:22:27
User: N/A
Computer: MONTGOMERY
Description:
NTDS (768) NTDSA: The log range read from the file "C:\WINDOWS\NTDS\edb.log"
at offset 5206016 (0x00000000004f7000) for 512 (0x00000200) bytes failed
verification due to a range checksum mismatch. The read operation will fail
with error -501 (0xfffffe0b). If this condition persists then please
restore the logfile from a previous backup.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: NTDS ISAM
Event Category: Logging/Recovery
Event ID: 465
Date: 20/06/2005
Time: 00:22:27
User: N/A
Computer: MONTGOMERY
Description:
NTDS (768) NTDSA: Corruption was detected during soft recovery in logfile
C:\WINDOWS\NTDS\edb.log. The failing checksum record is located at position
10168:19. Data not matching the log-file fill pattern first appeared in
sector 10168. This logfile has been damaged and is unusable.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: NTDS ISAM
Event Category: Logging/Recovery
Event ID: 300
Date: 20/06/2005
Time: 00:22:27
User: N/A
Computer: MONTGOMERY
Description:
NTDS (768) NTDSA: The database engine is initiating recovery steps.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: NTDS ISAM
Event Category: Logging/Recovery
Event ID: 477
Date: 20/06/2005
Time: 00:22:31
User: N/A
Computer: MONTGOMERY
Description:
NTDS (768) NTDSA: The log range read from the file "C:\WINDOWS\NTDS\edb.log"
at offset 5206016 (0x00000000004f7000) for 512 (0x00000200) bytes failed
verification due to a range checksum mismatch. The read operation will fail
with error -501 (0xfffffe0b). If this condition persists then please
restore the logfile from a previous backup.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: NTDS ISAM
Event Category: Logging/Recovery
Event ID: 465
Date: 20/06/2005
Time: 00:22:31
User: N/A
Computer: MONTGOMERY
Description:
NTDS (768) NTDSA: Corruption was detected during soft recovery in logfile
C:\WINDOWS\NTDS\edb.log. The failing checksum record is located at position
10168:19. Data not matching the log-file fill pattern first appeared in
sector 10168. This logfile has been damaged and is unusable.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: NTDS ISAM
Event Category: Logging/Recovery
Event ID: 477
Date: 20/06/2005
Time: 00:22:34
User: N/A
Computer: MONTGOMERY
Description:
NTDS (768) NTDSA: The log range read from the file "C:\WINDOWS\NTDS\edb.log"
at offset 5206016 (0x00000000004f7000) for 512 (0x00000200) bytes failed
verification due to a range checksum mismatch. The read operation will fail
with error -501 (0xfffffe0b). If this condition persists then please
restore the logfile from a previous backup.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: NTDS ISAM
Event Category: Logging/Recovery
Event ID: 465
Date: 20/06/2005
Time: 00:22:34
User: N/A
Computer: MONTGOMERY
Description:
NTDS (768) NTDSA: Corruption was detected during soft recovery in logfile
C:\WINDOWS\NTDS\edb.log. The failing checksum record is located at position
10168:19. Data not matching the log-file fill pattern first appeared in
sector 10168. This logfile has been damaged and is unusable.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: NTDS ISAM
Event Category: Logging/Recovery
Event ID: 301
Date: 20/06/2005
Time: 00:22:38
User: N/A
Computer: MONTGOMERY
Description:
NTDS (768) NTDSA: The database engine has begun replaying logfile
C:\WINDOWS\NTDS\edb.log.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: NTDS ISAM
Event Category: Logging/Recovery
Event ID: 454
Date: 20/06/2005
Time: 00:22:39
User: N/A
Computer: MONTGOMERY
Description:
NTDS (768) NTDSA: Database recovery/restore failed with unexpected
error -501.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: NTDS General
Event Category: Internal Processing
Event ID: 1168
Date: 20/06/2005
Time: 00:22:39
User: N/A
Computer: MONTGOMERY
Description:
Internal error: An Active Directory error has occurred.

Additional Data
Error value (decimal):
-501
Error value (hex):
fffffe0b
Internal ID:
40751

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: NTDS General
Event Category: Internal Processing
Event ID: 1003
Date: 20/06/2005
Time: 00:22:39
User: N/A
Computer: MONTGOMERY
Description:
Active Directory could not be initialized.

The operating system cannot recover from this error.

User Action
Restore the local domain controller from backup media.

Additional Data
Error value:
-501 %2

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: NTDS Backup
Event Category: Backup
Event ID: 1913
Date: 20/06/2005
Time: 00:25:43
User: N/A
Computer: MONTGOMERY
Description:
Internal error: The Active Directory backup and restore operation
encountered an unexpected error.

Backup or restore will not succeed until this is corrected.

Additional Data
Error value:
1062 The service has not been started.
Internal ID:
160200fa

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

I then just hit the OK button and then let Windows re-start normally and:

Event Type: Information
Event Source: NTDS ISAM
Event Category: General
Event ID: 102
Date: 20/06/2005
Time: 00:32:45
User: N/A
Computer: MONTGOMERY
Description:
NTDS (756) NTDSA: The database engine started a new instance (0).

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: NTDS General
Event Category: Service Control
Event ID: 1000
Date: 20/06/2005
Time: 00:33:22
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: MONTGOMERY
Description:
Microsoft Active Directory startup complete, version 5.2.3790.62

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: NTDS General
Event Category: Service Control
Event ID: 1394
Date: 20/06/2005
Time: 00:33:52
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: MONTGOMERY
Description:
Attempts to update the Active Directory database are succeeding. The Net
Logon service has restarted.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: NTDS General
Event Category: Global Catalog
Event ID: 1869
Date: 20/06/2005
Time: 00:48:23
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: MONTGOMERY
Description:
Active Directory has located a global catalog in the following site.

Global catalog:
\\montgomery.KingswoodHouse.local
Site:
Default-First-Site-Name

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: NTDS ISAM
Event Category: Online Defragmentation
Event ID: 700
Date: 20/06/2005
Time: 00:48:23
User: N/A
Computer: MONTGOMERY
Description:
NTDS (756) NTDSA: Online defragmentation is beginning a full pass on
database 'C:\WINDOWS\NTDS\ntds.dit'.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: NTDS ISAM
Event Category: Online Defragmentation
Event ID: 701
Date: 20/06/2005
Time: 00:48:25
User: N/A
Computer: MONTGOMERY
Description:
NTDS (756) NTDSA: Online defragmentation has completed a full pass on
database 'C:\WINDOWS\NTDS\ntds.dit'.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


I'm loathe to use the NTDSUTIL tools to work on this database in case it
ends up in a worse state than it is already.

I've come across a number of articles in around 2 hours of searching, and
apart from the article above, 2 seemed to strike a chord - 1 was deleting
edb.log and re-starting, and the other was to perform an offline defrag. I
did come across 1 article http://support.microsoft.com/?id=258062 which
seemed to describe my symptoms, but I've checked the version number of
ntdsa.dll and it matches that of the file included in the hotfix.

Thoughts please?


.