These unmonitored attributes should be disabled by removing them from ‘unmonitored attributes’ screen from the user (and possibly computer) object classes until you can apply the appropriate hot fix. If you leave these attributes enabled you will need to be extremely cautious as the chances of exploding the database size is extremely high. It is extremely important you do not try and continue to audit those attributes on computer object class, as they will in short order explode the database size.
These AD ‘housekeeping’ attributes will be shut off again in 6.
Hotfix 6.5.167+ and 6.6.653+ released with:
TF00418617 - 'After upgrading to Change Auditor 6.5, auditing of logon attributes causes an excessive amount of events'.