While I do have an Agent job that runs DBCC CheckDB once a week as well (at a time that doesn't impact any other jobs,) I'll manually run it as you suggest this weekend (I have to wait that long, there's Agent jobs that fire every 30 minutes to load data throughout the week. They don't run on the weekends...)

As for the select *, it's about 3/4 done (8.4 million rows in the table) with no problems so far...

And it just finished with the same error. Sounds like the DBCC CheckDB job isn't catching this problem. I'll run your code this weekend, and see what it spits up.