You're not alone. I'm experiencing a similar if not the exact same error on a MacBook Pro 16. I've found a similar entry on the Macrumors forums - no one seems to know what the exact cause is or what a workaround or fix might be.
ReliantWV
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
From
College Park, MD, United States