TeamCity + ClearCase causes cleartool.exe to crash on server

We are running:

- TeamCity 6.5.3
- ClearCase 7.1.1
- 3 build agents
- 11 build configurations

Our builds run great for a while, but then after an indeterminate amount of time (usually a day or so), the TeamCity server suddenly stops checking for changes in all build configurations.

Around the time the server stops checking for changes, the Windows Event Log on the TeamCity server reports the following error messages:

Faulting application cleartool.exe, version 7.1100.0.180, time stamp 0x4b1565fa,  faulting module kernel32.dll, version 6.0.6001.18538, time stamp 0x4cb733dc,  exception code 0xc0000142, fault offset 0x00009cfc, process id 0xe0c,  application start time 0x01cca496ccbf06e6.
Faulting application  cleartool.exe, version 7.1100.0.180, time stamp 0x4b1565fa, faulting module  kernel32.dll, version 6.0.6001.18538, time stamp 0x4cb733dc, exception code  0xc0000142, fault offset 0x00009cfc, process id 0xd54, application start time  0x01cca4972036a5a2.
Faulting application cleartool.exe, version 7.1100.0.180,  time stamp 0x4b1565fa, faulting module kernel32.dll, version 6.0.6001.18538,  time stamp 0x4cb733dc, exception code 0xc0000142, fault offset 0x00009cfc,  process id 0x2a8, application start time 0x01cca497321866a2.
Faulting  application cleartool.exe, version 7.1100.0.180, time stamp 0x4b1565fa, faulting  module kernel32.dll, version 6.0.6001.18538, time stamp 0x4cb733dc, exception  code 0xc0000142, fault offset 0x00009cfc, process id 0x880, application start  time 0x01cca49735135c22.
Faulting application cleartool.exe, version  7.1100.0.180, time stamp 0x4b1565fa, faulting module kernel32.dll, version  6.0.6001.18538, time stamp 0x4cb733dc, exception code 0xc0000142, fault offset  0x00009cfc, process id 0xb28, application start time  0x01cca49735135c22.
Faulting application cleartool.exe, version 7.1100.0.180,  time stamp 0x4b1565fa, faulting module kernel32.dll, version 6.0.6001.18538,  time stamp 0x4cb733dc, exception code 0xc0000142, fault offset 0x00009cfc,  process id 0xbe0, application start time 0x01cca497ffcd42b4.

Apparently, cleartool.exe (the ClearCase command line executor) is crashing several times in a row.

Additionally (at the time of the crash) Windows Task Manager on the TeamCity server is reporting that 98 processes of cleartool.exe are running simultaneously (with a command line of:  cleartool.exe -status).  This seems highly excessive.

Without understanding what is happening, it appears that we are checking for changes too quickly?  And cleartool.exe cannot handle this?  For most of our build configurations, we are using the default of 60 seconds to check for VCS changes before triggering a build.

Should we use a longer interval?  One of our ClearCase views is somewhat large (14,000 files), and I suspect this might be causing cleartool.exe to overrun itself.

Any ideas?

Thanks,
Bryan