Warning NTDS ISAM Event ID 507 and Event id 508

I am getting some issue with my Active Directory, with domain controller, sometime appears this warning in the even viewer:

Event Type: Warning
Event Source: NTDS ISAM
Event Category: Performance
Event ID: 507
Date: 05/09/2006
Time: 9.25.07
User: N/A
Computer: ERACLE
Description: NTDS (500) NTDSA: A request to read from the file "C:\WINDOWS\NTDS\ntds.dit" at offset 15908864 (0x0000000000f2c000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (87 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

And also:

Event Type: Warning
Event Source: NTDS ISAM
Event Category: Performance
Event ID: 508
Date: 05/09/2006
Time: 9.25.07
User: N/A
Computer: ERACLE
Description: NTDS (500) NTDSA: A request to write to the file "C:\WINDOWS\NTDS\edb.log" at offset 1230848 (0x000000000012c800) for 512 (0x00000200) bytes succeeded, but took an abnormally long time (95 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

Please help.

You can try to check whether the antivirus is looking at your NTDS Folder. You can also try to check whether the disk performance is bad or disk is starting to crash or having other performance issues.

I think that I had installed another DC and replicated AD information on this server all roles and AD objects. After that the first server was shutting down and off. Now the AD is ok. I think that it was a hw issue.

I have the same problem on 2 DCs. It started happening at the same time so I don't think it is related to hardware. I can reproduce the problem every time I try to copy a large file (> 1GB).

Has anyone found a solution to the problem that is *not* hardware related? I have no AV running.

NTDS (400) NTDSA: A request to read from the file "C:\WINDOWS\NTDS\ntds.dit" at offset 25772032 (0x0000000001894000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (146 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

I have this problem as well.

I just recently turned my member server in a Domain Controller.
My problem is NOT related to a hardware fault.

MS doesn't help with this error.

Both servers are 2k3 and very active Terminal Servers. If I'm in remote desktop and this occurs, the screen freezes but not all at once. My only solution is to wait it out.
This is causing problems with the client workstations. Main issue is because My Documents is redirected to the server, makes the workstations freeze up till the problem goes away.

I cannot reproduce this error.

I'm anxious to troubleshoot but I'm not sure where to start... denouncing it as a domain controller might be a start.

(by the way, I just joined this site to reply to this)

I just noticed that I have this event logged as well. Did anybody find an answer to this? It is possible that mine is hardware related since it is a server that is at least five years old. Here is a copy of my error.

Event Type: Warning
Event Source: NTDS ISAM
Event Category: Performance
Event ID: 508
Date: 4/21/2009
Time: 10:13:30 PM
User: N/A
Computer: server
Description:
NTDS (416) NTDSA: A request to write to the file "C:\WINDOWS\NTDS\edb.chk" at offset 0 (0x0000000000000000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (123 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

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

Thinking that this is a recurring error, other than the checking the obvious hardware issue, you may want to verify firmware/drivers for your disk controller and monitor disk performance to check if these do now come into play?

You need to also check that antivirus software excludes that directory during the scans or not. Also check the hardware drivers and run diagnostic test for hardware. I think that the hardware might gonna be crash.