Debugging In Progress...

This blog is intended to provide information on debug issues encountered in Microsoft Support, such as STOP errors or hanging servers.

[RESOLVED] Win2012 - STOP 0xD1 in NETIO!RtlCopyMdlToMdlIndirect+0x32

[RESOLVED] Win2012 - STOP 0xD1 in NETIO!RtlCopyMdlToMdlIndirect+0x32

  • Comments 2
  • Likes

Status: Resolved, external.

This was the first STOP I saw on Win2012 from one of my customers. The problem here was confirmed by HP to be in the NIC driver. Have a look at the stack below, and contact HP support if you encounter the same issue.

00 fffff802`80eb6058 fffff802`7f47a069 nt!KeBugCheckEx
01 fffff802`80eb6060 fffff802`7f4788e0 nt!KiBugCheckDispatch+0x69
02 fffff802`80eb61a0 fffff880`01561422 nt!KiPageFault+0x260
03 fffff802`80eb6330 fffff880`02135270 NETIO!RtlCopyMdlToMdlIndirect+0x32
04 fffff802`80eb63b0 fffff880`021688d5 tcpip!TcpSatisfyReceiveRequests+0x110
05 fffff802`80eb65c0 fffff880`02170a70 tcpip!TcpDeliverDataToClient+0xd5
06 fffff802`80eb6730 fffff880`0215fdf8 tcpip!TcpDeliverReceive+0xa0
07 fffff802`80eb6820 fffff880`02176fd7 tcpip!TcpTcbFastDatagram+0x248
08 fffff802`80eb6a00 fffff880`021776e3 tcpip!TcpTcbReceive+0x207
09 fffff802`80eb6b60 fffff880`02171b01 tcpip!TcpMatchReceive+0x1f3
0a fffff802`80eb6ce0 fffff880`0217353e tcpip!TcpPreValidatedReceive+0x381
0b fffff802`80eb6dc0 fffff880`0215f24a tcpip!IpFlcReceivePreValidatedPackets+0x68e
0c fffff802`80eb6f30 fffff802`7f4bbf15 tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda
0d fffff802`80eb7030 fffff802`7f4bcea5 nt!KeExpandKernelStackAndCalloutInternal+0xe5
0e fffff802`80eb7130 fffff880`0215f45e nt!KeExpandKernelStackAndCalloutEx+0x25
0f fffff802`80eb7170 fffff880`01459e2e tcpip!FlReceiveNetBufferListChain+0xae
10 fffff802`80eb71f0 fffff880`01459750 NDIS!ndisMIndicateNetBufferListsToOpen+0x373
11 fffff802`80eb7290 fffff880`01459a05 NDIS!ndisInvokeNextReceiveHandler+0x650
12 fffff802`80eb7360 fffff880`191984c3 NDIS!NdisMIndicateReceiveNetBufferLists+0xc5
13 fffff802`80eb73e0 fffff880`19198a3b NICdriver+0x154c3
14 fffff802`80eb7460 fffff880`016c5a3d NICdriver+0x15a3b
15 fffff802`80eb7500 fffff880`016c9cb4 VirtualBusDriver+0x12a3d
16 fffff802`80eb7580 fffff880`016c60c6 VirtualBusDriver+0x16cb4
17 fffff802`80eb7600 fffff880`016d0457 VirtualBusDriver+0x130c6
18 fffff802`80eb78e0 fffff880`016c803d VirtualBusDriver+0x1d457
19 fffff802`80eb7940 fffff802`7f471968 VirtualBusDriver+0x1503d
1a fffff802`80eb79b0 fffff802`7f4a1bd0 nt!KiExecuteAllDpcs+0x198
1b fffff802`80eb7af0 fffff802`7f4a63fa nt!KiRetireDpcList+0xd0
1c fffff802`80eb7c60 00000000`00000000 nt!KiIdleLoop+0x5a

When in doubt, you can always create a support case with us or HP to confirm. 

  • Thanks for sharing the solution Rob.

  • Hey what was the network card they are using in the server?  Broadcom, Intel, Qlogic?  Or what did HP change / update to correct.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment