Do these servers running any applications - i.e. SQL, Exchange etc.
What file does it have problems scanning?
Are there any other similar entries in the on-access scan log that suggest something is having problems?
there are applications running (including databases) but these Paths are excluded from scanning. The Timout errors occur on basicly random Files. Some dlls in system32 , nothing that points out.
I've seen those same problems with the about screen though I'm not sure if that indicates a corrupt VSE install or not. Have you tried uninstall/reboot/reinstall yet on any of these three systems to see if that resolves the issue? It may be worth a shot if it's a corrupted installation.
In the application Log there are 5051 events stating that Mcshield used more then 90000 ms to scan some file.
Timeout events should not be ignored (unless you were expecting them). There are 2 kinds of timeouts, graceful and fatal.
They both mean that a file has gone unscanned, but the latter also means the scanner had to self-terminate in order to abort the scan.
These events should be investigated and understood why they are occurring, especially if occurring in numbers that suggest it's frequent, or if found to be from touching the same filename.
The About screen anomaly means we failed to pull the proper text strings from our strings binary. This is cosmetic. You can close and open the window again without issue. It would be "curious" to find there is a relationship between timeouts occurring and the About window displaying like that.
just a tip: please use a File Monitor application to see what file is that VSE could be scanning at time of slowdown...