<?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 41b)</title>
	<link>https://www.dumpanalysis.org/blog/index.php/2007/12/17/crash-dump-analysis-patterns-part-41b/</link>
	<description>Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics</description>
	<pubDate>Wed, 06 May 2026 03:09:29 +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/2007/12/17/crash-dump-analysis-patterns-part-41b/#comment-741688</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Wed, 18 Nov 2015 12:58:47 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/12/17/crash-dump-analysis-patterns-part-41b/#comment-741688</guid>
		<description>Clone Dump: 
http://www.dumpanalysis.org/blog/index.php/2015/11/18/crash-dump-analysis-patterns-part-233/</description>
		<content:encoded><![CDATA[<p>Clone Dump:<br />
<a href="http://www.dumpanalysis.org/blog/index.php/2015/11/18/crash-dump-analysis-patterns-part-233/" rel="nofollow">http://www.dumpanalysis.org/blog/index.php/2015/11/18/crash-dump-analysis-patterns-part-233/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dmitry Vostokov</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/12/17/crash-dump-analysis-patterns-part-41b/#comment-741641</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Sun, 17 Nov 2013 21:14:47 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/12/17/crash-dump-analysis-patterns-part-41b/#comment-741641</guid>
		<description>When using ProcDump we can see the comment in WinDbg output when we load a memory dump:

*** procdump.exe  -ma 8792
*** Manual dump'</description>
		<content:encoded><![CDATA[<p>When using ProcDump we can see the comment in WinDbg output when we load a memory dump:</p>
<p>*** procdump.exe  -ma 8792<br />
*** Manual dump&#8217;</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/2007/12/17/crash-dump-analysis-patterns-part-41b/#comment-186339</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Structural Memory Patterns (Part 1)</dc:creator>
		<pubDate>Fri, 24 Sep 2010 10:53:17 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/12/17/crash-dump-analysis-patterns-part-41b/#comment-186339</guid>
		<description>[...] Manual Dump (process) [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Manual Dump (process) [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Icons for Memory Dump Analysis Patterns (Part 67)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/12/17/crash-dump-analysis-patterns-part-41b/#comment-180878</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Icons for Memory Dump Analysis Patterns (Part 67)</dc:creator>
		<pubDate>Fri, 03 Sep 2010 15:38:47 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/12/17/crash-dump-analysis-patterns-part-41b/#comment-180878</guid>
		<description>[...] Experts Magazine Online Today we introduce an icon for Manual Dump (process) [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Experts Magazine Online Today we introduce an icon for Manual Dump (process) [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Manual dump, virtualized process, stack trace collection, multiple exceptions, optimized code, wild code pointer, incorrect stack trace and hidden exception: pattern cooperation</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/12/17/crash-dump-analysis-patterns-part-41b/#comment-77718</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Manual dump, virtualized process, stack trace collection, multiple exceptions, optimized code, wild code pointer, incorrect stack trace and hidden exception: pattern cooperation</dc:creator>
		<pubDate>Thu, 04 Jun 2009 09:33:51 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/12/17/crash-dump-analysis-patterns-part-41b/#comment-77718</guid>
		<description>[...] it is good to show the basic techniques for component identification using WinDbg. I took a manual user dump of that unresponsive process while it was showing that dialog above using Task [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] it is good to show the basic techniques for component identification using WinDbg. I took a manual user dump of that unresponsive process while it was showing that dialog above using Task [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Manual dump, wait chain, blocked thread, dynamic memory corruption and historical information: pattern cooperation</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/12/17/crash-dump-analysis-patterns-part-41b/#comment-68188</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Manual dump, wait chain, blocked thread, dynamic memory corruption and historical information: pattern cooperation</dc:creator>
		<pubDate>Sat, 14 Mar 2009 07:36:17 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/12/17/crash-dump-analysis-patterns-part-41b/#comment-68188</guid>
		<description>[...] (0x7D9) - The Year of Debugging  2010 (0x7DA) - The Year of Dump Analysis For one manual user dump of a hanging service neither !analyze -v nor !analyze -v -hang command found the [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] (0&#215;7D9) - The Year of Debugging  2010 (0&#215;7DA) - The Year of Dump Analysis For one manual user dump of a hanging service neither !analyze -v nor !analyze -v -hang command found the [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Manual dump, dynamic memory corruption, blocked threads, stack trace collection, multiple exceptions, wait chains and deadlock: pattern cooperation</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/12/17/crash-dump-analysis-patterns-part-41b/#comment-67311</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Manual dump, dynamic memory corruption, blocked threads, stack trace collection, multiple exceptions, wait chains and deadlock: pattern cooperation</dc:creator>
		<pubDate>Sun, 08 Mar 2009 00:16:19 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/12/17/crash-dump-analysis-patterns-part-41b/#comment-67311</guid>
		<description>[...] 2009 (0x7D9) - The Year of Debugging  2010 (0x7DA) - The Year of Dump Analysis The following memory dump of a hanging process was manually generated: [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] 2009 (0&#215;7D9) - The Year of Debugging  2010 (0&#215;7DA) - The Year of Dump Analysis The following memory dump of a hanging process was manually generated: [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; WOW64, blocked threads and coupled processes: pattern cooperation</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/12/17/crash-dump-analysis-patterns-part-41b/#comment-58135</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; WOW64, blocked threads and coupled processes: pattern cooperation</dc:creator>
		<pubDate>Fri, 28 Nov 2008 13:13:46 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/12/17/crash-dump-analysis-patterns-part-41b/#comment-58135</guid>
		<description>[...] a user complains. In this case it was a hanging application from a document processing suit. The manual dump was [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] a user complains. In this case it was a hanging application from a document processing suit. The manual dump was [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sunil</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/12/17/crash-dump-analysis-patterns-part-41b/#comment-46797</link>
		<dc:creator>Sunil</dc:creator>
		<pubDate>Tue, 14 Oct 2008 11:40:15 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/12/17/crash-dump-analysis-patterns-part-41b/#comment-46797</guid>
		<description>Hi,

In one of my applications I am facing the exception "Break Instruction Exception" frequently. I have collected the Dr Watson dumps but unable to make out why this is happening?

There aren't any debuggers or debugging tools installed on this machine, since its a test machine. So wondering how could this exception occur and causing this application to crash.

Is it possible that this is due to a memory corruption and the logged exception type is wrong.

Thanks for your response.

-Sunil</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>In one of my applications I am facing the exception &#8220;Break Instruction Exception&#8221; frequently. I have collected the Dr Watson dumps but unable to make out why this is happening?</p>
<p>There aren&#8217;t any debuggers or debugging tools installed on this machine, since its a test machine. So wondering how could this exception occur and causing this application to crash.</p>
<p>Is it possible that this is due to a memory corruption and the logged exception type is wrong.</p>
<p>Thanks for your response.</p>
<p>-Sunil</p>
]]></content:encoded>
	</item>
</channel>
</rss>
