<?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 32)</title>
	<link>https://www.dumpanalysis.org/blog/index.php/2007/10/23/crash-dump-analysis-patterns-part-32/</link>
	<description>Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics</description>
	<pubDate>Tue, 19 May 2026 08:17:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Icons for Memory Dump Analysis Patterns (Part 55)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/10/23/crash-dump-analysis-patterns-part-32/#comment-164555</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Icons for Memory Dump Analysis Patterns (Part 55)</dc:creator>
		<pubDate>Thu, 08 Jul 2010 16:01:04 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/10/23/crash-dump-analysis-patterns-part-32/#comment-164555</guid>
		<description>[...] we introduce an icon for Main Thread [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] we introduce an icon for Main Thread [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Spiking thread, main thread, message hooks, hooked functions, semantic split, coincidental symbolic information and not my version: pattern cooperation</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/10/23/crash-dump-analysis-patterns-part-32/#comment-164233</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Spiking thread, main thread, message hooks, hooked functions, semantic split, coincidental symbolic information and not my version: pattern cooperation</dc:creator>
		<pubDate>Wed, 07 Jul 2010 16:32:34 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/10/23/crash-dump-analysis-patterns-part-32/#comment-164233</guid>
		<description>[...] process was reported consuming CPU and its user memory dump was saved. The main thread was a spiking thread [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] process was reported consuming CPU and its user memory dump was saved. The main thread was a spiking thread [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Icons for Memory Dump Analysis Patterns (Part 54)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/10/23/crash-dump-analysis-patterns-part-32/#comment-163611</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Icons for Memory Dump Analysis Patterns (Part 54)</dc:creator>
		<pubDate>Mon, 05 Jul 2010 16:53:40 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/10/23/crash-dump-analysis-patterns-part-32/#comment-163611</guid>
		<description>[...] we introduce an icon for Main Thread [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] we introduce an icon for Main Thread [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Stack trace collection, suspended threads, not my version, special process, main thread and blocked LPC chain threads: pattern cooperation</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/10/23/crash-dump-analysis-patterns-part-32/#comment-88190</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Stack trace collection, suspended threads, not my version, special process, main thread and blocked LPC chain threads: pattern cooperation</dc:creator>
		<pubDate>Tue, 11 Aug 2009 15:13:57 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/10/23/crash-dump-analysis-patterns-part-32/#comment-88190</guid>
		<description>[...] we zoom into NTSD process we would see that its main thread was waiting for a console [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] we zoom into NTSD process we would see that its main thread was waiting for a console [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; WOW64 process, NULL data pointer, stack overflow, main thread, incorrect stack trace, nested exceptions, hidden exception, manual dump, multiple exceptions and virtualized system: pattern cooperation</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/10/23/crash-dump-analysis-patterns-part-32/#comment-84356</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; WOW64 process, NULL data pointer, stack overflow, main thread, incorrect stack trace, nested exceptions, hidden exception, manual dump, multiple exceptions and virtualized system: pattern cooperation</dc:creator>
		<pubDate>Sun, 12 Jul 2009 17:09:54 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/10/23/crash-dump-analysis-patterns-part-32/#comment-84356</guid>
		<description>[...] we have never seen NtUserGetProp on stack traces, there is a possibility of an exception in main GUI thread and also the stack traces itself looks incorrect, suddenly sending a Windows message without any [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] we have never seen NtUserGetProp on stack traces, there is a possibility of an exception in main GUI thread and also the stack traces itself looks incorrect, suddenly sending a Windows message without any [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Manual and early crash dump, stack trace collection, main thread, blocked threads and pass through functions: pattern cooperation</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/10/23/crash-dump-analysis-patterns-part-32/#comment-71426</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Manual and early crash dump, stack trace collection, main thread, blocked threads and pass through functions: pattern cooperation</dc:creator>
		<pubDate>Thu, 16 Apr 2009 11:23:42 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/10/23/crash-dump-analysis-patterns-part-32/#comment-71426</guid>
		<description>[...] its startup so we went further to look at a stack trace collection of all its threads and found the main thread of spooler was hanging for about 23 seconds after 4 seconds since process [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] its startup so we went further to look at a stack trace collection of all its threads and found the main thread of spooler was hanging for about 23 seconds after 4 seconds since process [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 42d)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/10/23/crash-dump-analysis-patterns-part-32/#comment-49862</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 42d)</dc:creator>
		<pubDate>Fri, 07 Nov 2008 17:19:37 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/10/23/crash-dump-analysis-patterns-part-32/#comment-49862</guid>
		<description>[...] synchronization object whose owner is a thread so they can be easily identified. For example, the main application thread is waiting for an [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] synchronization object whose owner is a thread so they can be easily identified. For example, the main application thread is waiting for an [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
