<?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 4)</title>
	<link>https://www.dumpanalysis.org/blog/index.php/2006/11/03/crash-dump-analysis-patterns-part-4/</link>
	<description>Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics</description>
	<pubDate>Wed, 06 May 2026 00:06:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Dmitry Vostokov</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2006/11/03/crash-dump-analysis-patterns-part-4/#comment-741668</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Thu, 26 Mar 2015 17:41:44 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2006/11/03/crash-dump-analysis-patterns-part-4/#comment-741668</guid>
		<description>0: ???&gt; ~0s
...
WARNING: Many commands will not work
...

0:000&gt; .ecxr
Unable to get exception context, HRESULT 0x80004005

0:000&gt; .exr -1
ExceptionAddress: ...(ModuleA!func+offset)</description>
		<content:encoded><![CDATA[<p>0: ???> ~0s<br />
&#8230;<br />
WARNING: Many commands will not work<br />
&#8230;</p>
<p>0:000> .ecxr<br />
Unable to get exception context, HRESULT 0&#215;80004005</p>
<p>0:000> .exr -1<br />
ExceptionAddress: &#8230;(ModuleA!func+offset)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dmitry Vostokov</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2006/11/03/crash-dump-analysis-patterns-part-4/#comment-741667</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Thu, 26 Mar 2015 17:21:08 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2006/11/03/crash-dump-analysis-patterns-part-4/#comment-741667</guid>
		<description>In case of process memory dumps where .ecxr doesn't work we may try .exr -1 to display the last exception record which may show an exception address, code, and parameters (such as a write or read address)</description>
		<content:encoded><![CDATA[<p>In case of process memory dumps where .ecxr doesn&#8217;t work we may try .exr -1 to display the last exception record which may show an exception address, code, and parameters (such as a write or read address)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 114)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2006/11/03/crash-dump-analysis-patterns-part-4/#comment-201568</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 114)</dc:creator>
		<pubDate>Tue, 09 Nov 2010 12:03:24 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2006/11/03/crash-dump-analysis-patterns-part-4/#comment-201568</guid>
		<description>[...] above. In some cases exception information might not be valid though, for example, in the case of laterally damaged or truncated memory dump [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] above. In some cases exception information might not be valid though, for example, in the case of laterally damaged or truncated memory dump [&#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/2006/11/03/crash-dump-analysis-patterns-part-4/#comment-186336</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Structural Memory Patterns (Part 1)</dc:creator>
		<pubDate>Fri, 24 Sep 2010 10:52:04 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2006/11/03/crash-dump-analysis-patterns-part-4/#comment-186336</guid>
		<description>[...] Lateral Damage [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Lateral Damage [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 104)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2006/11/03/crash-dump-analysis-patterns-part-4/#comment-173273</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 104)</dc:creator>
		<pubDate>Wed, 04 Aug 2010 23:07:29 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2006/11/03/crash-dump-analysis-patterns-part-4/#comment-173273</guid>
		<description>[...] The same also applies to user dumps where thread times information is omitted so it is not possible to use !runaway WinDbg command or to a dump saved with various options of .dump command (including privacy-aware) instead of /ma or deprecated /f option. On the contrary, manually erased data in crash dumps looks more like an example of another pattern called Lateral Damage. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] The same also applies to user dumps where thread times information is omitted so it is not possible to use !runaway WinDbg command or to a dump saved with various options of .dump command (including privacy-aware) instead of /ma or deprecated /f option. On the contrary, manually erased data in crash dumps looks more like an example of another pattern called Lateral Damage. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Icons for Memory Dump Analysis Patterns (Part 6)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2006/11/03/crash-dump-analysis-patterns-part-4/#comment-134599</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Icons for Memory Dump Analysis Patterns (Part 6)</dc:creator>
		<pubDate>Mon, 15 Mar 2010 15:15:44 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2006/11/03/crash-dump-analysis-patterns-part-4/#comment-134599</guid>
		<description>[...] we introduce an icon for Lateral Damage [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] we introduce an icon for Lateral Damage [&#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/2006/11/03/crash-dump-analysis-patterns-part-4/#comment-49660</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:35:18 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2006/11/03/crash-dump-analysis-patterns-part-4/#comment-49660</guid>
		<description>[...] I mentioned in comments to Lateral Damage pattern it lies in between the normal healthy dump files and corrupt dumps. For example, the [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] I mentioned in comments to Lateral Damage pattern it lies in between the normal healthy dump files and corrupt dumps. For example, the [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dmitry Vostokov</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2006/11/03/crash-dump-analysis-patterns-part-4/#comment-49655</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Wed, 05 Nov 2008 16:39:15 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2006/11/03/crash-dump-analysis-patterns-part-4/#comment-49655</guid>
		<description>Sometimes you get some vital information missing for default or usual analysis techniques and you need to seek other ways to look at dump data - this is the essence of Lateral Damage pattern.</description>
		<content:encoded><![CDATA[<p>Sometimes you get some vital information missing for default or usual analysis techniques and you need to seek other ways to look at dump data - this is the essence of Lateral Damage pattern.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: !analyze -v : Crash Dump Analysis Patterns (Part 4)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2006/11/03/crash-dump-analysis-patterns-part-4/#comment-43015</link>
		<dc:creator>!analyze -v : Crash Dump Analysis Patterns (Part 4)</dc:creator>
		<pubDate>Wed, 17 Sep 2008 08:53:23 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2006/11/03/crash-dump-analysis-patterns-part-4/#comment-43015</guid>
		<description>[...] 원문링크 [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] 원문링크 [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
