Frequent BSOD from ndis.sys, ntoskrnl.exe and tcpip.sys(windows 11)

Manul Abeyratne 20 Reputation points
2026-06-20T23:24:40.6566667+00:00

Since I reset my system I keep getting BSODs pretty frequently and the culprits seem to be ndis.sys, ntoskrnl.exe and tcpip.sys. I found them using BlueScreenView, Dump files here: https://drive.google.com/drive/folders/1h-gbgfdngbnWWNuWyhUwclAuwYdJpYFX?usp=drive_link

windows is up to date, network drivers too, so I don't know what's going on. Last time it happened when i was downloading a game with high netowork load( it almost always bsod when in high network load with a few exceptions likw gaming)
MY specs Intel i9 11900 ES QVYE , 32 Gb ram ddr4, gigabyte b460m ds3h v2 mb, Rtx 5060 8GB, Also i dont use any external anti virus , only defender.

Windows for home | Windows 11 | Performance and system failures
0 comments
Answer accepted by question author
TaoLi 113.2K Reputation points Independent Advisor
2026-06-24T03:03:13.33+00:00

Hi, this makes sense.

XMP was likely causing RAM instability, especially under high load. That can lead to random kernel/network crashes.

Windows dump doesn’t show it clearly because unstable RAM often corrupts data and makes it look like: ndis.sys / tcpip.sys / ntoskrnl.exe are the issue, but they’re usually just the “victims”.

So lowering from 3200 → 2933 fixed stability = confirms memory instability, not driver bug.

Was this answer helpful?

1 person found this answer helpful.
0 comments

3 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. TaoLi 113.2K Reputation points Independent Advisor
    2026-06-23T12:50:15.93+00:00

    Thanks for trying those steps and confirming.

    Since the issue still happens even after reinstalling the network driver and resetting the network stack, this is less likely to be a normal Windows/network configuration problem now.

    Because the BSOD appears under high network load and involves ndis.sys / tcpip.sys / ntoskrnl.exe, I would start suspecting either the network adapter driver branch itself or a hardware-related issue with the network adapter/motherboard.

    You can still try one last thing: install a different version of the network adapter driver, not necessarily the newest one. For example, try the driver from the motherboard/laptop manufacturer’s support page, or one older stable version.

    If the same BSOD continues after changing driver versions, I’d recommend testing with another network device, such as a USB Ethernet/Wi-Fi adapter. If the crashes stop with another adapter, the built-in network adapter is very likely the problem. If it still crashes, then motherboard or other hardware stability should be checked.

    Was this answer helpful?

  2. TaoLi 113.2K Reputation points Independent Advisor
    2026-06-22T01:00:20.3+00:00

    Hi, this type of BSOD (ndis.sys / tcpip.sys) is usually related to the network driver or network adapter, especially since it happens under high network load.

    You can try the following:

    • Change the network driver version: don’t use the latest one, try an older stable version from the motherboard vendor or Intel’s official driver
    • Reset network stack (run CMD as admin):

    netsh winsock reset

    netsh int ip reset

    ipconfig /flushdns

    Then reboot the PC

    It could be unstable onboard network hardware (NIC) or even motherboard-related, you can test with a USB network adapter to confirm.

    Was this answer helpful?

  3. TaoLi 113.2K Reputation points Independent Advisor
    2026-06-21T01:08:52.4466667+00:00

    Hello,

    This is an issue with the network adapter.

    Open Device Manager, locate and uninstall the network adapter driver, and make sure to check the box to delete the driver software.

    After uninstalling, restart your computer and visit the manufacturer's official website to download the driver for your specific model.

    Reinstall the network adapter driver to see if the issue is resolved.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.