Author Topic: [fixed] Avast causes Blue Screen after Windows 10 Anniversary Update  (Read 101646 times)

0 Members and 1 Guest are viewing this topic.

Offline anarkii

  • Jr. Member
  • **
  • Posts: 54
Re: Avast causes Blue Screen after Windows 10 Anniversary Update
« Reply #135 on: August 05, 2016, 07:47:36 AM »
Hi, glad to see the problem for this has been found since I reported it a week ago.
I will wait for the new installer, Things are running fine with Windows Defender but I would like to be running Avast again.

With an internet connection, it is safe to use the online installer :)

Greetz, Red.

Hi, thank you, updated using the online installer and all is good once again.
Thanks Red. :)

REDACTED

  • Guest
Re: Avast causes Blue Screen after Windows 10 Anniversary Update
« Reply #136 on: August 05, 2016, 09:02:10 AM »
no troubles any more :)

REDACTED

  • Guest
Re: Avast causes Blue Screen after Windows 10 Anniversary Update
« Reply #137 on: August 05, 2016, 09:11:02 AM »
VT-x might have another name in your Bios. Mine wasn't called VT-x, but "Intel Virtualization Tech" or "Intel Virtualization Technology". Another term used for it is "Vanderpool technology". But maybe your motherboard does not give BIOS access to VT-x. In which case it is probably on by default (if avast crashes for you) and cannot be turned off.

If people want to post their exact motherboard name here, I can help see if there is a setting for you to enable / disable VT-x, even if it is another name.

That way you might be able to try and see if after disabling it, Avast will install and run.

Hi, can you help me? my motherboard does not show VT-x only VT-d the model is gigabyte ga-z170x gaming 3

I checked your motherboard, and it only has settings in the BIOS to change VT-d, not VT-x, unfortunately. But the avast fix is here, so no need to worry.

For those who are unclear, as I understand it, with the new, updated / patched Avast, there is now no need to disable Vt-x in your BIOS. For those who have gigabyte boards that don't support enabling or disabling VT-x (they only show VT-d), it doesn't matter now, the Avast fix addresses this, so no need to change anything in your BIOS.

And again as far as I understand it, you need to either update Avast (and verify that it is the patched version as described above) and then do the anniversary upgrade. Or, alternatively, you can uninstall Avast, perform the upgrade, and then re-install Avast using the updated version, and you should be fine.

I will go and update Avast now, and then re-enable VT-x in my BIOS, just to confirm all is well.

Update: Avast had already patched my system (through program auto-updates), so I re-enabled Intel Virtualization Tech (Vt-x) in my BIOS, rebooted, and voila!

All is working fine now.

Thank you Avast and petr for the speedy fix! Might be time to get out the cheque-book and upgrade to a paid version of Avast  :)
« Last Edit: August 05, 2016, 09:30:29 AM by jsljustin »

Offline bob3160

  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 48512
  • 64 Years of Happiness
    • bob3160 Protecting Yourself, Your Computer and, Your Identity
Re: [fixed] Avast causes Blue Screen after Windows 10 Anniversary Update
« Reply #138 on: August 05, 2016, 03:01:50 PM »
"Thank you Avast and petr for the speedy fix! Might be time to get out the cheque-book and upgrade to a paid version of Avast  "
Hurry Up, make their day.
Free Security Seminar: https://bit.ly/bobg2023  -  Important: http://www.organdonor.gov/ -- My Web Site: http://bob3160.strikingly.com/ - Win 11 Pro v22H2 64bit, 16 Gig Ram, 1TB SSD, Avast Free 23.5.6066, How to Successfully Install Avast http://goo.gl/VLXdeRepair & Clean Install https://goo.gl/t7aJGq -- My Online Activity https://bit.ly/BobGInternet

REDACTED

  • Guest
Re: Avast causes Blue Screen after Windows 10 Anniversary Update
« Reply #139 on: August 05, 2016, 05:51:23 PM »
Same problem:
Win10 x64
i7 6700k
960gtx
SM951 NVME 256GB

I don't want to disable Virtualization, so I'll just wait for an update.

Fixed for me as well. Good job.

Offline petr.chytil

  • Quality Assurance Director
  • Avast team
  • Full Member
  • *
  • Posts: 124
Re: [fixed] Avast causes Blue Screen after Windows 10 Anniversary Update
« Reply #140 on: August 05, 2016, 05:59:43 PM »
Big thank you to everyone for your help!

If you are interested in a more detailed report, please see this post:
https://forum.avast.com/index.php?topic=189503.0

Have a great weekend,
Petr

Offline Ch3vr0n

  • Jr. Member
  • **
  • Posts: 35
Re: [fixed] Avast causes Blue Screen after Windows 10 Anniversary Update
« Reply #141 on: August 05, 2016, 07:26:43 PM »
took the plunge earlier yesterday, though did disable all shield just to be safe. 30min later, back up & running 1607 running AIS

REDACTED

  • Guest
Re: [fixed] Avast causes Blue Screen after Windows 10 Anniversary Update
« Reply #142 on: August 05, 2016, 08:43:24 PM »
Big thank you to everyone for your help!

If you are interested in a more detailed report, please see this post:
https://forum.avast.com/index.php?topic=189503.0

Have a great weekend,
Petr

Many many thanks to you and all the staff !!! ;)

Offline Ch3vr0n

  • Jr. Member
  • **
  • Posts: 35
Re: [fixed] Avast causes Blue Screen after Windows 10 Anniversary Update
« Reply #143 on: August 07, 2016, 05:05:59 AM »
@petr.chytil this may not be fully fixed!!! i tried updating my laptop and i'm still getting issues. I checked the drivers folder, and there were 2 awsvmm files with that weird numeric extension. After a reboot 1 was gone, but i'm still having one. The actual file version does end with .4. HOWEVER i noticed a possible 2nd problematic driver!!! I have a duplicate for aswSP.sys as well, currently named aswsp.sys.146706085400002 and still that second aswvmm.sys.147024167892104. I tried manual delete but windows won't let me and multiple reboots nor re-running program update will delete the files.

For the record here this is NOT a skylake model, far from it. This is an "old" laptop: Model Sony Vaio VGN-AW11M

please advise.
« Last Edit: August 07, 2016, 05:16:46 AM by Ch3vr0n »

REDACTED

  • Guest
Re: [fixed] Avast causes Blue Screen after Windows 10 Anniversary Update
« Reply #144 on: August 09, 2016, 04:21:25 PM »
Hello everyone. I have some questions: Do I need to delete aswvmm.sys. 147014374867104 for myself, after standard uninstallation of Avast Free Antivirus? Is it necessary? And can I install Anniversary Update without problems right now?