Another Windows update cycle, another Avast crash

[danmb]

Hi,

Win 7 Pro SP1 64 bit system, Avast free.

Was running well until the April windows update cycle. Then it crashed. Installed the latest version of Avast, was fine again.

May update cycle comes in, PC crashes again. Twice. First time, first reboot after Windows Update, runs for about 10 minutes, then it just froze. Booted into safe mode. Suspected it might be Avast again, did a repair. Next reboot, runs for about 10 minutes, Blue screen, Stop 3B system service exception. Module asw.. something. So now I know for sure it's Avast again. Did not generate a crash dump even though I had the settings correct. Not even a minidump. I should have taken a picture of the bluescreen, my bad. Was not expecting this. My apologies. Sorry.

Just about ready to give up on Avast. Removed it with avastclear. I need my PC right now to get some work done. Do not want an antivirus that crashes with every windows update cycle.

Cheers.

[Be Secure]

If you disable avast during windows updates and restart pc and restart avast your problem might be solved.

Give it a go.
If possible disable avast and capture the dump and send it to avast lab and post the file ID here.https://support.avast.com/en-in/article/Submit-support-file

[kwiq]

Hi danmb,
you may find the BSOD message in system event logs. It would help us to identify avast driver,   address and the exception code.
Thank you for report !

[danmb]

No, I'm afraid I looked there too, it's not in event log. I see the Kernel Power event that you get on reboot when the PC is not shut down properly, but no BSOD event prior to that. It crashed and froze, no dump. no event. Strange. I was looking at the disk activity light when it was supposed to be writing out the memory dump, but nada, it was not flashing. So I hit the power button. Like I said, in 20/20 hindsight, I should have taken a picture of the blue screen, at least I would have had something to offer. My bad.

Anyhow, I'm running the new 19.5.2378 (build 19.5.4444.439) beta, and the system is stable now.

Why is it that Avast has coexisted with Windows 7 Updates for lo these many years, and now I have to turn off Avast in order to get some stability? Does that sound right to you?

[kwiq]

Hi,
It is not only win7 but also win10. In last update microsoft changed a way how system loads dlls into process. This small change lead into system deadlock in AV fileshields. Prev win 10 update wasnt better. So when you ask why I would say because Av has to by deeply integrated into os system to work properly and any small change in system affects also Av.

[dbdan22]

Spoke too soon. PC is still unstable with the beta. Still cannot get a complete crash dump out of the damn thing, this time it wrote out 30% of the crash dump and froze, and windbg can't make heads or tails out of it.

I will say this. Prior to these incidents the last time my PC crashed was in 2017, and it's been stable since I removed Avast. Draw your own conclusions.

Forum won't accept a picture of the blue screen. this time it was PAGE_FAULT_IN_NONPAGED_AREA STOP 0X00000050

This was the beta version. It's been removed now. Please let me know when this is fixed. I can't let my PC be a testbed, got work to do.

[kwiq]

Hi dbdan2,
if you have a dump file please upload if for analysis to avast ftp server we will take a look. Page fault in nonpage area may point to wrong memory dereference or bad pool usage both can be fixed !
Zip the memory.dmp as db2dan_5_2019.zip and upload it to avast ftp server (ftp://ftp.avast.com/incoming)
https://support.avast.com/en-eu/article/FTP-file-upload
Thank you

[danmb]

So....

My dear PC finally got around to doing something which it had heretofore refrained from doing...

It gave me a Beep code!!!!

And which beep code you ask?

(Drum roll please)

Memory error!!! But of course.

Which explains the multiple failures to write out a crash dump.

So the fact that it crashed after Windows Updates, and on an Avast module, was pure coincidence.

No, I haven't taken leave of my senses and turned into a raving lunatic just yet LOL.

My sincerest apologies.

[bob3160]

So....

My dear PC finally got around to doing something which it had heretofore refrained from doing...

It gave me a Beep code!!!!

And which beep code you ask?

(Drum roll please)

Memory error!!! But of course.

Which explains the multiple failures to write out a crash dump.

So the fact that it crashed after Windows Updates, and on an Avast module, was pure coincidence.

No, I haven't taken leave of my senses and turned into a raving lunatic just yet LOL.

My sincerest apologies.

Nothing to apologize for, something many of us have unfortunately experienced.
A new mem. stick should fix the problem.