<?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: What is KiFastSystemCallRet?</title>
	<link>https://www.dumpanalysis.org/blog/index.php/2008/01/10/what-is-kifastsystemcallret/</link>
	<description>Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics</description>
	<pubDate>Wed, 06 May 2026 02:22:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Andrew Murray</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/01/10/what-is-kifastsystemcallret/#comment-172587</link>
		<dc:creator>Andrew Murray</dc:creator>
		<pubDate>Mon, 02 Aug 2010 14:52:52 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/01/10/what-is-kifastsystemcallret/#comment-172587</guid>
		<description>I have a stack trace that I took from a dump file which looks very much like the first stack trace in this article:

ntdll!KiFastSystemCallRet    
ntdll!NtReplyWaitReceivePortEx+c    
rpcrt4!LRPC_ADDRESS::ReceiveLotsaCalls+198    
rpcrt4!RecvLotsaCallsWrapper+d    
rpcrt4!BaseCachedThreadRoutine+9d    
rpcrt4!ThreadStartRoutine+1b    
kernel32!BaseThreadStart+34    

This thread is apparently causing a "blocking or leaked critical section" with a thread executing our code waiting on it:

ntdll!KiFastSystemCallRet    
ntdll!ZwWaitForSingleObject+c    
ntdll!RtlpWaitOnCriticalSection+1a3    
ntdll!RtlEnterCriticalSection+a8    
odbc32!CCriticalSection::Enter+f    
odbc32!ODBCEnterCriticalSection+f    
odbc32!EnterDbcCS+2b    
odbc32!SQLDisconnect+2d    
LibRdac!rdacCConnection::Close+21    
LibRdac!rdacCConnection::~rdacCConnection+41    
RmsSrvc!busiCPooledObject::OnOutputXMLSent+1ac    
RmsSrvc!busiCPooledObject::~busiCPooledObject+71    
RmsAcci!acciCAccessControlInterface::Run+5eea 

The result is that the process hangs. Can anyone shed any light?</description>
		<content:encoded><![CDATA[<p>I have a stack trace that I took from a dump file which looks very much like the first stack trace in this article:</p>
<p>ntdll!KiFastSystemCallRet<br />
ntdll!NtReplyWaitReceivePortEx+c<br />
rpcrt4!LRPC_ADDRESS::ReceiveLotsaCalls+198<br />
rpcrt4!RecvLotsaCallsWrapper+d<br />
rpcrt4!BaseCachedThreadRoutine+9d<br />
rpcrt4!ThreadStartRoutine+1b<br />
kernel32!BaseThreadStart+34    </p>
<p>This thread is apparently causing a &#8220;blocking or leaked critical section&#8221; with a thread executing our code waiting on it:</p>
<p>ntdll!KiFastSystemCallRet<br />
ntdll!ZwWaitForSingleObject+c<br />
ntdll!RtlpWaitOnCriticalSection+1a3<br />
ntdll!RtlEnterCriticalSection+a8<br />
odbc32!CCriticalSection::Enter+f<br />
odbc32!ODBCEnterCriticalSection+f<br />
odbc32!EnterDbcCS+2b<br />
odbc32!SQLDisconnect+2d<br />
LibRdac!rdacCConnection::Close+21<br />
LibRdac!rdacCConnection::~rdacCConnection+41<br />
RmsSrvc!busiCPooledObject::OnOutputXMLSent+1ac<br />
RmsSrvc!busiCPooledObject::~busiCPooledObject+71<br />
RmsAcci!acciCAccessControlInterface::Run+5eea </p>
<p>The result is that the process hangs. Can anyone shed any light?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Reflecting on 2008 (Part 1)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/01/10/what-is-kifastsystemcallret/#comment-119530</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Reflecting on 2008 (Part 1)</dc:creator>
		<pubDate>Wed, 27 Jan 2010 00:46:51 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/01/10/what-is-kifastsystemcallret/#comment-119530</guid>
		<description>[...] provide answers or point to other resources): kifastsystemcallret crash dump analysis crash dump ntdll!kifastsystemcallret vista crash dump time travel debugging dump analysis crash dumps windbg commands memory dump [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] provide answers or point to other resources): kifastsystemcallret crash dump analysis crash dump ntdll!kifastsystemcallret vista crash dump time travel debugging dump analysis crash dumps windbg commands memory dump [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Unintended Results &#187; Blog Archive &#187; Malware Tricks I</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/01/10/what-is-kifastsystemcallret/#comment-107448</link>
		<dc:creator>Unintended Results &#187; Blog Archive &#187; Malware Tricks I</dc:creator>
		<pubDate>Wed, 02 Dec 2009 21:57:47 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/01/10/what-is-kifastsystemcallret/#comment-107448</guid>
		<description>[...] basically, we&#8217;re jumping to a return only function (see a detailed description of KiFastSystemCallRet) efectively returning into the &#8220;some_func&#8221; function. The emulators I tested, as in [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] basically, we&#8217;re jumping to a return only function (see a detailed description of KiFastSystemCallRet) efectively returning into the &#8220;some_func&#8221; function. The emulators I tested, as in [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; The mystery of top hit kifastsystemcallret</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/01/10/what-is-kifastsystemcallret/#comment-49429</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; The mystery of top hit kifastsystemcallret</dc:creator>
		<pubDate>Mon, 03 Nov 2008 13:25:11 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/01/10/what-is-kifastsystemcallret/#comment-49429</guid>
		<description>[...] What is KiFastSystemCallRet? [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] What is KiFastSystemCallRet? [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug H.</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/01/10/what-is-kifastsystemcallret/#comment-34836</link>
		<dc:creator>Doug H.</dc:creator>
		<pubDate>Sat, 19 Jul 2008 12:07:01 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/01/10/what-is-kifastsystemcallret/#comment-34836</guid>
		<description>Hi,

I have an application, "RSLogix5000", that won't shut down (same problem on three different computers running two different builds of the app).  The thread that keeps it from shutting down is in a Wait state: WrLpcReply and the thread's stack always shows ntdll.dll!KiFastSystemCallRet .  I haven't been able to find out why that hangs the thread and keeps the exe alive yet but was interested in your info and links.  Thanks.

Bye,
dh</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I have an application, &#8220;RSLogix5000&#8243;, that won&#8217;t shut down (same problem on three different computers running two different builds of the app).  The thread that keeps it from shutting down is in a Wait state: WrLpcReply and the thread&#8217;s stack always shows ntdll.dll!KiFastSystemCallRet .  I haven&#8217;t been able to find out why that hangs the thread and keeps the exe alive yet but was interested in your info and links.  Thanks.</p>
<p>Bye,<br />
dh</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: If broken it is, fix it you should : ntdll!kifastSystemcallret, SharedUserData!SystemCallStub and search engines...</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/01/10/what-is-kifastsystemcallret/#comment-26196</link>
		<dc:creator>If broken it is, fix it you should : ntdll!kifastSystemcallret, SharedUserData!SystemCallStub and search engines...</dc:creator>
		<pubDate>Wed, 07 May 2008 09:31:35 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/01/10/what-is-kifastsystemcallret/#comment-26196</guid>
		<description>[...] paint&#160;dry:)&#160;&#160;but if you're interested in the details you can read more about it here.&#160; What is interesting though is where you see it, and that is probably what gets people [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] paint&nbsp;dry:)&nbsp;&nbsp;but if you&#8217;re interested in the details you can read more about it here.&nbsp; What is interesting though is where you see it, and that is probably what gets people [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Bugchecks: SYSTEM_SERVICE_EXCEPTION</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/01/10/what-is-kifastsystemcallret/#comment-24145</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Bugchecks: SYSTEM_SERVICE_EXCEPTION</dc:creator>
		<pubDate>Tue, 22 Apr 2008 12:31:22 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/01/10/what-is-kifastsystemcallret/#comment-24145</guid>
		<description>[...] x64 Windows platforms KiSystemServiceCopyEnd has the similar purpose as KiFastSystemCallRet on x86 [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] x64 Windows platforms KiSystemServiceCopyEnd has the similar purpose as KiFastSystemCallRet on x86 [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
