BSOD - random ndis.sys error

Hi Jurien,

I would like to know why you attached the zip you downloaded. There are files inside this zip that you should run to generate log files that we need.

No worries, I am genuinely curious.

We've noticed more people do the same thing and are wondering why so we can improve the posting instructions.

From what it looks like, you mostly had the exact same crash. Presumably an invalid address was used when the Qualcomm driver was trying to get the NDIS driver to associate a scatter/gather list with the buffer to perform a DMA request.

Code:

1: kd> .trap 0xffff958244e8a100
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000100 rbx=0000000000000000 rcx=0000000000000000
rdx=ffffc687a91e0bc0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80747da16b6 rsp=ffff958244e8a290 rbp=ffffc687a5616dc0
 r8=ffffc687a53ae3e0  r9=0000000000000001 r10=0000000000000fff
r11=ffff9efec6400000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
ndis!NdisMAllocateNetBufferSGList+0x3cab6:
fffff807`47da16b6 8b4728          mov     eax,dword ptr [rdi+28h] ds:00000000`00000028=????????

1: kd> knL
  *** Stack trace for last set context - .thread/.cxr resets it
 # Child-SP          RetAddr           Call Site
00 ffff9582`44e8a290 fffff807`4b7d70e4 ndis!NdisMAllocateNetBufferSGList+0x3cab6
01 ffff9582`44e8a350 fffff807`4b7d7512 L1C63x64!DmaSendNetBufferList+0x1d0
02 ffff9582`44e8a430 fffff807`47d650ae L1C63x64!MiniportSendNetBufferLists+0x11e
03 ffff9582`44e8a470 fffff807`47d64f9e ndis!ndisMSendNBLToMiniportInternal+0xfe
04 ffff9582`44e8a540 fffff807`47d658e8 ndis!ndisMSendNBLToMiniport+0xe
05 ffff9582`44e8a580 fffff807`47d9df95 ndis!ndisCallSendHandler+0x58
06 ffff9582`44e8a5d0 fffff807`47d625dd ndis!ndisInvokeNextSendHandler+0x191
07 ffff9582`44e8a6a0 fffff807`48027b9d ndis!NdisSendNetBufferLists+0x17d
08 ffff9582`44e8a7a0 fffff807`480278c7 tcpip!FlpSendPacketsHelper+0x2bd
09 ffff9582`44e8a850 fffff807`47fea3e5 tcpip!FlSendPackets+0x57
0a ffff9582`44e8a880 fffff807`47fe9903 tcpip!IppFragmentPackets+0x2a5
0b ffff9582`44e8a960 fffff807`47fe9588 tcpip!IppDispatchSendPacketHelper+0xbf
0c ffff9582`44e8aa30 fffff807`47fe81d8 tcpip!IppPacketizeDatagrams+0x2e8
0d ffff9582`44e8ab60 fffff807`47fe4b89 tcpip!IppSendDatagramsCommon+0x498
0e ffff9582`44e8ace0 fffff807`47ff4e24 tcpip!IpNlpFastSendDatagram+0x349
0f ffff9582`44e8ada0 fffff807`47ff7a84 tcpip!TcpTcbSend+0x6d4
10 ffff9582`44e8b120 fffff807`47ff76ee tcpip!TcpEnqueueTcbSend+0x374
11 ffff9582`44e8b260 fffff807`44a37218 tcpip!TcpTlConnectionSendCalloutRoutine+0x2e
12 ffff9582`44e8b2a0 fffff807`44a3718d nt!KeExpandKernelStackAndCalloutInternal+0x78
13 ffff9582`44e8b310 fffff807`48019670 nt!KeExpandKernelStackAndCalloutEx+0x1d
14 ffff9582`44e8b350 fffff807`4937c07f tcpip!TcpTlConnectionSend+0x80
15 ffff9582`44e8b3c0 fffff807`4937beaa afd!AfdTLStartBufferedVcSend+0x9f
16 ffff9582`44e8b470 fffff807`49361720 afd!AfdFastConnectionSend+0x2a2
17 ffff9582`44e8b540 fffff807`44e0e182 afd!AfdFastIoDeviceControl+0xf90
18 ffff9582`44e8b8e0 fffff807`44e0dde6 nt!IopXxxControlFile+0x382
19 ffff9582`44e8ba20 fffff807`44bef478 nt!NtDeviceIoControlFile+0x56
1a ffff9582`44e8ba90 00007ffd`0db6ae74 nt!KiSystemServiceCopyEnd+0x28
1b 0000002b`9e3feca8 00000000`00000000 0x00007ffd`0db6ae74

1: kd> lmvm L1C63x64
Browse full module list
start             end                 module name
fffff807`4b7d0000 fffff807`4b7f2000   L1C63x64   (pdb symbols)          g:\symbols\L1c63x64.pdb\DF9236FBD6744CE8A7D9FF5A931BF7271\L1c63x64.pdb
    Loaded symbol image file: L1C63x64.sys
    Mapped memory image file: g:\symbols\L1C63x64.sys\5158FBC522000\L1C63x64.sys
    Image path: \SystemRoot\System32\drivers\L1C63x64.sys
    Image name: L1C63x64.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Apr  1 05:15:17 2013 (5158FBC5)
    CheckSum:         0002612D
    ImageSize:        00022000
    File version:     2.1.0.16
    Product version:  2.1.0.16
    File flags:       8 (Mask 3F) Private
    File OS:          40004 NT Win32
    File type:        3.6 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    Information from resource tables:
        CompanyName:      Qualcomm Atheros Co., Ltd.
        ProductName:      Qualcomm Atheros Ar81xx series PCI-E Gigabit Ethernet Controller
        InternalName:     L1c63x64.sys
        OriginalFilename: L1c63x64.sys
        ProductVersion:   2.1.0.16
        FileVersion:      2.1.0.16
        FileDescription:  Qualcomm Atheros Ar81xx series PCI-E Gigabit Ethernet Controller
        LegalCopyright:   2001-2012 Qualcomm Atheros Co., Ltd. All Rights Reserved.

This driver is officially not compatible with Windows 10 because it's date is 2 years before Windows 10 was released in 2015.

It does not appear that Gigabyte provides network drivers for Windows 10, try the drivers Gigabyte provides for Windows 8.1 instead, if you already have them I would recommend to reinstall them.

I do not know the exact revision of your motherboard, if you don't know open your computer and check the motherboard. It should be showing in the corner near the GPU slots.

Then check GA-Z77X-D3H (rev. 1.0) | Motherboard - GIGABYTE Global, change the rev if necessary, select Windows 8.1 and download the LAN drivers.

Please fill in your system specs

Please follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU, cooling and other used stuff like mouse, keyboard, monitor, case, etc. If there's anything you don't know, leave it out.
The PSU, cooling and other stuff are NOT mentioned in the tool.

In the left corner below in your post you find 'My System Specs'. After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.

Great, do you by any chance know the case of your computer?