28
2017
Capture High CPU consuming process using Process Explorer
As a DBA we encounter situations when CPU is high on a DB server but DB is not consuming any CPU, we can see the processes consuming high CPU but don’t know how to identify that what process is doing causing issue and in cases where process is an encapsulated process like wscript.exe or any other system process we generally recommend server reboot but that generally washes out all logging; now as a DBA we know we can’t control such situations, so it’s always better to dump such process for future investigations and help identifying root cause, below is one such method to use process explorer utility to dump the problematic process and either open a MS case and provide it to them for analysis or download windbg utility and respective symbols to analyze on own, whatever be the case, this is an important thing to be handy always,
- Download process explorer from https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer
- Copy procexp.exe to the impacted server
- Execute procexp.exe
- Go to Find > “Handle or DLL substring”
- Search for the process, match the PID of task explorer process with the searched process in process explorer
- Once process is identified, then select process in top pane and do following:
right click > create dump > create full dump… > select location which has more than 2GB free space and give a proper file name
- Once export is complete, compress file
-
Open a Microsoft case and supply the dump file to them for further analysis
Or
-Go to https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/
-Download appropriate version of windbg and respective symbol files
-Open the dump
-Analyze
Hope this helps!

Leave a comment
Subscribe to this blog via Email
Old Posts
- November 2017 (3)
- October 2017 (4)
- September 2017 (2)
- May 2017 (1)
- April 2017 (1)
- July 2016 (3)
- May 2016 (1)
- April 2016 (1)
- February 2016 (2)
- January 2016 (1)
- October 2015 (1)
- September 2015 (1)
- August 2015 (1)
- July 2015 (2)
- June 2015 (3)
- April 2015 (1)
- March 2015 (1)
- December 2014 (1)
- September 2014 (2)
- April 2014 (1)
- January 2014 (3)
- October 2013 (2)
- September 2013 (2)
- August 2013 (4)
- July 2013 (1)
- June 2013 (2)
- May 2013 (5)
- April 2013 (3)
- March 2013 (1)
- February 2013 (9)
- January 2013 (11)
- December 2012 (14)
- November 2012 (3)
- October 2012 (4)
- July 2012 (2)
- June 2012 (3)
- May 2012 (2)
- April 2012 (8)
- March 2012 (6)
- February 2012 (3)
- January 2012 (1)
- December 2011 (5)
- November 2011 (8)
- October 2011 (5)
- September 2011 (3)
- August 2011 (3)
- July 2011 (3)
- May 2011 (1)
- November 2010 (1)
Tags
Calender
M | T | W | T | F | S | S |
---|---|---|---|---|---|---|
« Nov | ||||||
1 | 2 | 3 | 4 | 5 | 6 | 7 |
8 | 9 | 10 | 11 | 12 | 13 | 14 |
15 | 16 | 17 | 18 | 19 | 20 | 21 |
22 | 23 | 24 | 25 | 26 | 27 | 28 |
29 | 30 | 31 |
View Post by Categories
Recent Articles
- Setting up Always ON Availability Group in Multi Subnet Cluster – Recommendations
- Configuring Replication with Always ON Availability Group
- Login failed for user ‘DOMAIN\COMPUTER$’. Reason: Could not find a login matching the name provided. [CLIENT: ]
- Modern Servicing Model (Service Pack and Cumulative Updates) for SQL Server 2017 and onwards
- Fix: SSMS 2012 opening Debug window when pressing F5