Author Topic: Every month Avast causes crash?  (Read 12512 times)

0 Members and 1 Guest are viewing this topic.

Offline jbionic2010

  • Jr. Member
  • **
  • Posts: 59
Every month Avast causes crash?
« on: January 01, 2016, 01:52:36 AM »
The issue that I have is not fully investigated yet, but the preliminary conclusion is that it may be due to Avast

Below is the link to discussion on Microsoft forum
https://social.msdn.microsoft.com/Forums/en-US/1d34d165-80c4-48ba-9684-0f121a971878/system-suddenly-goes-off-how-to-find-logfiles-to-understand-why-it-happened?forum=winforms

Will there be any comments?
Windows 10 Home 64-bit
Avast 12.3.2280 or newer
Chrome 54.0.2840.71 or newer

Offline Eddy

  • Avast Evangelist
  • Maybe Bot
  • ***
  • Posts: 31309
  • Watching (over?) you
    • Malware removal, Biljart and other things.
Re: Every month Avast causes crash?
« Reply #1 on: January 01, 2016, 02:19:44 AM »
There is nothing in avast that only runs once a month unless you scheduled a automatic scan once a month.
The problem in the post on the MS forum has nothing to do with avast.

Offline Charyb

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 2328
Re: Every month Avast causes crash?
« Reply #2 on: January 01, 2016, 05:15:17 AM »
The issue that I have is not fully investigated yet, but the preliminary conclusion is that it may be due to Avast

Below is the link to discussion on Microsoft forum
https://social.msdn.microsoft.com/Forums/en-US/1d34d165-80c4-48ba-9684-0f121a971878/system-suddenly-goes-off-how-to-find-logfiles-to-understand-why-it-happened?forum=winforms

Will there be any comments?
You could try using Blue Screen View or Who Crashed to see what may have caused the crash.


http://www.nirsoft.net/utils/blue_screen_view.html


or


http://www.resplendence.com/whocrashed

Offline jbionic2010

  • Jr. Member
  • **
  • Posts: 59
Re: Every month Avast causes crash?
« Reply #3 on: January 01, 2016, 03:35:25 PM »
You could try using Blue Screen View or Who Crashed to see what may have caused the crash.


http://www.nirsoft.net/utils/blue_screen_view.html


or


http://www.resplendence.com/whocrashed

Thanks, Charyb. I have already shared the information, including minidump files, msinfo32 and evenviewer logs on MS forum (copy the link below):
https://drive.google.com/file/d/0B-j1nGDcVQKKaUlYUmQtUGVJZFk/view?usp=sharing

As you can see from those (using your BlueSreen utility, for instance) all 3 reported crash cases were somehow related to file ntoskrnl.exe.

What else should I investigate with that respect, in your view?
« Last Edit: January 01, 2016, 04:06:10 PM by jbionic2010 »
Windows 10 Home 64-bit
Avast 12.3.2280 or newer
Chrome 54.0.2840.71 or newer

Offline Eddy

  • Avast Evangelist
  • Maybe Bot
  • ***
  • Posts: 31309
  • Watching (over?) you
    • Malware removal, Biljart and other things.
Re: Every month Avast causes crash?
« Reply #4 on: January 01, 2016, 05:43:30 PM »
If Windows would be a car, you could call that application the engine (or at least a major part of the engine).

Technical information :
https://en.wikipedia.org/wiki/Ntoskrnl.exe

Do you happen to have multiple av's running ?

Offline jbionic2010

  • Jr. Member
  • **
  • Posts: 59
Re: Every month Avast causes crash?
« Reply #5 on: January 01, 2016, 08:39:35 PM »
Quote
If Windows would be a car, you could call that application the engine (or at least a major part of the engine).

Technical information :
https://en.wikipedia.org/wiki/Ntoskrnl.exe

Do you happen to have multiple av's running ?

Apart from Avast in Chrome and on computer, I have MS EMET and Spybot's resident running, which I think is normal in our days. My Chrome also has Adguard Adblocking engine activated. Nothing else, this is it.

Please check today's ZigZag3143x answer in MS forum thread
https://social.msdn.microsoft.com/Forums/en-US/1d34d165-80c4-48ba-9684-0f121a971878/system-suddenly-goes-off-how-to-find-logfiles-to-understand-why-it-happened?forum=winforms
« Last Edit: January 01, 2016, 08:58:36 PM by jbionic2010 »
Windows 10 Home 64-bit
Avast 12.3.2280 or newer
Chrome 54.0.2840.71 or newer

Offline lakrsrool

  • Advanced Poster
  • **
  • Posts: 712
  • Get the Picture !
Re: Every month Avast causes crash?
« Reply #6 on: January 01, 2016, 11:46:32 PM »
In regards to MS EMET:
Quote
The security mitigation technologies that EMET uses have an application-compatibility risk. Some applications rely on exactly the behavior that the mitigations block. It is important to thoroughly test EMET on all target computers by using test scenarios before you deploy EMET in a production environment. If you encounter a problem that affects a specific mitigation, you can individually enable and disable that specific mitigation. For more information, refer to the EMET user's guide.

FYI LINK: The Enhanced Mitigation Experience Toolkit, scroll down to "Are there any risks in using EMET?".
Processor: i3 2.53 GHz 4 GIG RAM, OS: WIN 7, Connection: High Speed, Virus/Malware Protection: Avast-2015, SpywareBlaster, Windows Firewall & Defender. Email: Outlook 2010 w/ POP Peeper Email Notifiers.

