<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>&amp;quot;Page cannot be displayed&amp;quot; due to Non-Paged Pooled Memory Depletion</title><link>http://blogs.msdn.com/chaun/archive/2008/02/21/page-cannot-be-displayed-due-to-non-paged-pooled-memory-depletion.aspx</link><description>Overview It’s not unnatural to assume an IIS process hang when web client browsers begin reporting either “Page cannot be displayed . . . cannot find server or dns error” (IE6) or "Internet Explorer cannot display the webpage. . .” (IE7). But when an</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator></channel></rss>