<?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 for Software Diagnostics Library</title>
	<link>https://www.dumpanalysis.org/blog</link>
	<description>Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics</description>
	<pubDate>Tue, 05 May 2026 10:13:37 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>Comment on Crash Dump Analysis Patterns (Part 291) by Dmitry Vostokov</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2024/03/14/crash-dump-analysis-patterns-part-291/#comment-767753</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Sat, 11 Apr 2026 09:46:22 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2024/03/14/crash-dump-analysis-patterns-part-291/#comment-767753</guid>
		<description>Categorize this stack trace: …
Split this stack trace into appropriate categories: …</description>
		<content:encoded><![CDATA[<p>Categorize this stack trace: …<br />
Split this stack trace into appropriate categories: …</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Crash Dump Analysis Patterns (Part 293) by Dmitry Vostokov</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2024/03/18/crash-dump-analysis-patterns-part-293/#comment-767752</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Sat, 11 Apr 2026 09:15:52 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2024/03/18/crash-dump-analysis-patterns-part-293/#comment-767752</guid>
		<description>Explain all symbolic references.</description>
		<content:encoded><![CDATA[<p>Explain all symbolic references.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Crash Dump Analysis Patterns (Part 291) by Dmitry Vostokov</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2024/03/14/crash-dump-analysis-patterns-part-291/#comment-767751</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Sat, 11 Apr 2026 08:43:45 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2024/03/14/crash-dump-analysis-patterns-part-291/#comment-767751</guid>
		<description>Annotate 10/10</description>
		<content:encoded><![CDATA[<p>Annotate 10/10</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Crash Dump Analysis Patterns (Part 291) by Dmitry Vostokov</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2024/03/14/crash-dump-analysis-patterns-part-291/#comment-767750</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Sat, 11 Apr 2026 08:40:11 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2024/03/14/crash-dump-analysis-patterns-part-291/#comment-767750</guid>
		<description>Brutally assess the annotation and score it.</description>
		<content:encoded><![CDATA[<p>Brutally assess the annotation and score it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Crash Dump Analysis Patterns (Part 291) by Dmitry Vostokov</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2024/03/14/crash-dump-analysis-patterns-part-291/#comment-767749</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Sat, 11 Apr 2026 08:38:59 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2024/03/14/crash-dump-analysis-patterns-part-291/#comment-767749</guid>
		<description>Write the best prompt to annotate stack traces. ...</description>
		<content:encoded><![CDATA[<p>Write the best prompt to annotate stack traces. &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Crash Dump Analysis Patterns (Part 41a) by Dmitry Vostokov</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/12/12/crash-dump-analysis-patterns-part-41a/#comment-767748</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Sat, 31 Jan 2026 10:46:39 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/12/12/crash-dump-analysis-patterns-part-41a/#comment-767748</guid>
		<description>The stack trace from USB-keyboard generated dump on Windows 11 ARM64

MANUALLY_INITIATED_CRASH (e2)
The user manually initiated this crash dump.
Arguments:
Arg1: 0000000000000000
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

0: kd&gt; kc
 # Call Site
00 nt!KeBugCheck2
01 nt!KeBugCheckEx
02 kbdhid!KbdHidProcessCrashDump
03 kbdhid!KbdHid_InsertCodesIntoQueue
04 HIDPARSE!HidP_ModifierCode
05 HIDPARSE!HidP_TranslateUsageAndPagesToI8042ScanCodes
06 kbdhid!KbdHid_ReadComplete
07 nt!IopUnloadSafeCompletion
08 nt!IopfCompleteRequest
09 HIDCLASS!HidpDistributeInterruptReport
0a HIDCLASS!HidpInterruptReadComplete
0b nt!IopfCompleteRequest
0c Wdf01000!FxIrp::CompleteRequest
0d Wdf01000!FxRequest::CompleteInternal
0e Wdf01000!FxRequest::Complete
0f Wdf01000!imp_WdfRequestComplete
10 USBXHCI!Bulk_ProcessTransferEventWithED1
11 USBXHCI!Bulk_EP_TransferEventHandler
12 USBXHCI!Endpoint_TransferEventHandler
13 USBXHCI!Interrupter_DeferredWorkProcessor
14 Wdf01000!FxInterrupt::DpcHandler
15 Wdf01000!FxInterrupt::_InterruptDpcThunk
16 nt!KiExecuteAllDpcs
17 nt!KiRetireDpcList
18 nt!KxPlatformSwapStacksAndCall
19 nt!KiPlatformSwapStacksAndCallReturn
1a nt!KiDispatchInterrupt
1b nt!HalpInterruptCheckForSoftwareInterrupt
1c nt!KiInterruptException
1d nt!KiUserInterruptHandler
1e ntdll!RtlpHpTagFreeHeap
1f ntdll!RtlFreeHeap
20 msvcrt!free
21 diagperf!XPerfCore::CPathNode::`scalar deleting destructor'
22 diagperf!XPerfCore::CPathNode::Insert
23 diagperf!XPerfCore::CPathNode::Insert
24 diagperf!XPerfCore::CPathNode::Insert
25 diagperf!XPerfCore::CPathNode::Insert
26 diagperf!XPerfAddIn::CProcessInfoSource::ImageEvent
27 diagperf!XPerfAddIn::CProcessInfoSource::OnEvent
28 diagperf!XPerfCore::CSession::OnEventRecord
29 diagperf!XPerfCore::CSession::EventRecordCallback
2a diagperf!XPerfCore::CEtwTrace::EventRecordCallback
2b sechost!EtwpProcessTraceLog
2c sechost!ProcessTrace
2d diagperf!XPerfCore::CEtwTraceGroup::ProcessEvents
2e diagperf!XPerfCore::CSession::ProcessEvents
2f diagperf!PerfDiagBoot::CTraceContext::Open
30 diagperf!BootScenario::PerformTroubleshooting
31 diagperf!BootScenario::TroubleShoot
32 diagperf!PerfDiagDm::CDmManager::HandleInstance
33 diagperf!WdiHandleInstance
34 wdi!WdipHandleInstance
35 wdi!WdipProcessDiagnosticMessage
36 wdi!WdipProcessSessionMessage
37 wdi!WdipSessionListener
38 ntdll!TppAlpcpExecuteCallback
39 ntdll!TppWorkerThread
3a KERNEL32!BaseThreadInitThunk
3b ntdll!RtlUserThreadStart</description>
		<content:encoded><![CDATA[<p>The stack trace from USB-keyboard generated dump on Windows 11 ARM64</p>
<p>MANUALLY_INITIATED_CRASH (e2)<br />
The user manually initiated this crash dump.<br />
Arguments:<br />
Arg1: 0000000000000000<br />
Arg2: 0000000000000000<br />
Arg3: 0000000000000000<br />
Arg4: 0000000000000000</p>
<p>0: kd> kc<br />
 # Call Site<br />
00 nt!KeBugCheck2<br />
01 nt!KeBugCheckEx<br />
02 kbdhid!KbdHidProcessCrashDump<br />
03 kbdhid!KbdHid_InsertCodesIntoQueue<br />
04 HIDPARSE!HidP_ModifierCode<br />
05 HIDPARSE!HidP_TranslateUsageAndPagesToI8042ScanCodes<br />
06 kbdhid!KbdHid_ReadComplete<br />
07 nt!IopUnloadSafeCompletion<br />
08 nt!IopfCompleteRequest<br />
09 HIDCLASS!HidpDistributeInterruptReport<br />
0a HIDCLASS!HidpInterruptReadComplete<br />
0b nt!IopfCompleteRequest<br />
0c Wdf01000!FxIrp::CompleteRequest<br />
0d Wdf01000!FxRequest::CompleteInternal<br />
0e Wdf01000!FxRequest::Complete<br />
0f Wdf01000!imp_WdfRequestComplete<br />
10 USBXHCI!Bulk_ProcessTransferEventWithED1<br />
11 USBXHCI!Bulk_EP_TransferEventHandler<br />
12 USBXHCI!Endpoint_TransferEventHandler<br />
13 USBXHCI!Interrupter_DeferredWorkProcessor<br />
14 Wdf01000!FxInterrupt::DpcHandler<br />
15 Wdf01000!FxInterrupt::_InterruptDpcThunk<br />
16 nt!KiExecuteAllDpcs<br />
17 nt!KiRetireDpcList<br />
18 nt!KxPlatformSwapStacksAndCall<br />
19 nt!KiPlatformSwapStacksAndCallReturn<br />
1a nt!KiDispatchInterrupt<br />
1b nt!HalpInterruptCheckForSoftwareInterrupt<br />
1c nt!KiInterruptException<br />
1d nt!KiUserInterruptHandler<br />
1e ntdll!RtlpHpTagFreeHeap<br />
1f ntdll!RtlFreeHeap<br />
20 msvcrt!free<br />
21 diagperf!XPerfCore::CPathNode::`scalar deleting destructor&#8217;<br />
22 diagperf!XPerfCore::CPathNode::Insert<br />
23 diagperf!XPerfCore::CPathNode::Insert<br />
24 diagperf!XPerfCore::CPathNode::Insert<br />
25 diagperf!XPerfCore::CPathNode::Insert<br />
26 diagperf!XPerfAddIn::CProcessInfoSource::ImageEvent<br />
27 diagperf!XPerfAddIn::CProcessInfoSource::OnEvent<br />
28 diagperf!XPerfCore::CSession::OnEventRecord<br />
29 diagperf!XPerfCore::CSession::EventRecordCallback<br />
2a diagperf!XPerfCore::CEtwTrace::EventRecordCallback<br />
2b sechost!EtwpProcessTraceLog<br />
2c sechost!ProcessTrace<br />
2d diagperf!XPerfCore::CEtwTraceGroup::ProcessEvents<br />
2e diagperf!XPerfCore::CSession::ProcessEvents<br />
2f diagperf!PerfDiagBoot::CTraceContext::Open<br />
30 diagperf!BootScenario::PerformTroubleshooting<br />
31 diagperf!BootScenario::TroubleShoot<br />
32 diagperf!PerfDiagDm::CDmManager::HandleInstance<br />
33 diagperf!WdiHandleInstance<br />
34 wdi!WdipHandleInstance<br />
35 wdi!WdipProcessDiagnosticMessage<br />
36 wdi!WdipProcessSessionMessage<br />
37 wdi!WdipSessionListener<br />
38 ntdll!TppAlpcpExecuteCallback<br />
39 ntdll!TppWorkerThread<br />
3a KERNEL32!BaseThreadInitThunk<br />
3b ntdll!RtlUserThreadStart</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Crash Dump Analysis Patterns (Part 305) by Dmitry Vostokov</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2026/01/09/crash-dump-analysis-patterns-part-305/#comment-767747</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Sat, 10 Jan 2026 17:17:38 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2026/01/09/crash-dump-analysis-patterns-part-305/#comment-767747</guid>
		<description>If you open an ARM64 dump of a 32-bit process, use .effmach CHPE and .effmach ARM64 to switch between both modes.</description>
		<content:encoded><![CDATA[<p>If you open an ARM64 dump of a 32-bit process, use .effmach CHPE and .effmach ARM64 to switch between both modes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Crash Dump Analysis Patterns (Part 155) by Dmitry Vostokov</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2011/11/10/crash-dump-analysis-patterns-part-155/#comment-767746</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Sat, 10 Jan 2026 11:36:02 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2011/11/10/crash-dump-analysis-patterns-part-155/#comment-767746</guid>
		<description>These can surface in kv args output</description>
		<content:encoded><![CDATA[<p>These can surface in kv args output</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Crash Dump Analysis Patterns (Part 56) by Dmitry Vostokov</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/03/27/crash-dump-analysis-patterns-part-56/#comment-767745</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Tue, 23 Dec 2025 22:07:46 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/03/27/crash-dump-analysis-patterns-part-56/#comment-767745</guid>
		<description>Wild Code memory dump analysis pattern example:

0:000&gt; db @$scopeip L10
04fd0002  48 61 70 70 79 20 48 6f-6c 69 64 61 79 73 21 00  Happy Holidays!.

0:000&gt; u @$scopeip
04fd0002 48              dec     eax
04fd0003 61              popad
04fd0004 7070            jo      04fd0076
04fd0006 7920            jns     04fd0028
04fd0008 48              dec     eax
04fd0009 6f              outs    dx,dword ptr [esi]
04fd000a 6c              ins     byte ptr es:[edi],dx
04fd000b 6964617973210000 imul    esp,dword ptr [ecx+79h],2173h</description>
		<content:encoded><![CDATA[<p>Wild Code memory dump analysis pattern example:</p>
<p>0:000> db @$scopeip L10<br />
04fd0002  48 61 70 70 79 20 48 6f-6c 69 64 61 79 73 21 00  Happy Holidays!.</p>
<p>0:000> u @$scopeip<br />
04fd0002 48              dec     eax<br />
04fd0003 61              popad<br />
04fd0004 7070            jo      04fd0076<br />
04fd0006 7920            jns     04fd0028<br />
04fd0008 48              dec     eax<br />
04fd0009 6f              outs    dx,dword ptr [esi]<br />
04fd000a 6c              ins     byte ptr es:[edi],dx<br />
04fd000b 6964617973210000 imul    esp,dword ptr [ecx+79h],2173h</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Crash Dump Analysis Patterns (Part 160) by Dmitry Vostokov</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2011/12/11/crash-dump-analysis-patterns-part-160/#comment-767744</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Sat, 15 Nov 2025 19:23:51 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2011/12/11/crash-dump-analysis-patterns-part-160/#comment-767744</guid>
		<description>Another example from Windows ARM64: aligned local variable:

_Alignas(4096) long long ll = 1;

0:000&gt; dv /V
00000037`30b8e690 @x27+0x1000                    ll = 0n-3689348814741910324
00000037`30b8d8c0 @x27+0x0230                 align = 8

They are stored indirectly instead:

00007ff6`e7afafdc f9533f69 ldr         x9,[x27,#0x2678]
00007ff6`e7afafe0 d2800028 mov         x8,#1
00007ff6`e7afafe4 f9000128 str         x8,[x9]

0:000&gt; ? @x27+0x2678
Evaluate expression: 237040631048 = 00000037`30b8fd08
0:000&gt; dp 00000037`30b8fd08 L1
00000037`30b8fd08  00000037`30b8d000
0:000&gt; dpp 00000037`30b8fd08 L1
00000037`30b8fd08  00000037`30b8d000 00000000`00000001</description>
		<content:encoded><![CDATA[<p>Another example from Windows ARM64: aligned local variable:</p>
<p>_Alignas(4096) long long ll = 1;</p>
<p>0:000> dv /V<br />
00000037`30b8e690 @x27+0&#215;1000                    ll = 0n-3689348814741910324<br />
00000037`30b8d8c0 @x27+0&#215;0230                 align = 8</p>
<p>They are stored indirectly instead:</p>
<p>00007ff6`e7afafdc f9533f69 ldr         x9,[x27,#0&#215;2678]<br />
00007ff6`e7afafe0 d2800028 mov         x8,#1<br />
00007ff6`e7afafe4 f9000128 str         x8,[x9]</p>
<p>0:000> ? @x27+0&#215;2678<br />
Evaluate expression: 237040631048 = 00000037`30b8fd08<br />
0:000> dp 00000037`30b8fd08 L1<br />
00000037`30b8fd08  00000037`30b8d000<br />
0:000> dpp 00000037`30b8fd08 L1<br />
00000037`30b8fd08  00000037`30b8d000 00000000`00000001</p>
]]></content:encoded>
	</item>
</channel>
</rss>
