BSOD EXCEPTION from Sbiedrv.sys caused by AVG

Discussion in 'Sandboxie (SBIE Open Source) Plus & Classic' started by waking, Jul 22, 2022.

  1. waking

    waking Registered Member

    Joined:
    Jan 25, 2016
    Posts:
    176
    I have been using Sandboxie intermittently for years,
    and have had it installed without issues on a number
    of PCs and versions of Windows. Most recently I have
    been using it on a PC with Win10 21H2 and AVG Internet
    Security without issues for the past four months, since
    I switched to AVG from another AV. Currently AVG is
    ver 22.6.3242

    I regularly run an AVG Smart Scan manually every 24 hrs
    or so. All went well until a few days ago, circa July
    20 and since. For some reason it now always results in
    a BSOD with a SYSTEM SERVICE EXCEPTION from Sbiedrv.sys
    which causes a system restart.

    When it first occurred I was using SB Classic x64 v5.55.22,
    but have since tried SB Classic x64 v5.56.3 and
    SB Plus x64 v1.1.3 with the same problem occurring with
    all versions.

    Presumably this is caused by some change that AVG made
    during one of its "minor" updates. If I remove AVG and
    use Windows/Microsoft Defender there are no problems
    with SB. I can run Defender scans, as well as on-demand
    scans using Malwarebytes (non-resident) and Trend Micro
    Housecall.

    With AVG installed I also got the BSOD from Sbiedrv.sys
    when running a Malwarebytes on-demand scan.

    As I have more than a year and a half left on my AVG
    subscription I am reluctant to remove it permanently.
    So I must abandon SB at this time.

    I have Windows minidumps from the system crashes if
    they are any use.
     
  2. DavidXanatos

    DavidXanatos Developer

    Joined:
    Sep 6, 2006
    Posts:
    2,327
    Location:
    Viena
    hello, I'm sorry to h ear that, could you please provide the crash dumps you have collected
    Can this issue be reproduced with the free avg version? Or what exact AVG product do you have installed?
     
  3. waking

    waking Registered Member

    Joined:
    Jan 25, 2016
    Posts:
    176
    I'll give you a Zip file with several dumps in it, all as a result of this problem AFAIK. What is the best way to get them to you?

    While testing ways around this, I uninstalled AVG and then later reinstalled using the online installer for the latest version of AVG Internet Security. When it asked for an activation code I chose the option for a free 30 day trial. With that running and the default settings the same problem occurred.

    Later I inserted my activation code to resume my subscription, and restored my settings. (After removing SB.)

    AVG IS About.jpg
     
  4. DavidXanatos

    DavidXanatos Developer

    Joined:
    Sep 6, 2006
    Posts:
    2,327
    Location:
    Viena
    best is to send the dumps by email, my email address can be found in my github profile also please write down to which driver versions the dumps belong
     
  5. DavidXanatos

    DavidXanatos Developer

    Joined:
    Sep 6, 2006
    Posts:
    2,327
    Location:
    Viena
  6. DavidXanatos

    DavidXanatos Developer

    Joined:
    Sep 6, 2006
    Posts:
    2,327
    Location:
    Viena
    In my windows 10 Vm 21h2 i installed avg_internet_security_setup.exe and sandboxie+ v1.2.5 and run a smart scan and it finished fine.
    What shoudl i do to make i crash should i have active processes in a box?
     
  7. waking

    waking Registered Member

    Joined:
    Jan 25, 2016
    Posts:
    176
    David -

    FYI - Reports of users getting BSODs from AVG and Avast after a recent update are starting to appear in the forums. Different drivers, etc. appear to be getting affected. See for example:

    BSOD every time Avast does a smart scan

    https://forum.avast.com/index.php?topic=320468.0


    BSOD with recent update

    https://forum.avast.com/index.php?topic=320457.0
     
  8. henryg1

    henryg1 Registered Member

    Joined:
    Jun 14, 2020
    Posts:
    410
    Location:
    uk
    AVG just updated but thankfully ok for me
     
  9. DavidXanatos

    DavidXanatos Developer

    Joined:
    Sep 6, 2006
    Posts:
    2,327
    Location:
    Viena
    The problem is that currently I am unable to reproduce this crash, in my test VM using free/trail version of this software.
    So I need one or possible more then one volunteer to debug the issue with, someone willing to enable test signing ode and try out a couple test drivers, providing sumps etc.

    This may take quite a few tries and some time, but if it works out to fix the issue the volunteers would be rewarded for their time and effort each with a HUGE Supporter Certificate that never expires.

    So who wants to help?
     
  10. waking

    waking Registered Member

    Joined:
    Jan 25, 2016
    Posts:
    176
    David -

    My impression - based in part on the threads I referenced - is that
    this is an Avast/AVG issue which is affecting different drivers on
    different systems. While not affecting any drivers on other systems
    apparently. If that's the case then I think you should defer trying
    to identify an issue in SB, as it doesn't appear to be a problem
    which is specific to SB.

    I am communicating with the Avast team via the Avast forum, and
    will be retrying the combo of AVG Smart Scan with SB installed
    as I am advised to do so by their developers.
     
  11. waking

    waking Registered Member

    Joined:
    Jan 25, 2016
    Posts:
    176
    Avast support posted a reply in the Avast thread I've been following
    and participating in, advising us to update the signature file(s) to
    version VPS 20220726-6

    After doing so, I reinstalled Sandboxie Classic x64 5.56.3 and started
    it. I then ran an AVG Smart Scan and it ran to a successful completion
    with no BSODs. I also ran Malwarebytes and Trend Micro Housecall on-demand
    scans with AVG IS realtime protection active. No issues were encountered.

    At the moment it appears that Avast/AVG have resolved the BSOD issues
    happening with some drivers on some systems. Whether it was done via
    code correction or code regression only their developers know.

    So it appears that no further investigation re Sandboxie BSODs during
    AVG scans is needed (at this time). Thanks for the prompt willingness
    to seek the cause and a solution.
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.