Avast WEBforum

Avast Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Wahnfried1883 on August 03, 2016, 01:03:56 AM

Title: [fixed] Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Wahnfried1883 on August 03, 2016, 01:03:56 AM
Hi all!

First of all, the Windows 10 Anniversary Update failed two times with BSOD today, so I uninstalled Avast and the Anniversary Update went fine. Next I tried to install Avast Free Antivirus Version 12.2.2276, and during the installation process my PC re-booted and I got a BSOD (error: system thread exception not handled) every time as result. Finally, I found out that Avast is creating a file named "aswvmm.sys.147017696412504" in "C:\Windows\system32\drivers" what seemed suspect to me. So I deleted manually this file as well as the "aswvmm.sys" and my PC booted fine. Next step was deleting the entire Avast Installation by the tool "AvastClear" and now everything is fine, except the fact I cannot use Avast anymore, so I think the suspicious "aswvmm.sys.147017696412504" created by the installation process is the culprit here.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Rednose on August 03, 2016, 01:50:03 AM
Hi wahnfried1883, welcome to the forum :)

Please submit a support file using the Avast Support Tool https://www.avast.com/faq.php?article=AVKB33
In step 7 select " Full dumps ".

When you have finished, post the Support Package ID in your next reply.

Greetz, Red.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Rednose on August 03, 2016, 01:59:43 AM
Of course I could have asked for just the c:\windows\memory.dmp file , but maybe the procedure provides more information.
I am not sure in this case.

Greetz, Red.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Wahnfried1883 on August 03, 2016, 02:43:52 AM
Hi Red,

I submitted a support file using the Avast Support Tool as you requested. The support ID is "2CHIT".  By the way, Avast is not fully installed yet, because of the described problem, so I hope there are no problems using the Support tool.

Greetings, Wahnfried
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Darecki2k on August 03, 2016, 04:06:11 AM
I have excaly the same problem. Please let me know as soon as you have the sollution. Poor job on not solving this during beta tests of anniversary edition, that ran for months ...
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: misterp28516 on August 03, 2016, 05:54:50 AM
I also had the same problem.  The only way I could install the Anniversary Update was to completely uninstall Avast and then run the Avastclear utility.  Otherwise, I just bootlooped with the BSOD with the system thread not handled exception error.  Yuck.

Computer is running fine now, except that I have no antivirus protection.  Windows Defender will not even run because it still thinks Avast is on my computer.  My guess is there's still a line in the registry somewhere, but who knows.

Please help.  This is a real problem.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Scott39 on August 03, 2016, 06:04:27 AM
Confirmed...same issue here.  Updated to Windows 1607 (Anniversary Update).  Ran fine with Avast Internet Security the first boot.  But after rebooting, BSOD.  SYSTEM_THREAD_EXCEPTION_NOT_HANDLED.  The only option was to restore to previous point, go into Safe Mode, and uninstall Avast for the time being.  I hope this will be fixed soon as I am also running with only 'Windows Defender' as my protection.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Texas Kelly on August 03, 2016, 06:21:48 AM
+1. Happened on my Acer Aspire R14 laptop after both an in-place upgrade and then again after I did a fresh re-install from the USB stick I created with Microsoft's media creation tool. Weirdly, my custom-built desktop did not have the same problem - it failed to recognize Avast after the in-place upgrade, but I was able to uninstall and re-install Avast on that machine with no problems whatsoever. (I'm glad the issue happened on the laptop, not the desktop - the desktop is my daily machine, and I only use the laptop when I travel and I don't keep any real data on it, so a rebuild of the machine won't be too painful.)

I suspect that there is a conflict between the aswvmm.sys file mentioned by the thread creator and a device driver that my Acer laptop uses. No idea which device could be the culprit, but it's definitely not an instance of the driver being out of date, because I always update all drivers/BIOS before I do a system pack OS upgrade.

Very disappointed with Avast; this is something that should have been caught during beta testing of the Anniversary Edition.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: petr.chytil on August 03, 2016, 07:38:01 AM
Hi all,
could you please post a specific description of your HW and state whether do you use 32b or 64b version of Windows 10 Anniversary?
Thank you in advance,
Petr
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Scott39 on August 03, 2016, 07:54:03 AM
Here is a copy from Belarc Advisor.

Windows 10 Home (x64) Version 1607 (build 14393.10)
Install Language: English (United States)
System Locale: English (United States)
Installed: 8/2/2016 5:04:46 PM
Servicing Branch: Current Branch (CB)
Boot Mode: Legacy BIOS in UEFI (Secure Boot not supported)
System Model
Enclosure Type: Desktop
Processor a
3.20 gigahertz Intel Core i5-6500
256 kilobyte primary memory cache
1024 kilobyte secondary memory cache
6144 kilobyte tertiary memory cache
64-bit ready
Multi-core (4 total)
Not hyper-threaded
Main Circuit Board b
Board: ASRock H170 Pro4S
Serial Number: M80-62004600034
Bus Clock: 100 megahertz
UEFI: American Megatrends Inc. P1.80 01/22/2016
Drives
255.53 Gigabytes Usable Hard Drive Capacity
140.92 Gigabytes Hard Drive Free Space

ATAPI iHAS124 W [Optical drive]

aSsmnu gSS D59 0RP O52G6 B [Hard drive] -- drive 0, s/n 2SLGXNH0066934 Y, rev B1Q0XB7X, Not SMART
Memory Modules c,d
16318 Megabytes Usable Installed Memory

Slot 'ChannelA-DIMM0' has 8192 MB
Slot 'ChannelA-DIMM1' is Empty
Slot 'ChannelB-DIMM0' has 8192 MB
Slot 'ChannelB-DIMM1' is Empty

It doesn't get it right, but the hard drive is an M.2 Samsung 950 PRO
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Milos on August 03, 2016, 09:28:49 AM
Hello,
regarding the HDD name. Yes, there are switched bytes in pairs (I suspect storing word value (2 Bytes) in big endian and reading in little endian)) correct name should be "Samsung SSD 950 PRO 256GB".

Milos
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Shaun985 on August 03, 2016, 09:47:21 AM
Same problem here, update failed to install due to "system exception thread not handled".  Are you guys sure this is caused by Avast?  Using Windows 10 Home 64bit, fresh install but updated to 1511, latest version of Avast.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: THE BIG ONE on August 03, 2016, 10:32:18 AM
Identical issue here with a client's notebook using a paid subscription of Avast Internet Security after recent Windows build update. Brand new high end ASUS GL752VW system. I've been managing their systems for quite some time now as well as a few custom built systems I've made. This issue has only occurred on the newer ASUS notebook; obviously a conflict. Windows 10 Build 14393.10 (AE) results in "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED" BSOD on each boot. Removing the Avast asw*.sys files from \Windows\System32\Drivers results in system booting successfully. Updated BIOS, Onboard GPU, Dedicated GPU, Audio, LAN, WAN, Motherboard Chipset, Bluetooth, SATA drivers, etc and Avast still causes a BSOD reboot loop of death. Removed from client's PC for now until this is resolved.

Unfortunately, I deleted all the crash dumps prior to seeing this thread; however, I did debug a couple. Sadly, debugging the dumps did not narrow down the conflict with Avast's driver files. Here are the results:

Quote
BugCheck 7E, {ffffffffc000001d, fffff80309dd2109, ffffa38111673518, ffffa38111672d40}

Probably caused by : ntkrnlmp.exe ( nt!SwapContext+a9 )

Followup:     MachineOwner
---------

6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff80309dd2109, The address that the exception occurred at
Arg3: ffffa38111673518, Exception Record Address
Arg4: ffffa38111672d40, Context Record Address

Debugging Details:
------------------


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  14393.0.amd64fre.rs1_release.160715-1616

DUMP_TYPE:  1

BUGCHECK_P1: ffffffffc000001d

BUGCHECK_P2: fffff80309dd2109

BUGCHECK_P3: ffffa38111673518

BUGCHECK_P4: ffffa38111672d40

EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP:
nt!SwapContext+a9
fffff803`09dd2109 0fc729          xsaves  [rcx]

EXCEPTION_RECORD:  ffffa38111673518 -- (.exr 0xffffa38111673518)
ExceptionAddress: fffff80309dd2109 (nt!SwapContext+0x00000000000000a9)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT:  ffffa38111672d40 -- (.cxr 0xffffa38111672d40)
rax=000000000000001c rbx=ffffa38111280180 rcx=ffffa38111673c40
rdx=0000000000000000 rsi=ffffa3811128ccc0 rdi=ffffe100edc0a040
rip=fffff80309dd2109 rsp=ffffa38111673750 rbp=000000edbd9bbfff
 r8=0000000000000003  r9=0000000000000028 r10=0000000000000001
r11=00000000000003f8 r12=00000000000003f8 r13=0000000000000001
r14=ffffe100edc0a048 r15=0000000000000000
iopl=0         nv up ei pl zr na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210247
nt!SwapContext+0xa9:
fffff803`09dd2109 0fc729          xsaves  [rcx]
Resetting default scope

