Avast! Free Antivirus BSOD Crash

Avast Free Antivirus / Premium Security
1

Stop damaging people’s systems with your well-for-nothing products!

BSOD
Mini060311-01.dmp

==================================================
Filename : aswSnx.SYS
Address In Stack : aswSnx.SYS+376c1
From Address : 0xa90d6000
To Address : 0xa9146000
Size : 0x00070000
Time Stamp : 0x4dc929a9
Time String : 5/10/2011 15:03:53
Product Name : avast! Antivirus System
File Description : avast! Virtualization Driver
File Version : 6.0.1125.0
Company : AVAST Software
Full Path : C:\WINDOWS\system32\drivers\aswSnx.SYS

==================================================
Filename : aswSP.SYS
Address In Stack : aswSP.SYS+103c4
From Address : 0xa9146000
To Address : 0xa918f180
Size : 0x00049180
Time Stamp : 0x4dc9299f
Time String : 5/10/2011 15:03:43
Product Name : avast! Antivirus System
File Description : avast! self protection module
File Version : 6.0.1125.0
Company : AVAST Software
Full Path : C:\WINDOWS\system32\drivers\aswSP.SYS

==================================================
Filename : ntoskrnl.exe
Address In Stack : ntoskrnl.exe+98910
From Address : 0x804d7000
To Address : 0x80700000
Size : 0x00229000
Time Stamp : 0x4d00dcb6
Time String : 12/9/2010 16:42:14
Product Name : Microsoft® Windows® Operating System
File Description : NT Kernel & System
File Version : 5.1.2600.6055 (xpsp_sp3_gdr.101209-1647)
Company : Microsoft Corporation
Full Path : C:\WINDOWS\system32\ntoskrnl.exe

System Info:

Windows XP SP3 (fully updated)
Internet Explorer 8 (fully updated)
Avast! Free Antivirus 6.0.1125.0 (fully updated)
PC Tools Firewall Plus 7.0.0.123

Thanks :-[

2

Dump files are not posted here on the forum, they are uploaded directly to Avast. Here is the proper way to submit a dump file instead of ranting and raving about it for everyone including Google to see:

Here is additional information on how to invoke a memory dump file: http://support.avast.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=71.

Please, zip and upload the C:\Windows\Memory.dmp file to this anonymous ftp server and name it uniquely giving us the name of the file in this thread: ftp.avast.com/incoming. Avast will analyze it and respond back to you in this thread.

If you are having difficulty with dump file:

  • Using Internet Explorer, Connect to the link and drag the file into the Right pane and drop it, that starts the upload, you don’t have read access to this folder, so you won’t be able to see it once uploaded.
    Or

  • Upload it using the Run command-line in Windows: Windows Key + R (to get the run box), copy and paste this:
    Code: explorer ftp.avast.com/incoming

    and drag the file into the window, from another explorer window.

Thank you. :slight_smile:

3

I’ve not come here to upload dumps.
My system is not a laboratory mouse for Avast software alchemists to make experiments.

Thanks :-[

4

We are trying to help you with your issue and this is one way to do it. No one except you mentioned anything about your machine being used for an experiment. Avast analyzes your data that you submit to see if you have any conflicting software or OS problems that are causing your issues. This is the best way to determine your problem and fix it.

However you are free to submit a technical issues with Avast, which may take longer here: http://www.avast.com/contact-form.php?loadStyles - use the drop down menu and reference this thread. Keep in mind that you can only submit this once for a problem. Good luck to you.

5

Then what did you come here for ?

How can the Avast software alchemists analyse you problem without information. Uploading the dump files won’t turn you or your system into a lab rat; but help to resolve the problem for you and possibly others with a similar system setup.

I have XP Pro SP3 and haven’t experienced any BSOD even during the various beta and pre-release trials, lucky I guess.

6

How lucky you are :slight_smile: But for me :frowning: http://forum.avast.com/index.php?topic=78365.0

7

Well if you take it out of context with the rest of my post, it doesn’t sit right.

The whole point is to show the OP that it doesn’t happen to everyone as systems have some multitudes of different configurations and why sending the minidumps (or preferably the full memory.dmp) is important if you want any progress at all.

8

(Off Topic)Thanks for the reply.Anyway,the purpose for me to post my thread link here is to alert all of you.I have been waiting for the response for so long.I am quite feeling impatient now.

9

Then you should bump the topic again to bring it to the top of the order.

10

I already bumped for several times.I will bump it again on the right time.

11

Here we go again the “Avast” people

Mini060311-02.dmp

==================================================
Filename : aswSP.SYS
Address In Stack : aswSP.SYS+42118
From Address : 0xa9152000
To Address : 0xa919b180
Size : 0x00049180
Time Stamp : 0x4dc9299f
Time String : 5/10/2011 15:03:43
Product Name : avast! Antivirus System
File Description : avast! self protection module
File Version : 6.0.1125.0
Company : AVAST Software
Full Path : C:\WINDOWS\system32\drivers\aswSP.SYS

==================================================
Filename : ntoskrnl.exe
Address In Stack : ntoskrnl.exe+95694
From Address : 0x804d7000
To Address : 0x80700000
Size : 0x00229000
Time Stamp : 0x4d00dcb6
Time String : 12/9/2010 16:42:14
Product Name : Microsoft® Windows® Operating System
File Description : NT Kernel & System
File Version : 5.1.2600.6055 (xpsp_sp3_gdr.101209-1647)
Company : Microsoft Corporation
Full Path : C:\WINDOWS\system32\ntoskrnl.exe

::slight_smile: