Errors in file increase with AUDIT command

[Anonymous]

I have a file where AUDIT finds and corrects errors, and then a subsequent run of AUDIT (no other commands between) results in more or less errors.  Nothing was done by the user between these commands:

Command: audit
Fix any errors detected? [Yes/No] <N>: y
Auditing Header
Auditing Tables
Auditing Entities Pass 1
Pass 1 8300    objects audited
Auditing Entities Pass 2
Pass 2 8300    objects audited
Auditing Blocks
 192     Blocks audited
Total errors found 18 fixed 18
Erased 0 objects

Command: audit
Fix any errors detected? [Yes/No] <N>: y
Auditing Header
Auditing Tables
Auditing Entities Pass 1
Pass 1 8300    objects audited
Auditing Entities Pass 2
Pass 2 8200    objects audited
Auditing Blocks
 192     Blocks audited
Total errors found 36 fixed 36
Erased 0 objects

What would cause this?  I am having crashes when I try to move feature lines from one site to another, which prompted me to run AUDIT several times in a row.  No matter how many times I run AUDIT, errors persist.  Sometimes the increase, sometimes they decrease with each subsequent execution of AUDIT.

[Adam_Farnsworth]

Just a random thought, but have you tried a purge after auditing?  Would you get the same results?

Sometimes I've found that a file is just corrupted beyond repair, and a fix that works (although it takes time and effort depending on how much is in the file) is to thaw and turn on everything, wblock it out, then insert it all into a new fresh file.  Then save that with the same name as the original file.

Of course, on complex jobs, this is easier said than done, and is mostly a last resort.  I'd love to find a better way to fix these little gremlins that seem to occasionally infect my files as well.

--Adam

[Neilw_05]

It is not uncommon for audit to return a second set of errors after repairing the first ones. My guess is that the repaired objects have dependencies that also are corrupted and they appear after the first run. Usually it clears up after the second run.

If there are XREFs attached, audit will find any errors in them but cannot fix them. To find the errant XREF, detach them one at a time until Audit runs clean. Once you know which file is causing the errors, open it and repair it.

It is rare that C3D can recover a file after a crash, so it wouldn't surpirise me if a file can't be repaired.