How to identify a driver that calls a Windows API leading to a pool leak on behalf of NT Kernel?


Hello my name is Gurpreet Singh Jutla and I would like to share information on how we can trace the caller which ends up allocating “Se  “ Pool tag. When we use the Windows debugger and investigate the pool allocation and the binary associated with...(read more)

Comments (0)

Skip to main content