[RESOLVED] Win2008R2 RTM/SP1: STOP 0x44 in mrxsmb!RxCeCompleteConnectRequest+367

  • Article

Status: Resolved

Update 110815: The KB for this STOP error has gone live. You can find it here.

Update 110522: I am still trying to replicate the circumstances that triggered this problem to happen so often at one customer, but not for millions of other customers. As soon as we understand the trigger/catalyst, I'll update this post.

Update 110518: Customer approved the private, the problem is resolved. Now we wait for KB2549724, to be released as part of the August Hotfix Release Cycle (HTP11-08). Please contact me if you encounter this issue in the meantime.

Update 110517: The machines running the private have been stable now for over 24 hours! :)

Update 110516: The private has now been applied to eight servers. Stay tuned for the results!

Update 110514: We have provided the customer with a private hotfix, which is being tested this weekend. An update will follow shortly. By the way, an RSS feed for (recently) released hotfixes for Win2008R2/SP1 is here.

Update 110512: We have a pretty good understanding what the root cause of this problem is, and we are working on a test hotfix to provide to the customer who reported this. If you think your machine might also be experiencing this, drop me an e-mail so we can discuss.

When opening the dump for this issue, I saw a MULTIPLE_IRP_COMPLETE_REQUESTS error:

BugCheck 44, {fffff98014c94ee0, 1d7b, 0, 0}
Probably caused by : mrxsmb.sys ( mrxsmb!RxCeCompleteConnectRequest+363 )

The crashing stack:

0: kd> knL
 # Child-SP RetAddr Call Site
00 fffff880`02bf7068 fffff800`01738301 nt!KeBugCheckEx
01 fffff880`02bf7070 fffff880`053d6b47 nt! ?? ::FNODOBFM::`string'+0x31aec
02 fffff880`02bf70b0 fffff880`053d732e mrxsmb!RxCeCompleteConnectRequest+0x363
03 fffff880`02bf7130 fffff880`053d720c mrxsmb!SmbWskAsynchronousConnectCompletionWorker+0x106
04 fffff880`02bf71d0 fffff800`016c8d26 mrxsmb!SmbWskAsynchronousConnectCompletion+0xb8
05 fffff880`02bf7220 fffff880`050f0d59 nt!IopfCompleteRequest+0x3a6
06 fffff880`02bf7300 fffff880`01656ba3 afd!WskProTLConnectComplete+0x109
07 fffff880`02bf73c0 fffff880`0166a568 tcpip!TcpCreateAndConnectTcbComplete+0x233
08 fffff880`02bf74d0 fffff880`01677334 tcpip!TcpTcbCarefulDatagram+0x7f8
09 fffff880`02bf7680 fffff880`0167b86a tcpip!TcpTcbReceive+0x694
0a fffff880`02bf7830 fffff880`0167b3b7 tcpip!TcpMatchReceive+0x1fa
0b fffff880`02bf7980 fffff880`0165d6c7 tcpip!TcpPreValidatedReceive+0x177
0c fffff880`02bf7a30 fffff880`0165d799 tcpip!IppDeliverListToProtocol+0x97
0d fffff880`02bf7af0 fffff880`0165dc90 tcpip!IppProcessDeliverList+0x59
0e fffff880`02bf7b60 fffff880`016347c2 tcpip!IppReceiveHeaderBatch+0x231
0f fffff880`02bf7c40 fffff800`019c2c43 tcpip!IppLoopbackTransmit+0x72
10 fffff880`02bf7c80 fffff800`016d3961 nt!IopProcessWorkItem+0x23
11 fffff880`02bf7cb0 fffff800`0196ac06 nt!ExpWorkerThread+0x111
12 fffff880`02bf7d40 fffff800`016a4c26 nt!PspSystemThreadStartup+0x5a
13 fffff880`02bf7d80 00000000`00000000 nt!KxStartSystemThread+0x16

Note: On Win2008R2 SP1 this STOP 0x44 shows as "mrxsmb!RxCeCompleteConnectRequest+367", instead of "mrxsmb!RxCeCompleteConnectRequest+367". Not all STOP 0x44 errors are caused by this problem.

Stay tuned for updated on this issue.