Not sure if you made progress on this issue. We saw the same thing when a UI section (or visible when, etc) referenced a data page that was aborting with a stack overflow (in 8.2.1). Try tracing with stream rule events included and you might see more details about the true underlying error.
You can also try to reproduce by finding the offending harness/section and do a preview on it from dev studio, it will also throw the component stack mismatch error.
Try to preview the section from the designer studio and you would usually get a readable error message which highlights the issue. In my case, I got the above error and after preview, I recognized that a wrong page reference was given while embedding a section.