CPU_COUNT: 8

CPU_MHZ: a20

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  System

CURRENT_IRQL:  2

ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

EXCEPTION_CODE_STR:  c000001d

ANALYSIS_SESSION_HOST:  TBO

ANALYSIS_SESSION_TIME:  08-03-2016 04:27:45.0753

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

BAD_STACK_POINTER:  ffffa38111673750

LAST_CONTROL_TRANSFER:  from fffff80309dd1da6 to fffff80309dd2109

FAILED_INSTRUCTION_ADDRESS:
nt!SwapContext+a9
fffff803`09dd2109 0fc729          xsaves  [rcx]

STACK_TEXT: 
ffffa381`11673750 fffff803`09dd1da6 : ffffe100`e8fe6060 fffff803`09ca207a ffffe100`ea700000 00000000`00269faf : nt!SwapContext+0xa9
ffffa381`11673790 fffff803`09cbccdc : 00000000`00000000 00000000`00000001 00000000`00000502 fffff803`09d1c897 : nt!KiSwapContext+0x76
ffffa381`116738d0 fffff803`09ce9288 : ffffe100`edc0a040 fffff803`00000000 ffffe100`edc0a048 fffff803`09ce9bba : nt!KiSwapThread+0x17c
ffffa381`11673980 fffff803`0a0ac684 : ffffe100`edc0a600 00000000`00000000 00000000`00000000 ffffe100`edc0a040 : nt!KeTerminateThread+0x17c
ffffa381`11673a10 fffff803`0a0c2c56 : ffffe100`00000000 ffffe100`edc0a040 00000000`00000000 ffffe100`e8ea7040 : nt!PspExitThread+0x328
ffffa381`11673b50 fffff803`09d1f4bd : ffffe100`edc0a040 00000000`00000080 fffff80a`de12e590 ffffe100`edc0a040 : nt!PspTerminateThreadByPointer+0x96
ffffa381`11673b90 fffff803`09dd2456 : fffff803`09fc5180 ffffe100`edc0a040 fffff803`09d1f47c 00000000`00000000 : nt!PspSystemThreadStartup+0x41
ffffa381`11673be0 00000000`00000000 : ffffa381`11674000 ffffa381`1166d000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


THREAD_SHA1_HASH_MOD_FUNC:  ea0e8700cafffeab3340e261e2240411c3be9ab4

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  98688cedda0ef7027ba1a79a4d0e8683c39508a6

THREAD_SHA1_HASH_MOD:  cb5f414824c2521bcc505eaa03e92fa10922dad8

FOLLOWUP_IP:
nt!SwapContext+a9
fffff803`09dd2109 0fc729          xsaves  [rcx]

FAULT_INSTR_CODE:  eb29c70f

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!SwapContext+a9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  578998f1

IMAGE_VERSION:  10.0.14393.0

STACK_COMMAND:  .cxr 0xffffa38111672d40 ; kb

BUCKET_ID_FUNC_OFFSET:  a9

FAILURE_BUCKET_ID:  AV_STACKPTR_ERROR_BAD_IP_nt!SwapContext

BUCKET_ID:  AV_STACKPTR_ERROR_BAD_IP_nt!SwapContext

PRIMARY_PROBLEM_CLASS:  AV_STACKPTR_ERROR_BAD_IP_nt!SwapContext

TARGET_TIME:  2016-08-03T08:01:00.000Z

OSBUILD:  14393

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE: 

USER_LCID:  0

OSBUILD_TIMESTAMP:  2016-07-15 22:16:17

BUILDDATESTAMP_STR:  160715-1616

BUILDLAB_STR:  rs1_release

BUILDOSVER_STR:  10.0.14393.0.amd64fre.rs1_release.160715-1616

ANALYSIS_SESSION_ELAPSED_TIME: ae2

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_stackptr_error_bad_ip_nt!swapcontext

FAILURE_ID_HASH:  {79bc9c3c-9f59-2583-44ac-cf3dcaa205fc}

Followup:     MachineOwner
---------

6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff80309dd2109, The address that the exception occurred at
Arg3: ffffa38111673518, Exception Record Address
Arg4: ffffa38111672d40, Context Record Address

Debugging Details:
------------------


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  14393.0.amd64fre.rs1_release.160715-1616

DUMP_TYPE:  1

BUGCHECK_P1: ffffffffc000001d

BUGCHECK_P2: fffff80309dd2109

BUGCHECK_P3: ffffa38111673518

BUGCHECK_P4: ffffa38111672d40

EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP:
nt!SwapContext+a9
fffff803`09dd2109 0fc729          xsaves  [rcx]

EXCEPTION_RECORD:  ffffa38111673518 -- (.exr 0xffffa38111673518)
ExceptionAddress: fffff80309dd2109 (nt!SwapContext+0x00000000000000a9)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT:  ffffa38111672d40 -- (.cxr 0xffffa38111672d40)
rax=000000000000001c rbx=ffffa38111280180 rcx=ffffa38111673c40
rdx=0000000000000000 rsi=ffffa3811128ccc0 rdi=ffffe100edc0a040
rip=fffff80309dd2109 rsp=ffffa38111673750 rbp=000000edbd9bbfff
 r8=0000000000000003  r9=0000000000000028 r10=0000000000000001
r11=00000000000003f8 r12=00000000000003f8 r13=0000000000000001
r14=ffffe100edc0a048 r15=0000000000000000
iopl=0         nv up ei pl zr na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210247
nt!SwapContext+0xa9:
fffff803`09dd2109 0fc729          xsaves  [rcx]
Resetting default scope

CPU_COUNT: 8

CPU_MHZ: a20

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  System

CURRENT_IRQL:  2

ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

EXCEPTION_CODE_STR:  c000001d

ANALYSIS_SESSION_HOST:  TBO

ANALYSIS_SESSION_TIME:  08-03-2016 04:29:08.0146

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

BAD_STACK_POINTER:  ffffa38111673750

LAST_CONTROL_TRANSFER:  from fffff80309dd1da6 to fffff80309dd2109

FAILED_INSTRUCTION_ADDRESS:
nt!SwapContext+a9
fffff803`09dd2109 0fc729          xsaves  [rcx]

STACK_TEXT: 
ffffa381`11673750 fffff803`09dd1da6 : ffffe100`e8fe6060 fffff803`09ca207a ffffe100`ea700000 00000000`00269faf : nt!SwapContext+0xa9
ffffa381`11673790 fffff803`09cbccdc : 00000000`00000000 00000000`00000001 00000000`00000502 fffff803`09d1c897 : nt!KiSwapContext+0x76
ffffa381`116738d0 fffff803`09ce9288 : ffffe100`edc0a040 fffff803`00000000 ffffe100`edc0a048 fffff803`09ce9bba : nt!KiSwapThread+0x17c
ffffa381`11673980 fffff803`0a0ac684 : ffffe100`edc0a600 00000000`00000000 00000000`00000000 ffffe100`edc0a040 : nt!KeTerminateThread+0x17c
ffffa381`11673a10 fffff803`0a0c2c56 : ffffe100`00000000 ffffe100`edc0a040 00000000`00000000 ffffe100`e8ea7040 : nt!PspExitThread+0x328
ffffa381`11673b50 fffff803`09d1f4bd : ffffe100`edc0a040 00000000`00000080 fffff80a`de12e590 ffffe100`edc0a040 : nt!PspTerminateThreadByPointer+0x96
ffffa381`11673b90 fffff803`09dd2456 : fffff803`09fc5180 ffffe100`edc0a040 fffff803`09d1f47c 00000000`00000000 : nt!PspSystemThreadStartup+0x41
ffffa381`11673be0 00000000`00000000 : ffffa381`11674000 ffffa381`1166d000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


THREAD_SHA1_HASH_MOD_FUNC:  ea0e8700cafffeab3340e261e2240411c3be9ab4

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  98688cedda0ef7027ba1a79a4d0e8683c39508a6

THREAD_SHA1_HASH_MOD:  cb5f414824c2521bcc505eaa03e92fa10922dad8

FOLLOWUP_IP:
nt!SwapContext+a9
fffff803`09dd2109 0fc729          xsaves  [rcx]

FAULT_INSTR_CODE:  eb29c70f

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!SwapContext+a9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  578998f1

IMAGE_VERSION:  10.0.14393.0

STACK_COMMAND:  .cxr 0xffffa38111672d40 ; kb

BUCKET_ID_FUNC_OFFSET:  a9

FAILURE_BUCKET_ID:  AV_STACKPTR_ERROR_BAD_IP_nt!SwapContext

BUCKET_ID:  AV_STACKPTR_ERROR_BAD_IP_nt!SwapContext

PRIMARY_PROBLEM_CLASS:  AV_STACKPTR_ERROR_BAD_IP_nt!SwapContext

TARGET_TIME:  2016-08-03T08:01:00.000Z

OSBUILD:  14393

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE: 

