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?
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.
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
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?
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 ?
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.exeDo 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
In regards to MS EMET:
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?”.
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.
Let’s see…
1]
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 basisI 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 ?
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
Did you use the removal tool for McAfee ?
Yes, I did
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
and Spybot's resident runningSpybot'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.
I used Spybot for many years and really liked the resident TeaTimer tool best of all regarding Spybot but I started running into compatibility issues (can’t recall the problems now as that was so many years ago) and eventually ended up turning TeaTimer off and finally just gave up on Spybot not long after that. You might consider turning TeaTimer off and see if you still get the monthly crash that you’ve been getting on a regular basis.
If you still get the crash with TeaTimer off you could try the Avast Support Tool to see if this helps you out.
Yah, Spybot S&D with Tea Timer is certainly outdated.
Pls see attached the 2 logs of Farbar Recovery Scan Tool
I have also disabled autostartup of Spybot S&D
Does this happen at the same time every month ?
CAUTION : This fix is only valid for this specific machine, using it on another may break your computer
Open notepad and copy/paste the text in the quotebox below into it:
CreateRestorePoint: Winlogon\Notify\SDWinLogon-x32: SDWinLogon.dll [X] HKU\S-1-5-18\...\Run: [SpybotPostWindows10UpgradeReInstall] => "C:\Program Files\Common Files\AV\Spybot - Search and Destroy\Test.exe" R2 SDScannerService; C:\Program Files (x86)\Spybot - Search & Destroy 2\SDFSSvc.exe [1738168 2014-06-24] (Safer-Networking Ltd.) R2 SDUpdateService; C:\Program Files (x86)\Spybot - Search & Destroy 2\SDUpdSvc.exe [2088408 2014-06-27] (Safer-Networking Ltd.) R2 SDWSCService; C:\Program Files (x86)\Spybot - Search & Destroy 2\SDWSCSvc.exe [171928 2014-04-25] (Safer-Networking Ltd.) Task: {33D63D7D-4D18-4CCD-8F9C-92EB8659A8CE} - System32\Tasks\Safer-Networking\Spybot - Search and Destroy\Scan the system => C:\Program Files (x86)\Spybot - Search & Destroy 2\SDScan.exe [2014-06-24] (Safer-Networking Ltd.) Task: {7AD1327B-B56B-4928-958A-3A127CE13CA6} - System32\Tasks\Safer-Networking\Spybot - Search and Destroy\Check for updates => C:\Program Files (x86)\Spybot - Search & Destroy 2\SDUpdate.exe [2014-06-27] (Safer-Networking Ltd.) Task: {D5B1E4A3-DC7F-4371-9D7B-F97877F968E7} - System32\Tasks\Safer-Networking\Spybot - Search and Destroy\Refresh immunization => C:\Program Files (x86)\Spybot - Search & Destroy 2\SDImmunize.exe [2014-06-24] (Safer-Networking Ltd.) C:\Program Files (x86)\Spybot - Search & Destroy 2 C:\Users\jbionic\AppData\Local\Temp\_MEI60402 C:\Program Files\Common Files\AV\Spybot - Search and Destroy Reg: reg delete HKLM\SOFTWARE\Policies\Microsoft\Windows\IPSec\Policy\Local /f Reg: reg add HKLM\SOFTWARE\Policies\Microsoft\Windows\IPSec\Policy\Local /f RemoveProxy: EmptyTemp: CMD: bitsadmin /reset /allusers
Save this as fixlist.txt, in the same location as FRST.exe
https://dl.dropboxusercontent.com/u/73555776/FRSTfix.JPG
Run FRST and press Fix
On completion a log will be generated please post that
Thanks, Essexboy. I think your script partially did what I had already done by disabling Spybot S&D.
See below the log from FRST64.exe.