B
bruhimsodone
System Guard Runtime Monitor Is using absolutely insane amounts of ram.
I have 16 Gigabytes of RAM along with 25 Gigabytes of vRAM, this single program manages to sometime use 20% of that. I can't click end task on it, it says "access denied", if I restart it stays at a few MB for about 5 minutes then shoots back up to hundreds of MB or even a few thousand. I can't even change its priority in the details menu of the task manager because I again get an "access denied" message.
I have seen this problem in many other forum posts, all of which have incorrect answers that "fix" the wrong problem or don't work at all. Often people have been saying to close the Runtime Broker even though this is a different program and I have not had any problems with it. They also say to close it, which again, doesn't work, as you can close Runtime Broker but not System Guard Runtime Monitor. Even an answer saying to close the task and restart the person's computer when in their question they stated that they couldn't close the task and restarting didn't fix it.
Microsoft, I (and probably many others) would like an actual method of fixing this from an actual person for this problem.
Continue reading...
I have 16 Gigabytes of RAM along with 25 Gigabytes of vRAM, this single program manages to sometime use 20% of that. I can't click end task on it, it says "access denied", if I restart it stays at a few MB for about 5 minutes then shoots back up to hundreds of MB or even a few thousand. I can't even change its priority in the details menu of the task manager because I again get an "access denied" message.
I have seen this problem in many other forum posts, all of which have incorrect answers that "fix" the wrong problem or don't work at all. Often people have been saying to close the Runtime Broker even though this is a different program and I have not had any problems with it. They also say to close it, which again, doesn't work, as you can close Runtime Broker but not System Guard Runtime Monitor. Even an answer saying to close the task and restart the person's computer when in their question they stated that they couldn't close the task and restarting didn't fix it.
Microsoft, I (and probably many others) would like an actual method of fixing this from an actual person for this problem.
Continue reading...