Debugging Tools for Windows |
Use the following techniques to determine the cause of a kernel-mode memory leak:
If you do not know which kernel-mode driver or component is responsible for the leak, you should use the PoolMon technique first. This technique reveals the pool tag associated with the memory leak; the driver or component that uses this pool tag is responsible for the leak.
If you have already identified the responsible driver or component, use the second and third techniques in the preceding list to determine the cause of the leak more specifically.