What is wrong with the distributed file service?

OK, more info.  I have found from monitoring the security event log and the application log the the high processor usage on the server by lsass and dfs starts when people come into the office in the morning and ends when people leave.  I thought it went all night but it does not.

Also throughout the day these two errors occur in the server Application log:

Windows cannot perform filter check for Group Policy object CN={99BCF64E-D350-401E-9FBF-24AEB17CE9FC},CN=Policies,CN=System,DC=CrownWestRealty,DC=local. The associated filter cannot be found. This Group Policy Object will be skipped.

Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this.

I have checked gpresult and dcdiag and everything seems fine.  I have 4 2003 dc and this is only occuring on one.

I am also receiving this error in the app log:

Windows cannot bind to Crown.local domain. (Local Error). Group Policy processing aborted.

This also only occurs during the day.

As a followup.  Don't know if the high processor activity for lsass and dfssrv is even related to the Application log errors of 1030,1006,1104.  Those errors have ceased this afternoon about 2pm.  The high processor levels of lsass and dfssrv are still running and generating the security log events of 538, 540, and 576.  Hundreds per second which is in keeping with the high processor activity of lsass and dfssrv.

The security logs are all the same of the local dc logging on, getting special permissions, and logging off.
Remember, if I disable dfs then the security logs back off to normal and processor use drops totally off.