Microsoft is aware of this problem and it is under investigation. It is scheduled to be corrected in the next release of Windbg. At this time no release date or correcting version number is available. Since Windbg is incorporated with the Software Development Kit (SDK), the next update may occur with the next major release of the Windows.
To work around the problem you can either download and use one of the previous versions of Windbg or wait for the next released version.
Debugging Tools: More Information and Previous VersionsDebugging Tools for Windows 32-bit Versions
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx#bDebugging Tools for Windows 64-bit Versions
http://www.microsoft.com/whdc/devtools/debugging/install64bit.mspxSteps to Reproduce:
Download Windows Debugging Tools which is available in the SDK from the following hyperlink
http://www.microsoft.com/whdc/devtools/debugging/default.mspx#Select the respective platform for your version of Windows
x86 - GRMSDK_EN_DVD.iso567.3MB
x64 - GRMSDKX_EN_DVD.iso570.9MB
Install at a minimum Windbg
Create a folder on the root of drive C:\ named “websymbols” which will be used for a local symbol store
Open Windbg and set the “Symbol file path...” from the File drop down menu to the local and external symbol server as follows;
SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Open a memory dump file in Windbg and run the command !vm, you may see something similar to the following;
NonPagedPool Usage: 996199185 (3984796740 Kb) <- Excessive NPP usage 3.9 TB