Unusual behavior in Windows 10's Task Manager regarding memory usage or bugs.
Unusual behavior in Windows 10's Task Manager regarding memory usage or bugs.
So I've encountered an issue with Task Manager (Modern Variant, The one in Windows 8 and later) where it uses lots of RAM after being open for a long period of time, I know i can simply close task manager and restart it, however i prefer for that RAM to be used effectively, the system this is occurring on uses the majority of it's RAM at all times (It's supposed to), so i want to conserve RAM when possible and i like leaving Task Manager open (Both Variants) to monitor things on the system, I also have the older style Task Manager running alongside it, which isn't affected by this issue (Both Variants of Task Manger have been running for the same period of time), is this a well documented issue with the modern variant of Task Manager or Windows 10 specific or just an isolated incident, I've searched around but haven't found a solution. Here's a visualization of the issue prior to closing the "Modern" Task Manager: And a moment after the "Modern" style is closed as viewed through the legacy Task Manager If there isn't a fix I'll just stick to running Process Explorer and the legacy Task Manger and open the "Modern" Task Manager when needed then close it, but i prefer to fix this if possible. EDIT: Messed up the image.
It appears this process keeps happening repeatedly. The background script is initiating searches, timeouts, and pings—excluding registry-related actions. It’s not clear why Task Manager reacts this way after closing batch files; the older version of Task Manager also behaves similarly, suggesting the problem might be elsewhere.
It's strange seeing Task Manager start processes directly instead of using cmd.exe, but checking poolmon shows no driver conflicts. I update drivers regularly and usually check them monthly. This problem has been happening for six months now, and I'm starting to get frustrated because it means RAM is being wasted.
I noticed no issues visible so far. It’s worth noting a prolonged wait time might be linked to the non-paged pool (last two weeks). This applies to the server PC (not my primary system) which operates continuously except during driver updates or when an application needs a restart.
Looks like to me you got a lot more going on that a task manager issue.
The CPU activity can be understood as this machine joining Folding@home, while the other applications I no longer see are trustworthy and genuine programs that I'm confident aren't malicious. I performed a MBAM scan—quick checks on process lists and common malware registry entries—to confirm 100% certainty, though nothing was found. EDIT: Before the PC began folding, I experienced a Task Manager issue.