Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: ChasErnst on May 25, 2013, 12:05:22 AM
-
I have been using Avast for many years and never ever had any issues with it. Recently rebuilt my machine and installed the latest Avast and boom... constant Blue screen of death. Because I never had issues with Avast before I thought for sure it was another bogus driver or user error etc. Reinstalled Vista 64 and as soon as Avast went on... blue screen.
I have a AMD 8 core 990fx based machine, 16gb ram
Like the subject says... went back to the older version of Avast and every thing is smooth as butter.
couldn't put the dmp file in here... too big... so here is a link
https://dl.dropboxusercontent.com/u/7155952/Mini052413-01.zip (https://dl.dropboxusercontent.com/u/7155952/Mini052413-01.zip)
here is what WhoCrashed is saying.
On Fri 5/24/2013 11:46:24 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini052413-37.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x57150)
Bugcheck code: 0x50 (0xFFFFFA600C74F000, 0x0, 0xFFFFF80002928E2E, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 5/24/2013 11:46:24 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFFA600C74F000, 0x0, 0xFFFFF80002928E2E, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 5/24/2013 11:29:36 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini052413-36.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x57150)
Bugcheck code: 0x50 (0xFFFFFA60109C7000, 0x0, 0xFFFFF800028EDE2E, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 5/24/2013 10:44:06 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini052413-35.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x57150)
Bugcheck code: 0x50 (0xFFFFFA600EF5E000, 0x0, 0xFFFFF800026E2E2E, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
-
Please check for the corresponding minidump files (in C:\Windows\Minidump) and upload them to ftp://ftp.avast.com/incoming
-
they are up there.
-
Hmm..this seems to be quite a common occurance with the latest version of avast.It would appear i am not the only one to be having issues.
This is not good when an av is having such a wide spectrum of bluescreens on a variety of computers.
-
Same case to me but it happened to Windows XP SP3 x86, and instead of BSOD it just freezes.
The version is 8.0.1489.
Went back to 7.0.1426, no more problems.
-
upload dumps to ftp.avast.com/incoming
dumps should be in C:\windows\minidumps
-
That's another reason I've temporarily ditched Avast... as well as pushing you know what!
Why on Gods Earth is Avast not allowing people to use a version that they are happy with, I do feel we are being used as guinea pigs for many of their updates.... and without being 'pushy', they'd probably find many people not using Avast 8 - am I right?
I had a BSOD doing a boot scan with Avast - no don't bother, one or two on here will ask for a dump file - think about it before you do uh! There wasn't any.
Yes we can understand AV's giving problems but not for causing BSODs - why, didn't they beta them properly?
Avast has seriously gone down hill and needs to get a grip 'prompt'! Avast could do well to understand not everyone has the same computer config. nor is everyone using the latest operating system.
Would it not be feasible to keep Avast releases for separate operating systems rather than rely on one program for all operating systems?
Avast has plainly gone from being a stable system to a problematic one - will it crash or won't it, we never had to worry before.
Dave
-
Why were you performing a boot scan? Those are only for emergencies when your system is infected.
-
Interesting.
I must admit i have never seen the word BSOD mentioned so much as in this very forum and in relation to the new release.
-
I had a BSOD doing a boot scan with Avast - no don't bother, one or two on here will ask for a dump file - think about it before you do uh! There wasn't any.
The boot-time scan is a user mode application (not a kernel mode component) - so to be able to bluescreen the system, it would actually have to exploit a bug in Windows itself.
So I'm afraid it's not a problem in the boot-time scan. Might be a hardware problem (remember any scan stresses the system), or a conflict with some other software, or a bug in drivers - but unrelated to the boot-time scan.
Yes we can understand AV's giving problems but not for causing BSODs - why, didn't they beta them properly?
avast! v8.0.1489 is currently being used by more than 20 millions of users, and the vast majority is fine. The beta team did a good job - but it's simply not possible to cover all the configurations and all the software existing on the userbase avast! has. (And of course, the cause of the BSODs may actually be in other software, it can only manifest together with avast! installed/updated.)
Avast has plainly gone from being a stable system to a problematic one - will it crash or won't it, we never had to worry before.
Might be "plain" for you (according to what? a few posts on the forum? Sorry, but people will always post on the forum mainly when they have a problem, not when they are OK), but I believe you are wrong.
We are monitoring the crashes (e.g. via the Microsoft reporting program) - and avast! 8 is crashing less than previous versions.
-
@ChasErnst: is there \windows\memory.dmp file in Windows folder? If not, you can enable it in Control Panel (System). I'm afraid we'll need kernel-mode dump to see which Windows component caused your BSODs.
-
I've been running Avast for years and couldn't be happier (well you did miss one virus on me) - until the last update to 8.0.1489. I now get consistent BSOD after my computer is idle for 6 to 10 minutes. As long as I am actively using the computer it's fine. Once the first BSOD occurred, Avast was the last thing I thought was causing the problem. I updated drivers, ran a memory check, ran a heat test all passed with flying colors. Wish I would have had a restore point, but didn't. Hmmm, where did those go? Used to have them. But that's another story. The machine also doesn't crash in SAFE mode. Having researched BSOD in general I noticed several references to anti-virus software in general. As a last ditch effort (after having ordered a new computer) I disabled Avast and haven't had a problem since. It may help to mention I am running Vista Home Premium, Service Pack 2
It is a mighty unsettling feeling to NOT be running any anti-virus software :-\ HELP!!! Any suggestions from the Avast Team? Anyone??? I may have a new computer coming, but I'm not ready to ditch this one if the only problem it has is Avast. I am going to try and ftp the mini dump files.
Thanks for any help - it will so much appreciated!
-
Well, FTP'ing the mini dump files to the ftp site mentioned above didn't work. I guess I wait for further directions if you need to see my mini dumps.
Sorry about that.
-
you can send me (kurtin@avast.com) minidump on my email address
-
I updated Avast last week and got a BSOD the next day. Just got another BSOD last night. I'm running Vista 64. Both times I was away from the computer for a few hours and not running any applications.
Mini dump info from BlueScreenView.
aswSnx.SYS aswSnx.SYS+5f075 fffffa60`04409000 fffffa60`04508000 0x000ff000 0x518b62de 5/9/2013 1:48:30 AM
ntoskrnl.exe ntoskrnl.exe+bba20 fffff800`03249000 fffff800`0375f000 0x00516000 0x513a94a9 3/8/2013 6:47:21 PM
-
Davy . . . I am finding Tech Support to be outstanding. The Avast Team (PK) has asked for my min-dumps, which by the way, in my case there were plenty of them. That wasn't enough to see my spedific problem, so I was also asked for my memory.dmp. I have since been asked to download a patch to fix my problems. This back and forth e-mail exchanged was on a SUNDAY!! I couldn't have asked for better tech support. So I don't think it is fair to even suggest Avast is going down hill.
However I am going to wait to install the patch until this machine becomes my secondary machine. My new computer is coming in tomorrow. I will be running Windows 7 instead of Vista and I expect the standard version of Avast 8 will work just fine. My partner is running Windows 7 and has no problems at all with Avast 8.
The response for tech support was outstanding compared to other companies. THANK YOU PK!
-
Welcome to forums and avast! support Karola :)
-
KarolaW, whats that gotta do with me?
Why on Gods Earth should I need contact PK support, or any Avast support?
Are you reading the threads properly?
Dave
-
KarolaW, whats that gotta do with me?
Why on Gods Earth should I need contact PK support, or any Avast support?
Are you reading the threads properly?
Dave
Do you have anything useful to contribute towards solving the problem some users appear to be having or are you just
here to bitch ???
If you can't help or contribute, stop complaining. You aren't accomplishing anything.
-
Got better things to do Bob, just that it seemed to be making out that it was me who needed to contact teck support hence, "whats its gotta do with me".
I've never had to contact Tech support as far as I know, I recall posting a question or two on here from time to time and indeed was resolved either by advice here or otherwise... certainly no problem with that!
But the post suggested otherwise, don't you thin, thus my reply?
The only niggle I have is Avast piggy backing, like so many others here, and indeed installing Chrome without ones knowledge... and yes it did/does just that, OK?
Now then to you:
Looking through the threads I've noted one or two comments by your good self that has neither been useful or 'informative'.....
just like the comment YOU just made - helpful to all thus my reply.
Dave
-
Unfortunately this has also been my problem with this forum.
I have stated a few times that avast was causing bsods on my system and i have been met with nothing but personal criticism and no clear endeavour to actually help with the problem.
There is an air of distinct avast fanboyism within this forum and some people INSIST that avast is totally bug free when the countless threads on here dictate otherwise.
I certainly hope the avast technical support is better.
-
@Arnold72 and Davy
If you read instead of posting you would have noticed that the request has been made several times to send in your mini dump files
for analysis.
Complaining without the willingness to help solve the problem is totally useless for those that have the problem or for Avast in their ability to resolve the problem.
-
Bob.
I will complain, whinge, bitching as you called it because Avast has not only given ME grief, it wasted my time in the process - you can call it what you like BOB, I do not want Chrome, I will not have Chrome yet Avast was pushing it onto me....
if I had known this when I came to Avast in the first instance - I would have stayed well clear, yes I have a right to whinge, moan, complain or bitch, I did not pay for this?
By the Way your comments don't exactly help either so stop antagonizing people, you need to realize BOB, Avast is causing itself problems.... along with folks denying that Avast doesn't install Chrome without ones permission or knowledge is wrong - completely wrong, that's why so many folks are whinging, complaining or bitching as you put it.
You may not like the answer but is fact that Avast can install Chrome without consent, which in some cases Chrome causing one hell of a problem along with the other 'usual' Anti Virus problems... so where is the root of the problem, Chrome, Avast or both?
This is why I said Avast needs to get itself sorted out, it's all here in black and white on the forum, it isn't a fairy tail BOB - it's real!
Dave
-
Davy said: I had a BSOD doing a boot scan with Avast - no don't bother, one or two on here will ask for a dump file - think about it before you do uh! There wasn't any.
I apologize for my comment IF I misread your post. But I don't think so.
I was responding to your suggestion that people shouldn't bother looking for mini dump files because there weren't any. That may have been true in your case, but please don't give advice to others based on the assumption that their results are the same as yours. It just confuses users who are not as tech savvy as you think you are. That is why I made the reference, "in my case there were plenty of mini dump files." I didn't even know what a mini dump was much less that I have a memory.dmp. From reading your posts you are a lot more tech savvy than I am. And that is what users rely on. We hope to find solutions not only from the Avast team but other users with the same/similar issues. The OP of the thread rolled back to an earlier version. Great suggestion, I can totally believe that is a solution for people who have that option. I don't have access to earlier versions, so for me I have to look elsewhere for a fix. But at least the OP didn't confuse me like you did.
Many people come to this forum after they exhaust all other possibilities of what the problem may be. I for one was very happy to see that Avast monitors and is responsive to users posting on their forum. How often have you been on forums where the company totally ignores an issue/bug?
Complain all you want, but show me one software package that isn't occasionally released with bugs. So are they all, as you put it "going downhill?"
-
No problem KarolaW....
BTW: I was responding to your suggestion that people shouldn't bother looking for mini dump files because there weren't any.
I said
I had a BSOD doing a boot scan with Avast - no don't bother, one or two on here will ask for a dump file - think about it before you do uh! There wasn't any.
Please note the word 'I'. Then I said no don't bother, one or two on here will ask for a dump file - think about it before you do uh! There wasn't any
.
Please note.... 'There wasn't any'.
Indeed Dump files can be a savior whether hardware problems or ANY software problems - remember I was doing a boot scan so there won't be any will there?
Please do show where I suggested people shouldn't send their dump files?
Dave
-
Update time - My problem with constant BSOD's when my machine was left idle has been solved. PK had me download a patch after reviewing my memory.dmp file and it is working flawlessly. The patch was installed over 48 hours ago and I haven't seen a single BSOD. The machine has seen more idle time in the last couple days than it usually does, not to mention the 8 hours when I sleep. I can't thank you enough for your patience with me, PK.
As far as my discussion with Davy goes, maybe we better put it to rest. I am all too willing to argue my point out of conviction in great length, I just don't think this is the place to do it. Let it suffice to say that I felt a lot of negative vibes that set me on edge. Again I apologize for any misinterpretation of your comments. I hope you reach a happy resolution as I have.
-
KarolaW,
Any chance you can send me the patch PK sent you? I've been experiencing the exact same problem with the new version and vista 64.
-
I don't mind sharing, but I have no idea how specific this patch is to my problem. How do I send it to you? I was sent a link that automatically downloaded a zip file. There must be a reason why they do not post that link here on the forum. I would guess it only solves certain problems? Hence I wasn't sent the patch till after they looked at my mini dumps and my memory.dmp file. But if you want to take a chance on it, I need someplace to send it.
-
KarolaW,
Any chance you can send me the patch PK sent you? I've been experiencing the exact same problem with the new version and vista 64.
I suggest that you contact PK. Patches are usually based on information supplied by a user.
The patch supplied to mcguirk may not work on your system and could actually harm your system.
-
Things are getting confused. The patch was offered to KarolaW. And I agree and was trying to suggest the same thing. I don't want anyone messing up their system more than necessary.
-
Thanks guys. I understand. Just hoping for an easy fix. How would I go about generating and sending PK a minidump?
-
Thanks guys. I understand. Just hoping for an easy fix. How would I go about generating and sending PK a minidump?
Look for the latest minidump in C:\WINDOWS\Minidump or in C:\Windows\MEMORY.DMP. Compress it with ZIP, RAR or 7Zip and give it an original name. Add a text ( use notepad ) with your Forum e-mail and this post URL.
Open Windows Explorer and copy/paste this:
ftp://ftp.avast.com/incoming
Drag/drop compressed dump file into the right open window. Wait for transmission to conclude.
You can also do it like this:
Start > Run.
Copy/paste
explorer ftp://ftp.avast.com/incoming
Drag dump file into the ftb window.
E-mail PK and let him know the name of the dump. kurtin[at]avast[dot]com
-
Thanks. I appreciate the help.
-
Thanks. I appreciate the help.
You are welcome. Good luck.
-
I have the newest Avast! running on Vista64. Same problem here. BSOD when opening certain programs like Fifa13 - 100% of the time. Disabling shields fixes this. Started after updating to Avast8. Would appreciate a fix :)
Error happens here: ntoskrnl.exe+57150
edit:
Looking at minidumps pasted in this thread I get exactly the same errors and most people seem to be using Vista64. Yeah I know Vista is old and sucks but I'd rather not upgrade just yet.
-
I have the newest Avast! running on Vista64. Same problem here. BSOD when opening certain programs like Fifa13 - 100% of the time. Disabling shields fixes this. Started after updating to Avast8. Would appreciate a fix :)
Error happens here: ntoskrnl.exe+57150
edit:
Looking at minidumps pasted in this thread I get exactly the same errors and most people seem to be using Vista64. Yeah I know Vista is old and sucks but I'd rather not upgrade just yet.
http://forum.avast.com/index.php?topic=117134.msg951968#msg951968
-
I have the newest Avast! running on Vista64. Same problem here. BSOD when opening certain programs like Fifa13 - 100% of the time. Disabling shields fixes this. Started after updating to Avast8. Would appreciate a fix :)
Error happens here: ntoskrnl.exe+57150
edit:
Looking at minidumps pasted in this thread I get exactly the same errors and most people seem to be using Vista64. Yeah I know Vista is old and sucks but I'd rather not upgrade just yet.
http://forum.avast.com/index.php?topic=117134.msg951968#msg951968
Seems to be a different problem? I have exactly the same error codes as this thread's OP and that thread has something else I think.
-
You say its game related so try it.
-
Yesterday afternoon at around 15:00, after what appeared to have been an upgrade in avast 8, i got the dreaded BSOD x50 when rebooting. Could not even get into safe mode anymore. Took me 8 hours to get recover into safe mode.
Finally one hour ago (!) I was able to run a Whocrashed report:
On Fri 28/06/2013 04:14:19 GMT your computer crashed
crash dump file: C:\windows\Minidump\062813-5850-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x50 (0xFFFFF8000622E400, 0x8, 0xFFFFF8000622E400, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 28/06/2013 04:14:19 GMT your computer crashed
crash dump file: C:\windows\memory.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x42ABE)
Bugcheck code: 0x50 (0xFFFFF8000622E400, 0x8, 0xFFFFF8000622E400, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\windows\system32\drivers\aswsp.sys
product: avast! Antivirus
company: AVAST Software
description: avast! self protection module
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswsp.sys (avast! self protection module, AVAST Software).
Google query: AVAST Software PAGE_FAULT_IN_NONPAGED_AREA
Needless to say I have since reverted to good old avast 7 and disabled automatic program updates. Looks like I am one amongst many, many others with this problem.
Learnt a lot from this experience, don't want to go through this again EVER!
:)
-
as explain in this thread: http://forum.avast.com/index.php?topic=128242.msg299892#new
it was update for Windows 8.1 , the issue was found and fixed ... so you can return back to Avast 8
-
Well I thought it did as yesterday it booted fine.
Today it crashed again on booting up.
Are AVAST sneaking in programme updates with their daily updates even though I've chosen to download programme updates manually?
regards
EDIT; Did a dump analysis, Commodo is the culprint!
-
Same thing happened to a friend of mine. Updated to the last version of Avast Free and got a BSOD on restart. His machine is running Windows XP SP3 32-bit. The mere uninstallation of Avast through Control Panel, via Safe Mode, got the system to run smooth again. Told him to try AVG if I couldn't find another solution. The ones I've read here until now are for 64-bit systems. If anyone would care to help me, it would be much aprecciated.
Thanks for your attention.
-
Same thing happened to a friend of mine. Updated to the last version of Avast Free and got a BSOD on restart. His machine is running Windows XP SP3 32-bit. The mere uninstallation of Avast through Control Panel, via Safe Mode, got the system to run smooth again. Told him to try AVG if I couldn't find another solution. The ones I've read here until now are for 64-bit systems. If anyone would care to help me, it would be much aprecciated.
Thanks for your attention.
If you truly want help, then start your own topic and give us as much information as possible regarding your problem and your system. :)