TanyaS

I have been having issues since beginning of January to the point where I could not even start up windows in normal mode before it gave me a BSOD. I finally owned in safe mode with network and investigated the processes. Ultimately I stopped the TrustedInstaller.exe and the windows update service wuauser which were using high amounts of cpu. This is apparently a known problem with those services running constantly. By stopping those services I was at least able to move past the BSOD and see that I was also having issues with Malwarebytes during scan. I would still see occasional BSOD and/or laptop freezing while running Malwarebyted. Since then I have updated the settings as described in my first note. When monitoring I can see it go up as high as 99%. What is happening now is it will just get so far and freeze and the laptop become unresponsive. I have run all of the windows diagnostics with no errors reported. At this point I don't know if the BSOD was caused by multiple processes exceeding the cpu or what. Since I stopped those processes and changed Malawarebytes settings I have not had more BSOD. I did uninstall and reinstall last week so I thought I had the latest version of Malwarebytes. Will do the reinstall and let you know what happens.

FarBar files attached. One additional item that may be helpful. I appear to have more issue when the scan runs on reboot of the system then in is periodic run. Thank you Tanya FRST.txt Addition.txt

I am having issue with extremely high CPU usage during scan, to the point where my laptop locks up forcing a hard reboot. I have turned off self protection mode and also lowered the impact of scans on the system to the lower priority setting. SOMETIMES I can get through a scan before it locks up but most of the time it will freeze the desktop when it is the only running besides task manager. Its hit or miss if it will peg out the CPU or complete. I have downloaded the malwarebyte support tool and run the gather logs. Those logs are attached. Please let me know what else you might need to trouble shoot. mbst-grab-results.zip