Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Aco on November 01, 2012, 03:02:04 PM
-
Well Windows 8 is still crashing for me with Avast Free Antivirus version 7.0.1474, giving me aswnet,sys error. I'm using Windows 8 Pro x64.
One thing I noticed while checking Avast forums last few days since I got Windows 8 is that some people here were saying they have no problems, and most people that had BSOD problems said they were using 64bit version, I even saw some people saying they have BSOD with Windows XP 64bit.
If I'm not wrong Avast is 32bit application? Usually when some programs have both 32bit and 64bit versions you have 2 separate installers, and for Avast there is only 1, so I assume it's 32bit.
But weird thing is that in Windows 8 x64 Avast install itself in "Program Files" folder, while it should go into "Program Files (x86)" folder if it's 32bit application. If I'm not wrong, could something banal like this be the cause of malfunctioning?
-
Having the same problem now too had a different one that was fixed now I have this one..
Log Name: Application
Source: Windows Error Reporting
Date: 11/1/2012 10:06:50 AM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: stefanie
Description:
Fault bucket AV_aswnet+25a4c, type 0
Event Name: BlueScreen
Response: http://wer.microsoft.com/responses/resredir.aspx?sid=10&Bucket=AV_aswnet+25a4c&State=1&ID=45fef28b-9beb-4eaa-aa92-f3c28a4a7fa6
Cab Id: 45fef28b-9beb-4eaa-aa92-f3c28a4a7fa6
Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Attached files:
C:\Windows\Minidump\103112-20638-01.dmp
C:\Users\MIKE AND STEF\AppData\Local\Temp\WER-42609239-0.sysdata.xml
C:\Windows\MEMORY.DMP
C:\Users\MIKE AND STEF\AppData\Local\Temp\WERA12B.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_06beb2d7
Analysis symbol:
Rechecking for solution: 0
Report Id: 103112-20638-01
Report Status: 0
Hashed bucket:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-11-01T14:06:50.000000000Z" />
<EventRecordID>424698</EventRecordID>
<Channel>Application</Channel>
<Computer>stefanie</Computer>
<Security />
</System>
<EventData>
<Data>AV_aswnet+25a4c</Data>
<Data>0</Data>
<Data>BlueScreen</Data>
<Data>http://wer.microsoft.com/responses/resredir.aspx?sid=10&Bucket=AV_aswnet+25a4c&State=1&ID=45fef28b-9beb-4eaa-aa92-f3c28a4a7fa6</Data>
<Data>45fef28b-9beb-4eaa-aa92-f3c28a4a7fa6</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
C:\Windows\Minidump\103112-20638-01.dmp
C:\Users\MIKE AND STEF\AppData\Local\Temp\WER-42609239-0.sysdata.xml
C:\Windows\MEMORY.DMP
C:\Users\MIKE AND STEF\AppData\Local\Temp\WERA12B.tmp.WERInternalMetadata.xml</Data>
<Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_06beb2d7</Data>
<Data>
</Data>
<Data>0</Data>
<Data>103112-20638-01</Data>
<Data>0</Data>
<Data>
</Data>
</EventData>
</Event>
-
Can anyone with knowledge on the subject confirm if this could cause the problem or not?
-
There is actually a topic above your's that confirms it already...and yes, I get the BSOD from that system file too. :)
-
I think you maybe misunderstood what I was asking. I know that aswnet.sys is responsible for BSOD in Windows 8. I asked something differently.
I noticed that only users of 64bit versions of Windows 8 and XP were complaining about BSOD, and since Avast is 32bit app (correct me if I'm wrong) it should be installed in "Program Files (x86)" folder on 64bit machines, but it's installed in "Program Files" folder instead where only 64bit apps are placed if I'm not wrong. So I wanted to know could it be possible that wrong install location would cause this malfunctions? I know it's a long shot and highly unlikely that folder location could cause such a problems, but I only noticed people with 64bit versions complaining so...
-
I think you maybe misunderstood what I was asking. I know that aswnet.sys is responsible for BSOD in Windows 8. I asked something differently.
I noticed that only users of 64bit versions of Windows 8 and XP were complaining about BSOD, and since Avast is 32bit app (correct me if I'm wrong) it should be installed in "Program Files (x86)" folder on 64bit machines, but it's installed in "Program Files" folder instead where only 64bit apps are placed if I'm not wrong. So I wanted to know could it be possible that wrong install location would cause this malfunctions? I know it's a long shot and highly unlikely that folder location could cause such a problems, but I only noticed people with 64bit versions complaining so...
I've got it only happening on a 32-Bit system under Windows 8, whereas my 64-Bit system under the same OS is working just fine. :(
-
there should be either full memory.dmp in C:\Windows\ or xyz.dmp in C:\Windows\Minidump. PLease upload it to ftp.avast.com/incoming (and let us know the name of the dump).
thank you
Lukas.
-
Can anyone with knowledge on the subject confirm if this could cause the problem or not?
On x64 systems, the drivers are always 64bit. No other way around, so it does not matter whether the application itself is 32bit or 64bit (and avast is not such a memory eater to justify the later).
I have also noticed more crashes on 64bits - possibly because 64bits Windows 8 are simply more common than 32bit ones.
-
I uploaded only last 4 minidump files cause those 4 BSODs happened with latest version of Avast, if you need those that happened with previous version let me know.
Last BSOD happened when I was trying to install FileZilla to upload these minidump logs. It mostly happens when installing something or running executable files, and it happens on very start of installation after you click on "Yes" in that popup by Windows' UAC.
BSOD also happened to me twice while I was away from computer, so it could be that screensaver can also trigger it (Windows' default 3D text screensaver). But each time BSOD happened I think I had metro apps running in background.
-
Hello Everybody Hello Avast,
Yesterday I had installed win 8 Pro. Everything went well until the current avast Internet security is installed. Irregular, I had then a blue screen with the note on the ASWNET.SYS. Avast Deinstalliert and everything runs again fine. Am dodged now on AVG. My license is valid for 1 year. Here is a solution in sight?
Greetz Heiko
-
Hello Everybody Hello Avast,
Yesterday I had installed win 8 Pro. Everything went well until the current avast Internet security is installed. Irregular, I had then a blue screen with the note on the ASWNET.SYS. Avast Deinstalliert and everything runs again fine. Am dodged now on AVG. My license is valid for 1 year. Here is a solution in sight?
Greetz Heiko
They are working on it my friend. The issue isn't consistent, so they need to find the exact cause before they can solve the problem. :)
-
It seems so that Avast is also making it difficult to access control panel of my ADSL router.
-
It seems so that Avast is also making it difficult to access control panel of my ADSL router.
Yes. It's caused by the network shield bug.
-
It seems so that Avast is also making it difficult to access control panel of my ADSL router.
Yes. It's caused by the network shield bug.
Well I saw few people suggesting to turn off network shield, but I'd rather leave it on and be patient with BSODs untill next version of Avast and hopefully a fix.
I also noticed that starting task manager on desktop when metro apps are running in background also causes BSOD.
-
It seems so that Avast is also making it difficult to access control panel of my ADSL router.
Yes. It's caused by the network shield bug.
Well I saw few people suggesting to turn off network shield, but I'd rather leave it on and be patient with BSODs untill next version of Avast and hopefully a fix.
I also noticed that starting task manager on desktop when metro apps are running in background also causes BSOD.
It seems to be random, but it appears certain things will trigger it randomly too. A few days ago I tried 7 times to install Adobe Reader and kept getting the BSOD when running the installer. The 8th time it let it install fine. Sadly, I opened another installer afterwards and got the BSOD. :(
-
I'm having the same problem ... I am using windows 8 Pro, pause when all modules residing on the screen count if I click yes or no, a BSOD occurs, the file appears in the BSOD and aswnet.sys my system and 64-bit, but already happened when used the 32-bit
-
Please try the freshly built driver, as described here: http://forum.avast.com/index.php?topic=108441.msg858780#msg858780 (http://forum.avast.com/index.php?topic=108441.msg858780#msg858780)
-
Please try the freshly built driver, as described here: http://forum.avast.com/index.php?topic=108441.msg858780#msg858780 (http://forum.avast.com/index.php?topic=108441.msg858780#msg858780)
Well I replaced it, I'll report back tomorrow if I had BSOD or not.
-
Newbie coogan607 here. Windows 8 Pro 64-bit. Dell XPS15z laptop. I have uploaded my 2 most recent mini dumps, labelled coogan607_minidmp.zip. Just like others, it usually crashes whenever I try to install a program. For the moment I've had to uninstall Avast because I need my machine to function. I hope Windows Defender will keep me (reasonably) safe.
Good, satisfied Avast customer with 2 home PCs for more than a year. I'd really like to use the product.
-
So far so good. I didn't have time to thoroughly test it though, but so far it seems to be fixed.
-
So far so good. I didn't have time to thoroughly test it though, but so far it seems to be fixed.
Same here. Nearly 24 hours going strong! :)
-
After more thorough testing BSOD is definitely gone. Only problem still remaining that I noticed is that you still need to disable Network Shield to be able to access control panel of your router.