Troubleshooting Pool Leaks Part 2 – Poolmon

re: Troubleshooting Pool Leaks Part 2 – Poolmon

Bluberr3 — Sat, 27 Apr 2013 00:38:29 GMT

Hello Andre, I am facing simillar problems. On poolmon the file says Mini Nonp, is the the same driver whos fault it is to blame? I am currently running 13.4 on my 7970.

[Hi Bluberr3. I am not Andre, but you can use the steps in our xperf article to determine what driver is allocating pool with the tag "Mini". http://blogs.msdn.com/b/ntdebugging/archive/2012/11/30/troubleshooting-pool-leaks-part-7-windows-performance-toolkit.aspx]

re: Troubleshooting Pool Leaks Part 2 – Poolmon

Andre.Ziegler — Fri, 01 Feb 2013 19:44:51 GMT

@Lars

MINI is used by the AMD GPU driver. Do you use Win8 and get the paged poll issue while playing BF3? Update to version 13.1 which includes the fix for this issue.

re: Troubleshooting Pool Leaks Part 2 – Poolmon

Lars — Wed, 26 Dec 2012 19:40:16 GMT

I have a big pool leak, but i can`t found the leakdriver... "MINI" ist the drivertag, can anyone help me?

[Hi Lars. We demonstrated various techniques to identify the driver using the tag in Part 4, 5, 6, and 7. You can see the complete list of related articles at http://blogs.msdn.com/b/ntdebugging/archive/tags/pool+leak+series/]

re: Troubleshooting Pool Leaks Part 2 – Poolmon

Andre.Ziegler — Sun, 02 Sep 2012 19:56:22 GMT

I prefer xperf for this. With stackwalking I can see more data compared to poolmon.

[Xperf is very useful for leak analysis and we will have an article to cover this in detail. Keep in mind that xperf is only useful if your leak happens quickly, as the .etl logs can grow large very quickly. Also, because xperf logs typically only cover a short period of time it is useful to know what tag is leaking before starting xperf analysis.]