Found this using Google:
This is the kind of thing that may be a sign of virus damage, so give 'er a good scan with up-to-date virus definitions. Some report it as a result of older software that's not compatible with Windows XP.
But whatever the cause, Windows XP found a problem and wasn't able to detect it with the quick scanning method it uses. To do a better job and get rid of the scanning, go to My Computer, find and right-click on your C:/ drive, go to Properties. . .Tools. . .and Check Error, and let it do a thorough scan. That ought to take care of it.
In some cases this error seems to be a complete false alarm, and people have developed a registry tweak to stop Windows XP from doing this check. Messing with the registry is a dangerous thing for a beginner, but I'll include
THIS LINKfor those who are experts or fearless.
osprey4
4 Operator
•
34.2K Posts
0
November 28th, 2003 13:00
This is the kind of thing that may be a sign of virus damage, so give 'er a good scan with up-to-date virus definitions. Some report it as a result of older software that's not compatible with Windows XP.
But whatever the cause, Windows XP found a problem and wasn't able to detect it with the quick scanning method it uses. To do a better job and get rid of the scanning, go to My Computer, find and right-click on your C:/ drive, go to Properties. . .Tools. . .and Check Error, and let it do a thorough scan. That ought to take care of it.
In some cases this error seems to be a complete false alarm, and people have developed a registry tweak to stop Windows XP from doing this check. Messing with the registry is a dangerous thing for a beginner, but I'll include THIS LINKfor those who are experts or fearless.