Discusses ongoing issues with Windows leaks. Continues the conversation about Windows vulnerabilities.
Discusses ongoing issues with Windows leaks. Continues the conversation about Windows vulnerabilities.
request wasn't exactly what I needed—clarification will come once an app asks for a lot of memory. Win 11 should be able to quickly allocate just a few gigabytes, meaning even large tasks like running 7zip with big settings should be able to secure enough RAM without locking it at full capacity.
It would fully utilize available memory but stop before reaching 38GB. The test dictionary size limits it to 512MB, making the 768MB option unavailable. This is my first experience, so I’m adjusting settings as I go. The background usage drops around 90% during the test, staying between 99% and 100%.
It seems unusual with only about 5GB active and a reported usage of 44%. Windows typically uses just a few gigabytes, so you might be seeing higher numbers. Check the performance tab for details on memory usage in the non-paged pool. The tool rammap can provide more specific information about RAM allocation.
taskmanager is commonly known for its inaccuracies. Use hwinfo64 to obtain more precise statistics.
This indicates a significant memory leak issue. After restarting, does the system usage of RAM remain stable? Which antivirus software are you using? Network drivers often contribute to memory leaks, so you can verify by downloading a large file and observing the non-paged memory usage. Overall, I’d start with rammap to gather precise information about the problem.
Do automatic updates have settings active? The process consumes significant memory and greatly increases the non-paged pool usage.