That's part of checkDB.
Nothing 'triggers' it. It happens when a user or job runs DBCC CheckTable or DBCC CheckDB.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability