"Driver_irql_not_less_or_equal caused by ndis.sys" even after fresh install of Windows 10

[Lustro]

Hey,
I’ve been having a BSOD problem for quite some time and don’t know what to do anymore about it, I hope I can find help here.

Short version: almost an hour ago I’ve had a BSOD which said that it was caused by “ndis.sys” and its code was “Driver irql not less or equal”; as per the instructions, I’ve attached the associated dump.

Long version: this is not the first time I’ve had this problem; recently, I’ve had this problem some days ago, so I searched on the internet and saw this was tipically caused by drivers or ram. So i’ve done a memtest and it came out ok, then did some maintenance on the computer (changed cpu’s thermal paste), and in the end I’ve done a fresh install of windows 10, less than a week ago; I’ve installed the drivers from the motherboard website and only then I’ve connected it to the internet, hoping there would be no driver problems. Now, some days later, this problem reoccured.
Both times it happened while I had a live from twitch open and also onenote, but I tend to do this often and don’t usually have this problem, so I don’t think it’s related to these two specific applications (but I really don’t know to be fair), to me it almost seems like it’s random.

If it can be useful, this is a screenshot from HWiNFO so that you can have some info about my hardware
[ATTACH type=“full”]8683[/ATTACH]

I’ll post this too because maybe it could be useful: this is a screenshot from event viewer
[ATTACH type=“full”]8684[/ATTACH]
Sadly these are all in Italian, but if it can be helpful I’d be more than happy to translate some or all of them in English. This particular one says “Control events not elaborated from transport. 0.”, the “Critico” one is when I’ve had the BSOD.

Optional info: I don’t think this could be useful so this text can be skipped, but I’m writing it because maybe it can help if an hardware failure is feared. This PC is quite old, I’ve had it since around 2013 and changed hard disks and ram because they had failed in the past. In late 2013 I tried to change the heatsink and I think I did some damage to the motherboard: some USB ports didn’t work anymore and I had some bsod that had a code that was like “Bugcode-Usb-something”. Reinstalling windows solved the bsod, but since then, if I went in “devices” there had always been an “unknown device” listed, and I always assumed they were the usb ports I broke (haven’t tried them anymore in fear of causing more hardware malfunctions). This time though there is not, and I’m always scared that that malfunction could come up, cause bsod and force me to change motherboard and everything else. I list this as “optional info” because for these eight years it’s been fine, I’ve had other bsod but not never relating to the moterboard at all, so I think it would be unlikely.

I’m not sure, but I think some years ago I’ve had this same bsod, and I noticed at first it was caused by launching an online game, and then it escalated and blocked me from using the computer because it would come up minutes after booting windows. Reinstalling windows did solve the problem that time though. If you think this could be related, I’d be more to happy to be more specific about this story.

I’m truly at a loss, and I thank you kindly for reading and possibly helping. If you need anything - more info, results of tests etc. - I’ll be more than happy to comply!

[veeg]

Hello
Hopefully some of our members will chime in soon..

jmarket @phillpower2

[Lustro]

Hello, thanks! In the meantime, I thought it could be useful to publish a Speccy snapshot, here it is if needed: http://speccy.piriform.com/results/f...CP5Fl5yYvRgzKx

[jmarket]

I’ve analyzed your dump file and found:
[ICODE]Image path: \SystemRoot\System32\drivers\L1C63x64.sys[/ICODE]
as the cause of the crash. This driver is for an Ethernet Controller

[Lustro]

Thank you for your answer!

If it indeed is a driver problem and not something hardware related, I think “Qualcomm Atheros AR8161” could be the culprit

[ATTACH type=“full”]8687[/ATTACH]

I say that because in the “Event” tab the name of the driver “netl1c63x64.inf” can be read (the messages says, from top to bottom : “Device installation requested” “Device installation requested” “Device configured (netl1c63x64.inf)” “Device started (L1C)”).

When I fresh installed Windows, before connecting the computer to the internet I had downloaded from another pc and transfered the five drivers listed for windows 10 64 bit on the motherboard’s site, here, and then the driver for the GPU. But, as you can see, of these 5 drivers not one is for the LAN.

[ATTACH type=“full”]8688[/ATTACH]

By removing the filtering on the motherboard’s site, I’ve found this old LAN driver, but it seems like “Windows 10” is not a listed OS for it.

I’ve also done some quick research on the internet, and I’ve found a thread on another forum, here, where someone had a similar problem but with a different motherboard. He tried installing the driver from the motherboard site, though, as in my case, windows 10 was not a listed OS for the driver, but that didn’t solve the case; apparently, installing a newer version found on the internet solved his case.

What would you advice me to do?

[Rustys]

While you are waiting for a response form jmarket lets look here.

Click Start
Setting
Select Update and Security
Select View Optional Updates

What is listed under Driver Updates?

[Lustro]

Thanks for your answer! This is what I see

[ATTACH type=“full”]8704[/ATTACH]