USER_LCID:  0

OSBUILD_TIMESTAMP:  2016-07-15 22:16:17

BUILDDATESTAMP_STR:  160715-1616

BUILDLAB_STR:  rs1_release

BUILDOSVER_STR:  10.0.14393.0.amd64fre.rs1_release.160715-1616

ANALYSIS_SESSION_ELAPSED_TIME: b02

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_stackptr_error_bad_ip_nt!swapcontext

FAILURE_ID_HASH:  {79bc9c3c-9f59-2583-44ac-cf3dcaa205fc}

Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: misterp28516 on August 03, 2016, 12:05:56 PM
I posted earlier about this issue.  As I said there, I can't even get Windows Defender to take over because it still thinks Avast is taking care of my antivirus protection, even after several runs of Avastclear in safe mode.  Here are my details:

Operating System
Windows 10 Professional (x64) Version 1607 (build 14393.10)
Install Language: English (United States)
System Locale: English (United States)
Installed: 8/2/2016 10:43:24 PM
Servicing Branch: Current Branch (CB)
Boot Mode: UEFI with Secure Boot disabled
System Model
System Serial Number: Default string
Asset Tag: Default string
Chassis Serial Number: Default string
Enclosure Type: Desktop
Processor a
3.50 gigahertz Intel Core i5-6600K
256 kilobyte primary memory cache
1024 kilobyte secondary memory cache
6144 kilobyte tertiary memory cache
64-bit ready
Multi-core (4 total)
Not hyper-threaded
Main Circuit Board b
Board: Z170A GAMING M3 (MS-7978) 2.0
Serial Number: F816510739
Bus Clock: 100 megahertz
UEFI: American Megatrends Inc. A.10 09/06/2015
Drives
1761.71 Gigabytes Usable Hard Drive Capacity
1249.29 Gigabytes Hard Drive Free Space

ATAPI iHAS124 F [Optical drive]

Brother MFC-290C USB Device [Hard drive] -- drive 2
HGST TOURO S SCSI Disk Device (1000.20 GB) -- drive 1, s/n 52500120001040610012
SanDisk SD7SB7S512G1122 (512.11 GB) -- drive 0, s/n 152054400237, rev X3510000, SMART Status: Healthy
TOSHIBA MK2552GSX USB Device [Hard drive] (250.06 GB) -- drive 3, s/n 2008042400008de9, SMART Status: Healthy
Memory Modules c,d
16340 Megabytes Usable Installed Memory

Slot 'ChannelA-DIMM0' is Empty
Slot 'ChannelA-DIMM1' has 8192 MB
Slot 'ChannelB-DIMM0' is Empty
Slot 'ChannelB-DIMM1' has 8192 MB
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: bob3160 on August 03, 2016, 01:02:57 PM
I updated two systems yesterday.
One 32 bit and one 64 bit system. No problem on either.
I did turn off the Avast Shields prior to the update.
https://forum.avast.com/index.php?topic=156141.msg1329764#msg1329764
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: CaptainLeonidas on August 03, 2016, 01:53:49 PM
Microsoft Surface Pro 4 with a clean Windows 10 Anniversary install crashed on me shortly after the Avast icon became visible on the taskbar.

Mind you a clean install.
Windows 10 Pro (1511) was it's previous version and Avast! was fine -> upgrade and BSOD. The Surface did however upgrade the hidden installtion/recovery partition so a reset will now grant me a Windows 10 Pro (1607).
Specs: Microsoft Surface Pro 4 (i7 + 16GBram and a 512 GB SSD).
Avast! Internet Security online installer used.
Bitlocker is enabled (just in case this is the issue at hand).

I started the installer of Avast after I made sure all App's (Windows apps) and Windows itself was up-to-date. Same for the UEFI etc.
Not too pleased ofcourse.

Resetted my Surface once again and I will not install Avast! until some clear message is given by the people of Avast! concerning full compatibility of Windows 10 Po (1607) and Avast! Internet Security on A Microsoft Surface Pro 4.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: bob3160 on August 03, 2016, 02:08:11 PM
Microsoft Surface Pro 4 with a clean Windows 10 Anniversary install crashed on me shortly after the Avast icon became visible on the taskbar.

Mind you a clean install.
Windows 10 Pro (1511) was it's previous version and Avast! was fine -> upgrade and BSOD. The Surface did however upgrade the hidden installtion/recovery partition so a reset will now grand me a Windows 10 Pro (1607).
Specs: Microsoft Surface Pro 4 (i7 + 16GBram and a 512 GB SSD).
Avast! Internet Security online installer used.
Bitlocker is enabled (just in case this is the issue at hand).

I started the installer of Avast after I made sure all App's (Windows apps) and Windows itself was up-to-date. Same for the UEFI etc.
Not too pleased ofcourse.

Resetted my Surface once again and I will not not install Avast! until some clear message is given by the people of Avast! concerning full compatibility of Windows 10 Po (1607) and Avast! Internet Security on A Microsoft Surface Pro 4.
Which version of Avast ???
Current version is 12.2.2276 build 12.2.3126.2
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Bill_D on August 03, 2016, 02:18:37 PM
"the Windows 10 Anniversary Update failed two times with BSOD today, so I uninstalled Avast and the Anniversary Update went fine. Next I tried to install Avast Free Antivirus Version 12.2.2276, and during the installation process my PC re-booted and I got a BSOD (error: system thread exception not handled) every time as result."

I had the same thing happen with my new Dell XPS 8900 desktop that came with pre-installed Windows 10.  The Anniversary update works fine, but I cannot install Avast Free.  I also had to use the avast uninstaller utility to get Windows to load without a BSOD.  If I try to install Avast, I get the BSOD with the same above error message, during the install process.  Then I have to boot in safe mode and run the Avast uninstall utility to remove the remnants, before I can do a regular boot of Windows.

For now am just using Windows Defender until this can be resolved.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: CaptainLeonidas on August 03, 2016, 02:20:52 PM
Microsoft Surface Pro 4 with a clean Windows 10 Anniversary install crashed on me shortly after the Avast icon became visible on the taskbar.

Mind you a clean install.
Windows 10 Pro (1511) was it's previous version and Avast! was fine -> upgrade and BSOD. The Surface did however upgrade the hidden installtion/recovery partition so a reset will now grant me a Windows 10 Pro (1607).
Specs: Microsoft Surface Pro 4 (i7 + 16GBram and a 512 GB SSD).
Avast! Internet Security online installer used.
Bitlocker is enabled (just in case this is the issue at hand).

I started the installer of Avast after I made sure all App's (Windows apps) and Windows itself was up-to-date. Same for the UEFI etc.
Not too pleased ofcourse.

Resetted my Surface once again and I will not install Avast! until some clear message is given by the people of Avast! concerning full compatibility of Windows 10 Po (1607) and Avast! Internet Security on A Microsoft Surface Pro 4.
Which version of Avast ???
Current version is 12.2.2276 build 12.2.3126.2

Yes, downloaded the online installer for Avast! Internet Security today directly from the Avast! website just minutes before I wrote the post. Ran it and a BSOD as I wrote (even before the desktop icons of Avast! would appear).

(Edited the post to make it clearer.)
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: misterp28516 on August 03, 2016, 02:32:41 PM
Confirmed that I am using Avast Free version 12.2.2276 build 12.2.3126.2.

I have rolled back the update and deferred upgrades until Avast releases a patch.  As I stated above, I was able to complete the Anniversary Update after uninstalling Avast and using Avastclear, but I could not get Windows Defender to stay on because it still thought Avast was handling antivirus responsibilities.  I have used Avast for a long time and did not really want to move to another antivirus program, so I will wait until this issue is resolved.

Yuck.

Penn
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: jsljustin on August 03, 2016, 03:36:18 PM
Same problems here - was running the latest Avast free, and twice I tried to install the Windows 10 anniversary update, and twice it got stuck in a BSOD loop. So after finding this thread, I uninstalled Avast and then I was able to successfully install the Windows 10 anniversary update.

So, from what I am reading here, I am not game to try and reinstall Avast until there is a fix for it. Note I am running Windows 10 Home, 64 bit, on an Intel i7, 16GB RAM, Samsung SSD and Nvidia GTX 970.

Is there anyway to be notified if this issue is noted by Avast staff, and, when a fix is available? I am running Windows Defender, but to be honest, it isn't my preferred anti-virus. Would rather use Avast, when it is fixed.

Thanks.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: MGFirewater on August 03, 2016, 03:43:21 PM
I get 2 time an uncompleted win10 1607 upgrade.

for the first time i use windows update. at the second attempt i use the actually windows media creation tool.

every time win show the the same bug after 70% of update process. win10 can't restart in win 101607. and starts a workaround back to 1511
at the sceond crash i get the error 0xc1900101 - 0x40017 from the media creation tool.

in the evening i will clean avast free from my system and repeat the update procedure. than i will report my impressions
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: jan@surfacebook on August 03, 2016, 03:45:45 PM
Same problems (BSOD during Windows 10 update, installation works fine with uninstallation of Avast before performing update) here on a Surface Book i5.

