<?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 3)</title>
	<link>https://www.dumpanalysis.org/blog/index.php/2006/11/01/crash-dump-analysis-patterns-part-3/</link>
	<description>Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics</description>
	<pubDate>Tue, 19 May 2026 01:52:57 +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/01/crash-dump-analysis-patterns-part-3/#comment-362571</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Mon, 31 Oct 2011 13:04:47 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2006/11/01/crash-dump-analysis-patterns-part-3/#comment-362571</guid>
		<description>I think you need to see what module calls OutputDebugString. You may also have other issues on other threads that !analyze -v is not able to figure out. You can ask for memory dump analysis audit:
http://www.dumpanalysis.com/memory-dump-analysis-audit-service</description>
		<content:encoded><![CDATA[<p>I think you need to see what module calls OutputDebugString. You may also have other issues on other threads that !analyze -v is not able to figure out. You can ask for memory dump analysis audit:<br />
<a href="http://www.dumpanalysis.com/memory-dump-analysis-audit-service" rel="nofollow">http://www.dumpanalysis.com/memory-dump-analysis-audit-service</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob A</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2006/11/01/crash-dump-analysis-patterns-part-3/#comment-361547</link>
		<dc:creator>Bob A</dc:creator>
		<pubDate>Sat, 29 Oct 2011 00:55:27 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2006/11/01/crash-dump-analysis-patterns-part-3/#comment-361547</guid>
		<description>Thanks for the great article.
I think I see a variant of this signature in another crash scenario:

We're seeing WER AppCrash reports, ending in
  Kernelbase!RaiseException
  OutputDebugString

We've closely inspected our machines, and can't see any debuggers present, nor does '!analyze -v' mention one.
The common theme in our issue is that we see this on Win Server 2008 R2 (64), where other OSes don't fail (XP 32/64, Win7).
We are a 32bit app.

I suspect (and this is hunches) that in this OS, RaiseException is sometimes used to trigger a heap corruption check, we fail, and get terminated.  Is this paranoia or FUD?

Though (head/tail) pageheap and other lenses don't seem to catch the corruption (it may be subtle?).

Thanks again for a great blog, you're an indispensable resource for Win developers!</description>
		<content:encoded><![CDATA[<p>Thanks for the great article.<br />
I think I see a variant of this signature in another crash scenario:</p>
<p>We&#8217;re seeing WER AppCrash reports, ending in<br />
  Kernelbase!RaiseException<br />
  OutputDebugString</p>
<p>We&#8217;ve closely inspected our machines, and can&#8217;t see any debuggers present, nor does &#8216;!analyze -v&#8217; mention one.<br />
The common theme in our issue is that we see this on Win Server 2008 R2 (64), where other OSes don&#8217;t fail (XP 32/64, Win7).<br />
We are a 32bit app.</p>
<p>I suspect (and this is hunches) that in this OS, RaiseException is sometimes used to trigger a heap corruption check, we fail, and get terminated.  Is this paranoia or FUD?</p>
<p>Though (head/tail) pageheap and other lenses don&#8217;t seem to catch the corruption (it may be subtle?).</p>
<p>Thanks again for a great blog, you&#8217;re an indispensable resource for Win developers!</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/01/crash-dump-analysis-patterns-part-3/#comment-186341</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Structural Memory Patterns (Part 1)</dc:creator>
		<pubDate>Fri, 24 Sep 2010 10:54:24 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2006/11/01/crash-dump-analysis-patterns-part-3/#comment-186341</guid>
		<description>[...] False Positive Dump [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] False Positive Dump [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Icons for Memory Dump Analysis Patterns (Part 5)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2006/11/01/crash-dump-analysis-patterns-part-3/#comment-133597</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Icons for Memory Dump Analysis Patterns (Part 5)</dc:creator>
		<pubDate>Fri, 12 Mar 2010 16:08:51 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2006/11/01/crash-dump-analysis-patterns-part-3/#comment-133597</guid>
		<description>[...] we introduce an icon for False Positive Dump [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] we introduce an icon for False Positive Dump [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aviv Greenberg</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2006/11/01/crash-dump-analysis-patterns-part-3/#comment-87056</link>
		<dc:creator>Aviv Greenberg</dc:creator>
		<pubDate>Tue, 04 Aug 2009 09:31:09 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2006/11/01/crash-dump-analysis-patterns-part-3/#comment-87056</guid>
		<description>Thanks for posting this! it really saved me time because i just could not figure out from this dump i got what was wrong with the string that was passed - the memory was valid....</description>
		<content:encoded><![CDATA[<p>Thanks for posting this! it really saved me time because i just could not figure out from this dump i got what was wrong with the string that was passed - the memory was valid&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: !analyze -v : Crash Dump Analysis Patterns (Part 3) – False Positive Dump</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2006/11/01/crash-dump-analysis-patterns-part-3/#comment-43014</link>
		<dc:creator>!analyze -v : Crash Dump Analysis Patterns (Part 3) – False Positive Dump</dc:creator>
		<pubDate>Wed, 17 Sep 2008 08:50:55 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2006/11/01/crash-dump-analysis-patterns-part-3/#comment-43014</guid>
		<description>[...] http://www.dumpanalysis.org/blog/index.php/2006/11/01/crash-dump-analysis-patterns-part-3/ [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] <a href="http://www.dumpanalysis.org/blog/index.php/2006/11/01/crash-dump-analysis-patterns-part-3/" rel="nofollow">http://www.dumpanalysis.org/blog/index.php/2006/11/01/crash-dump-analysis-patterns-part-3/</a> [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Management Bits and Tips &#187; Blog Archive &#187; Project Failure Analysis Patterns (Part 3)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2006/11/01/crash-dump-analysis-patterns-part-3/#comment-18283</link>
		<dc:creator>Management Bits and Tips &#187; Blog Archive &#187; Project Failure Analysis Patterns (Part 3)</dc:creator>
		<pubDate>Tue, 12 Feb 2008 11:50:59 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2006/11/01/crash-dump-analysis-patterns-part-3/#comment-18283</guid>
		<description>[...] mapping from False Positive Dump pattern brings us to False Project Failure pattern that usually happen when assessing the current [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] mapping from False Positive Dump pattern brings us to False Project Failure pattern that usually happen when assessing the current [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
