In the past, when this was seen it usually meant that there was either an issue with the web page display code, or an underlying issue with the database (possibly a schema issue). The first thing I'd look at is /var/log/httpd/error_log. You could parse it by scrolling back or if you want to be sure, tail that log file and then revisit the report page to get just the crash that happens when you hit that page. That will be the best hint for support if you happen to open a support case.
If it's a database issue, it'll manifest as a large crash message showing details about the table and row and the line of code calling it. (some 15-30 lines depending on the code path it's going through)