<?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 28)</title>
	<link>https://www.dumpanalysis.org/blog/index.php/2007/09/26/crash-dump-analysis-patterns-part-28/</link>
	<description>Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics</description>
	<pubDate>Thu, 07 May 2026 07:37:56 +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/09/26/crash-dump-analysis-patterns-part-28/#comment-301621</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Thu, 23 Jun 2011 10:58:05 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/09/26/crash-dump-analysis-patterns-part-28/#comment-301621</guid>
		<description>Good diagrams explaining basic printing architecture:
http://blogs.technet.com/b/askperf/archive/2007/06/19/basic-printing-architecture.aspx
Also about print driver isolation in W2K8 R2/W7
http://blogs.technet.com/b/askperf/archive/2009/10/08/windows-7-windows-server-2008-r2-print-driver-isolation.aspx</description>
		<content:encoded><![CDATA[<p>Good diagrams explaining basic printing architecture:<br />
<a href="http://blogs.technet.com/b/askperf/archive/2007/06/19/basic-printing-architecture.aspx" rel="nofollow">http://blogs.technet.com/b/askperf/archive/2007/06/19/basic-printing-architecture.aspx</a><br />
Also about print driver isolation in W2K8 R2/W7<br />
<a href="http://blogs.technet.com/b/askperf/archive/2009/10/08/windows-7-windows-server-2008-r2-print-driver-isolation.aspx" rel="nofollow">http://blogs.technet.com/b/askperf/archive/2009/10/08/windows-7-windows-server-2008-r2-print-driver-isolation.aspx</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 111)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/09/26/crash-dump-analysis-patterns-part-28/#comment-197158</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 111)</dc:creator>
		<pubDate>Tue, 26 Oct 2010 21:22:46 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/09/26/crash-dump-analysis-patterns-part-28/#comment-197158</guid>
		<description>[...] additional value or to coexist peacefully in a larger environment. The system thus becomes coupled strongly and / or weekly with other processes it was never intended to work with as opposed to [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] additional value or to coexist peacefully in a larger environment. The system thus becomes coupled strongly and / or weekly with other processes it was never intended to work with as opposed to [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 103)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/09/26/crash-dump-analysis-patterns-part-28/#comment-173241</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 103)</dc:creator>
		<pubDate>Wed, 04 Aug 2010 20:06:14 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/09/26/crash-dump-analysis-patterns-part-28/#comment-173241</guid>
		<description>[...] link: Memory Dump Analysis ServicesIn addition to strong and weak process coupling patterns we also have another variant that I call semantic coupling. Some [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] link: Memory Dump Analysis ServicesIn addition to strong and weak process coupling patterns we also have another variant that I call semantic coupling. Some [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 101)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/09/26/crash-dump-analysis-patterns-part-28/#comment-167408</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 101)</dc:creator>
		<pubDate>Fri, 16 Jul 2010 00:49:26 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/09/26/crash-dump-analysis-patterns-part-28/#comment-167408</guid>
		<description>[...] that wait for a response from another machine (for example, via RPC) and for most of the time Coupled Processes pattern covers that if we assume that processes in that pattern are not restricted to same [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] that wait for a response from another machine (for example, via RPC) and for most of the time Coupled Processes pattern covers that if we assume that processes in that pattern are not restricted to same [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Icons for Memory Dump Analysis Patterns (Part 47)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/09/26/crash-dump-analysis-patterns-part-28/#comment-158251</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Icons for Memory Dump Analysis Patterns (Part 47)</dc:creator>
		<pubDate>Mon, 14 Jun 2010 11:31:03 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/09/26/crash-dump-analysis-patterns-part-28/#comment-158251</guid>
		<description>[...] Today we introduce an icon for Coupled Processes (strong) pattern: [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Today we introduce an icon for Coupled Processes (strong) pattern: [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Software Generalist &#187; Blog Archive &#187; Reading Notebook: 12-May-10</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/09/26/crash-dump-analysis-patterns-part-28/#comment-151949</link>
		<dc:creator>Software Generalist &#187; Blog Archive &#187; Reading Notebook: 12-May-10</dc:creator>
		<pubDate>Thu, 13 May 2010 22:44:05 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/09/26/crash-dump-analysis-patterns-part-28/#comment-151949</guid>
		<description>[...] So according to memory dump analysis pattern terminology these 2 processes are strongly coupled and this fact can be used for analysis logon problems in terminal services environments: http://www.dumpanalysis.org/blog/index.php/2007/09/26/crash-dump-analysis-patterns-part-28/  [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] So according to memory dump analysis pattern terminology these 2 processes are strongly coupled and this fact can be used for analysis logon problems in terminal services environments: <a href="http://www.dumpanalysis.org/blog/index.php/2007/09/26/crash-dump-analysis-patterns-part-28/" rel="nofollow">http://www.dumpanalysis.org/blog/index.php/2007/09/26/crash-dump-analysis-patterns-part-28/</a>  [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Strong process coupling, stack trace collection, critical section coruption and wait chains, message box, self-diagnosis and hidden exception and dynamic memory corruption: pattern cooperation</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/09/26/crash-dump-analysis-patterns-part-28/#comment-147468</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Strong process coupling, stack trace collection, critical section coruption and wait chains, message box, self-diagnosis and hidden exception and dynamic memory corruption: pattern cooperation</dc:creator>
		<pubDate>Mon, 26 Apr 2010 19:54:01 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/09/26/crash-dump-analysis-patterns-part-28/#comment-147468</guid>
		<description>[...] print spooler service process was hanging and blocking print-related requests from other coupled processes. Default analysis of its dump doesn&#8217;t show any problem (it shows normal service main [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] print spooler service process was hanging and blocking print-related requests from other coupled processes. Default analysis of its dump doesn&#8217;t show any problem (it shows normal service main [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 28b)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/09/26/crash-dump-analysis-patterns-part-28/#comment-141749</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 28b)</dc:creator>
		<pubDate>Wed, 07 Apr 2010 13:49:52 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/09/26/crash-dump-analysis-patterns-part-28/#comment-141749</guid>
		<description>[...] introduced Coupled Processes pattern involves an active request (or an action) and an active wait for a response (or the [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] introduced Coupled Processes pattern involves an active request (or an action) and an active wait for a response (or the [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Software Generalist &#187; Blog Archive &#187; Reading Notebook: 11-March-10</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/09/26/crash-dump-analysis-patterns-part-28/#comment-133249</link>
		<dc:creator>Software Generalist &#187; Blog Archive &#187; Reading Notebook: 11-March-10</dc:creator>
		<pubDate>Thu, 11 Mar 2010 17:12:05 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/09/26/crash-dump-analysis-patterns-part-28/#comment-133249</guid>
		<description>[...] Explorer usage to inspect hung threads (p. 383) - useful for coupled processes (http://www.dumpanalysis.org/blog/index.php/2007/09/26/crash-dump-analysis-patterns-part-28/) and could be great with simultaneous WinDbg session to inspect wait chains [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Explorer usage to inspect hung threads (p. 383) - useful for coupled processes (http://www.dumpanalysis.org/blog/index.php/2007/09/26/crash-dump-analysis-patterns-part-28/) and could be great with simultaneous WinDbg session to inspect wait chains [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 92)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/09/26/crash-dump-analysis-patterns-part-28/#comment-106045</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 92)</dc:creator>
		<pubDate>Tue, 24 Nov 2009 00:30:00 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/09/26/crash-dump-analysis-patterns-part-28/#comment-106045</guid>
		<description>[...] failure scenarios we should check these processes for their presence (and also the presence of any coupled processes), hence the name of this pattern: Missing Process. However, if the vital process is present we [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] failure scenarios we should check these processes for their presence (and also the presence of any coupled processes), hence the name of this pattern: Missing Process. However, if the vital process is present we [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
