BSOD On "Run Smart Scan"

[badass]

I was working on this computer that sat for about 6mo Unplugged.  The CMOS seemed to be dead and I think that corrupted the BIOS.  Once I got a new CMOS in it and Fixed the BIOS Configuration it all worked perfectly. 

Then I opened Avast to do a quick scan and the BSOD happened.  Here is the Minidump.  Hope you guys can help as I see two others with the same issue here on the first page of the forum.  I don't want to mess around with it to much myself so as not to make it worse.

Code: [Select]

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.24059.amd64fre.win7sp1_ldr_escrow.180308-1637
Machine Name:
Kernel base = 0xfffff800`03013000 PsLoadedModuleList = 0xfffff800`03252c90
Debug session time: Thu Nov 22 16:28:33.706 2018 (UTC - 5:00)
System Uptime: 0 days 0:05:08.079
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880045b6be7, The address that the exception occurred at
Arg3: fffff88006c91908, Exception Record Address
Arg4: fffff88006c91170, Context Record Address

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
aswHdsKe+10be7
fffff880`045b6be7 0f1003          movups  xmm0,xmmword ptr [rbx]

EXCEPTION_RECORD:  fffff88006c91908 -- (.exr 0xfffff88006c91908)
ExceptionAddress: fffff880045b6be7 (aswHdsKe+0x0000000000010be7)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000048
Attempt to read from address 0000000000000048

CONTEXT:  fffff88006c91170 -- (.cxr 0xfffff88006c91170)
rax=0000000000000000 rbx=0000000000000048 rcx=0000000000000000
rdx=fffff88006c91b00 rsi=fffffa80071d1a00 rdi=fffffa800891e340
rip=fffff880045b6be7 rsp=fffff88006c91b40 rbp=fffff88006c91bc0
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=fffffa800a59bc10 r12=0000000000000001 r13=fffffa800891f010
r14=fffffa800891f0b8 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
aswHdsKe+0x10be7:
fffff880`045b6be7 0f1003          movups  xmm0,xmmword ptr [rbx] ds:002b:00000000`00000048=????????????????????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000048

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b6100
GetUlongFromAddress: unable to read from fffff800032b61c8
 0000000000000048 Nonpaged pool

FOLLOWUP_IP:
aswHdsKe+10be7
fffff880`045b6be7 0f1003          movups  xmm0,xmmword ptr [rbx]

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from fffff88006c91ba0 to fffff880045b6be7

STACK_TEXT: 
fffff880`06c91b40 fffff880`06c91ba0 : 00000000`00000000 fffffa80`071d1a00 fffffa80`071d1a00 fffffa80`0891e340 : aswHdsKe+0x10be7
fffff880`06c91b48 00000000`00000000 : fffffa80`071d1a00 fffffa80`071d1a00 fffffa80`0891e340 fffffa00`0891f010 : 0xfffff880`06c91ba0


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  aswHdsKe+10be7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: aswHdsKe

IMAGE_NAME:  aswHdsKe.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5bf147c4

STACK_COMMAND:  .cxr 0xfffff88006c91170 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_aswHdsKe+10be7

BUCKET_ID:  X64_0x7E_aswHdsKe+10be7

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


[NON]

It's a known issue, devs are working on fix.

Hello Mr. Martin. I'm just your everyday avast user

Yesterday at 21 nov after i updated my avast and finished it. I run smart scan like always i done after successfully updated it. But when i do smart scan suddenly my computer goes blue screen and restarted. I already do this: https://support.avast.com/en-eu/article/Troubleshoot-blue-screen-crash | But still it failed and still goes blue screen. Now i am desperate and do you have any idea or opinion on how to fix it?

I apologize for the inconvenience. We are already working on fix. Please do not run the smart scan unless we release the hotfix.

[badass]

Thanks!  I'll wait for the next hotfix.

[badass]

It looks like this has been fixed, can someone confirm?

[Tangy]

It looks like this has been fixed, can someone confirm?

https://forum.avast.com/index.php?topic=223244.60

[badass]

Thank you very much, this was an important issue for me today.

[Tangy]

You are welcome !