Memory leak Detection and driver verifier

Driver verifier is telling me that I have memory leak. But the minidump log that it creates, does not tell me the memory block’s tag name.
It seems “!verifier 3” command does not work on a log.
How can I find out the memory tag that leaks?
Do I have to have debugger attached to the target system to use the “!verifier 3” command?

Thanks for your help.


You have to enable pool taging in registry or by Gflags. The simplest way is download PoolTag gui application from OSR. It enables pool taging during first startup.

Thanks Bronislav.