from Tech Net
The Resource Exhaustion Detector component of Windows Resource Exhaustion Detection and Resolution (RADAR) identifies the top three consumers of commited memory and warns you when the system commit charge reaches a critical level.
from TechNet Lib
The Memory Leak Diagnoser will not run on:
| Event ID | Source Message |
| 1001 | started. |
| 1002 | stopped. |
| 1003 | received a notification that the computer is low on virtual memory. |
| 1005 | failed to start due to an error. |
| 1006 | failed to stop due to an error. |
| 1007 | experienced a memory allocation failure. |
| 1008 | Windows failed to diagnose a low virtual memory condition. |
| 1009 | Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: %1 (%2) consumed %4 bytes, %5 (%6) consumed %8 bytes, and %9 (%10) consumed %12 bytes. |
> sc queryex dps
SERVICE_NAME: dps
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
PID : 1420
FLAGS :
> tasklist /m radardt.dll
Image Name PID Modules
========================= ======== =============
svchost.exe 1420 radardt.dll
The file Radardt.dll is not loaded until approximately ten minutes after the Diagnostic Policy service starts. It may not appear to be enabled if you check the system status immediately after a restart.