I had a similar issue but didn't touch Avast while attempting fixes. Stable for 6h now so I'll post my findings for future reference.
How I got into the mess:
I run Windows Update which installed
KB4507004
KB4507449
KB4506997
After this I performed a disc cleanup while copying 200-300G at the same time (100M/s disk speed glowing red). Since this is my server I often let it handle heavy tasks regardless of how inefficient it is to run much disc activity at once.
At some point I realized the copying from my main machine had stopped and lo and behold, the server had booted.
While investigating it booted again... and again... and again.
At this point I shut down vmware autorunning my sql server virtual machine not to destroy it.
And no more BSOD. Huh?
I doubt system stress was the reason although the first crashes were all MULTIPLE_IRP_COMPLETE_REQUESTS (and it's over 10 years since vmware had these problems before - quick check of the forum). I just haven't had crashes before even when copying terabytes between ssd's and normal HDD's. Also, everything is just fine, until I start a virtual machine (no, I didn't start another just to check if the important one had become corrupt).
Run the virtual machine and within minutes, BSOD. Tried this a few times. Ok, vmware (player) is causing a serious problem at least with this virtual machine.
Uninstalled the KB's Windows Update added. Start the virtual machine and BSOD.
Downloaded the newest version of Vmware Player, rebooted, start vm... bang.
At this point BSOD's are not even getting to the login screen in the vm anymore, from the logs I can see vmware restoring at 1%...5%...93% and bang.
Uhum.
Run sfc /scannnow and disk checking on the server.
Virtual machine on... bang.
NOT GOOD.
Since it was around midnight at this point I called it a day. Since I spent like 8h resolving this with long breaks I doubt just waiting would have helped. Just mentioning it since I took a longer break going to sleep.
Next day I copied the virtual machine to my main machine, where it started nicely. Run sfc and disk checking and rebooted a few times with shutdowns, everything just run fine.
Transferred the vm back to my server, started it... crossed my fingers... and it has stayed up since.
Guess I'm not installing those Windows updates again in a while although removing them didn't help.
Here are the 3 BSOD's that were occurring (IRP's was most common at the start), just copied some here:
On Wed 17/07/2019 18:32:33 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\071719-47673-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
On Wed 17/07/2019 16:34:58 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x44 (0xFFFFFA800DCA09D0, 0xEC0, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
Dump file: C:\Windows\Minidump\071719-46550-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
On Wed 17/07/2019 16:24:01 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x44 (0xFFFFFA800726C010, 0xEC0, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
Dump file: C:\Windows\Minidump\071719-50903-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
On Wed 17/07/2019 16:05:48 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x44 (0xFFFFFA800A32B010, 0xEC0, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
Dump file: C:\Windows\Minidump\071719-50279-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
On Wed 17/07/2019 15:34:53 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0x80000004, 0xFFFFF80003255008, 0xFFFFF880037B0F10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\071719-56955-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
I have a copy of the original vm that was causing all this. I probably should try to start it once to see if it still bsods but I kinda don't want to end up in a mess again.
In case vmware support sends me a request to "do this, then this to make sure you get everything possible logged" I might do it just to find a root cause for this. After taking full partition backups of the entire server so not a small operation. But eventually I will toss the "faulty" vm. Knowing me that might be 5 years from now.
Ok, pretty lengthy and somewhat detailed. But as other people have had problems, avast or not, it's better to have more info if this is something new and common.
