Two Computers, One Virus - Malwarebytes doesn't detect anything

[UninvitedChaos]

Hello!

My boyfriend's computer started acting up weirdly today. It said it was running out of disc space and suffered from low memory. He ran CCleaner, deleted some files and restarted. Suddenly 20GB space! We thought that was it..

Until my computer also went all "NO SPACE ON C, LOW MEMORY". I thought it could be a coincidence until it notified me about the low memory. I have 16GB RAM, after all. My boyfriend has 8GB.

Just a moment later, Malwarebytes notified me that real time protection was off. I had not turned it off. So I tried to turn it back on. It didn't want to. So I immediately shut off sharing, made sure my firewall was on and restarted in safe mode with networking. Checked disc space and now I suddenly had 29GB free. So I started a scan with Malwarebytes. Also enabled start self-protection module early. Didn't find anything, scanned at least 3 times. Downloaded AdwCleaner It detected one thing and removed it. Booted computer normally, but now malwarebytes were acting up. I got the error "can't connect to service" or something, and when I tried to manipulate the processes to shut it down and restart, it told me I didn't have access. Once again I booted into safe mode with networking, tried to start malwarebytes. Same problem. So I downloaded Malwarebyte camoflagued  and installed it again, removing the other one. I finally managed to start it. Scanned one last time, but nothing. Downloaded Malwarebytes rootkit scan. Nothing found.

At the same time, my bf notified me that the problem with the space and memory had arisen again, and that real time protection was turned off for him. Did the same procedure with his computer, and nothing detected either.

TLDR;

- Low disc space out of nowhere, low memory despite having 16GB and 8GB RAM.

- Malwarebytes real time protection off

- Turned off network sharing and made sure firewall was on

- Restarted in safe mode with networking

- Suddenly more disc space

- Ran Malewarebytes threat scan. Nothing detected.

- Adwcleaner found one thing and removed it.

- Booted normally, now malwarebytes gave me the middle finger "can't connect to service"

- Safe mode again, reinstalled malwarebytes under camoflague

- Downloaded anti-rootkit, ran it, nothing detected.

Also, my bf's hdd space didn't improve until I booted in safe mode WITHOUT network. Maybe because I ticked off the start early self-protection module on my own computer and not his?

Now I'm running out of options, so I'm hoping someone can help us out. Or else I have to reinstall Windows on both without figuring out what might have unleashed this hell upon us...

Attached are my computer's logs from Malwarebytes threat scan, AdwCl, unhide.exe and FRST

I will comment below with my bf's logs attached.

threatscanChaos.txt

unhide.txt

AdwCleaner[C1].txt

AdwCleaner[S1].txt

Addition.txt

FRST.txt

[UninvitedChaos]

Here are the same logs from my bf's computer.

 

unhide.txt

Addition.txt

FRST.txt

AdwCleaner[S0].txt

threatscanbf.txt

unhide.txt

[UninvitedChaos]

So, I've come to the conclusion that the memory leak issue is related to the update that was released, which explains why it hit the two computers at almost the same time. It does not explain the HDD space issue unless the update somehow utilized the space for RAM while there was the memory leak, as well as the issue of real time protection options turning off, but since this too seems to have normalized I'm crossing my fingers that it's all related to the update. (I have several GB less than what I have in safe mode, but I suppose this is normal?)

[lock]

16 hours ago, UninvitedChaos said:

I have 16GB RAM, after all. My boyfriend has 8GB.

I do not think this relationship is going to work...

[Breach]

51 minutes ago, UninvitedChaos said:

So, I've come to the conclusion that the memory leak issue is related to the update that was released, which explains why it hit the two computers at almost the same time. It does not explain the HDD space issue unless the update somehow utilized the space for RAM while there was the memory leak, as well as the issue of real time protection options turning off, but since this too seems to have normalized I'm crossing my fingers that it's all related to the update. (I have several GB less than what I have in safe mode, but I suppose this is normal?)

That's textbook. The low disk space was because when Windows runs out of memory is starts increasing the virtual memory (swap or paging file). When you rebooted in safe mode Windows automatically downsized the swap file. Provided you follow the recovery instructions (update definitions, restart), you should be good.

[UninvitedChaos]

53 minutes ago, lock said:

I do not think this relationship is going to work...

He cares much less about his specs and hardware, so I think this relationship will work JUST fine. (I bought new RAM for myself when I built his computer and used my old RAM for his build, no complaints!....)

[UninvitedChaos]

54 minutes ago, Breach said:

That's textbook. The low disk space was because when Windows runs out of memory is starts increasing the virtual memory (swap or paging file). When you rebooted in safe mode Windows automatically downsized the swap file. Provided you follow the recovery instructions (update definitions, restart), you should be good.

Great, thanks for checking it out!

[BuonJovi]

Hi UninvitedChaos. I have same problem. My wife filled out employment application  and saw a  flag on screen warning of virus and now we're getting Out of Memory messages and the computer locks up after booting up. . I tried booting into Safe Mode using F8 and it won't boot into SafeM.. Any tips on how you rid yourself of this hassle. Fyi. We barely use this PC except for Google news, aol email,etc. Barely used otherwise. -- No gaming or heavy use.  The MalWareBytes found  nothing and also said real time protection is off similar to your pc.  Any tips would be helpful. Thanks.

[BuonJovi]

No idea what I did, but for the record:  I logged in Safe Mode, removed a few unfamiliar programs, ran chkdsk /f, upped the virtual mem to 5,000 mb from 1,280mb as recommended, and things appear to be fine.  Also ran Spybot and MalWareBytes which found no problems.  Go figure.