Antimalware Service Executable extremely high memory usage

[Joeythedudeguy]

Sometimes, seeming randomly, my antimalware service executable shoots up to nearly 6000 mb of memory usage for seemingly no reason. I have done literally every single thing I could find online and nothing has worked. Does anyone here know any reason as to why it might be happening?

[Midnight Aurais]

https://answers.microsoft.com/en-us/windows/forum/all/antimalware-service-executable-high-disk-memory/cc35dee2-032c-4e39-a04d-9a94c7964b0d

https://www.reddit.com/r/computers/comments/130bp5q/antimalware_service_executable_high_cpu_and_ram/

[_I_]

add steam and other game library drives to its ignore list

[76561199389059995]

Well it was mentioned just last year or few years ago. Windows Defender was in top list Antivirus cost more and more resource in OS.

[Joeythedudeguy]

İlk olarak Midnight Aurais tarafından gönderildi:

https://answers.microsoft.com/en-us/windows/forum/all/antimalware-service-executable-high-disk-memory/cc35dee2-032c-4e39-a04d-9a94c7964b0d

https://www.reddit.com/r/computers/comments/130bp5q/antimalware_service_executable_high_cpu_and_ram/

I have tried all of those before and it hasn't worked.

[Alice Liddell]

Maybe, just maybe, it could be a scheduled task if this is not happening all the time constantly, look into the Task Scheduler and Real-Time Protection.

There is one task in Task Scheduler, 'Windows Defender Verification', that could hold a clue, mine actually triggered earlier.

Task Scheduler Library < Microsoft < Windows < Windows Defender.

I would run SFC and DISM as well, if applicable.

You could also check Event Viewer (EV) around the time this happens to check if something is hanging or causing an error/break, you could also issue a pop-up notification log if you can find something of interest in the EV, also take note of any failed Account Audits.

[egs]

does it matter which games you run? what happens if you reboot and try again?

[Joeythedudeguy]

Ok so I fixed it and its solely because I was an idiot. It was the issue where you add MsMpEng.exe as an exclusion, I just did that incorrectly.