BSOD issues with computer

[PEKFL72]

I too have been having problems with recurring BSOD events, in increasing frequency the last two months- so it sounds like a very similar situation to mine!

 

At first, (2 months ago) I had restored my entire system, by doing a reinstall of Win 10 over my system output files and re-installing a new windows over it, as I was led to believe it was corrupted Windows system files from the cryptic event log. (unable to decrypt / view the logger files such as DefenderApiLog, (event log said the file was full, and I haven't figured out how to load and view it yet, etc.)  I was in the process doing that yesterday, when it took a left turn as follows:

I had tried to trace many, many error events,   and ran many CMD commands, it seemed to help, but the BSOD's kept coming back. I did find that somehow my boot SSD drive's automatic Trim command was turned off  and had gone 28 days without a trim on the C: drive (SSD drive). 

That helped, and I set it to automatic trim every 7 days.  THen the BSOD returned on day 6, Trimmed C again, then it BSOD'd again on day 4,  Trim, BSOD on day 2, Trim, BSOD, next day.

I too, had been wondering about upgrading from windows 20H2 version to 21H1, but decided against it.  My Nephew-in-law (an IT serurity specialist) said "You gotta start all over again, wipe the drive, save all your files, move them, etc., etc."  (I figured I had to dig a little deeper, having already rebuilt Windows once before about 2 months ago, and worried that an infected data file might be the culprit)

I started seeing messages where certain MBAM and AVAST files were involved, so I started by contacting AVAST and Malwarebytes. I ran the malware bytes tool, and uploaded my files, and am awaiting a response. In the process, MBAM tools, I never got to the part where I could analyze the logs I uploaded, but MBAM got deleted and re-installed.

Next, I got a response from Avast, and started a virtual session.  they immediately told me that the two programs would not be compatible together, so they asked to delete Malwarebytes, so I granted permission.  Next they ran their own scan and a cleanup tool (via scan at boot up, followed by their own file to scan -everything came up clean- they said no virus.  I did not feel secure, given that the scan came up empty.    I decided to run a Microsoft security scan, and I found that it cleaned out a VirTool: DefenderTampering Restore virus on my C: drive (SSD)

So, apparently, removing both the corrupted versions of avast and MBAM, and restoring them new, allowed MS Safety scanner (64bit for me)  to find and remove this file, so that brings me to the point of where I am now:  I see that malwarebytes on the web states it can detect virTool real time (and it did not happen), and MS Safety scanner can also find it, but apparently, with the "crippled" versions of both AV systems, the MS Safety scanner tool was unable to find this problem, so now I'm starting to believe that these two programs can interfere with each other, so  I'm feeling that I may be better off with just Malwarebytes and Windows Defender, jettisoning avast...?  I'm still awaiting malware bytes to get back to me on the program logs.   This is disturbing, as our corporate had recommended installing MBAM over the base AV tool and I've been doing so for over 5 years, so I don't know if it is because Avast has grown and made it more difficult to co-exist with other malware tools.  (They did tell me that MBAM interfered with their program, as a first-time message)!  Now I'm considering dumping it next month when it expires, and may just go back to MBAM on top of Windows Defender AV (if they can co-exist together) I know they've been working on my wife's laptop, but I should check the settings to be sure that Defender is turned on and it is not only MBAM operating on hers.

MS safety scanner link: 
                   https://docs.microsoft.com/en-us/windows/security/threat-protection/intelligence/safety-scanner-download
  (you have to use the correct version for your CPU (32 or 64 bit)  (however, with the corrupted AV files, in both programs, I  came up empty, but after removing them and restarting the safety scanner, I hit the jackpot and found the culprit: VirTool: DefenderTampering Restore virus !!!  The only problem, is that I don't know which file it was, or where it came from.

(after all this, i was finally comfortable with updating windows 20H2 to 21H1, and that completed an hour ago.)

My goal now is to figure out how to use the MBAM tools to analyze the log files. (many of the event ID's I chased down indicated that they were routine and nothing to worry about, but  early on, I saw kernel power issues, and had started thinking it was the power supply or motherboard, memory or other components starting to go also!)  This problem had me going in so many different directions:  memory tests,  sfc scannow,  etc., etc., etc.

[Porthos]

1 hour ago, PEKFL72 said:

I'm feeling that I may be better off with just Malwarebytes and Windows Defender, jettisoning avast...?  I'm still awaiting malware bytes to get back to me on the program logs.   This is disturbing, as our corporate had recommended installing MBAM over the base AV tool and I've been doing so for over 5 years, so I don't know if it is because Avast has grown and made it more difficult to co-exist with other malware tools.  (They did tell me that MBAM interfered with their program, as a first-time message)!  Now I'm considering dumping it next month when it expires, and may just go back to MBAM on top of Windows Defender AV (if they can co-exist together) I know they've been working on my wife's laptop, but I should check the settings to be sure that Defender is turned on and it is not only MBAM operating on hers.

Malwarebytes and Avast do have issues working together as noted in this support article

After removing Avast,turn off the following setting in MB so Defender and MB are both enabled.

 

Edited July 4, 2021 by Porthos

[PEKFL72]

@Porthos
Thanks!  In the interim, is there any way for Avast and MBAM to co-exist, say turning off real time web monitoring for MBAM as the article outlines, and then in 2 months, switching over to Defender when Avast expires as your initial post implies? 
I'm trying to sort out how to configure MBAM and Defender   vs MBAM with Avast.  Seems a bit confusing at present!

Thanks in Advance!

 

[Porthos]

4 minutes ago, PEKFL72 said:

is there any way for Avast and MBAM to co-exist, say turning off real time web monitoring for MBAM as the article outlines

That should fix the blue screens.

4 minutes ago, PEKFL72 said:

I'm trying to sort out how to configure MBAM and Defender   vs MBAM with Avast.  Seems a bit confusing at present!

When Avast is removed Malwarebytes will probably take over as primary which will keep Defender disabled so doing what I mentioned earlier will turn Defender on and will work alongside Malwarebytes.

In my experience since windows 10 was released, many Win 10 installs have been broken during updates causing a reinstall of Windows because of Avast.

Also their current privacy practices are not great either.

[PEKFL72]

Seems like a plan.  Will have to check my wife's laptop, as she has both, and I wonder if Malwarebytes is overriding Defender or not!   Thanks so much for the help!  I was at wits end for a while, trying to figure out whether i needed memory chips, a power supply or a mother board until the avast and mbam event errors started showing up.  Avast seems to keep growing and they want to sell more and more, so it's good to be done with them now!   Thanks again!!

[PEKFL72]

Malwarebytes now configured similarly to wife’s laptop (as she leaves all the installs, updates & General tech stuff to me) and that malwarebytes install was able to self-configure for Defender use! 
 

Thanks again hoping the other person originating this thread is able to achieve similar results!!