<?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 74)</title>
	<link>https://www.dumpanalysis.org/blog/index.php/2008/08/05/crash-dump-analysis-patterns-part-74/</link>
	<description>Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics</description>
	<pubDate>Tue, 19 May 2026 09:58:24 +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/2008/08/05/crash-dump-analysis-patterns-part-74/#comment-741665</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Sat, 21 Mar 2015 19:51:27 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/08/05/crash-dump-analysis-patterns-part-74/#comment-741665</guid>
		<description>In case of Virtualized Processes !gle may show Win32 last error and status values incorrectly:

0:000:x86&gt; !gle
LastErrorValue: (Win32) 0 (0) - The operation completed successfully.
LastStatusValue: (NTSTATUS) 0 - STATUS_WAIT_0
Wow64 TEB status:
LastErrorValue: (Win32) 0 (0) - The operation completed successfully.
LastStatusValue: (NTSTATUS) 0 - STATUS_WAIT_0

0:000:x86&gt; !teb
Wow64 TEB32 at 00000000fffde000
    ExceptionList:        00000000002fb108
    StackBase:            0000000000390000
    StackLimit:           0000000000255000
    SubSystemTib:         0000000000000000
    FiberData:            0000000000001e00
    ArbitraryUserPointer: 0000000000000000
    Self:                 00000000fffde000
    EnvironmentPointer:   0000000000000000
    ClientId:             00000000000016d8 . 00000000000011e0
    RpcHandle:            0000000000000000
    Tls Storage:          0000000000e12978
    PEB Address:          00000000fffdf000
    LastErrorValue:       38
    LastStatusValue:      c0000011
    Count Owned Locks:    0
    HardErrorMode:        0


Wow64 TEB at 00000000fffdc000
    ExceptionList:        00000000fffde000
    StackBase:            000000000008fd30
    StackLimit:           0000000000083000
    SubSystemTib:         0000000000000000
    FiberData:            0000000000001e00
    ArbitraryUserPointer: 0000000000000000
    Self:                 00000000fffdc000
    EnvironmentPointer:   0000000000000000
    ClientId:             00000000000016d8 . 00000000000011e0
    RpcHandle:            0000000000000000
    Tls Storage:          0000000000000000
    PEB Address:          00000000fffd6000
    LastErrorValue:       0
    LastStatusValue:      0
    Count Owned Locks:    0
    HardErrorMode:        0</description>
		<content:encoded><![CDATA[<p>In case of Virtualized Processes !gle may show Win32 last error and status values incorrectly:</p>
<p>0:000:x86> !gle<br />
LastErrorValue: (Win32) 0 (0) - The operation completed successfully.<br />
LastStatusValue: (NTSTATUS) 0 - STATUS_WAIT_0<br />
Wow64 TEB status:<br />
LastErrorValue: (Win32) 0 (0) - The operation completed successfully.<br />
LastStatusValue: (NTSTATUS) 0 - STATUS_WAIT_0</p>
<p>0:000:x86> !teb<br />
Wow64 TEB32 at 00000000fffde000<br />
    ExceptionList:        00000000002fb108<br />
    StackBase:            0000000000390000<br />
    StackLimit:           0000000000255000<br />
    SubSystemTib:         0000000000000000<br />
    FiberData:            0000000000001e00<br />
    ArbitraryUserPointer: 0000000000000000<br />
    Self:                 00000000fffde000<br />
    EnvironmentPointer:   0000000000000000<br />
    ClientId:             00000000000016d8 . 00000000000011e0<br />
    RpcHandle:            0000000000000000<br />
    Tls Storage:          0000000000e12978<br />
    PEB Address:          00000000fffdf000<br />
    LastErrorValue:       38<br />
    LastStatusValue:      c0000011<br />
    Count Owned Locks:    0<br />
    HardErrorMode:        0</p>
<p>Wow64 TEB at 00000000fffdc000<br />
    ExceptionList:        00000000fffde000<br />
    StackBase:            000000000008fd30<br />
    StackLimit:           0000000000083000<br />
    SubSystemTib:         0000000000000000<br />
    FiberData:            0000000000001e00<br />
    ArbitraryUserPointer: 0000000000000000<br />
    Self:                 00000000fffdc000<br />
    EnvironmentPointer:   0000000000000000<br />
    ClientId:             00000000000016d8 . 00000000000011e0<br />
    RpcHandle:            0000000000000000<br />
    Tls Storage:          0000000000000000<br />
    PEB Address:          00000000fffd6000<br />
    LastErrorValue:       0<br />
    LastStatusValue:      0<br />
    Count Owned Locks:    0<br />
    HardErrorMode:        0</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Heap and early crash dump: pattern cooperation</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/08/05/crash-dump-analysis-patterns-part-74/#comment-40730</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Heap and early crash dump: pattern cooperation</dc:creator>
		<pubDate>Tue, 02 Sep 2008 16:15:17 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/08/05/crash-dump-analysis-patterns-part-74/#comment-40730</guid>
		<description>[...] one of last error values was access violation (Last Error Collection [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] one of last error values was access violation (Last Error Collection [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
