0x0D1 - ndis.sys/tcpip.sys

Page 1 of 2 12 LastLast

  1. Posts : 261
    Windows 10 Pro 21H2 (OS Build 19044.1706)
       #1

    0x0D1 - ndis.sys/tcpip.sys


    Windows 10 Pro 21H2 (OS Build 19044.1706)
    0x0D1 - ndis.sys/tcpip.sys-bluescreenview_3jusiteu6t.png
    So all I was doing at the time of this BSOD was watching a TV show on Firefox.
    KYLE-PC-(2022-07-07_14-45-41).zip
      My Computer


  2. Posts : 1,538
    Windows 8.1 Enterprise x64
       #2
      My Computer


  3. Posts : 261
    Windows 10 Pro 21H2 (OS Build 19044.1706)
    Thread Starter
       #3

    Updated the driver. I just had another BSOD a few moments ago:
    0x0D1 - ndis.sys/tcpip.sys-bluescreenview_sz5bhxqeg3.png

    KYLE-PC-(2022-07-08_20-03-55).zip
      My Computer


  4. Posts : 1,538
    Windows 8.1 Enterprise x64
       #4

    Maybe it's a coincidence? Observe if you still have BSODs
      My Computer


  5. Posts : 14,903
    Windows 10 Pro
       #5

    Not too sure about it being a coincidence, if you look in the event logs you'll see there are lots of chkdsk events for partition F specifically.

    May be worth checking the drives using SeaTools, and if that doesn't detect problems then chkdsk.
    SeaTools for DOS - Hard Drive Diagnostic | Tutorials (tenforums.com)
    Drive Error Checking in Windows 10 | Tutorials (tenforums.com)
      My Computers


  6. Posts : 261
    Windows 10 Pro 21H2 (OS Build 19044.1706)
    Thread Starter
       #6

    axe0 said:
    Not too sure about it being a coincidence, if you look in the event logs you'll see there are lots of chkdsk events for partition F specifically.

    May be worth checking the drives using SeaTools, and if that doesn't detect problems then chkdsk.
    SeaTools for DOS - Hard Drive Diagnostic | Tutorials (tenforums.com)
    Drive Error Checking in Windows 10 | Tutorials (tenforums.com)
    Yeah the disk check commands and the DISM were the first ones I did to troubleshoot before and after the second BSOD but it reported no integrity issues. I'll do another diagnostic for my Seagate external drive and report back.

    If that external drive is failing then I'm F'd because I don't currently have the money to replace it and I have a lot of backups on that drive, specifically for my web development and dedicated server cPanel account backups, etc.

    EDIT: The SeaTools DOS doesn’t seem to pick up my external drive or my SSD. Only my 2 WD internal drives.
    EDIT 2: Well this seems unlikely...
    0x0D1 - ndis.sys/tcpip.sys-explorer_kky4cfqxxi.png
    EDIT 3: I just found a relatively cheap internal 1TB to potentially replace my Seagate External Desktop USB drive. (Drive F). Instead of risking data loss or further corruption it's probably best I replace it considering the importance of the backups stored on F. I think I have a spare third SATA III drive bay unused.
    Last edited by Kyle; 09 Jul 2022 at 09:05.
      My Computer


  7. Posts : 14,903
    Windows 10 Pro
       #7

    Keep in mind for chkdsk, although it reports it could not find any errors, it will most likely still have made changes regardless of how significant those changes are (e.g. cleanup of attributes on a particular file). If chkdsk reports errors they are the most significant to report, but anything else won't be reported, even those that may still be relevant but aren't as critical as errors won't be reported directly.

    You may also want to consider testing the RAM just in case, it's another common cause for 0xEF.
    MemTest86+ - Test RAM | Tutorials (tenforums.com)
      My Computers


  8. Posts : 261
    Windows 10 Pro 21H2 (OS Build 19044.1706)
    Thread Starter
       #8

    axe0 said:
    Keep in mind for chkdsk, although it reports it could not find any errors, it will most likely still have made changes regardless of how significant those changes are (e.g. cleanup of attributes on a particular file). If chkdsk reports errors they are the most significant to report, but anything else won't be reported, even those that may still be relevant but aren't as critical as errors won't be reported directly.
    Agreed. I'm going to do checks on all of my drives just in case too.
    You may also want to consider testing the RAM just in case, it's another common cause for 0xEF.
    MemTest86+ - Test RAM | Tutorials (tenforums.com)
    I'll give this a try later on when I go to bed. Although I had my CPU overclocked at the times it crashed I have backed it to default OC settings (OC was from 4GHz stock to 4.5GHz) as my NB was reaching 75C constant and its really hot in my bedroom as well as all over the place. Cambridge region (UK) has a week and a half of heatwaves so my PC is a bit hot. 47C GPU | 62C NB (without the OC) and 45C CPU.

    I'll report back soon on memory test results. Though the last time I did a 3 day constant memtest was last week and it reported no errors. Still, it can't hurt to test again to be sure.

    As per my rep comment, thank you again, axe.
      My Computer


  9. Posts : 14,903
    Windows 10 Pro
       #9

    What memory test did you run last time?
      My Computers


  10. Posts : 261
    Windows 10 Pro 21H2 (OS Build 19044.1706)
    Thread Starter
       #10

    axe0 said:
    What memory test did you run last time?
    Erm I ran the 48 hour one and then nearly 2 hours the following morning and still passed with no memory errors.

    EDIT: Just had another BSOD but the system shut down at 48% collecting data. -_- KMODE something it was. My system always BSODs frequently when the ambient temperature in my bedroom is high. NB 65C, CPU 50C
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 14:24.
Find Us




Windows 10 Forums