Article ID: 250453 - Last Review: February 28, 2007 - Revision: 2.2 Determining Special Pool Tagging Options When DebuggingThis article was previously published under Q250453 IMPORTANT: This article contains information about modifying the registry. Before you
modify the registry, make sure to back it up and make sure that you understand how to restore
the registry if a problem occurs. For information about how to back up, restore, and edit the
registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986
(http://support.microsoft.com/kb/256986/EN-US/
)
Description of the Microsoft Windows Registry
SUMMARYNOTE: This article assumes that you are familiar with the information in the following Microsoft Knowledge Base article regarding the Windows NT Special Pool feature:
188831
(http://support.microsoft.com/kb/188831/EN-US/
)
How to Use the Special Pool Feature to Isolate Pool Damage
When you are using the Special Pool tagging features of Windows NT 4.0 Service Pack 4 and later, you can verify the configuration of the registry options by using a Memory.dmp file or a live debug.You can check the various Special Pool options by using several of the global variables available. The ability to verify the settings can be useful when you are working with computers that require that Special Pool be used. MORE INFORMATIONWARNING: If you use Registry Editor incorrectly, you may cause serious problems that may
require you to reinstall your operating system. Microsoft cannot guarantee that you can solve
problems that result from using Registry Editor incorrectly. Use Registry Editor at your own
risk. The Windows NT global variable for the PoolTag registry value is MmSpecialPoolTag:
dd nt!MmSpecialPoolTag
The Windows NT global variable for the PoolTagOverruns registry value is MmSpecialPoolCatchOverruns:
0x00000000 = No tag specified; Pool Tagging is basically disabled. (Default value) 0x0000002a = Most typically used; used to look at all tags. This is the ASCII representation of the asterisk wildcard.
dd nt!MmSpecialPoolCatchOverruns
The Windows NT global variable for the EnableKStackPool registry value
is MmEnableKStackPool.
0x00000000 = Underruns 0x00000001 = Overruns (Default value) This option is available only with Windows NT 4.0, Terminal Server Edition. For additional information about this option, click the article number below to view the article in the Microsoft Knowledge Base: 188831
(http://support.microsoft.com/kb/188831/EN-US/
)
How to Enable the Special Pool Feature to Isolate Pool Damage
dd nt!MmEnableKStackPool
The Windows NT global variable MiSpecialPoolEnabled is hard coded to be enabled.
0x00000000 = KStack pool disabled. 0x00000001 = KStack pool always enabled. 0x00000002 = KStack pool enabled for >= 256 MB computers.
LOGICAL MiSpecialPoolEnabled = TRUE;
dd nt!MiSpecialPoolEnabled 0x00000000 = Disabled 0x00000001 = Enabled (Default value) REFERENCESFor additional information, click the article number below
to view the article in the Microsoft Knowledge Base:
148658
(http://support.microsoft.com/kb/148658/EN-US/
)
How to Load Windows NT Memory.dmp File Using I386kd.exe
APPLIES TO
| Article Translations
|
| United States | Change | | | All Microsoft Sites |
Back to the top
|
