BSOD caused by Avast

Avast Free Antivirus / Premium Security
1

hello

Since a month ago a weird BSOD happens with Avast at startup just before entering desktop Driver IRQL Not Less or Equal then system restarts and works normally

at another forum according to the DUMP file it caused by aswVmm.sys

Could it be it conflicts with Windows SANDBOX ? Have that enabled

4: kd> lmvm aswVmm
Browse full module list
start             end                 module name
fffff806`79600000 fffff806`79676000   aswVmm   T (no symbols)       
    Loaded symbol image file: aswVmm.sys
    Image path: \SystemRoot\system32\drivers\aswVmm.sys
 Image name: aswVmm.sys
    Browse all global symbols  functions  data  Symbol Reload
 Timestamp:        Tue Jul 14 10:08:13 2026 (6A55E05D)
    CheckSum:         00081CB9
    ImageSize:        00076000
    Mapping Form:     Loaded
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

would post the full dump files but no links allowed here

2

checked this aswVmm.sys , created in 2018 but modified recently in 21st July 2026 when this BSOD issues became more common , it’s possible it conflicts with HYPER V that it occasionally creates this BSOD , as mentioned I had Windows Sandbox enabled

3

You can use the free tool Bluescreenview to analyze dump files in more detail. Maybe it can shed more light on the matter.

4

^ wanted to upload them directly so the Avast team can look themselves but no links and no attachment “ Sorry, new users can not upload attachments.”

really I had Windows sandbox enabled and believe since the last Avast updated it causes this occassional BSOD with aswVmm.sys according to who analyzed them in another forum

5

Edit this doesn’t fall under the area I was thinking about False Positive/Negative. But that isn’t the case.
If you reply to a couple more posts, doesn’t have to be much.

I think you should be able to link to the file after 3-5 posts/replies and take you out of the newbie category (this is an anti spam measure)..

6

I haven’t forgotten about your issue, did some searching.

Try reading this Avast link

This is something else you could check.

7

Hi user7988, the aswVmm kernel driver is a framework component used by other installed Avast drivers. The Hyper-V (Windows Sandbox) incompatibility is unlikely. Can you please provide a diagnostic package from the product? You can use support tool: How to submit a support file using the Avast Support Tool | Avast Kernel mini-dumps should be gathered by the tool as well. Please provide the resulting “File ID” so I can identify your package.

Thank you

8

I disabled windows sandbox and no more BSOD so far

9

this rule about newbies not being able to post attachments is really stupid

anyway here the last 3 dump files when it BSOD just before entering Desktop and then restarted and it booted properly , had Sandbox enabled since 2025 but since july it started to have this issue it became much more often after I had Avast client update on 21st july , don’t have safeboot or TPM enabled and no fast startup either DUMP FIles : file.kiwi/e0c7ca30#zx5-R6nJM2EDa6HrZh3_kQ with at front h.t.t.p.s.:././.

1 Like
10

It is an anti spam measure, though on occasion the spammers get through and have to be dealt with manually..

That said I don’t know if this option would help in your plight (enabling Debug Logging).

b10257
b10257850Ă—567 124 KB

11

All three dumps shows same issue in Microsoft’s Hyper-V/VHD stack and it is unrelated to Avast AV. Looks like MS Windows Sandbox issue similar to [Bug]: Sandbox crashes Windows 24H2 since the February 2025 security updates · Issue #84 · microsoft/Windows-Sandbox · GitHub
It matches your dumps perfectly, crashes/freezes 60–120 seconds after boot. Microsoft acknowledged an integrated scheduler defect, internal bug 56225026. The issue remains open.

Also interesting: exactly same crash signature from 3 years ago: BSOD during windows startup · GitHub

1 Like
12

Ok if that is the case I am sorry to the Avast team and good that it’s not related to them !! gladly that the issue it’s at least gone now by disabling that thing

you can’t imagine how much stress such a thing can causes since I did multiple times DSIM plus SFC, chkdsk , full system scan with Avast , all with no issues and then you think it can be expensive Hardware failures , did RAM tests and no results , full 100% CPU usage with Handbrake (since I am not gamer can’t use those) and nothing either so you left wondering if maybe some motherboard and silently failing PSU and specially bad in this exceisvly overpriced hardware times

1 Like