I also downloaded the actual online setup package and had BSODs after new Avast installation on the updated Windows 10.

Right now I rolled back Windows 10 and reinstalled Avast on it ...

I also started a ticket 445780 at Avast.

Waiting for a fix by Avast. :-\
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Scott39 on August 03, 2016, 04:04:39 PM
I have a total of three systems that I have updated to Anniversary Update Windows 10.  The only one that has BSOD'd is my Intel based processor desktop.  My AMD laptop and desktop both seem to be functioning fine (For The Moment).  Maybe it has to do with a conflict between Avast and the Intel Rapid Storage Technology driver or the processor itself.  Who else has an Intel based system that has BSOD'd (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED) or an AMD system the has or has not BSOD'd?
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: jan@surfacebook on August 03, 2016, 04:06:06 PM
Intel i5
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: MGFirewater on August 03, 2016, 04:11:59 PM
I have a total of three systems that I have updated to Anniversary Update Windows 10.  The only one that has BSOD'd is my Intel based processor desktop.  My AMD laptop and desktop both seem to be functioning fine (For The Moment).  Maybe it has to do with a conflict between Avast and the Intel Rapid Storage Technology driver or the processor itself.  Who else has an Intel based system that has BSOD'd (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED) or an AMD system the has or has not BSOD'd?

after a look of the signature in this thread it should be possible.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: misterp28516 on August 03, 2016, 04:15:46 PM
Intel i5 here.

I also started a support ticket:  Ticket ID: 445899

Hopefully it is a quick fix.

Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: bob3160 on August 03, 2016, 04:30:02 PM
I7 no problems.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: sonichedgehog360 on August 03, 2016, 04:36:00 PM
...
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: jsljustin on August 03, 2016, 04:38:26 PM
Intel i7 Skylake here, on an MSI Gaming M7 z170a motherboard. I don't install the intel rapid storage driver, but got the BSOD anyway.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Scott39 on August 03, 2016, 04:52:22 PM
The weird thing is that Anniversary Update installed on my i5-6500, but AFTER rebooting from the update is when it BSOD'd.  It was not like how the gentleman with the multiple i-core processors was having the issue with the Anniversary Update failing.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: bob3160 on August 03, 2016, 04:58:19 PM
Curious, was Avast on or were the shields disabled during the update ???
I had no problem with an I7 Intel update using the Media Creation Tool to do the update but, the Avast Shields were disabled.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: sonichedgehog360 on August 03, 2016, 05:00:39 PM
...
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: misterp28516 on August 03, 2016, 05:02:22 PM
I tried it with shields on and off, Anniversary Update failed, BSOD, same error message either way.  I could only get the update to complete after a full uninstall and run of Avastclear, but then it went right back to BSOD and same error message once I tried to reinstall Avast after update completed.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: petr.chytil on August 03, 2016, 05:05:54 PM
sonichedgehog360,
thank you for the report. Do you by any chance know which Avast version was installed before the upgrade process to Windows 10 Anniversary Update started?
Is the OS 32b or 64b?

Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: jsljustin on August 03, 2016, 05:07:42 PM
I didn't try to just turn off the shields, I just uninstalled Avast and then the Anniversary update went just fine. I didn't even need to use AvastClear or whatever it is called, I just uninstalled Avast via control panel, did a reboot and then successfully did the Windows 10 anniversary dance thingy..

Not game to reinstall Avast as yet.. don't want to get stuck not being able to boot etc.. Mind you, I only use Avast file-shield.. I only use the bare minimum of Avast components.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: jsljustin on August 03, 2016, 05:15:27 PM
sonichedgehog360,
thank you for the report. Do you by any chance know which Avast version was installed before the upgrade process to Windows 10 Anniversary Update started?
Is the OS 32b or 64b?

I don't know if this helps you, but I checked via the avast interface within the last 24 hours for both program and virus signature updates, and it was all up-to-date when I checked, so whatever version of Avast I was using, there was nothing newer (unless there has been an update the past few hours)..

I am on Windows 10 64 bit, Home. Intel Skylake i7. (6700).. Avast free version.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: sonichedgehog360 on August 03, 2016, 05:16:16 PM
sonichedgehog360,
thank you for the report. Do you by any chance know which Avast version was installed before the upgrade process to Windows 10 Anniversary Update started?
Is the OS 32b or 64b?
64-bit on all the Core i-based PCs. Avast! Free is updated regularly across all devices, so it was updated to the latest version prior to attempting to install Anniversary Update. When I tried to install Avast! on a clean install of Anniversary Update on my i7-6700K system with Defender disabled, I used the latest installation executable of Avast!.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: misterp28516 on August 03, 2016, 05:17:01 PM
I said this earlier, but I can confirm that I was using Avast Free 12.2.2276 build 12.2.3126.2 before attempting Anniversary Update.  I have Windows 10 Pro 64.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: simone.mesca.75 on August 03, 2016, 05:25:44 PM
Dear petr.chytil

I am a Microsoft consultant for home users. I have here 2 PCs, for which i update you as the situation as regards BSOD:

>>> PC 1 (mine), formatted and clean-installed W10 1607 AU from Official ISO (new Media Creation Tool): CRASHED at first reboot after avast installation,
Motherboard: Asus Z170-A, updated bios on latest version
CPU: Core i7 6700 (non K)
RAM: 32 GB DDR4 Corsair Vengeance
VGA: Intel HD530 (in outstanding for nVidia GTX 1060 6GB delivery)
SSD: Samsung SM951 NVMe 256 GB

>>> PC 2 (customer), formatted and clean-installed W10 1607 AU from Official ISO (new Media Creation Tool): ALL OK,
Samsung NP350-V5C, updated bios on yesterday
CPU: Core i7 3630QM
RAM: 8 GB DDR3 OEM
VGA: AMD HD7650M
HDD: Seagate 1 TB

Please take note of this specs to examine the problem. Thanks.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Zedrid on August 03, 2016, 05:54:13 PM
Hi

Exact same issue here, I actually reset my notebook back to factory settings and thus reinstalled avast to have another bsod happen just before completion of install, I did this before seeing this forum post, so imagine how many people are suffering the same issues, that's my time wasted and theirs and I can only imagine the number of people that will be taking their units in for service due to this

Without Avast my unit runs 100% with the latest Windows 10 anniversary update

I am rather annoyed that been a paying customer and long time user, that this is the type of service I am getting

Windows 10 64 bit,  Intel i7 6820HK, 16gb ddr4 ram, GTX980M 8gb.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Scott39 on August 03, 2016, 06:17:57 PM
More information...
When I tried to reinstall Avast! Internet Security on Anniversary Update, it BSOD'd in the middle of install.  This caused a reboot loop that said an Avast file (.sys) was missing.  Had to system restore, THEN go into Safe Mode to remove Avast to get the system back up and going.  Again, the system works fine AS LONG AS Avast is not installed.  I hope some people have AMD processor systems that can confirm Avast works fine on them with AU.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Patrick2 on August 03, 2016, 06:24:29 PM
Well for what it's worth, No BSOD here, but I also have AMD FX Processor, and AMD A6-3620 Quad Core APU, Reporting no issues with Anniversary update with Avast,  So does appear to be only Intel Processor based sadly issue,  (unforuately I don't have any Intel based systems here to test on to offer anything more though) 

Way I installed was

Clean Install via ISO,  (upstairs machine was via Windows Update)

Wish I could offer more help for folks that are having issues though

Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Darecki2k on August 03, 2016, 07:59:00 PM
Confirmed avast fault. Removed it and the anniversary update went smooth. Tried to install it afterwards and BSOD all over again. Managed to remove avast again in windows safe mode. No chance to properly run avast on my PC now.

Win 10 Home 64bit, Intel 6700k.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: indask8 on August 03, 2016, 08:05:33 PM
Looks like the issue only affect skylake intel CPU,

I have an intel NUC Skullcanyon with a Core I7 6770HQ and I had the permanent blue screen upon startup after a successful install of the Anniversary update and a reboot.

Troubleshooting the issue (Google results seemed to say the issue was due to the graphic card drivers) I ended up eventually trying to uninstall Avast and bingo it worked fine, I then reinstalled Avast and it blue screened during the install, had to use the avast unistaller utility while in safe mode to remove it once again.

Computer running fine currently with no antivirus (Windows defender, if we can call that an antivirus, is on).

I hope you'll fix this issue soon.

