Windows Performance Trouble shooting

1.Open the Dump file using windbg.exe


2. First use !analyze –v command it will give the exception code, errors, stacks, faulty image or driver name.


3. See the Bug check code, Module name or Image name if it point to any driver’s .sys files related to windows check for any latest version or hotfix available. You can check version of drivers by collecting MPS report. You need google with driver file BSOD error code mostly it will give you hotfix KB



4.For memory Leak and Non paged file usage use !vm command to see the memory usage.

Use !vm 1 . It will give the memory details will show excessive Memory usage.


5. !poolused /t10 2 this command will top 10 users of paged and non-paged memory. So with Pooltag identify the driver and check any latest update available or known issues with driver and update it to latest version.


Tools for troubleshooting



for understanding the memory limits.

Understanding Crash dump files:

Ask performance Blog:

Debugging Blog: (Memory Leak series)

Windbg commands:







About jaihunt
Working as Technical consultant in Windows technologies

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: