Question - do you really need to check for NULLs for all fields that have domains in the seven point feature classes? I know sometimes not all fields are being used in the geodatabase, but may be they're for future use.
If you check on the "Search for Nulls Values" option, the Domain check could potentially be returning hundred of thousand errors. And since you are using a personal geodatabase as the Reviewer workspace, you could be hitting the max size threshold for Microsoft Access databases, which is what a personal geodatabase is. The max size is 2GB.
Try unchecking the "Search for Null Values" option in your Domain checks and re-run the batch job. Or use a file geodatabase as the Reviewer workspace and re-run the batch job.
Let me know if this helps.