Note: other computers running Avast including a Core I5 3210m + a Core M 5Y10C laptop updated with no issues.

Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Scott39 on August 03, 2016, 08:08:24 PM
Well, if it was graphic related to the processor I should not have BSOD'd with my i5-6500.  I use a GeForce GTX 660Ti as my video output, not onboard.  But, you never know.  Also, a gentleman before on here stated the BSOD with multiple generations of i-Core processors.  6000 series, 2000 series, and original series.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: MGFirewater on August 03, 2016, 08:52:36 PM
so i'm back at the internet  ;D with win10 1607 but without avast 12.
the update failure was definitely a problem with avast 12 and my intel system (infos at my signature)
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: robscom on August 03, 2016, 08:57:45 PM
Another victim with a i7-6700HQ reporting in. Like many already described, initial BSOD during installation and others following up during startup.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Hansifer on August 03, 2016, 09:03:56 PM
Same issue here.

Win10 Anniversary update BSOD at around 35% completion. Initial stop code was SYSTEM_THREAD_EXCEPTION_NOT_HANDLED.

After updating BIOS, all drivers, and version of Avast to 12.2.2276 (build 12.2.3126.2), Win10 Anniversary update failed again with BSOD, this time with stop code IRQL_NOT_LESS_OR_EQUAL.

I also disabled Avast shields prior to starting the second update attempt.

Running Win10 64-bit but version of Avast installed is 32-bit.

Hardware:

- Motherboard: MSI Z170A Gaming M9 ACK
- Processor: Intel Core i7 6700K Quad-Core 4.0GHz (4.2GHz TurboBoost)
- Graphic Card: 4GB NVIDIA GTX 970
- Memory: 32GB Corsair LPX 2800MHz (4x8GB)
- Hard Drive: 500GB Samsung 850 Evo Series
- Audio: Creative Sound Blaster X-Fi Surround 5.1 Pro USB Sound Card
- Networking: ASUS PCE-AC68 Dual-band Wireless-AC1900 Adapter
- Operating System: MS Windows 10 Professional

Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: RedFan on August 03, 2016, 09:09:03 PM
After reading this topic i uninstalled avast prior to the anniversary update
Think i will install avast again after all the problems been solved.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Systeem on August 03, 2016, 09:27:58 PM
Weirdest thing is, i was running the insider version of the anniversary update (sr-version) and that gave me no problems at all...
But after leaving the pc for an hour, microsoft thought it would be nice to install the anniversary update and added the complimentary reboot, which bsod'd (multiple times, but is was not able to autocorrect/repair it).
Not knowing it was a compatibility issue windows10anni/avast, after two hours of trying to 'systemrestore' my system to relative health, i reverted to a clean install (not so bad after a year of tweaking) only to be greeted with a bsod on install of avast free.... bang!
That made it clear (at least part of) the issue was with avast...

So until avast and microsoft agree on what where etc. i will keep extra alert while using defender.
Pity, been using avast for many years now, only one real hickup for me (besides this one, that is).
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Scott39 on August 03, 2016, 09:37:52 PM
Glad to hear that we are definitely getting it narrowed down and seeming to confirm that Intel based systems have the BSOD with Windows 10 AU.  Hopefully Avast! will release an update to their program fast, as I fear a LOT of customers are going to come in with the same problem!  They might have even wiped their system before coming in and asking us, and we recommend Avast to everyone!

