[Windows 7 x64], [Version 6.2.437.2171], adgnetworktdidrv.sys, BSOD.

Discussion in 'Quality Control' started by Pentlands, Jan 20, 2018.

  1. Pentlands

    Pentlands Beta Tester

    Joined:
    Mar 11, 2014
    Messages:
    43
    Hi,

    A couple of days ago for the first time in a very long time my PC crashed to a BSOD, "adgnetworktdidrv.sys" appears to have been involved.

    Having checked the file properties of adgnetworktdidrv.sys it appears this is an AdGuard file, are you aware of any issues?

    If it helps i have copied the minidump file to another location and can upload it if it would help.

    Capture.JPG
     
  2. avatar

    avatar Administrator Staff Member Administrator

    Joined:
    Oct 26, 2010
    Messages:
    13,029
    What AV do you have?
     
  3. Pentlands

    Pentlands Beta Tester

    Joined:
    Mar 11, 2014
    Messages:
    43
    Microsoft Security Essentials, also Malwarbytes Premium (current version 3.3.1)... sorry, i can't be specific about the build numbers when the BSOD occurred because they've since updated, that said, the minidump file that i still have may have that info.
     
  4. avatar

    avatar Administrator Staff Member Administrator

    Joined:
    Oct 26, 2010
    Messages:
    13,029
    We should re-test it on the newer beta version of AdGuard. It will bring a TDI driver update that *might* help.
     
  5. avatar

    avatar Administrator Staff Member Administrator

    Joined:
    Oct 26, 2010
    Messages:
    13,029
    ETA is 3 weeks btw.
     
  6. Pentlands

    Pentlands Beta Tester

    Joined:
    Mar 11, 2014
    Messages:
    43
    I'm reading your posts above as their might be an issue with the TDI driver causing a BSOD? Would that be a correct assumption?
     
  7. avatar

    avatar Administrator Staff Member Administrator

    Joined:
    Oct 26, 2010
    Messages:
    13,029
    Yes, and that's basically what's printed on the screenshot. AG driver alone does not cause it, but in conjunction with some other network drivers, it might happen.
     
  8. Pentlands

    Pentlands Beta Tester

    Joined:
    Mar 11, 2014
    Messages:
    43
    Thanks, as that was the first time I've had a BSOD i could attribute to AG in four years of being a beta tester i was somewhat surprised it happened... as you're aware of an issue i'll step back from this thread.
     
  9. Pentlands

    Pentlands Beta Tester

    Joined:
    Mar 11, 2014
    Messages:
    43
    I know i said I'd step back, but....

    I do hope so, a couple of days ago i had a second BSOD, this time it was tdx.sys, which according to the properties of the file in c:\windows\system32\drivers... is a "TDI translation Driver".

    If it helps, i tracked down when my network driver was last updated, it was August 2017, tdx.sys reports it was last modified in July 2017, I'm still running AG for Windows 6.2.437.2171
    I haven't kept track of the AG releases and dates but it would suggest something has recently changed in AG for these crashes to be happening... for over 4 months i didn't have an issue and the only other common denominator appears to be AG.

    Latest BSOD follows:
    Capture.JPG
     
    Last edited: Feb 11, 2018
  10. Pentlands

    Pentlands Beta Tester

    Joined:
    Mar 11, 2014
    Messages:
    43
    And another BSOD, different Check Code this time, 0x3b, something to do with Firewire apparently?

    Capture.JPG