大网数据广告活动
启动与系统组件

Troubleshoot issues using Process Explorer

· 52CE 我爱测

Helps troubleshoot issues using Process Explorer.

This article helps troubleshoot issues using Process Explorer.

The Process Explorer tool is part of the Sysinternals tool suite. It shows all the processes that are currently running on the computer, along with details about who invoked them and the total system resources they (including their stacks and threads) are consuming.

If you want to verify an operating system-related process (for example, System), follow these steps:

  1. Run Process Explorer as an administrator.
  2. Right-click the process, select Properties, and then select the Threads tab.
  3. Select the thread that you want to verify, and then select Stack to view the functions that are being run.

To get a better stack information result, configure symbols in Process Explorer by following these steps:

  1. Install Debugging Tools for Windows.
  2. Run Process Explorer as an administrator.
  3. Select the Options menu, and then select Configure Symbols.
  4. Change the Dbghelp.dll path to C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\dbghelp.dll.
  5. Change the Symbols path to srv*c:\symbols*https://msdl.microsoft.com/download/symbols, and then select OK.

Here's an example of whether the symbols are resolved. If the symbols aren't resolved, the Start Address of thread 9384 shows SearchUI.exe+0x120cd0, where 0x120cd0 (in hexadecimal) is the offset of the function after the plus sign.

If the symbols are resolved, you'll see the actual function name as follows. For example, SearchUI.exe!WinMainCRTStartup:

You can view more information in Process Explorer by right-clicking a column and selecting Select Columns. Then, you can select the columns that will appear in Process Explorer and select OK.

Troubleshooting example

When you use CpuStres to simulate CPU activity by running several threads, you can see that the CPUSTRES.EXE process in Process Explorer consumes the highest CPU. For example:

Double-click CPUSTRES.EXE (or right-click CPUSTRES.EXE and select Properties) and go to the Threads tab.

You can see that many threads are consuming the CPU, among which TID 15080 consumes the most. There are many more details. When you select the most consuming thread, you get the call stack information:

The call stack information isn't updated automatically. To get the latest stack information, select Refresh. However, this refresh has a minimum interval of one second. To see what's happening in the thread each second, you can use Windows Performance Recorder (WPR) or Windows Performance Analyzer (WPA).

References

Defrag Tools: #2 - Process Explorer

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
- Supported versions of Windows Server · Source date 02/12/2026
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。