I saw Avast had a program update on 7/28/16.  Did anybody have the BSOD with the prior version that we know of?
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: worf105 on August 03, 2016, 09:38:22 PM
Me too  :-[

Clean install of Windows 10 Pro 64 Anniversary on my system.

BSOD: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Spec:
I7 6700K, Corsair H110i GTX, Asus Z170-A, Corsair Vengeance LPX 16GB (2x8GB) 2400MHz DDR4
Zotac GTX 1070 AMP Extreme, BenQ GL2460HM, 256GB Samsung 950 Pro M.2 PCI-e 3.0 x 4 NVMe
Samsung 840 SSD 256GB, WD 2TB Caviar Green & Samsung 1TB SpinPoint F3
Wndows 10 64, Corsair Obsidian 750D, Logitech G502 Proteus Spectrum, Microsoft SideWinder X6

Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: misterp28516 on August 03, 2016, 09:39:46 PM
Mine was definitely with the latest version of Avast from 7/28.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: pdvelazquez on August 03, 2016, 10:04:06 PM
Excuse my bad english.
Same problem here, but with two different results.
My system:
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: bob3160 on August 03, 2016, 10:12:53 PM
Excuse my bad english.
Same problem here, but with two different results.
  • I am a Windows Insider user, and I am using Windows 10 Anniversary Update (14393.10) with Avast (12.2.2276 - build 12.2.3126.2 with the latest virus definitions (160803-1)) with no problem.
  • In my regular Windows installation (not the Insider Preview), I can't install Avast because the BSOD's just before the completion of the Avast installation.
My system:
  • Intel Core i3 6100
  • Gigabyte GA-B150-HD3
  • 8 GB DDR4 (Dual Channel)
  • No graphic card
SSD or IDE Hard drive ???
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: pdvelazquez on August 03, 2016, 10:19:53 PM
SATA HDD.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Shaun985 on August 03, 2016, 10:40:15 PM
Ugh, first the "you are unprotected" bug and now this.  I think it would be great if Avast slowed down on the updates a bit and fully tested them out before release.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: grasshpr on August 03, 2016, 10:44:58 PM
Same here.
System Thread Exception Not Handled BSOD loop after updating to Redstone.
In fact was not able to update in the first place until uninstalled Avast. Nor successfully upgrade from W7 to W10 before.

i5 6600
Asus Z170M-Plus (BIOS settings default, except Intel VT on)
SATA SSD/HDD (tried both)
AMD R9 390
Clean Win install
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: MBvB on August 03, 2016, 10:55:34 PM
I also had the BSOD Loop 4 times during 4 installations.

On the 5th I came across that AVAST might be the "terror" causing the problem.

Uninstalled it before updating to Windows 10 (1607) Build 14393.10. No problems installing Windows update after.

Reconfigured the system and tried to reinstall AVAST:_ Shouldn't have done that... During installation it BSOD again and goes into Boot-loop.

Please take a look at it, Avast. All my drivers are up to date and it is something with Avast and the new MS Windows 10 update(1607) that doesn't seem to like each other.

System:
Windows 10 Professional (x64Bit)
Processor: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz 4.01 GHz
RAM: Corsair Vengeance LPX 32GB 3600MHz DDR4
Motherboard: MSI Z170A Xpower Gaming Titanium ED S-1151 ATX
Graphics: 2x Evga FTW Gaming ACX 3.0 Nvidia GeForce GTX 1080 8GB
SSD: 2x Samsung 850 EVO 500GB 2.5" SATA-600 (RAID-0)
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Wahnfried1883 on August 03, 2016, 11:00:32 PM
I saw Avast had a program update on 7/28/16.  Did anybody have the BSOD with the prior version that we know of?

I can confirm that the previous Version (12.1.2272) also caused the known problems. This Version (12.1.2272) I was having  during the Anniversary Update process which failed first.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: petr.chytil on August 03, 2016, 11:02:25 PM
Thanks everyone for posting details of your HW configurations! It helped us a lot, because the issue really seems to occur only on the last generation of Intel CPUs. Previous generations of Intel Core CPUs are fine. Moreover, it did not show up during the testing on the Win 10 preview builds.

We are already working on a fix and hopefully, we are going to deliver it via an emergency update. I will keep you posted.

Thank you also for your patience. We are having a hard time with this update as well.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: misterp28516 on August 03, 2016, 11:27:29 PM
Thank you for working the problem so quickly.  Appreciate the update on progress.

Penn
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: rock14 on August 03, 2016, 11:31:30 PM
Same problem here. Tried 3 times and always bsod. Then uninstalled avast and now I can update.
I have a little problem now.. I have uninstalled avast and use the uninstall utility but Windows defender keep saying that I have an antivirus software installed and it can't be activated.
My hardware:
i5-6500
Msi h170 gaming pro
R9 380x
Corsair 8gb Ddr4
Windows 10 pro.

Sorry for the English...
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: jvidal on August 03, 2016, 11:31:46 PM
Excuse me, but an emergency update won't solve anything if the PCs BSOD BEFORE they can even download the EmUpdate.
you need to UPDATE THE OFFLINE INSTALLERS!!!!!!
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: RedFan on August 03, 2016, 11:53:46 PM
Excuse me, but an emergency update won't solve anything if the PCs BSOD BEFORE they can even download the EmUpdate.
you need to UPDATE THE OFFLINE INSTALLERS!!!!!!
Yes also the offline installers that we need to reinstall avast
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Graig on August 04, 2016, 01:01:59 AM
I cannot install the Anniversary Update on my new computer, I get a SYSTEM THREAD EXCEPTION NOT HANDLED message and the system is restored to the previous build.  Uninstalled Avast and no problem whatsoever. Oddly enough it updated perfectly on my 6 year old machine without a hitch and running same version of the Avast, the latest.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Ch3vr0n on August 04, 2016, 01:10:26 AM
Just tried twice too, didn't figure it would be my AV. I'm using AIS and cpu is an i7 6700k (not overclocked). Using AIS build 12.2.2276
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: simone.mesca.75 on August 04, 2016, 04:23:34 AM
Just tried twice too, didn't figure it would be my AV. I'm using AIS and cpu is an i7 6700k (not overclocked). Using AIS build 12.2.2276

So, you are telling us that, with your i7 6700 skylake, the system go on without any problem ?!?!?
If yes, which type of VGA you use ? Integrated Intel HD or dedicated NVIDIA/AMD? Thanks
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Ch3vr0n on August 04, 2016, 04:25:32 AM
No, you're saying the exact opposite of what I said. I said I tried twice and failed twice. The type of VGA is irrelevant. Avast is the problem not a graphics adapter
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: kai.kudou on August 04, 2016, 06:58:34 AM
Hi everyone,
I had the same issue too.
I updated my Win10 from Version 1511 to 1607 yesterday, and when I was installing the avast(use online install package), windows 10 crased then reboot itself.
After the install failed, Win10 will go back to the nearest restore point, so the program I install before are gone....
Hope this error can be fix as soon as, thank you.

Below is my basic info
=======================================================================
Operating System: Windows 10 Home Edition 64-bit (10.0, Build 14393) (14393.rs1_release.160715-1616)
Language: Chinese (Traditional) (Regional Setting: Chinese (Traditional))
System Manufacturer: ASUSTeK COMPUTER INC.
System Model: UX303UB
BIOS: UX303UB.202
Processor: Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz (4 CPUs), ~2.6GHz
Memory: 12288MB RAM
Available OS Memory: 12184MB RAM
Page File: 2475MB used, 12140MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 12
==========================================================================
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: CaptainLeonidas on August 04, 2016, 07:40:41 AM
Assuming that indeed the latest Intel CPU's are effected by the BSOD I will continue to install my PC's (which have "older" CPU's) with Windows Pro 10 (1607) Anniversary updates.

If I run into trouble I will update my signature to include the older PC's too.

Note: the Asus Deluxe PC within the sign is fine including one of the virtual PC's (VMWare Workstation Pro 12 used as hypervisor) running on this configuration and Avast. (I use more then 1 anti-virus program. Malwarebytes, Avira, G-Data, Sofos/Surfright HitmanPro and Kaspersky are others I use.)

The issue I have is with a new (maybe 2 months old) Microsoft Surface Pro 4 only so far.

Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: jsljustin on August 04, 2016, 09:41:59 AM
Good to hear from Avast mods that they are hoping to provide an update / emergency fix soon.. and as others have said, obviously it would be necessary to provide the update / fix for the complete or offline installers as well, as no one with this issue will have Avast installed on their machines..
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: menno.debes on August 04, 2016, 09:55:59 AM
Goodmorning

took me a while and several clean installs before I realised my problem was caused by avast. I read this thread and know that a solotion is prepared. Anyway, I thought it would be good to share my hardware here:

Dell Inspiron 7559

Intel i7 6700HQ
Nvidia GTX960
RAM 16 GB
500 GB EVO 850 m.2 SSD
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: metarom on August 04, 2016, 10:00:23 AM
Hi, same on my config (BSOD @ 71 % of update process) (by the way, many thanks to MS for its recovery process).
My config on NUC6i5SYH
i5-6260U
8Go Crucial
SSD Crucial m.2
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: petr.chytil on August 04, 2016, 10:13:48 AM
Thanks everyone for all the reports. It really helped us to find the root cause.
If everything goes well, we are going to release an emergency update today. The update will be applied even during the clean installation. Beside that, we are going to include the fix in the offline installer of a Beta version which is also going to be released today.

Right now, the fix is being tested.

Once it is ready, I will let you all know!
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: jan@surfacebook on August 04, 2016, 10:25:11 AM
*clap-hands*

I really appreciate this. Thanks for the power!!

I do not understand why some people are really angry and shouting on Avast - this is my first issue for years now as a paying customer and I still would recommend Avast to every friend ...
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: jsljustin on August 04, 2016, 10:26:33 AM
Great news, thank you!
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: menno.debes on August 04, 2016, 10:27:42 AM
*clap-hands*

I really appreciate this. Thanks for the power!!

I do not understand why some people are really angry and shouting on Avast - this is my first issue for years now as a paying customer and I still would recommend Avast to every friend ...

As a non paying customer i second this. Mistakes are made everywhere, it is the reaction to made mistakes that make the difference... I wonder how these people react irl when a coworker or a friend makes a mistake.

anyway, thanks for the support Avast :)
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: CaptainLeonidas on August 04, 2016, 10:43:47 AM
Thanks everyone for all the reports. It really helped us to find the root cause.
If everything goes well, we are going to release an emergency update today. The update will be applied even during the clean installation. Beside that, we are going to include the fix in the offline installer of a Beta version which is also going to be released today.

Right now, the fix is being tested.

Once it is ready, I will let you all know!

I will check this thread closely so I can install the AIS once again on my Surface once the update/fix becomes available.

Thanks for the update.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: petr.chytil on August 04, 2016, 10:45:47 AM
One more note,
this issue occurs only on Intel Skylake CPUs when VT-x instructions are enabled in the BIOS. As a workaround, you can temporarily disable the VT-x in BIOS.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: CaptainLeonidas on August 04, 2016, 10:57:28 AM
One more note,
this issue occurs only on Intel Skylake CPUs when VT-x instructions are enabled in the BIOS. As a workaround, you can temporarily disable the VT-x in BIOS.

No idea if this applies on a standard Surface Pro 4. If so I will have to look up where this is hidden in it's UEFI.
Also does this mean VMWare/VirtualBox or Hyper-V users still have an issue when running Avast on their workstations?
I would assume so.

Can it also be solved by avoiding the use a loose component/not installing a component or is it part of the basic drivers needed to even run the Avast anti-virus software?
(Again I assume this being the case as some folks have issue's with the free version as well..)
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Hansifer on August 04, 2016, 11:06:13 AM
Thanks to Avast for an incredibly quick response on this. Pretty impressive.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: rock14 on August 04, 2016, 11:46:01 AM
Just for giving you more info.
I just update my second desktop with i5-760 + windows 10 + avast free.
Anniversary update installed at the first try.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Handsofdeath on August 04, 2016, 12:01:57 PM
ok on august the 2nd I tried install win10 anniversary update and it failed twice due to avast and BSOD.  ok so I uninstalled avast through add/remove programs.   then I got the win10 update installed.  so after its all working good stupid me installed avast fresh install and yeah you guessed it bsod.  so I had to go onto another computer and find that this forum shows all kinds of issues with this new update and avast.  Great.   so I found your avast cleaner and booted into safe mode and ran it.   got my computer working good.   Yes I have a skylake cpu i7  and now I see you MIGHT have it fixed.  but to be honest I don't know if I trust your software anymore over 15 years of using it and installing it on clients computers I work on.  its like you guys gave up and don't care anymore at all, this is a horrible issue that should of never happened PERIOD. 
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Eddy on August 04, 2016, 12:06:27 PM
Sure, and you are perfect and never do something wrong/make a mistake.
Besides, you should blame Microsoft for not testing all possible combinations of hardware/software before releasing the update.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: misterp28516 on August 04, 2016, 12:19:12 PM
Petr -

Thanks for the quick turnaround on a fix.  Please let those of us who restored to Windows 10 Build 1511 what we should do.  That is, will we need to uninstall Avast, perform the Anniversary Update, then do a clean install?  Or will we be able to apply the update, disable shields and not uninstall Avast, then perform the Anniversary Update?  I'd like to avoid any more BSODs or boot loops.

Thanks again.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Eddy on August 04, 2016, 12:22:00 PM
Apply the avast update before updating Windows and everything should be fine.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: zemlynin on August 04, 2016, 12:42:24 PM
One more note,
this issue occurs only on Intel Skylake CPUs when VT-x instructions are enabled in the BIOS. As a workaround, you can temporarily disable the VT-x in BIOS.
Have 2 new pc.  "Intel Skylake CPUs when VT-x instructions are enabled in the BIOS" is disable in bios.
Fresh instalation Windows 10 Anniversary Update. same BSOD after install Avast.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: simone.mesca.75 on August 04, 2016, 02:06:05 PM
One more note,
this issue occurs only on Intel Skylake CPUs when VT-x instructions are enabled in the BIOS. As a workaround, you can temporarily disable the VT-x in BIOS.

Not sure of this. In my Asus Z170-A with i7-6700, VT-d is DISABLED by default.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: petr.chytil on August 04, 2016, 02:49:45 PM
simone.mesca.75,
is on your system an option to disable VT-x as well? In our tests, disabling VT-d was not enough to workaround the issue.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: adamchamney on August 04, 2016, 04:08:43 PM
simone.mesca.75,
is on your system an option to disable VT-x as well? In our tests, disabling VT-d was not enough to workaround the issue.

I can confirm that  VT-d IS DISABLED in my BIOS.
I have the same issue as everyone. With AVAST installed after upgrade I get blue screen. I can uninstall AVAST and install the windows update, everything works fine until I install AVAST then it will blue screen again, until I either uninstall AVAST or roll back the windows update.

I have a 6600k, Gigabyte, Z170xp-SLI motherboard.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: memoadian on August 04, 2016, 04:20:54 PM
simone.mesca.75,
is on your system an option to disable VT-x as well? In our tests, disabling VT-d was not enough to workaround the issue.

Thanks a lot for your help

Effectively I have a intel 6700k and the same issue with blue screen everytime avast is installed.

My motherboard is a Gygabyte gaming 3 z 170x, and vt-x is not present in BIOS only VT-d. I suscribed in this post, for futeres updates.

PD: excuse me for my very bad English
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: jsljustin on August 04, 2016, 04:23:25 PM
Hi petr,

just some info for you. I can confirm that on my machine, disabling VT-x in the bios seems to have done the trick. In more detail:

For a baseline, I checked my BIOS settings, and in my particular bios, VT-d was disabled already (the default) but a setting called "Intel Virtualization Tech" was enabled. Anyway, with these original settings left unchanged, I attempted to install Avast Free (12.2.2276), and got the Blue Screen crash part the way through the install. So I rebooted into safe mode, ran the Avast clear utility to uninstall. Then I booted back into BIOS and disabled the "Intel Virtualization Tech" or VT-x.

Then, in full windows (normal mode, not safe mode) I re-ran the Avast Free installer. All went well. Did a smart scan, everything was fine. Then I ran a full system scan, everything went fine. Rebooted, no issues at all.

So it does appear that disabling VT-x does in fact stop the BSOD crashes. At least, so far for me, everything has been running just fine. Avast is working just fine.

Anyway, my specs, if it helps:

Windows 10 Home, 64 bit
Motherboard: MSI Gaming M7 z170a
CPU: Intel Core i7-6700
SSD (OS drive): Samsung 840 Evo 250GB
HDD (Data drive): Seagate Barracuda 5400 1TB
GPU: MSI Nvidia GTX 970 4GB
RAM: 16GB 2133 MHz Corsair
Soundcard: Steinberg UR12

Hope that helps.

Cheers
Justin
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: simone.mesca.75 on August 04, 2016, 04:26:30 PM
simone.mesca.75,
is on your system an option to disable VT-x as well? In our tests, disabling VT-d was not enough to workaround the issue.

It seems not. I have check all the bios section and ther is only vt-d (disabled bydefault).
How is your situation actually ?
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: jsljustin on August 04, 2016, 04:30:40 PM
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.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Scott39 on August 04, 2016, 04:32:58 PM
I have seen several people already blaming Avast for this issue.  While it is a MAJOR issue, with it not happening with the Insider Ring, or Beta version of AU, they had really no way of knowing.  I'm sure you guys, like the rest of us on this forum, immediately jumped at updating to AU, which is bound to have some issues.

Thank you very much for your fast response Avast!  Please keep us updated and what version number to look for to confirm Avast is up to date with this fix BEFORE anyone else tries to upgrade to AU.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: simone.mesca.75 on August 04, 2016, 04:57:39 PM
simone.mesca.75,
is on your system an option to disable VT-x as well? In our tests, disabling VT-d was not enough to workaround the issue.

Dear Petr,

I CONFIRM that:

1. In my Asus Z170-A, and i think in other Z170 motherboards series (not only Asus), Intel VT-x is called "Intel Virtualization Technology"
2. I have found it in my Asus Z170-A and i've disabled it. I reboot system. For safety I've disabled Windows Defender thru reg values modify in group policies (it is my personal procedure), then I reboot and I’ve installed avast free using online stub installer, then reboot once a time.

And...

... ALL IS OK !!!

So, i can say that, with 99,9% probability, the problem is a conflict between Avast and Intel Virtualization technology.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: CaptainLeonidas on August 04, 2016, 05:28:03 PM
simone.mesca.75,
is on your system an option to disable VT-x as well? In our tests, disabling VT-d was not enough to workaround the issue.

Dear Petr,

I CONFIRM that:

1. In my Asus Z170-A, and i think in other Z170 motherboards series (not only Asus), Intel VT-x is called "Intel Virtualization Technology"
2. I have found it in my Asus Z170-A and i've disabled it. I reboot system. For safety I've disabled Windows Defender thru reg values modify in group policies (it is my personal procedure), then I reboot and I’ve installed avast free using online stub installer, then reboot once a time.

And...

... ALL IS OK !!!

So, i can say that, with 99,9% probability, the problem is a conflict between Avast and Intel Virtualization technology.

Great. So if this is indeed the case those running VM's are now somewhat left in the cold. Option being to revert back to v1511 until a real fix is put into play or choose another anti-virus solution. I do wonder if Avast NG is the component acting up in this with the next gen Intel CPU's and windows 10 v1607
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: bob3160 on August 04, 2016, 05:36:40 PM
NG isn't used any more. It was replaced with Cyber Capture.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: sonichedgehog360 on August 04, 2016, 05:52:16 PM
Please let us know as soon as possible when the updated offline installer is available because I now need to do a fresh clean install with Anniversary Update.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: memoadian on August 04, 2016, 05:53:49 PM
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
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: sonichedgehog360 on August 04, 2016, 05:56:34 PM
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

Look for a virtualization option (such as "Intel Virtualization Technology" or maybe just virtualization) and disable that.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Karotte on August 04, 2016, 06:05:19 PM
Hello, sorry for my english .... google translate ^^


I confirm as many of the worries is resolved when you disable Intel VT in the BIOS. I had the blue screen loop when I made the installation of the anniversary >>> forced update avast uninstall in safe mode after finding the info on the net. So, end of the blue screen , update ok . By cons when I tried to reinstall avast again the blue screen ...
So I disable Intel VT and I managed to reinstall AVAST .

Merci à tous, Thanks all for helping me  ;)

my config
I5 6600 K
Zotac AMP 1070 Extrem
Asus Maximus Ranger VIII
Samsung 850 Pro SSD
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: sonichedgehog360 on August 04, 2016, 06:38:24 PM
If the update comes today, will the offline installer also be updated today?
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: adamchamney on August 04, 2016, 06:42:28 PM
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.

I have a Gigabyte Z170xp-SLI I can only find VT-d which is disabled. I can not locate any other mention of Virtualization Technology other then VT-d in the bios, manual, and googling the motherboard online. I do NOT believe there is any other option to disable Virtualiztion other then VT-d on this board.
Any help would be greatfull
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Sbordoni on August 04, 2016, 07:00:00 PM
So, i can say that, with 99,9% probability, the problem is a conflict between Avast and Intel Virtualization technology.

I suppose that the problem is some sort of incompatibility between AV and Win10 VSM into v1607.

Into 64-bits machines, the OS itself is running into a it's own virtual machine...

(
you can find some more info here:
https://channel9.msdn.com/Blogs/Seth-Juarez/Windows-10-Virtual-Secure-Mode-with-David-Hepkin
)

For sure, disabling Intel VT has effects on VSM itself.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: gtcrais.reg.info on August 04, 2016, 07:03:24 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.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: RedFan on August 04, 2016, 07:32:57 PM
I think almost solved ? because i see a new beta release with a fix called :

+ BSOD for Skylake processor running Windows 10 Anniversary Update(RS1)
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: petr.chytil on August 04, 2016, 07:42:47 PM
The emergency update was already released for Avast 12.2.2276

It is safe now to perform a clean installation using the on-line installer on Skylake CPUs running Windows Anniversary Update.

For those, who disabled VT-x as a workaround and want to verify that the emergency update was successfully applied on their Avast 12.2.2276, please reboot first and then check the file version of following file:
C:\Windows\System32\drivers\aswvmm.sys
File version of successfully patched file is: 12.2.3126.4

In fact, it is now safe to perform an installation using both offline and online installer. However, you need to be on-line while installing because all emergency updates are being downloaded during the installation. Anyway, it is safer to use the online installer, because it works only when internet connection is available.

When installation without internet connection is needed, the only way so far is the Beta offline installer:
https://forum.avast.com/index.php?topic=189468.0

We are going to release emergency updates for 12.1.2272 and some other previous Avast version Tomorrow.

Thank you all again for your reports. It really helped us to find the root cause sooner.

Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Labyrintho on August 04, 2016, 08:02:00 PM
I have 12.2.2276 but C:\Windows\System32\drivers\aswvmm.sys version ...3 instead of ...4.  Avast reports I am up-to-date.

Should I just wait for the new update in a day or two, or is there another way to get the updated version of 12.2.2276? 

It's not life or death, just annoying. 

EDIT: I saw the new thread discussing a way to update the update: https://forum.avast.com/index.php?topic=189131.0
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: petr.chytil on August 04, 2016, 08:29:50 PM
If anyone needs to speed up the delivery of the emergency update, then please:
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: adamchamney on August 04, 2016, 08:52:41 PM
The emergency update was already released for Avast 12.2.2276

It is safe now to perform a clean installation using the on-line installer on Skylake CPUs running Windows Anniversary Update.

Should I just download AVAST from your website and install it as usual, or is there a special link for the fix?
I have the windows anniversary update installed and spent time configuring my settings and I want to make sure if I try to install AVAST again, I will not have to revert back to the previous windows version.
Thanks
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Ch3vr0n on August 04, 2016, 08:56:35 PM
I have no desire whatsoever to do a fresh install of 1511 to do the update to anniversary. There's over 400gb of data installed. I currently have 2276 installed see previous post and NO anniversary update. I also don't want to uninstall and reinstall avast or go tinkering with the bios.

So how do I get the fix so I can apply the update?
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: worf105 on August 04, 2016, 09:41:30 PM
Downloaded online installer VERSION: 12.2.2276 and all went fine.

all working now, great work Avast for this quick fix.

cheers

worf105
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: suk on August 04, 2016, 09:53:15 PM
I have no desire whatsoever to do a fresh install of 1511 to do the update to anniversary. There's over 400gb of data installed. I currently have 2276 installed see previous post and NO anniversary update. I also don't want to uninstall and reinstall avast or go tinkering with the bios.

So how do I get the fix so I can apply the update?

If you're on 2276 and you want to make sure if the patch was applied before you start Win upgrade to anniversary, just check if the patch was applied:
https://forum.avast.com/index.php?topic=189403.msg1330207#msg1330207

If not and you want to speed up the update process (which runs twice a day and after reboot):
https://forum.avast.com/index.php?topic=189403.msg1330216#msg1330216

Full uninstall/fresh install of Avast AV is required only if run into BSOD cycle already.   
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: bob3160 on August 04, 2016, 09:56:07 PM
I have no desire whatsoever to do a fresh install of 1511 to do the update to anniversary. There's over 400gb of data installed. I currently have 2276 installed see previous post and NO anniversary update. I also don't want to uninstall and reinstall avast or go tinkering with the bios.

So how do I get the fix so I can apply the update?

If you're on 2276 and you want to make sure if the patch was applied before you start Win upgrade to anniversary, just check if the patch was applied:
https://forum.avast.com/index.php?topic=189403.msg1330207#msg1330207 (https://forum.avast.com/index.php?topic=189403.msg1330207#msg1330207)

If not and you want to speed up the update process (which runs twice a day and after reboot):
https://forum.avast.com/index.php?topic=189403.msg1330216#msg1330216 (https://forum.avast.com/index.php?topic=189403.msg1330216#msg1330216)

Full uninstall/fresh install is required only if run into BSOD cycle already.
Clean Install of Avast:
https://goo.gl/4Ptzkf
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Robert0507 on August 04, 2016, 09:59:01 PM
So with the new Avast EM update do we still have to uninstall Avast and disable Vt-x in bios before we upgrade to Windows 10 Anniversary Edition or can we just update as normal without having to uninstall Avast and disabling Vt-x ? I think there is some confusion on what will work and what wont!
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: grasshpr on August 04, 2016, 10:27:45 PM
Installed Avast using online installer. No BSOD, works fine.

Thanks for quick solution.

So with the new Avast EM update do we still have to uninstall Avast and disable Vt-x in bios before we upgrade to Windows 10 Anniversary Edition or can we just update as normal without having to uninstall Avast and disabling Vt-x ? I think there is some confusion on what will work and what wont!

I think you should be able to upgrade fine with updated Avast.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: HAPCAP on August 04, 2016, 10:30:26 PM
Does this emergency update apply to Avast Business Security as well?  I've tried running the AvastEmUpdate.exe file and rebooting, but I'm still stuck at ver 12.1.2512 (Build 12.1.3076.6)

Planning to try an uninstall/reinstall using a fresh copy of the online installer next.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Ch3vr0n on August 04, 2016, 10:34:48 PM
I'll wait for avast to push the update. Currently running on Windows build 1511 fully stable since 1607 would bsod and revert to 1511. That file is on .3 for me. A clean install of Windows? Not going to happen. I'm not going to reinstall over 400gb of data where a portion of the installs require major downloading.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: bob3160 on August 04, 2016, 10:38:23 PM
I'll wait for avast to push the update. Currently running on Windows build 1511 fully stable since 1607 would bsod and revert to 1511. That file is on .3 for me. A clean install of Windows? Not going to happen. I'm not going to reinstall over 400gb of data where a portion of the installs require major downloading.
No one said anything about a clean install of Windows. What was mentioned was a clean install of Avast. :)
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Wahnfried1883 on August 04, 2016, 10:48:10 PM
Thanks to Avast Team for quick solution. Now running Win 10 1607 AND Avast 12.2.2276 and everything is fine.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: memoadian on August 04, 2016, 10:57:27 PM
;D ;D Thank you, this version works fine in i7 6700k clean installation
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: adamchamney on August 05, 2016, 12:13:13 AM
Big thanks too: youpetr.chytil, and Bob3160! And everyone else on the forum!
I have successfully installed the fixed AVAST on my Skylake PC, running windows 10 anniversary update!

Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: RedFan on August 05, 2016, 12:17:58 AM
Everything is running smooth ! :D
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: rock14 on August 05, 2016, 12:19:10 AM
Thanks to Avast Team for quick solution. Now running Win 10 1607 AND Avast 12.2.2276 and everything is fine.
Same on my desktop. Thanks!
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Ch3vr0n on August 05, 2016, 01:31:28 AM
@petr.chytil a couple hours ago C:\Windows\System32\drivers\aswvmm.sys was stil 12.2.3126.3

