This article describes how to use the Memory Pool Monitor utility, Poolmon.exe, as a troubleshooting tool to monitor memory tags. When I left, they were in the process of changing to a new tracking system.How to use Memory Pool Monitor (Poolmon.exe) to troubleshoot kernel mode memory leaks INTRODUCTION It is a bit more convoluted than that, but you get the picture.īTW, the system MS uses for the ticket tracking, sux. The fix (known as a private) will then be tested (smoked) until they are sure it is ready for release.
If it needs fixing, then it will be escalated to Redmond where the Platform group will alter the code for a fix. CPR (critical product resolution) will then review and decide whether a problem is severe enough to require fixing. If the Exchange guys note an issue with a platform file, they will open a ticket with platform (in this case, networking) CPR and present them with evidence of a problem. However, during my time there, it was rare to see such regression.Īlso, when a group, like the Exchange group, needs a change to something like AFD.SYS, they don't make the change.
Their bugcheck page (MS internal only) helps keep things straight, but when you are dealing with a massive load of updates, things get screwy and you'll see a file regression. RE: AFDB tag in Poolmon using up non paged memoryĪctually they do a pretty good job cross referencing. Version 2 drivers operate in Kernel mode, whereas Version 3 driver operate ONLY in User mode. Since Non-paged pool is in kernel mode and the spooler is allocating all non-paged pool, then I suspect it is a Version 2 driver. If anything breaks outright, just restore the keys and restart the spooler. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\MonitorsĪnd sometimes Microsof Document Imaging Writer Monitor.īackup the entire Monitors key and delete any subkeys that are not listed above, then restart the spooler.
If you do have this key, and drivers listed in the subkey, then uninstall the driver, backup and delete the key, and restart the spooler.
If you do not have this key, then you don't have any Version2 drivers. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows NT x86\Drivers\Version-2 Remove any version 2 drivers and any 3rd part port monitors for good measure, then restart the spooler service. Most of the time I've seen non-paged pool leaks in the spooler, it has been caused by version 2 print drivers.
0 kommentar(er)
