<?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 38)</title>
	<link>https://www.dumpanalysis.org/blog/index.php/2007/11/22/crash-dump-analysis-patterns-part-38/</link>
	<description>Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics</description>
	<pubDate>Wed, 06 May 2026 22:05:02 +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/11/22/crash-dump-analysis-patterns-part-38/#comment-741685</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Fri, 25 Sep 2015 14:45:33 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/11/22/crash-dump-analysis-patterns-part-38/#comment-741685</guid>
		<description>Sometimes, several different modules from different products may patch different functions from the DLL. So, in general, we need to check all reported hooked functions.</description>
		<content:encoded><![CDATA[<p>Sometimes, several different modules from different products may patch different functions from the DLL. So, in general, we need to check all reported hooked functions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dmitry Vostokov</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/11/22/crash-dump-analysis-patterns-part-38/#comment-418239</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Fri, 03 Feb 2012 15:20:56 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/11/22/crash-dump-analysis-patterns-part-38/#comment-418239</guid>
		<description>To include the mismatch summary use this version:

The simplified version of the command:

!chkimg -db -d -v ModuleName

For example:

!chkimg -db -d -v ntdll</description>
		<content:encoded><![CDATA[<p>To include the mismatch summary use this version:</p>
<p>The simplified version of the command:</p>
<p>!chkimg -db -d -v ModuleName</p>
<p>For example:</p>
<p>!chkimg -db -d -v ntdll</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dmitry Vostokov</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/11/22/crash-dump-analysis-patterns-part-38/#comment-406878</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Mon, 09 Jan 2012 12:03:45 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/11/22/crash-dump-analysis-patterns-part-38/#comment-406878</guid>
		<description>The simplified version of the command:

!chkimg -db -v ModuleName

For example:

!chkimg -db -v ntdll</description>
		<content:encoded><![CDATA[<p>The simplified version of the command:</p>
<p>!chkimg -db -v ModuleName</p>
<p>For example:</p>
<p>!chkimg -db -v ntdll</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/11/22/crash-dump-analysis-patterns-part-38/#comment-197156</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 111)</dc:creator>
		<pubDate>Tue, 26 Oct 2010 21:21:53 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/11/22/crash-dump-analysis-patterns-part-38/#comment-197156</guid>
		<description>[...] command) we see the presence of the whole Pervasive System. It is not just a module that does function and / or message hooking but the whole system of modules from a single vendor that is [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] command) we see the presence of the whole Pervasive System. It is not just a module that does function and / or message hooking but the whole system of modules from a single vendor that is [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis of Defective Malware: A Case Study</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/11/22/crash-dump-analysis-patterns-part-38/#comment-194335</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis of Defective Malware: A Case Study</dc:creator>
		<pubDate>Mon, 18 Oct 2010 21:56:46 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/11/22/crash-dump-analysis-patterns-part-38/#comment-194335</guid>
		<description>[...] 0&#215;321aaaf address. We see that wininet function was hooked by a code running in 0&#215;0321XXXX [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] 0&#215;321aaaf address. We see that wininet function was hooked by a code running in 0&#215;0321XXXX [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Truncated dump, spiking thread, not my version and hooked functions: pattern cooperation</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/11/22/crash-dump-analysis-patterns-part-38/#comment-175806</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Truncated dump, spiking thread, not my version and hooked functions: pattern cooperation</dc:creator>
		<pubDate>Fri, 13 Aug 2010 19:16:36 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/11/22/crash-dump-analysis-patterns-part-38/#comment-175806</guid>
		<description>[...] We can stop here and still recommend to upgrade AppA product seen from the thread running on the first processor but the fact that the second thread belongs to innocent calc.exe demands some attention. Was it calculating incessantly some financial figures following button clicks from a financial genius? Taking advantage of a complete memory dump and the fact that this process spent most of the time in user space we can check for Hooked Functions pattern: [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] We can stop here and still recommend to upgrade AppA product seen from the thread running on the first processor but the fact that the second thread belongs to innocent calc.exe demands some attention. Was it calculating incessantly some financial figures following button clicks from a financial genius? Taking advantage of a complete memory dump and the fact that this process spent most of the time in user space we can check for Hooked Functions pattern: [&#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/11/22/crash-dump-analysis-patterns-part-38/#comment-164234</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:49 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/11/22/crash-dump-analysis-patterns-part-38/#comment-164234</guid>
		<description>[...] also see a message hook function implemented in DllA. To see if there are any other hooks including patched API we look at the raw [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] also see a message hook function implemented in DllA. To see if there are any other hooks including patched API we look at the raw [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 100)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/11/22/crash-dump-analysis-patterns-part-38/#comment-163878</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 100)</dc:creator>
		<pubDate>Tue, 06 Jul 2010 15:50:23 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/11/22/crash-dump-analysis-patterns-part-38/#comment-163878</guid>
		<description>[...] via windows message hooking mechanism that I call Message Hooks pattern to differentiate it from Hooked Functions pattern. In some cases message hooking become sources of aberrant software behaviour including [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] via windows message hooking mechanism that I call Message Hooks pattern to differentiate it from Hooked Functions pattern. In some cases message hooking become sources of aberrant software behaviour including [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 38b)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/11/22/crash-dump-analysis-patterns-part-38/#comment-150691</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 38b)</dc:creator>
		<pubDate>Fri, 07 May 2010 23:02:08 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/11/22/crash-dump-analysis-patterns-part-38/#comment-150691</guid>
		<description>[...] is a variation of Hooked Functions pattern for kernel space. In addition to trampoline patching we also see a modified service [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] is a variation of Hooked Functions pattern for kernel space. In addition to trampoline patching we also see a modified service [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; 10 Common Mistakes in Memory Analysis (Part 5)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/11/22/crash-dump-analysis-patterns-part-38/#comment-91557</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; 10 Common Mistakes in Memory Analysis (Part 5)</dc:creator>
		<pubDate>Mon, 31 Aug 2009 14:28:26 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/11/22/crash-dump-analysis-patterns-part-38/#comment-91557</guid>
		<description>[...] troubleshooting hypothesis. Here is a sample of !analyze -v output showing massive patching (hooked functions pattern) by DriverA [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] troubleshooting hypothesis. Here is a sample of !analyze -v output showing massive patching (hooked functions pattern) by DriverA [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
