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

0 Members and 1 Guest are viewing this topic.

Offline Wahnfried1883

  • Newbie
  • *
  • Posts: 4
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.
« Last Edit: August 05, 2016, 01:09:53 PM by petr.chytil »
Mainboard: Gigabyte GA-Z170X-Gaming 3 | CPU: Intel Core i7-6700K @ 4,00 GHz | RAM: 16 GB DDR4-2133 | Grafik: Gigabyte GTX 980 OC (NVidia-Treiber Version 358.91) | Windows 10 64-Bit

Offline Rednose

  • Pirate Party Member
  • Avast Überevangelist
  • Massive Poster
  • *****
  • Posts: 3624
  • Bits of Freedom : https://www.bof.nl
    • Nederlandstalig Avast! forum
Re: Avast causes Blue Screen after Windows 10 Anniversary Update
« Reply #1 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.
OS: Win 7 x64 SP1 / Ubuntu / Qubes OS / iOS
Real Time: Avast Premier Beta + AMS for iOS Beta WinPatrol Plus Unchecky MCShield  HOSTS File: MVPS + MDL
On Demand: MBAM SUMo
Backup: Win 7 Image
Proxy: ASL VPN's Socks 5 Tor

Offline Rednose

  • Pirate Party Member
  • Avast Überevangelist
  • Massive Poster
  • *****
  • Posts: 3624
  • Bits of Freedom : https://www.bof.nl
    • Nederlandstalig Avast! forum
Re: Avast causes Blue Screen after Windows 10 Anniversary Update
« Reply #2 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.
OS: Win 7 x64 SP1 / Ubuntu / Qubes OS / iOS
Real Time: Avast Premier Beta + AMS for iOS Beta WinPatrol Plus Unchecky MCShield  HOSTS File: MVPS + MDL
On Demand: MBAM SUMo
Backup: Win 7 Image
Proxy: ASL VPN's Socks 5 Tor

Offline Wahnfried1883

  • Newbie
  • *
  • Posts: 4
Re: Avast causes Blue Screen after Windows 10 Anniversary Update
« Reply #3 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
Mainboard: Gigabyte GA-Z170X-Gaming 3 | CPU: Intel Core i7-6700K @ 4,00 GHz | RAM: 16 GB DDR4-2133 | Grafik: Gigabyte GTX 980 OC (NVidia-Treiber Version 358.91) | Windows 10 64-Bit

Offline Darecki2k

  • Newbie
  • *
  • Posts: 2
Re: Avast causes Blue Screen after Windows 10 Anniversary Update
« Reply #4 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 ...

Offline misterp28516

  • Newbie
  • *
  • Posts: 10
Re: Avast causes Blue Screen after Windows 10 Anniversary Update
« Reply #5 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.

Offline Scott39

  • Newbie
  • *
  • Posts: 8
Re: Avast causes Blue Screen after Windows 10 Anniversary Update
« Reply #6 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.

Offline Texas Kelly

  • Newbie
  • *
  • Posts: 1
Re: Avast causes Blue Screen after Windows 10 Anniversary Update
« Reply #7 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.

Offline petr.chytil

  • Quality Assurance Director
  • Moderator
  • Full Member
  • *
  • Posts: 124
Re: Avast causes Blue Screen after Windows 10 Anniversary Update
« Reply #8 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

Offline Scott39

  • Newbie
  • *
  • Posts: 8
Re: Avast causes Blue Screen after Windows 10 Anniversary Update
« Reply #9 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

Offline Milos

  • Avast team
  • Super Poster
  • *
  • Posts: 2039
Re: Avast causes Blue Screen after Windows 10 Anniversary Update
« Reply #10 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

Offline Shaun985

  • Jr. Member
  • **
  • Posts: 62
Re: Avast causes Blue Screen after Windows 10 Anniversary Update
« Reply #11 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.

Offline THE BIG ONE

  • Newbie
  • *
  • Posts: 1
Re: Avast causes Blue Screen after Windows 10 Anniversary Update
« Reply #12 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}


Offline misterp28516

  • Newbie
  • *
  • Posts: 10
Re: Avast causes Blue Screen after Windows 10 Anniversary Update
« Reply #13 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

Offline bob3160

  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 40531
  • 59 Years of Happiness
    • bob3160 Protecting Yourself, Your Computer and, Your Identity
Re: Avast causes Blue Screen after Windows 10 Anniversary Update
« Reply #14 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
Free avast! Security Seminar: https://goo.gl/kh3cqR  -  Important: http://www.organdonor.gov/ -- My Web Site: http://bob3160.strikingly.com/ - Win 10 Pro v1809 64bit, 8 Gig Ram, AvastFree 19.4.2374, How to Successfully Install Avast http://goo.gl/VLXdeRepair & Clean Install https://goo.gl/t7aJGq