Offline jbionic2010

  • Jr. Member
  • **
  • Posts: 59
Re: Every month Avast causes crash?
« Reply #7 on: January 01, 2016, 11:56:38 PM »
Yes, I am fully aware of that. So what?

Where is the logical linkage that causes the simultaneous use of memory by Avast and EMET, and why is it happening if it is actually behind the crash?  :) By the way, is it the real cause of the problem or just a guess?
« Last Edit: January 02, 2016, 12:04:44 AM by jbionic2010 »
Windows 10 Home 64-bit
Avast 12.3.2280 or newer
Chrome 54.0.2840.71 or newer

Offline bob3160

  • Avast √úberevangelist
  • Probably Bot
  • *****
  • Posts: 45289
  • 61 Years of Happiness
    • bob3160 Protecting Yourself, Your Computer and, Your Identity
Re: Every month Avast causes crash?
« Reply #8 on: January 02, 2016, 12:54:09 AM »
Yes, I am fully aware of that. So what?

Where is the logical linkage that causes the simultaneous use of memory by Avast and EMET, and why is it happening if it is actually behind the crash?  :) By the way, is it the real cause of the problem or just a guess?
Since you have the problem, and you're using the program, you're the only one that can answer that question.
Free avast! Security Seminar: http://bit.ly/2N1eaR2  -  Important: http://www.organdonor.gov/ -- My Web Site: http://bob3160.strikingly.com/ - Win 10 Pro v20H2 64bit, 24 Gig Ram, 1TB SSD, AvastOmni 20.7.xxx, How to Successfully Install Avast http://goo.gl/VLXdeRepair & Clean Install https://goo.gl/t7aJGq

Offline Eddy

  • Avast Evangelist
  • Maybe Bot
  • ***
  • Posts: 31309
  • Watching (over?) you
    • Malware removal, Biljart and other things.
Re: Every month Avast causes crash?
« Reply #9 on: January 02, 2016, 01:06:28 AM »
Let's see...

1]
Quote
I installed Avast after McAfee trial was over, which was like in the mid of summer 2015. Month or two later I witnessed my system crashed for the 1st time. Since then it has been repeating almost like on once-per-month basis
I sure would not be surprised if McAfee wasn't removed completely and is (at least) part of the problem.

2]
As I said before, there is nothing that avast does once a month unless you scheduled a monthly scan.
That is a very strong indication that it is not avast what is causing the problem.

3]
He has solved 40.000 BSOD's for people ?
Let's say he is really good.
Helping 5 people a day would mean he is doing it for about 22 years.
And 5 is already a lot.
That is if he is helping 7 days a week which is not likely.
Illness, holidays/vacation, other things to do (real life) etc...
The first BSOD's where introduced in the first Windows NT family, 22 years ago
Simple math (statistic calculations) would say that he started helping people with BSOD's over 35 years ago.
Guess what?
Not possible because they didn't existed at that time.

3]
Take your pick.
Do you want help here or at the msdn website ?

Offline jbionic2010

  • Jr. Member
  • **
  • Posts: 59
Re: Every month Avast causes crash?
« Reply #10 on: January 02, 2016, 09:45:59 AM »
Let's see...

1]
Quote
I installed Avast after McAfee trial was over, which was like in the mid of summer 2015. Month or two later I witnessed my system crashed for the 1st time. Since then it has been repeating almost like on once-per-month basis
I sure would not be surprised if McAfee wasn't removed completely and is (at least) part of the problem.

I can assure you that my computer qualification allows me to state that McAfee was completely removed, and yes, before removing it I was aware  that the problem with McAfee left-overs had been existent :)
« Last Edit: January 10, 2016, 04:01:21 PM by jbionic2010 »
Windows 10 Home 64-bit
Avast 12.3.2280 or newer
Chrome 54.0.2840.71 or newer

Offline Eddy

  • Avast Evangelist
  • Maybe Bot
  • ***
  • Posts: 31309
  • Watching (over?) you
    • Malware removal, Biljart and other things.
Re: Every month Avast causes crash?
« Reply #11 on: January 02, 2016, 02:31:24 PM »
Did you use the removal tool for McAfee ?

Offline jbionic2010

  • Jr. Member
  • **
  • Posts: 59
Re: Every month Avast causes crash?
« Reply #12 on: January 09, 2016, 06:36:29 PM »
Did you use the removal tool for McAfee ?

Yes, I did
Windows 10 Home 64-bit
Avast 12.3.2280 or newer
Chrome 54.0.2840.71 or newer

Offline Pondus

  • Probably Bot
  • ****
  • Posts: 37014
Re: Every month Avast causes crash?
« Reply #13 on: January 09, 2016, 06:40:30 PM »
If you want a expert to check, i suggest posting diagnostic logs so essexboy can have a look inside



see instructions here  >>  https://forum.avast.com/index.php?topic=53253.0
scroll down to second picture ... Farbar Recovery Scan Tool ... run as instucted and attach the two diagnostic logs

see below the box you write in ... Attachments and other options




Offline Eddy

  • Avast Evangelist
  • Maybe Bot
  • ***
  • Posts: 31309
  • Watching (over?) you
    • Malware removal, Biljart and other things.
Re: Every month Avast causes crash?
« Reply #14 on: January 09, 2016, 07:11:09 PM »
Quote
and Spybot's resident running
Spybot's teatimer and avast do not work well together.
Besides that, Spybot isn't recommended anymore for a long time because the lack of detection.
It once was a good tool, but that was a long time ago.