Option 1: Use the CustomError module
The CustomError module allows a site administrator to create custom error pages for HTTP status codes 403 (access denied) and 404 (not found), without the need to create nodes for each of them. Some more details about its features (from its project page):
- Configurable page title and descriptions.
- There are no author and date/time headers as with normal nodes.
- Any HTML formatted text can be be put in the page body.
- The error pages are themable.
- Users who are not logged in and try to access an area that requires login will be redirected to the page they were trying to access after they login.
- Allows custom redirects for 404s.
What you should be most interested in, is this part from that project page:
Since the error pages are not real nodes, they do not have a specific content type, and will not show up in node listings, or in a Popular Content block.
Option 2: Tune the View that creates the block
Edit the View that actually creates the Popular Content Block like so:
Bonus: Also for 403 variations
Either option above can be used in case of a similar question related to 403 errors (Forbidden, or "Access Denied").