From the names you should have a clue what happens. net related groupings like GC or JIT:Įxpand the stack of the w3wp process to see what it is doing. In this sample most CPU usage from Internet Explorer comes from HTML stuff.įor. Now select your process in the graph, zoom in and expand the stack, here you see the weight of the CPU usage of all calls Open the generated ETL with WPA.exe (Perf analyzer), drag and drop the CPU Usage (Sampled) graph to the analysys paneĪnd load the Debug Symbols. This would be in 'Control Panel>System>Advanced System Settings>Startup & Recovery Box>Settings button'. Capture 1-2 minutes of the high CPU usage and next click on Save. The location (and type) of these dump files can be verified in the Advanced System Settings. If you are installing Windows 10 on a PC running Windows XP or Windows Vista, or if you need to create installation media to install Windows 10 on a different PC, see Using the tool to create installation media (USB flash drive, DVD, or ISO file) to install Windows 10 on a different PC section below. Install the Windows Performance Toolkit which is part of the Windows 10 SDK ( V1607 works on Win8/8.1(Server2012/R2) and Win10 or the V1511 SDK if you use Windows 7/Server2008R2)), run WPRUi.exe and select CPU UsageĪnd press on Start. Use ETW and here the CPU Sampling, which sums all calls and shows you in detail the CPU usage. You can also use the free Windows 10 Drivers Kit to open dump files from a past crash.
Dumps are only snapshots so you have no idea what happened before. If you're anticipating another crash or you want to test a program, you can use a free program called BlueScreenView to analyze your dump files. Windbg is not the right tool for this job.