<?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 33)</title>
	<link>https://www.dumpanalysis.org/blog/index.php/2007/11/05/crash-dump-analysis-patterns-part-33/</link>
	<description>Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics</description>
	<pubDate>Tue, 19 May 2026 09:04:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 102)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/11/05/crash-dump-analysis-patterns-part-33/#comment-171610</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 102)</dc:creator>
		<pubDate>Thu, 29 Jul 2010 16:59:51 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/11/05/crash-dump-analysis-patterns-part-33/#comment-171610</guid>
		<description>[...] Here we should also analyze stack traces for running and ready threads with priority 8 and check kernel and user times. If we find anything common between them we should also check ready threads with lower priority to see if that commonality is unique to threads with priority 8. See also the similar pattern: Busy System. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Here we should also analyze stack traces for running and ready threads with priority 8 and check kernel and user times. If we find anything common between them we should also check ready threads with lower priority to see if that commonality is unique to threads with priority 8. See also the similar pattern: Busy System. [&#8230;]</p>
]]></content:encoded>
	</item>
	<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/11/05/crash-dump-analysis-patterns-part-33/#comment-164748</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Icons for Memory Dump Analysis Patterns (Part 55)</dc:creator>
		<pubDate>Fri, 09 Jul 2010 07:54:20 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/11/05/crash-dump-analysis-patterns-part-33/#comment-164748</guid>
		<description>[...] Today we introduce an icon for Busy System pattern: [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Today we introduce an icon for Busy System pattern: [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Busy system, blocked threads, wait chains and deadlock: pattern cooperation</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/11/05/crash-dump-analysis-patterns-part-33/#comment-66888</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Busy system, blocked threads, wait chains and deadlock: pattern cooperation</dc:creator>
		<pubDate>Tue, 03 Mar 2009 18:53:45 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/11/05/crash-dump-analysis-patterns-part-33/#comment-66888</guid>
		<description>[...]  2010 (0x7DA) - The Year of Dump Analysis In one kernel memory dump we can see the signs of a busy system where all processors are executing non-idle [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;]  2010 (0&#215;7DA) - The Year of Dump Analysis In one kernel memory dump we can see the signs of a busy system where all processors are executing non-idle [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 81)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/11/05/crash-dump-analysis-patterns-part-33/#comment-65591</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 81)</dc:creator>
		<pubDate>Thu, 19 Feb 2009 21:53:41 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/11/05/crash-dump-analysis-patterns-part-33/#comment-65591</guid>
		<description>[...] memory dumps because they contain virtual memory. The problem usually manifests itself either on busy systems utilizing almost all physical memory or on over-aged systems where certain processes hadn&#8217;t [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] memory dumps because they contain virtual memory. The problem usually manifests itself either on busy systems utilizing almost all physical memory or on over-aged systems where certain processes hadn&#8217;t [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
