Author Topic: BSOD has occurred TWICE in 14 days; BSOD scan indicates Avast! is the cause???  (Read 1369 times)

0 Members and 1 Guest are viewing this topic.

Offline kls490

  • Sr. Member
  • ****
  • Posts: 208
  • Queen of the house
Good morning everyone!

      In the past 14 days, there have been two occasions when for no apparent reason, my computer suddenly displayed the BSOD.  On both occasions, I was offline, at the Desktop screen, and doing absolutely nothing.

I have pasted below the BSOD scan I ran just a short time ago which appears to indicate Avast! is causing the issue.  I would appreciate it if someone could take a look at the scan and advise how to remedy this BSOD from occurring again.
(Granted...twice in two weeks is not a lot...but is a cause for concern to me)

==================================================
Dump File : Mini082911-01.dmp
Crash Time : 8/29/2011 3:56:27 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x805062d0
Parameter 3 : 0xee503a38
Parameter 4 : 0x00000000
Caused By Driver : aswSP.SYS
Caused By Address : aswSP.SYS+1e27c
File Description : avast! self protection module
Product Name : avast! Antivirus System
Company : AVAST Software
File Version : 6.0.1203.0
Processor : 32-bit
Crash Address : ntoskrnl.exe+2f2d0
Stack Address 1 : aswSP.SYS+1e27c
Stack Address 2 : aswSP.SYS+1e9a3
Stack Address 3 : aswSP.SYS+1ee7f
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini082911-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 65,536
==================================================

Thanks very much for your time and any help!
« Last Edit: August 30, 2011, 06:57:21 AM by spc3rd »
kls490

Offline pk

  • Avast team
  • Super Poster
  • *
  • Posts: 2071
please update to beta 1273 (http://forum.avast.com/index.php?topic=83583.0), this bug is already fixed there.

thanks

Offline kls490

  • Sr. Member
  • ****
  • Posts: 208
  • Queen of the house
Thanks very much for the update info PK!  The problem seems to have been resolved.
kls490