I’m sorry that it’s not in English, but I think the text is just generic info (otherwise just tell me and I’ll be more than happy to translate!)

I’m pretty sure the HP - SmartCardReader driver is for the keyboard I’m using, but I’m not really sure about the others.

[Rustys]

No worried about it not being in English I can make it out.

Could you post an image of Device Manager?

Right Click or Press the Windows Key + X
Select Device Manager

Make sure the network list is open

The Intel should be the Chipsets
The HP Smart Card Reader should be for the card reader to read the card used in cameras.
[ATTACH type=“full” width=“69px”]8705[/ATTACH]

[Lustro]

Of course, here it is, and thanks again!

[ATTACH type=“full”]8706[/ATTACH]

Do you need the other lists to be open too?

[Lustro]

I’m just saying this out of curiosity and nothing else, as I think and hope it is not the cause of bsods, but about the card reader driver, I’ve always thought it was caused by the fact that in the keyboard I have, which is the one in this image, there’s a “smart card terminal” with a hole that I think is too big for memory cards. Don’t think it makes any difference in the appearance of bsods though
[ATTACH type=“full” alt=“1639512479957.png”]8708[/ATTACH]

[Rustys]

One other idea while waiting on jmarket to weigh in.

I’ve also done some quick research on the internet, and I’ve found a thread on another forum, here, where someone had a similar problem but with a different motherboard. He tried installing the driver from the motherboard site, though, as in my case, windows 10 was not a listed OS for the driver, but that didn’t solve the case; apparently, installing a newer version found on the internet solved his case.

They may have used the driver form here second one from the bottom.

https://www.catalog.update.microsoft.com/Search.aspx?q=Atheros+AR8161+PCI-E

[Lustro]

Right, they mentioned the .27 version and it seems to be there. For reference, the version of the driver I currently have and have had a BSOD with is the .16 version, as shown below

[ATTACH type=“full” alt=“1639521281077.png”]8709[/ATTACH]

This was installed automatically by Windows, because on Gigabyte’s site there are no Lan drivers listed for windows 10 for my motherboard, only up to Win8.

The version on the Gigabyte’s site (reply #5) is 2.1.0.21. In the microsoft site you linked, the .21 version is listed as a “Windows 8.1 and later drivers” version and that does make me wonder why on Gigabyte’s site compatibility with windows 10 is not listed (I have no knowledge about this type of things, so maybe they’re two different kinds of .21 drivers), and it also makes me wonder why Windows has installed the .16 version and not the .27, as it seems to be available to Microsoft.

While I’m at it, I’ll also give you a small update about these days. I have used this computer because it was needed, but I have not played online videogames with it nor have I watched lives, and no blue screens have appeared so far. I don’t know if these things are correlated or not; please note that I did a fresh install of Windows on 5/12/2021 and a bsod appeared only on 8/12/2021, and during the days from 5/12 to 8/12 I have played online games and watched lives everyday but the bsod appeared only on 8/12, that’s why I say I don’t know if they’re correlated or not. On the previous install of Windows, the computer has been working fine for 11 months and then started giving me this bsod. So it seems like a “sleeper” problem or I just don’t know how to replicate it, but sadly I’m sure that it’s still there and it hasn’t fixed itself just because it hasn’t appeared these days.

If you’ll come up with a solution, or even just an opinion, about which driver to install or what to do in general, then I’ll do it and will surely start testing it “properly” again (meaning playing videogames and watching lives), and keep you updated.

Thank you as always, I’m really grateful for all the help.

[Rustys]

Did you try the driver that was suggested in post #11?
Using the ink provided.

They may have used the driver form here second one from the bottom.

Microsoft Update Catalog

[jmarket]

Hello,

I’ve completed your analysis:

MODULE_NAME: L1C63x64

IMAGE_NAME:  L1C63x64.sys

IMAGE_VERSION:  2.1.0.16

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1d0

FAILURE_BUCKET_ID:  AV_L1C63x64!DmaSendNetBufferList

That driver is Qualcomm Atheros AR8171/8175 Gigabit Ethernet Controller driver. Please review the below excerpt from my analysis for more info:

Image path: \SystemRoot\System32\drivers\L1C63x64.sys
    Image name: L1C63x64.sys
    Timestamp:        Sun Mar 31 20: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.

[Lustro]

Thank you both for the answers!

        FileVersion:      2.1.0.16
        FileDescription:  Qualcomm Atheros Ar81xx series PCI-E Gigabit Ethernet Controller

I think this alone confirms the culprit is the device in the screenshot in post #12, as the driver version corresponds (2.1.0.16) and the name does too, as it’s an Ar8161. I’m already pretty happy it’s probably not hardware.

The tricky part now is to find a solution, because gigabyte has no lan drivers listed for windows 10 for my motherboard, only up to windows 8. But about that, I think Rustys may be onto something.

Did you try the driver that was suggested in post #11?
Using the ink provided.

No, I haven’t. But if you advise me to, I will try it as soon as I can - I’ll wait for a confirmation message just to be sure and then proceed.