• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Interesting memory management feature I discovered in Win8x

If the OS encounters a situation where physical memory is so low that it warns the user of it, an entry is written into the system log saying which programs used the most memory (and how much they used).

The event source is 'Resource-Exhaustion-Detector', event ID 2004.

I could be wrong in thinking that this is something that came in with Win8x, but this is the first time I've encountered it.
 
RADAR has been around a long time, I think it started with Windows server 2008, pretty sure all OSs since then have had it, so yeah, Win 7 has it as well.
 
Do you know if its event source the same regardless of OS version (since its inception)?

Yeah, think so, nothing has changed that I can tell, all event codes are the same. They may add new ones for windows 10, but, haven't yet ran into that yet.
 
How about uses ... I suppose if somebody call you/came into your shop, saying their computer was slow, this would be a quick was to see if they are having memory problems, and/or problems with a specific app historically hogging to much of it.
 
How about uses ... I suppose if somebody call you/came into your shop, saying their computer was slow, this would be a quick was to see if they are having memory problems, and/or problems with a specific app historically hogging to much of it.

The only thing of course is that it relies on a single process consuming all the available memory, which isn't really a typical 'high memory usage' scenario, at least not in my experience.

In the instance that I spotted it, a customer said that their computer had informed them of low memory, and the logs basically told a story of the Flash plugin consuming all the available memory.

It would be nice if memory usage hits say 80% then this event entry is added with all the processes with memory usage statistics, though maybe it needs to cite service names that are using lots of memory rather than just svchost.exe: While it's almost a given that if svchost.exe is using lots of RAM then WU is the problem, it's not guaranteed 🙂
 
Back
Top