Roy, I had the same problem when I turned on the PC today. I think McAfee AntiVirus Plus or MalwareBytes have must have recently updated, and something changed the compatibility between programs. It was working fine until I turned off the PC last night. I had a similar problem about a month ago when MalwareBytes and another anti-virus program conflicted. I'm paying for MalwareBytes now so I didn't want to remove it but I quit out of it today to have my PC run adequately. I'm paying for McAfee also but until today, they ran together without problems. At least I know now that I'm not alone.
Of course the softwares always tell you not to run more than one at the same time, but I figured if there's no problem, I'll let them continue. For now at least, it looks like an incompatibility of some sort.
If anyone finds out additional information pleas update the thread.
Thanks!
UPDATE...
I just checked the Malwarebytes support page https://support.malwarebytes.com/docs/DOC-2342 and saw this...
Earlier this morning, January 27th, 2018, we published a protection update that caused connection issues for many of our customers. As a side effect of the web protection blocks, the product also spiked memory usage and possibly caused a crash. We have triaged this issue and pushed a protection update that resolves it. Please follow the steps below on how to update to the latest database.
If you are having this issue while running our Malwarebytes for home product, please follow these steps:
Open Malwarebytes for home product.
Turn OFF web protection by Clicking on Settings, click to turn web protection OFF.
Under Scan Status (right side), click next to Updates to have Malwarebytes download the latest database
Restart your computer.
Note: It may take up to 2 restarts after the update to stabilize the system.
To confirm that you are on the latest database please follow the steps below:
Open Malwarebytes for home product.
Click on Settings.
Click on the About tab.
Next to Update package version, if you see version 1.0.3803 or higher, you are on the latest database which addresses this issue.