Share via

BSOD BUGCODE_NDIS_DRIVER with driver verifier (minidump available)

Anonymous
2022-07-15T22:16:02+00:00

While trying to track down trouble on my system and running driver verifier, I got a BUGCODE_NDIS_DRIVER BSOD fairly shortly after restarting. WhoCrashed wasn't able to determine the other driver that caused the BSOD inside ndis.sys unfortunately (seems like it generally fails where ndis.sys is concerned).

Minidump available here: https://www.dropbox.com/s/atl76zo0ec80bdm/071522-13484-01.dmp?dl=0

Can someone with better tooling than I have advise on what other driver on my system may have caused this BSOD?

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

4 answers

Sort by: Most helpful
  1. Anonymous
    2022-07-16T17:36:03+00:00

    So far so good, but time will tell. One nice thing about Driver Verifier is you can use it to easily get a list of drivers in your system that might not have .inf files in the driver store. After sorting by supplier, I found there were a few I still had in there from a previous motherboard that stood out, so I disabled them by renaming them to *.~sys. They might not have caused problems, but they also weren't helping, and I find that simplifying things as much as possible to remove unnecessary variables is generally a good idea in these situations.

    Let's see if I can get another 27 days of uptime again...

    Was this answer helpful?

    0 comments No comments
  2. Igor Leyko 111K Reputation points Independent Advisor
    2022-07-16T17:00:42+00:00

    OK, please tell the results.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-07-16T01:41:44+00:00

    I decided to enable a *full* memory dump instead of the minidump so it would be possible to enumerate the miniport drivers and see what might have been causing the error in the NDIS driver. It turned out to be the Intel V225-I NIC driver (found by loading the dump up in windbg64).

    I found there was a newer driver available from Intel, so I grabbed that, and then I also reconfigured Driver Verifier to exclude e2fn.sys. These network stack validation errors don't seem to pose any significant crash/freeze risk to the machine; at most, they'd probably result in dropped frames on the network.

    Hopefully Driver Verifier will help bring some stability back to this system... it had been up for 27 days, and then suffered from two hangs within as many days.

    Was this answer helpful?

    0 comments No comments
  4. Igor Leyko 111K Reputation points Independent Advisor
    2022-07-15T22:52:25+00:00

    Hi,

    My name is Igor, I have 12 Microsoft MVP awards. It's a pleasure for me to help others and I'll do all my best to help you. I'm sorry you have a problems.

    Dump points to NetAdapterCx.sys driver, Seems this file is damaged.

    Please repair system files by

    DISM.exe /Online /Cleanup-Image /RestoreHealth

    command from Windows Terminal (admin) environment.

    Was this answer helpful?

    0 comments No comments