<?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 9e)</title>
	<link>https://www.dumpanalysis.org/blog/index.php/2008/10/25/crash-dump-analysis-patterns-part-9e/</link>
	<description>Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics</description>
	<pubDate>Tue, 05 May 2026 11:14:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Icons for Memory Dump Analysis Patterns (Part 17)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/10/25/crash-dump-analysis-patterns-part-9e/#comment-140052</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Icons for Memory Dump Analysis Patterns (Part 17)</dc:creator>
		<pubDate>Thu, 01 Apr 2010 15:48:03 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/10/25/crash-dump-analysis-patterns-part-9e/#comment-140052</guid>
		<description>[...] we introduce an icon for Deadlock (mixed objects, kernel space) [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] we introduce an icon for Deadlock (mixed objects, kernel space) [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jaypee</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/10/25/crash-dump-analysis-patterns-part-9e/#comment-71406</link>
		<dc:creator>Jaypee</dc:creator>
		<pubDate>Thu, 16 Apr 2009 03:47:49 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/10/25/crash-dump-analysis-patterns-part-9e/#comment-71406</guid>
		<description>0:000&#62; !uniqstack
Processing 4 threads, please wait

.  0  Id: 24e4.24c4 Suspend: 1 Teb: 7ffdf000 Unfrozen
      Start: MyApp+0x6640 (00406640) 
      Priority: 0  Priority class: 32  Affinity: ff
ChildEBP RetAddr  
0012c984 7c827cfb ntdll!KiFastSystemCallRet
0012c988 77e6202c ntdll!NtWaitForMultipleObjects+0xc
0012ca30 7739bbd1 kernel32!WaitForMultipleObjectsEx+0x11a
0012ca8c 776c1ffa user32!RealMsgWaitForMultipleObjectsEx+0x141
0012cab4 776c1d74 ole32!CCliModalLoop::BlockFn+0x7d
0012cadc 7778d3aa ole32!ModalLoop+0x5b
0012caf8 7778c4c5 ole32!ThreadSendReceive+0xe3
0012cb14 7778c38b ole32!CRpcChannelBuffer::SwitchAptAndDispatchCall+0x112
0012cbf4 776c1f9b ole32!CRpcChannelBuffer::SendReceive2+0xd3
0012cc10 776c1f44 ole32!CCliModalLoop::SendReceive+0x1e
0012cc7c 776c04fa ole32!CAptRpcChnl::SendReceive+0x6f
0012ccd0 77ce247f ole32!CCtxComChnl::SendReceive+0x1a9
0012ccec 77ce252f rpcrt4!NdrProxySendReceive+0x43
0012d0d4 77d2b37f rpcrt4!NdrClientCall2+0x206
0012d0ec 77d2b349 oleaut32!IDispatch_RemoteInvoke_Proxy+0x1c
0012d3ac 00567062 oleaut32!IDispatch_Invoke_Proxy+0xb6
0012d448 005670f8 MFC71u!COleDispatchDriver::InvokeHelperV+0x248 [f:\vs70builds\3077\vc\mfcatl\ship\atlmfc\src\mfc\oledisp2.cpp @ 375]
0012d468 27e0dd67 MFC71u!COleDispatchDriver::InvokeHelper+0x1e [f:\vs70builds\3077\vc\mfcatl\ship\atlmfc\src\mfc\oledisp2.cpp @ 529]


.  1  Id: 24e4.12c Suspend: 1 Teb: 7ffdd000 Unfrozen
      Start: 022f7a3b
      Priority: 0  Priority class: 32  Affinity: ff
ChildEBP RetAddr  
022afe18 7c82783b ntdll!KiFastSystemCallRet
022afe1c 77c885ac ntdll!NtReplyWaitReceivePortEx+0xc
022aff84 77c88792 rpcrt4!LRPC_ADDRESS::ReceiveLotsaCalls+0x198
022aff8c 77c8872d rpcrt4!RecvLotsaCallsWrapper+0xd
022affac 77c7b110 rpcrt4!BaseCachedThreadRoutine+0x9d
022affb8 77e64829 rpcrt4!ThreadStartRoutine+0x1b
022affec 00000000 kernel32!BaseThreadStart+0x34

.  2  Id: 24e4.15c Suspend: 1 Teb: 7ffdb000 Unfrozen
      Start: pscmn!CEventThreadMech::CauseEvent+0x30 (24d161d0) 
      Priority: 0  Priority class: 32  Affinity: ff
ChildEBP RetAddr  
024dfec4 7c827cfb ntdll!KiFastSystemCallRet
024dfec8 77e6202c ntdll!NtWaitForMultipleObjects+0xc
024dff70 77e62fbe kernel32!WaitForMultipleObjectsEx+0x11a
024dff8c 24d16202 kernel32!WaitForMultipleObjects+0x18
WARNING: Stack unwind information not available. Following frames may be wrong.
024dffb8 77e64829 pscmn!CEventThreadMech::CauseEvent+0x62
024dffec 00000000 kernel32!BaseThreadStart+0x34

Total threads: 4</description>
		<content:encoded><![CDATA[<p>0:000&gt; !uniqstack<br />
Processing 4 threads, please wait</p>
<p>.  0  Id: 24e4.24c4 Suspend: 1 Teb: 7ffdf000 Unfrozen<br />
      Start: MyApp+0&#215;6640 (00406640)<br />
      Priority: 0  Priority class: 32  Affinity: ff<br />
ChildEBP RetAddr<br />
0012c984 7c827cfb ntdll!KiFastSystemCallRet<br />
0012c988 77e6202c ntdll!NtWaitForMultipleObjects+0xc<br />
0012ca30 7739bbd1 kernel32!WaitForMultipleObjectsEx+0&#215;11a<br />
0012ca8c 776c1ffa user32!RealMsgWaitForMultipleObjectsEx+0&#215;141<br />
0012cab4 776c1d74 ole32!CCliModalLoop::BlockFn+0&#215;7d<br />
0012cadc 7778d3aa ole32!ModalLoop+0&#215;5b<br />
0012caf8 7778c4c5 ole32!ThreadSendReceive+0xe3<br />
0012cb14 7778c38b ole32!CRpcChannelBuffer::SwitchAptAndDispatchCall+0&#215;112<br />
0012cbf4 776c1f9b ole32!CRpcChannelBuffer::SendReceive2+0xd3<br />
0012cc10 776c1f44 ole32!CCliModalLoop::SendReceive+0&#215;1e<br />
0012cc7c 776c04fa ole32!CAptRpcChnl::SendReceive+0&#215;6f<br />
0012ccd0 77ce247f ole32!CCtxComChnl::SendReceive+0&#215;1a9<br />
0012ccec 77ce252f rpcrt4!NdrProxySendReceive+0&#215;43<br />
0012d0d4 77d2b37f rpcrt4!NdrClientCall2+0&#215;206<br />
0012d0ec 77d2b349 oleaut32!IDispatch_RemoteInvoke_Proxy+0&#215;1c<br />
0012d3ac 00567062 oleaut32!IDispatch_Invoke_Proxy+0xb6<br />
0012d448 005670f8 MFC71u!COleDispatchDriver::InvokeHelperV+0&#215;248 [f:\vs70builds\3077\vc\mfcatl\ship\atlmfc\src\mfc\oledisp2.cpp @ 375]<br />
0012d468 27e0dd67 MFC71u!COleDispatchDriver::InvokeHelper+0&#215;1e [f:\vs70builds\3077\vc\mfcatl\ship\atlmfc\src\mfc\oledisp2.cpp @ 529]</p>
<p>.  1  Id: 24e4.12c Suspend: 1 Teb: 7ffdd000 Unfrozen<br />
      Start: 022f7a3b<br />
      Priority: 0  Priority class: 32  Affinity: ff<br />
ChildEBP RetAddr<br />
022afe18 7c82783b ntdll!KiFastSystemCallRet<br />
022afe1c 77c885ac ntdll!NtReplyWaitReceivePortEx+0xc<br />
022aff84 77c88792 rpcrt4!LRPC_ADDRESS::ReceiveLotsaCalls+0&#215;198<br />
022aff8c 77c8872d rpcrt4!RecvLotsaCallsWrapper+0xd<br />
022affac 77c7b110 rpcrt4!BaseCachedThreadRoutine+0&#215;9d<br />
022affb8 77e64829 rpcrt4!ThreadStartRoutine+0&#215;1b<br />
022affec 00000000 kernel32!BaseThreadStart+0&#215;34</p>
<p>.  2  Id: 24e4.15c Suspend: 1 Teb: 7ffdb000 Unfrozen<br />
      Start: pscmn!CEventThreadMech::CauseEvent+0&#215;30 (24d161d0)<br />
      Priority: 0  Priority class: 32  Affinity: ff<br />
ChildEBP RetAddr<br />
024dfec4 7c827cfb ntdll!KiFastSystemCallRet<br />
024dfec8 77e6202c ntdll!NtWaitForMultipleObjects+0xc<br />
024dff70 77e62fbe kernel32!WaitForMultipleObjectsEx+0&#215;11a<br />
024dff8c 24d16202 kernel32!WaitForMultipleObjects+0&#215;18<br />
WARNING: Stack unwind information not available. Following frames may be wrong.<br />
024dffb8 77e64829 pscmn!CEventThreadMech::CauseEvent+0&#215;62<br />
024dffec 00000000 kernel32!BaseThreadStart+0&#215;34</p>
<p>Total threads: 4</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jaypee</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/10/25/crash-dump-analysis-patterns-part-9e/#comment-71405</link>
		<dc:creator>Jaypee</dc:creator>
		<pubDate>Thu, 16 Apr 2009 03:44:27 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/10/25/crash-dump-analysis-patterns-part-9e/#comment-71405</guid>
		<description>Hi,

   Can you please suggest what is holding the application from execution about the following deadlock pattern? I could see the WaitForMultipleObjectsEx function being called which is making it to wait for an object. But I am not able to understand what type of object it is waiting for? How this deadlock can be resolved?
Thanks in advance 
Jaypee
0:000&#62; !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for psnxl.dll - 
*** WARNING: Unable to verify checksum for psnam.dll
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for psnam.dll - 
*** WARNING: Unable to verify checksum for psnvs.exe
*** ERROR: Module load completed but symbols could not be loaded for psnvs.exe
*** WARNING: Unable to verify checksum for pstls.dll
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for pstls.dll - 
*** WARNING: Unable to verify checksum for pscmn.dll
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for pscmn.dll - 
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: kernel32!pNlsUserInfo                         ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: kernel32!pNlsUserInfo                         ***
***                                                                   ***
*************************************************************************

FAULTING_IP: 
+0
00000000 ??              ???

EXCEPTION_RECORD:  ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 00000000
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 0

FAULTING_THREAD:  000024c4

DEFAULT_BUCKET_ID:  STATUS_BREAKPOINT

PROCESS_NAME:  MyApp.exe

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION}  Breakpoint  A breakpoint has been reached.

NTGLOBALFLAG:  0

APPLICATION_VERIFIER_FLAGS:  0

PRIMARY_PROBLEM_CLASS:  STATUS_BREAKPOINT

BUGCHECK_STR:  APPLICATION_FAULT_STATUS_BREAKPOINT

LAST_CONTROL_TRANSFER:  from 7c827cfb to 7c8285ec

STACK_TEXT:  
0012c984 7c827cfb 77e6202c 00000002 0012c9d4 ntdll!KiFastSystemCallRet
0012c988 77e6202c 00000002 0012c9d4 00000001 ntdll!NtWaitForMultipleObjects+0xc
0012ca30 7739bbd1 00000002 0012ca58 00000000 kernel32!WaitForMultipleObjectsEx+0x11a
0012ca8c 776c1ffa 00000001 0012cad4 000003e8 user32!RealMsgWaitForMultipleObjectsEx+0x141
0012cab4 776c1d74 0012cad4 000003e8 0012cae4 ole32!CCliModalLoop::BlockFn+0x7d
0012cadc 7778d3aa ffffffff 0012cbdc 0018d2bc ole32!ModalLoop+0x5b
0012caf8 7778c4c5 00000000 00000000 00000000 ole32!ThreadSendReceive+0xe3
0012cb14 7778c38b 0012cbdc 001a2b74 0012cc38 ole32!CRpcChannelBuffer::SwitchAptAndDispatchCall+0x112
0012cbf4 776c1f9b 001a2b74 0012cd08 0012ccf8 ole32!CRpcChannelBuffer::SendReceive2+0xd3
0012cc10 776c1f44 0012cd08 0012ccf8 001a2b74 ole32!CCliModalLoop::SendReceive+0x1e
0012cc7c 776c04fa 001a2b74 0012cd08 0012ccf8 ole32!CAptRpcChnl::SendReceive+0x6f
0012ccd0 77ce247f 001a2b74 0012cd08 0012ccf8 ole32!CCtxComChnl::SendReceive+0x1a9
0012ccec 77ce252f 001a2d9c 0012cd34 00000000 rpcrt4!NdrProxySendReceive+0x43
0012d0d4 77d2b37f 77d07aa8 77d0b772 0012d0f4 rpcrt4!NdrClientCall2+0x206
0012d0ec 77d2b349 001a2d9c 00000783 00569c4c oleaut32!IDispatch_RemoteInvoke_Proxy+0x1c
0012d3ac 00567062 001a2d9c 00000783 00569c4c oleaut32!IDispatch_Invoke_Proxy+0xb6
0012d448 005670f8 00000783 00000001 00000009 MFC71u!COleDispatchDriver::InvokeHelperV+0x248 [f:\vs70builds\3077\vc\mfcatl\ship\atlmfc\src\mfc\oledisp2.cpp @ 375]
0012d468 27e0dd67 0012d4b4 00000783 00000001 MFC71u!COleDispatchDriver::InvokeHelper+0x1e [f:\vs70builds\3077\vc\mfcatl\ship\atlmfc\src\mfc\oledisp2.cpp @ 529]

STACK_COMMAND:  ~0s; .ecxr ; kb

FOLLOWUP_IP: 
oleaut32!IDispatch_RemoteInvoke_Proxy+1c
77d2b37f 83c40c          add     esp,0Ch

SYMBOL_STACK_INDEX:  e

SYMBOL_NAME:  oleaut32!IDispatch_RemoteInvoke_Proxy+1c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: oleaut32

IMAGE_NAME:  oleaut32.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  467044ca

FAILURE_BUCKET_ID:  STATUS_BREAKPOINT_80000003_oleaut32.dll!IDispatch_RemoteInvoke_Proxy

BUCKET_ID:  APPLICATION_FAULT_STATUS_BREAKPOINT_oleaut32!IDispatch_RemoteInvoke_Proxy+1c

Followup: MachineOwner</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>   Can you please suggest what is holding the application from execution about the following deadlock pattern? I could see the WaitForMultipleObjectsEx function being called which is making it to wait for an object. But I am not able to understand what type of object it is waiting for? How this deadlock can be resolved?<br />
Thanks in advance<br />
Jaypee<br />
0:000&gt; !analyze -v<br />
*******************************************************************************<br />
*                                                                             *<br />
*                        Exception Analysis                                   *<br />
*                                                                             *<br />
*******************************************************************************</p>
<p>*** ERROR: Symbol file could not be found.  Defaulted to export symbols for psnxl.dll -<br />
*** WARNING: Unable to verify checksum for psnam.dll<br />
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for psnam.dll -<br />
*** WARNING: Unable to verify checksum for psnvs.exe<br />
*** ERROR: Module load completed but symbols could not be loaded for psnvs.exe<br />
*** WARNING: Unable to verify checksum for pstls.dll<br />
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for pstls.dll -<br />
*** WARNING: Unable to verify checksum for pscmn.dll<br />
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for pscmn.dll -<br />
*************************************************************************<br />
***                                                                   ***<br />
***                                                                   ***<br />
***    Your debugger is not using the correct symbols                 ***<br />
***                                                                   ***<br />
***    In order for this command to work properly, your symbol path   ***<br />
***    must point to .pdb files that have full type information.      ***<br />
***                                                                   ***<br />
***    Certain .pdb files (such as the public OS symbols) do not      ***<br />
***    contain the required information.  Contact the group that      ***<br />
***    provided you with these symbols if you need this command to    ***<br />
***    work.                                                          ***<br />
***                                                                   ***<br />
***    Type referenced: kernel32!pNlsUserInfo                         ***<br />
***                                                                   ***<br />
*************************************************************************<br />
*************************************************************************<br />
***                                                                   ***<br />
***                                                                   ***<br />
***    Your debugger is not using the correct symbols                 ***<br />
***                                                                   ***<br />
***    In order for this command to work properly, your symbol path   ***<br />
***    must point to .pdb files that have full type information.      ***<br />
***                                                                   ***<br />
***    Certain .pdb files (such as the public OS symbols) do not      ***<br />
***    contain the required information.  Contact the group that      ***<br />
***    provided you with these symbols if you need this command to    ***<br />
***    work.                                                          ***<br />
***                                                                   ***<br />
***    Type referenced: kernel32!pNlsUserInfo                         ***<br />
***                                                                   ***<br />
*************************************************************************</p>
<p>FAULTING_IP:<br />
+0<br />
00000000 ??              ???</p>
<p>EXCEPTION_RECORD:  ffffffff &#8212; (.exr 0xffffffffffffffff)<br />
ExceptionAddress: 00000000<br />
   ExceptionCode: 80000003 (Break instruction exception)<br />
  ExceptionFlags: 00000000<br />
NumberParameters: 0</p>
<p>FAULTING_THREAD:  000024c4</p>
<p>DEFAULT_BUCKET_ID:  STATUS_BREAKPOINT</p>
<p>PROCESS_NAME:  MyApp.exe</p>
<p>ERROR_CODE: (NTSTATUS) 0&#215;80000003 - {EXCEPTION}  Breakpoint  A breakpoint has been reached.</p>
<p>NTGLOBALFLAG:  0</p>
<p>APPLICATION_VERIFIER_FLAGS:  0</p>
<p>PRIMARY_PROBLEM_CLASS:  STATUS_BREAKPOINT</p>
<p>BUGCHECK_STR:  APPLICATION_FAULT_STATUS_BREAKPOINT</p>
<p>LAST_CONTROL_TRANSFER:  from 7c827cfb to 7c8285ec</p>
<p>STACK_TEXT:<br />
0012c984 7c827cfb 77e6202c 00000002 0012c9d4 ntdll!KiFastSystemCallRet<br />
0012c988 77e6202c 00000002 0012c9d4 00000001 ntdll!NtWaitForMultipleObjects+0xc<br />
0012ca30 7739bbd1 00000002 0012ca58 00000000 kernel32!WaitForMultipleObjectsEx+0&#215;11a<br />
0012ca8c 776c1ffa 00000001 0012cad4 000003e8 user32!RealMsgWaitForMultipleObjectsEx+0&#215;141<br />
0012cab4 776c1d74 0012cad4 000003e8 0012cae4 ole32!CCliModalLoop::BlockFn+0&#215;7d<br />
0012cadc 7778d3aa ffffffff 0012cbdc 0018d2bc ole32!ModalLoop+0&#215;5b<br />
0012caf8 7778c4c5 00000000 00000000 00000000 ole32!ThreadSendReceive+0xe3<br />
0012cb14 7778c38b 0012cbdc 001a2b74 0012cc38 ole32!CRpcChannelBuffer::SwitchAptAndDispatchCall+0&#215;112<br />
0012cbf4 776c1f9b 001a2b74 0012cd08 0012ccf8 ole32!CRpcChannelBuffer::SendReceive2+0xd3<br />
0012cc10 776c1f44 0012cd08 0012ccf8 001a2b74 ole32!CCliModalLoop::SendReceive+0&#215;1e<br />
0012cc7c 776c04fa 001a2b74 0012cd08 0012ccf8 ole32!CAptRpcChnl::SendReceive+0&#215;6f<br />
0012ccd0 77ce247f 001a2b74 0012cd08 0012ccf8 ole32!CCtxComChnl::SendReceive+0&#215;1a9<br />
0012ccec 77ce252f 001a2d9c 0012cd34 00000000 rpcrt4!NdrProxySendReceive+0&#215;43<br />
0012d0d4 77d2b37f 77d07aa8 77d0b772 0012d0f4 rpcrt4!NdrClientCall2+0&#215;206<br />
0012d0ec 77d2b349 001a2d9c 00000783 00569c4c oleaut32!IDispatch_RemoteInvoke_Proxy+0&#215;1c<br />
0012d3ac 00567062 001a2d9c 00000783 00569c4c oleaut32!IDispatch_Invoke_Proxy+0xb6<br />
0012d448 005670f8 00000783 00000001 00000009 MFC71u!COleDispatchDriver::InvokeHelperV+0&#215;248 [f:\vs70builds\3077\vc\mfcatl\ship\atlmfc\src\mfc\oledisp2.cpp @ 375]<br />
0012d468 27e0dd67 0012d4b4 00000783 00000001 MFC71u!COleDispatchDriver::InvokeHelper+0&#215;1e [f:\vs70builds\3077\vc\mfcatl\ship\atlmfc\src\mfc\oledisp2.cpp @ 529]</p>
<p>STACK_COMMAND:  ~0s; .ecxr ; kb</p>
<p>FOLLOWUP_IP:<br />
oleaut32!IDispatch_RemoteInvoke_Proxy+1c<br />
77d2b37f 83c40c          add     esp,0Ch</p>
<p>SYMBOL_STACK_INDEX:  e</p>
<p>SYMBOL_NAME:  oleaut32!IDispatch_RemoteInvoke_Proxy+1c</p>
<p>FOLLOWUP_NAME:  MachineOwner</p>
<p>MODULE_NAME: oleaut32</p>
<p>IMAGE_NAME:  oleaut32.dll</p>
<p>DEBUG_FLR_IMAGE_TIMESTAMP:  467044ca</p>
<p>FAILURE_BUCKET_ID:  STATUS_BREAKPOINT_80000003_oleaut32.dll!IDispatch_RemoteInvoke_Proxy</p>
<p>BUCKET_ID:  APPLICATION_FAULT_STATUS_BREAKPOINT_oleaut32!IDispatch_RemoteInvoke_Proxy+1c</p>
<p>Followup: MachineOwner</p>
]]></content:encoded>
	</item>
</channel>
</rss>
