Hi, yesterday I had an issue while trying to restart my device after reconnecting to the internet and the Task Host Window wouldn’t close on its own so I had to click restart anyway.
After I did that and checked reliability history this appeared as an error and I don’t know what it means exactly:
Source
Host Process for Windows Services
Summary
Stopped working
Date
07/06/2023 12:23
Status
Report sent
Description
Faulting Application Path: C:\Windows\System32\svchost.exe
Problem signature
Problem Event Name: APPCRASH
Application Name: svchost.exe
Application Version: 10.0.19041.1806
Application Timestamp: 7dcad237
Fault Module Name: aphostservice.dll
Fault Module Version: 10.0.19041.746
Fault Module Timestamp: 096db171
Exception Code: c0000005
Exception Offset: 000000000001ca9f
OS Version: 10.0.19045.2.0.0.768.101
Locale ID: 2057
Additional Information 1: 42fa
Additional Information 2: 42fa9d1a24f132973bd90f54f5b8443f
Additional Information 3: 7713
Additional Information 4: 7713ebc2c60e1297143efb7609a00fcc
Extra information about the problem
Bucket ID: 3311113afd26e7b43cecafd6e043efb8 (2084234064986107832)
I’ve basically been trying to figure out what’s causing my memory usage not to go down after running full scans with Malwarebytes Premium, and Microsoft Safety Scanner. I encountered this while trying to figure it out.
To elaborate on the memory usage thing. Basically, after I finish running a full scan with Microsoft safety scanner, or Malwarebytes, my memory usage won’t return to the normal amount when the system is idle. Reference, my idle memory usage is around 17% to 20%, but when a full scan is run with these programs, my memory usage will go as high as 40% during the scan which is normal, but after it’s finished, it won’t fall below ~30% and I have no idea if this is normal or not.
Came back to add that windows defender does the same thing for a full scan, it doesn’t fall below 26% memory usage. As far as I can tell its only anti-virus software that does it, though I haven’t done much else so it’s hard to say. Scans complete normally and run fine.
I want to say this has been occurring since April, and may either be related to ASUS armoury crate, or the latest BIOS update for my motherboard, as I updated it around then as it involved security improvements.
