Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: REDACTED on February 04, 2016, 04:48:52 PM
-
Yesterday Avast Free updated from 11.1.2245 to 11.1.2253 and asked me to restart. I just shutdown and restarted today, got an instant Bluescreen:
==================================================
Dump File : 020416-5054-01.dmp
Crash Time : 04.02.2016 14:21:33
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`0782b028
Parameter 3 : 00000000`be200000
Parameter 4 : 00000000`00051136
Caused By Driver : hal.dll
Caused By Address : hal.dll+12a3b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+73c00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\020416-5054-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 354.128
Dump File Time : 04.02.2016 14:22:22
==================================================
Windows 7 Pro SP 1 64-bit
Using the system restore to restore before the Avast update (the system restore tool also showed the affected software, and the list contained only Avast) fixed the BSOD.
Is this a known problem? Or maybe just coincidence and there is still something wrong with my PC/Hardware? Obviously i canceled the update now and will not install it again just to check if the BSOD is reproducable. Should i upload the minidump so someone can tell me if Avast was responsible for the BSOD and maybe Avast can fix the problem?
-
I have the same issue on Windows 10 :
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe001de28c028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000001001136, Low order 32-bits of the MCi_STATUS value.
...
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: svchost.exe
-
Reported to Avast. Since they are in Europe, it may be a while before they'll answer.
-
Try disabling "Enable hardware-assisted virtualization". That solved it for me. :)
I manually updated Avast Free when I read about the Project Zero security hole in Avast. I then rebooted and got a BSOD in Win7 SP1 at boot. Over and over. The error code of 124 is usually a flaky overclock. So I tinkered in the BIOS.
Finally found that disabling virtualization in the BIOS fixed the BSOD, but then I couldn't use my VM's, so that's no good. Found the virtualization option in Avast, disabled that, re-enabled virtualization in the BIOS, and presto. No more crashes. The overclock was and is fine. Avast is just broken again. ::)
I think it's weird this option is even enabled by default, since I don't have any of the functionality installed that uses it, such as the built-in sandbox.
-
Yes, this BSOD is caused by new nested virtualization support in the latest avast. We tested it with vmware workstation 12.x and it worked well. Do you guys use vmware workstation or player? Disabling "Enable hardware-assisted virtualization" should solve this problem.
-
I use Workstation 9.0.0
Please tell me why this option is enabled by default even when I haven't installed any of the Avast tools that would use it?
-
Avast itself uses a hardware virtualization for better protection. In older version, when we detected a user uses virtualbox/vmware/hyper-v/... we automatically disabled this feature, but now we tried to improve it with a nested virtualization. Right now, we're debugging those WHEA BSODs and we hope it will be fixed asap.
-
Avast itself uses a hardware virtualization for better protection. In older version, when we detected a user uses virtualbox/vmware/hyper-v/... we automatically disabled this feature, but now we tried to improve it with a nested virtualization. Right now, we're debugging those WHEA BSODs and we hope it will be fixed asap.
I am also seeing the blue screen with x124 stop code after this upgrade.
I have VMWare installed on this machine but not running when the blue screen happens. I sure hope you guys get this fixed soon.
-
Disabling "Enable hardware-assisted virtualization" should solve this problem.
-
Disabling "Enable hardware-assisted virtualization" should solve this problem.
(http://screencast-o-matic.com/screenshots/u/Lh/1454806340308-13295.png)
-
Thanks guys - another morning of my life down the plughole!
For the record unchecking "enable hardware assisted virtualization" solved the problem for me (I restored to a previous restore point in recovery console to get a boot, but the problem kept coming back, I guess because Avast would then update itself again).
I DO NOT have VMWare installed. I have VirtualBox and also Intel HAXM (required for Android Studio device emulators). The latter was quite tricky - claimed hardware acceleration was unavailable on my machine (wrongly) and refused to install. I had to turn Hyper-V off to get it installed, and it is still turned off. Hopefully this information will give you some clues.
And on another point CAN YOU PLEASE STOP USING THOSE DAMN CAPTCHAS! These things have been useless and unusable for the last decade! And the audio option does not work because Avast itself is blocking the QuickTime plugin!
-
Captchas are a way to prevent Spammers. Good new is that they stop after your third post. :)
-
I have the same problem here in Windows 7 pro 64bit.
After update and restart I had a blue screen.
I uninstalled Avast and all's well.
I tried to install it again, and I got Blue screen during installation.
What should I do?
I don't have those other software isntalled you mention (VMware, virtualbox etc.)
Will there be a fixed version?
I would like to continue using Avast.
-
I have the same problem here in Windows 7 pro 64bit.
After update and restart I had a blue screen.
I uninstalled Avast and all's well.
I tried to install it again, and I got Blue screen during installation.
What should I do?
I don't have those other software isntalled you mention (VMware, virtualbox etc.)
Will there be a fixed version?
I would like to continue using Avast.
Try a clean install:
https://goo.gl/4Ptzkf (https://goo.gl/4Ptzkf)
-
I have the same problem here in Windows 7 pro 64bit.
After update and restart I had a blue screen.
I uninstalled Avast and all's well.
I tried to install it again, and I got Blue screen during installation.
What should I do?
I don't have those other software isntalled you mention (VMware, virtualbox etc.)
Will there be a fixed version?
I would like to continue using Avast.
Try a clean install:
https://goo.gl/4Ptzkf (https://goo.gl/4Ptzkf)
ok, this will help installation.
But once I make the final reboot, won't I get the blue screen again like the first time?
or should I disable that virtualization before I do the reboot?
-
Hopefully not.It's the next logical step.
-
thanks.
unfortunately, although I did all this and after a restart it seemed all well, now, after one day when i shut my pc and started it, the blue screen appeared again.
I tried to uncheck that option in the software, but it says it will take effect after restart, and when i restart, blue screen again.
I really hope there's a new version to fix this.
Until then i should find the old version of Avast,
-
Follow instructions: https://www.avast.com/faq.php?article=AVKB33#artTitle
-
Any news on the BSOD problem? Is it fixed?
I'm still on .2245, but maybe it would be a good idea to update, on the other hand i dont wanna see this BSOD again ...
-
Any news on the BSOD problem? Is it fixed?
I'm still on .2245, but maybe it would be a good idea to update, on the other hand i dont wanna see this BSOD again ...
Did you follow these directions ???
https://forum.avast.com/index.php?topic=182540.msg1289583#msg1289583 (https://forum.avast.com/index.php?topic=182540.msg1289583#msg1289583)
-
Did you follow these directions ???
https://forum.avast.com/index.php?topic=182540.msg1289583#msg1289583 (https://forum.avast.com/index.php?topic=182540.msg1289583#msg1289583)
Yes, i disabled it, then a big red wall of text informed me that without it my system can be infected with malware from the sandbox, because the sandbox isnt secure anymore. Oh well, dunno if thats really what i want, probably better to uninstall Avast then completly? Now i can choose, stick with the old and maybe unsecure Avast version that works, or update to the new version and disable a security feature to open up a security hole. Lose-lose situation. Thats why im asking if there is any progress :/