<?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 8)</title>
	<link>https://www.dumpanalysis.org/blog/index.php/2007/02/02/crash-dump-analysis-patterns-part-8/</link>
	<description>Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics</description>
	<pubDate>Wed, 06 May 2026 12:37:19 +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/02/02/crash-dump-analysis-patterns-part-8/#comment-741702</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Sat, 07 May 2016 15:10:52 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/02/02/crash-dump-analysis-patterns-part-8/#comment-741702</guid>
		<description>On Windows 10 RSP below KiUserExceptionDispatch can be used as an address for .cxr command:

&lt;p align="left"&gt;[...]
00000023`d432f4e8  00000023`d3e3c190
00000023`d432f4f0  00000000`00000000
00000023`d432f4f8  00007ffa`e5c5577a ntdll!KiUserExceptionDispatch+0x3a
&lt;strong&gt;00000023`d432f500&lt;/strong&gt;  00000000`00000000
00000023`d432f508  00000000`00000810
[...]

&lt;p align="left"&gt;0:001&gt; .cxr 00000023`d432f500  
rax=0000000000000000 rbx=0000000000000000 rcx=00007ff676f399b0
rdx=0000000000000000 rsi=00000023d3e3c190 rdi=00007ff676f211e0
rip=00007ff676f2120d rsp=00000023d432fc30 rbp=0000000000000000
 r8=00006f6d5c4f5ead  r9=0000000000000032 r10=0000000000000032
r11=00000023d432f960 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
Application+0x120d:
00007ff6`76f2120d c70000000000    mov     dword ptr [rax],0 ds:00000000`00000000=????????</description>
		<content:encoded><![CDATA[<p>On Windows 10 RSP below KiUserExceptionDispatch can be used as an address for .cxr command:</p>
<p align="left">[&#8230;]<br />
00000023`d432f4e8  00000023`d3e3c190<br />
00000023`d432f4f0  00000000`00000000<br />
00000023`d432f4f8  00007ffa`e5c5577a ntdll!KiUserExceptionDispatch+0&#215;3a<br />
<strong>00000023`d432f500</strong>  00000000`00000000<br />
00000023`d432f508  00000000`00000810<br />
[&#8230;]</p>
<p align="left">0:001> .cxr 00000023`d432f500<br />
rax=0000000000000000 rbx=0000000000000000 rcx=00007ff676f399b0<br />
rdx=0000000000000000 rsi=00000023d3e3c190 rdi=00007ff676f211e0<br />
rip=00007ff676f2120d rsp=00000023d432fc30 rbp=0000000000000000<br />
 r8=00006f6d5c4f5ead  r9=0000000000000032 r10=0000000000000032<br />
r11=00000023d432f960 r12=0000000000000000 r13=0000000000000000<br />
r14=0000000000000000 r15=0000000000000000<br />
iopl=0         nv up ei pl nz na po nc<br />
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206<br />
Application+0&#215;120d:<br />
00007ff6`76f2120d c70000000000    mov     dword ptr [rax],0 ds:00000000`00000000=????????</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dmitry Vostokov</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/02/02/crash-dump-analysis-patterns-part-8/#comment-741672</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Fri, 15 May 2015 15:16:24 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/02/02/crash-dump-analysis-patterns-part-8/#comment-741672</guid>
		<description>Sometimes we can spot 0001003f and its address can be the beginning of a context record:

