<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Crash Dump Analysis Patterns (Part 43)</title>
	<link>https://www.dumpanalysis.org/blog/index.php/2008/01/24/crash-dump-analysis-patterns-part-43/</link>
	<description>Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics</description>
	<pubDate>Wed, 06 May 2026 18:56:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Structural Memory Patterns (Part 7)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/01/24/crash-dump-analysis-patterns-part-43/#comment-194263</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Structural Memory Patterns (Part 7)</dc:creator>
		<pubDate>Mon, 18 Oct 2010 15:57:39 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/01/24/crash-dump-analysis-patterns-part-43/#comment-194263</guid>
		<description>[...] Debugging Experts Magazine Online In order to start the analysis of a structured memory snapshot a debugger engine needs Anchor Region that describes memory layout and where to start unfolding of analysis. For example, it can be a list of modules (another forthcoming structural pattern). We can observe the importance of such regions when we try to open corrupt or severely truncated memory dumps: [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Debugging Experts Magazine Online In order to start the analysis of a structured memory snapshot a debugger engine needs Anchor Region that describes memory layout and where to start unfolding of analysis. For example, it can be a list of modules (another forthcoming structural pattern). We can observe the importance of such regions when we try to open corrupt or severely truncated memory dumps: [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Icons for Memory Dump Analysis Patterns (Part 75)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/01/24/crash-dump-analysis-patterns-part-43/#comment-186390</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Icons for Memory Dump Analysis Patterns (Part 75)</dc:creator>
		<pubDate>Fri, 24 Sep 2010 15:34:20 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/01/24/crash-dump-analysis-patterns-part-43/#comment-186390</guid>
		<description>[...] Experts Magazine Online Today we introduce an icon for Corrupt Dump pattern (the motivation is that we can&#8217;t open such [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Experts Magazine Online Today we introduce an icon for Corrupt Dump pattern (the motivation is that we can&#8217;t open such [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Structural Memory Patterns (Part 1)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/01/24/crash-dump-analysis-patterns-part-43/#comment-186340</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Structural Memory Patterns (Part 1)</dc:creator>
		<pubDate>Fri, 24 Sep 2010 10:53:55 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/01/24/crash-dump-analysis-patterns-part-43/#comment-186340</guid>
		<description>[...] Corrupt Dump [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Corrupt Dump [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Reflecting on 2008 (Part 1)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/01/24/crash-dump-analysis-patterns-part-43/#comment-119532</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Reflecting on 2008 (Part 1)</dc:creator>
		<pubDate>Wed, 27 Jan 2010 00:47:39 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/01/24/crash-dump-analysis-patterns-part-43/#comment-119532</guid>
		<description>[...] in trade windbg script kernel_mode_exception_not_handled practical foundations of debugging getcontextstate failed, 0&#215;80070026 memory analysis intelligence minidump analyzer dxg.sys crash dump vista dr watson vista [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] in trade windbg script kernel_mode_exception_not_handled practical foundations of debugging getcontextstate failed, 0&#215;80070026 memory analysis intelligence minidump analyzer dxg.sys crash dump vista dr watson vista [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Lateral damage, stack overflow and execution residue: pattern cooperation</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/01/24/crash-dump-analysis-patterns-part-43/#comment-49661</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Lateral damage, stack overflow and execution residue: pattern cooperation</dc:creator>
		<pubDate>Wed, 05 Nov 2008 17:38:57 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/01/24/crash-dump-analysis-patterns-part-43/#comment-49661</guid>
		<description>[...] in comments to Lateral Damage pattern it lies in between the normal healthy dump files and corrupt dumps. For example, the following 8Gb complete memory dump that fits perfectly into 16Gb page file had [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] in comments to Lateral Damage pattern it lies in between the normal healthy dump files and corrupt dumps. For example, the following 8Gb complete memory dump that fits perfectly into 16Gb page file had [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Pseudo-corrupt memory dumps</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/01/24/crash-dump-analysis-patterns-part-43/#comment-37168</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Pseudo-corrupt memory dumps</dc:creator>
		<pubDate>Thu, 07 Aug 2008 17:16:27 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/01/24/crash-dump-analysis-patterns-part-43/#comment-37168</guid>
		<description>[...] was wrong with his disk or network drive mapping where they were stored or this was another sign of Corrupt Dump pattern. I also noticed these errors when I keep dump files open for weeks and then come back to [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] was wrong with his disk or network drive mapping where they were stored or this was another sign of Corrupt Dump pattern. I also noticed these errors when I keep dump files open for weeks and then come back to [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dmitry Vostokov</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/01/24/crash-dump-analysis-patterns-part-43/#comment-29492</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Thu, 05 Jun 2008 14:15:20 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/01/24/crash-dump-analysis-patterns-part-43/#comment-29492</guid>
		<description>It depends on your problem :-) The main point is that if you have corrupt dump you can still identify the problem. Also system administrators and support engineers can identify corrupt dumps earlier and request the new ones...</description>
		<content:encoded><![CDATA[<p>It depends on your problem <img src='https://www.dumpanalysis.org/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> The main point is that if you have corrupt dump you can still identify the problem. Also system administrators and support engineers can identify corrupt dumps earlier and request the new ones&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: clint</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/01/24/crash-dump-analysis-patterns-part-43/#comment-29486</link>
		<dc:creator>clint</dc:creator>
		<pubDate>Thu, 05 Jun 2008 13:20:48 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/01/24/crash-dump-analysis-patterns-part-43/#comment-29486</guid>
		<description>and this helps me solve my problem how?</description>
		<content:encoded><![CDATA[<p>and this helps me solve my problem how?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
