Latest avast with latest virtualbox cause blue screen of death?

Avast Free Antivirus / Premium Security
1

Yesterday i updated my avast program to 17.5.2302 (build 17.5.3559.0). (windows 7)

After a couple hours i started the lastest version of virtualbox.

Next i tried running an existing virtual machine.

I started up fine but after a few minutes both of my monitors got scrambled images and my pc speakers beeps constantly.

A few restarts and retries later i now also get a blue screen after a while after starting a virtual machine.

I have another pc with the same hardware and software configuration without avast updated and virtualbox virtual machines are rock stable on that pc.

Does somebody have the same problems?

I ask this because i want to see if i can exclude avast as the source of the problem.

2

I’m also having similar problem running VMware.
After I start virtual machine, windows suddenly shuts down.

This started right after the latest Avast update…

3

Is hardware virtualization disabled ?

4

What is your CPU and OS configuration? Can you provide the dump file? Also please specify 32/64 in case of OS.

5

CPU: RYZEN 1700X with AMD-V turned on
MEM: CMK16GX4M2A2666C16 (Tried running on 2133MHz but no luck)
OS: Windows 10 Pro 64Bit
Virtual machine:Ubuntu 16.04 LTS 64Bit

I don’t get any BSoD or dump file from Windows, even though I turned off automatic restart.
All I get was Kernel-Power 41 error on windows log…

6

This should fix the problem.
I too noticed that during last beta they have changed something in terms of virtualization. My VMware reported Intel VT-x was disabled in BIOS. I did not change BIOS settings recently.

7

I don’t see that option on mine…

I am running Version 17.5.2302(Build 17.5.3559.0) right now.

8

I’ve disabled the “enable hardware-assisted visualization” option as @Eddy asked about it. And it seems to solve the problem, I’ve been running a virtual machine for 10 minutes without a crash.

Although a bit worried about all the warnings avast displays underneath that option ::slight_smile:

@Spec8472 cpu is a i7 920
EIST, XDBIT, VT and VT-D on
Windows 7 64 bit
Virtual machine is a centos 6.8 64 bit

No dumps cause i pressed the power off button quickly after a crash, all that beeping, fans spinning up and harddisk rattling scares me a bit.

9

Nested virtualization is not supported for AMD CPUs for now. I have found the problem, will be fixed soon.

10

Dang, I’m good ;D ;D ;D

11

I’ve also turned off “Enable hardware-assisted virtualization”

Seems to be working fine now!

12

got the same issue right after update (on virtualbox and vmware). host win 10 64bit, core i5. disabling the hardware-assisted virtualization solves the problem - but still this is not a good solution.

vmware guest win 7: “Binary translation is incompatible with long mode on this platform. Long mode will be disabled in this virtual environment and applications requiring long mode will not function properly as a result. See http://vmware.com/info?id=152 for more details.”

virtualbox guest win xp:

https://i.paste.pics/1T274.png

13

same problem after update to latest avast and virtualbox

https://habrastorage.org/web/690/86f/34a/69086f34a4f84a66a29efc96308cf5a6.jpg

14

A microupdate is already scheduled.

15

Thanks for everyone, after 2 years the problem happens for me and disable AV the Virtual Machines works perfectly, no BSOD, I’ll try disable “Enable Hardened Mode” to see if this solve the issue without disable AV.

Regards

16

Yes ,
an other same report with the latest avast version in the French section (VM started → BSOD aswbidsdriver.sys)
https://forum.avast.com/index.php?topic=228361.0

17

Hello everyone,

as Chris just wrote above, I met a similar issue. I use Avast Free edition with Windows 10 Home. and since the last update I cannot run any VM anymore without getting a Blue screen error wth the SYSTEM_SERVICE_EXCEPTION stop code.

To summarize my diagnosis, I already checked the Hyper-V and W10 Home incompatibility hypothesis, I also unplugged my last installed hardware and disabled the associated softwares auto-start.

And recently, I made a test, not with VirtualBox or VMware, but with Bluestacks (Android virtual device, FYI), the diagnosis data returned that a drivers and/or the Avast’s suspect behavior agent service failed and caused the issue.

I tried to start my VMs without this agent enabled, and then my system crashed and restarted without any blue screen error (like a hard reset actually).
Today, I removed Avast from my computer and my VMs worked perfectly, even with several VMs reboots, I also managed to install Fedora x64 on a new VM.

I reinstalled Avast and a new blue screen confirmed my hypothesis but I have no data to prove it.
Check chris’ hypertext link for more details.

Thanks for your attention.

18

avast developers should seriously consider disabling Hardware Virtualization option by default

it has been causing most incompatibility issues reported throughout the years

since I disabled the option, I have not had any compatibility problem for years

19

Bump, I recently updated avast and WhoCrashed? found that the Virtualization Driver used by Avast was messing with VMware and VirtualBox.

20

Hi,

the “nested virtualization” feature, which seems to be causing trouble to some of you will be disabled by default in next version. This will solve incompatibility/slowness of VMWare/Virtualbox(including clones like Nox/BlueStack) VMs on some systems.