[...]
0070f668 00000000
0070f66c 00000000
0070f670 00000000
0070f674 00000000
0070f678 00000000
0070f67c 0001003f
[...]</description>
		<content:encoded><![CDATA[<p>Sometimes we can spot 0001003f and its address can be the beginning of a context record:</p>
<p>[&#8230;]<br />
0070f668 00000000<br />
0070f66c 00000000<br />
0070f670 00000000<br />
0070f674 00000000<br />
0070f678 00000000<br />
0070f67c 0001003f<br />
[&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Coupled processes, wait chains, message box, waiting thread time, paged out data, incorrect stack trace, hidden exception, unknown component and execution residue: pattern cooperation</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/02/02/crash-dump-analysis-patterns-part-8/#comment-175796</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Coupled processes, wait chains, message box, waiting thread time, paged out data, incorrect stack trace, hidden exception, unknown component and execution residue: pattern cooperation</dc:creator>
		<pubDate>Fri, 13 Aug 2010 19:09:24 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/02/02/crash-dump-analysis-patterns-part-8/#comment-175796</guid>
		<description>[...] We also see that stack trace is incorrect and we try to reconstruct the point of exception by looking at thread raw stack and searching for any hidden exception:  [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] We also see that stack trace is incorrect and we try to reconstruct the point of exception by looking at thread raw stack and searching for any hidden exception:  [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 105)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/02/02/crash-dump-analysis-patterns-part-8/#comment-173583</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 105)</dc:creator>
		<pubDate>Thu, 05 Aug 2010 20:07:43 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/02/02/crash-dump-analysis-patterns-part-8/#comment-173583</guid>
		<description>[...] see any exception thread it doesn&#8217;t mean that no exception had occurred. There could be hidden exceptions on raw stack [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] see any exception thread it doesn&#8217;t mean that no exception had occurred. There could be hidden exceptions on raw stack [&#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/02/02/crash-dump-analysis-patterns-part-8/#comment-147474</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 20:00:29 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/02/02/crash-dump-analysis-patterns-part-8/#comment-147474</guid>
		<description>[...] was an exception indeed diagnosed by FilterException call. The exception is probably hidden somewhere on the raw [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] was an exception indeed diagnosed by FilterException call. The exception is probably hidden somewhere on the raw [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Icons for Memory Dump Analysis Patterns (Part 12)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/02/02/crash-dump-analysis-patterns-part-8/#comment-137901</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Icons for Memory Dump Analysis Patterns (Part 12)</dc:creator>
		<pubDate>Thu, 25 Mar 2010 15:55:17 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/02/02/crash-dump-analysis-patterns-part-8/#comment-137901</guid>
		<description>[...] we introduce an icon for Hidden Exception [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] we introduce an icon for Hidden Exception [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Statement current, coupled processes, wait chain, spiking thread, hidden exception, and not my version: memory dump and trace analysis pattern cooperation</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/02/02/crash-dump-analysis-patterns-part-8/#comment-98725</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Statement current, coupled processes, wait chain, spiking thread, hidden exception, and not my version: memory dump and trace analysis pattern cooperation</dc:creator>
		<pubDate>Mon, 12 Oct 2009 19:11:37 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/02/02/crash-dump-analysis-patterns-part-8/#comment-98725</guid>
		<description>[...] Looking at the raw stack data (using !teb and dds WinDbg commands) we see a hidden processed exception: [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Looking at the raw stack data (using !teb and dds WinDbg commands) we see a hidden processed exception: [&#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/02/02/crash-dump-analysis-patterns-part-8/#comment-84353</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 16:59:16 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/02/02/crash-dump-analysis-patterns-part-8/#comment-84353</guid>
		<description>[...] addresses we used to try for .exr and .cxr commands in hidden exception pattern are beyond user space and we therefore conclude that somehow such structures or pointers [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] addresses we used to try for .exr and .cxr commands in hidden exception pattern are beyond user space and we therefore conclude that somehow such structures or pointers [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Manual dump, virtualized process, stack trace collection, multiple exceptions, optimized code, wild code pointer, incorrect stack trace and hidden exception: pattern cooperation</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/02/02/crash-dump-analysis-patterns-part-8/#comment-77721</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Manual dump, virtualized process, stack trace collection, multiple exceptions, optimized code, wild code pointer, incorrect stack trace and hidden exception: pattern cooperation</dc:creator>
		<pubDate>Thu, 04 Jun 2009 09:34:51 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/02/02/crash-dump-analysis-patterns-part-8/#comment-77721</guid>
		<description>[...] or the case of incorrect stack trace. However using techniques to get exception context from hidden exceptions we get the following stack [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] or the case of incorrect stack trace. However using techniques to get exception context from hidden exceptions we get the following stack [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: !analyze -v : Crash Dump Analysis Patterns (Part 8)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/02/02/crash-dump-analysis-patterns-part-8/#comment-43171</link>
		<dc:creator>!analyze -v : Crash Dump Analysis Patterns (Part 8)</dc:creator>
		<pubDate>Thu, 18 Sep 2008 05:24:41 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/02/02/crash-dump-analysis-patterns-part-8/#comment-43171</guid>
		<description>[...] 원문 http://www.dumpanalysis.org/blog/index.php/2007/02/02/crash-dump-analysis-patterns-part-8/ [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] 원문 <a href="http://www.dumpanalysis.org/blog/index.php/2007/02/02/crash-dump-analysis-patterns-part-8/" rel="nofollow">http://www.dumpanalysis.org/blog/index.php/2007/02/02/crash-dump-analysis-patterns-part-8/</a> [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