I just checked again and now the file is .4 however i did neither manually do the emergency update, nor a reboot, nor a clean install of avast. Can i just do the update now? Is a reboot still advised prior to doing the update? Or should i for simplicities sake, just wait for the full next build of AIS? I also just noticed directly below a file called aswvmm.sys.147035281307801. What's that about?
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: misterp28516 on August 05, 2016, 01:51:07 AM
Hi all.  I had rolled back to Windows 10 version 1511, still had Avast installed and running.  I followed the instructions, forced the update, checked to make sure I had the correct version (12.2.3126.4).  Then I disabled Avast shields, just to be sure, and ran the Anniversary Update.  Updated fine, enabled shields, restarted.  All good.  :)

Thanks again to Petr and others from Avast who worked to push out an update so quickly.  Thanks also to the others on this board who helped troubleshoot the problem.

Nice working with you.

Penn
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: jvidal on August 05, 2016, 02:30:23 AM
PLEASE PLEASE PLEASE update the offline installers!!!!!!!
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: anarkii on August 05, 2016, 02:49:30 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.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Rednose on August 05, 2016, 04:04:49 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.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Rednose on August 05, 2016, 04:17:23 AM
If anyone needs to speed up the delivery of the emergency update, then please:
  • Double-click on C:\Program Files\AVAST Software\Avast\AvastEmUpdate.exe
  • Wait short while, because AvastEmUpdate.exe has no UI
  • Reboot

If C:\Windows\System32\drivers\aswvmm.sys is not on 12.2.3126.4 you can follow this procedure.
But wait at least 5 minutes before you reboot, just to be on the safe side.
Or else things can screw up !

Greetz, Red.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Shaun985 on August 05, 2016, 05:14:46 AM
So is it completely safe now, no more BSOD during install or after?  I ran Avast Emergency Updater, reboot, checked aswvmm.sys is 12.2.3126.4 and am about to run Windows Update.  Do I still have to disable Intel Virtualization Tech?
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: CaptainLeonidas on August 05, 2016, 07:01:59 AM
So is it completely safe now, no more BSOD during install or after?  I ran Avast Emergency Updater, reboot, checked aswvmm.sys is 12.2.3126.4 and am about to run Windows Update.  Do I still have to disable Intel Virtualization Tech?

On a Tablet PC on which I was getting reboot loops "my Microsoft Surface Pro 4 from my signature" the installation (Online) is now working once more without having to change UEFI settings.

For me the following PC's / Tablet PC are running Windows Pro 10 Anniversay Update (1607) fine:

So I assume it is "safe enough" to try once again.

Note: "safe" is never safe as any PC/Tablet PC is never the same.

Tonight I will also be running a Windows 10 Pro Anniversy Update virtual PC (also for "Windows 10 Pro Fast Ring Insider Preview" testing) in either VMWare Fusion 8 / Parallels 11 on the MacBookPro CPU i7 as I am sure enough it will run just fine with my "Avast! Internet Security" software.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: anarkii 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. :)
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: MGFirewater on August 05, 2016, 09:02:10 AM
no troubles any more :)
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: jsljustin 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  :)
Title: Re: [fixed] Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: bob3160 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.
Title: Re: Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: gtcrais.reg.info 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.
Title: Re: [fixed] Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: petr.chytil 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
Title: Re: [fixed] Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Ch3vr0n 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
Title: Re: [fixed] Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: simone.mesca.75 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 !!! ;)
Title: Re: [fixed] Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: Ch3vr0n 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.
Title: Re: [fixed] Avast causes Blue Screen after Windows 10 Anniversary Update
Post by: MichaelScott 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?